Building a new system or deciding how to evolve an existing one? I help connect business needs with a technical design that both management and developers can understand.

When to get in touch

You are planning a new product and need to define system boundaries, data models, and integrations.
Your existing solution is difficult to evolve and you need to identify technical obstacles.
You are considering a change of technology or supplier and want to compare options.
Your team needs a shared design to guide implementation.

How I can help

We start with the system’s purpose, users, and constraints. We review available documentation, important data flows, connections to other applications, and operations. I assess the design against maintainability, security, cost, and the team’s capabilities.

For an existing system, an architecture review can be the first step. Improvements do not always require a rewrite: clearer responsibilities, a revised integration interface, or removing a specific bottleneck may be enough.

What you can receive

We agree on the scope for your project. Deliverables can include:

a description of the current architecture and its risks;
a comparison of options and reasons for the recommended approach;
a design for components, interfaces, and data flows;
records of important technical decisions;
a phased development plan and priorities for the team.

How we work together

Initial conversation: clarify the problem, expectations, and available information.
Analysis: review the system with the people who develop and operate it.
Design: compare options and, where useful, validate uncertain parts with a focused prototype.
Handover: discuss the recommendations with the team and agree on next steps.

What to prepare

A short product description, current problems, a technology overview, and any existing documentation are helpful. If there is no documentation, we can begin by mapping the system together. Share sensitive material after agreeing on the scope and working arrangements.

Common questions

Do we need a complete technical brief?

No. Clarifying the brief can be part of the engagement. We do need to understand the problem and who will use the design.

Can you support implementation too?

We can agree on follow-up technical support, reviews, or technology leadership. We define specific responsibilities and scope in advance.

Software architecture