When does a conversation make sense?
The architecture holds – but for how long?
The system runs, but new requirements take disproportionate effort. You suspect the structure is the real problem, but no one has named it clearly yet.
The team ships, but value doesn't land.
Sprints close, features get built – but the business impact stays flat. There's a gap between delivery and outcome that nobody is closing.
AI tools in the team, but no clear workflow.
Agentic coding is happening. Everyone does it differently. Quality varies, ownership is unclear. The potential is there – the structure isn't.
Something's off – but you can't name it.
You're not deep in the technical details, but you sense it: software development isn't running the way it should. Before you act, you want to understand what's actually going on.
Not every situation calls for an external software architect.
Sometimes the answer is: this isn't a fit. Or: you don't need this at all. I'll say that directly in the first call – no detours, no offer you have to decline.
What to expect
How it works
- You write me a short note about the situation – two or three sentences are enough.
- I get back to you within two business days and suggest a time if the topic fits.
- In the first call (30–45 min.) we clarify together: what's the situation, what would be a sensible next step – and whether I'm the right person for it.
Useful to know upfront
- Brief description of the situation (not the solution)
- Approximate team size and company size
- What you're hoping to get from the conversation
- Whether there's a specific trigger (e.g. audit, pivot, escalation)
For initial enquiries, situation descriptions, or if you prefer writing over calling.
Sometimes a short call is faster than a long email.
If I am not available, please call again later or leave a message.