Services
System architecture
Decisions captured in diagrams and words, so engineering, security, and leadership share one picture of the system.
Who this is for
You need alignment before a major build, a migration, or a rebuild, or you inherited a system where nobody can explain how data flows end to end.
Related: A Code Rescue technical audit answers “what shape is the code in?” (security, debt, maintainability). Architecture work here answers “what should we build or migrate toward?” They can be sequenced; they are not the same engagement.
- Leadership needs an independent view of options and costs
- Teams disagree on boundaries between services or ownership
- Compliance or security asks for explicit data flows and controls
- You are splitting a monolith, merging products, or replatforming
- You want a phased roadmap instead of a single big-bang estimate
What we deliver
Artifacts you can reuse in RFPs, board decks, and engineering backlogs, not slides that age in a week.
Context & constraints
Business goals, non-functional requirements, and hard constraints (latency, residency, integrations) made explicit.
- Stakeholder interviews (asynchronous where possible)
- Risk register: technical debt, vendor lock-in, single points of failure
Architecture options
2–3 coherent approaches with trade-offs: cost, complexity, team skills, time-to-value.
- Context diagrams and container-level views
- Data ownership and API boundaries
Roadmap & estimates
Phased plan with ballpark ranges and dependencies, good enough to prioritize, honest about unknowns.
- Milestone slicing for build or migration
- “Must decide before code” checklist
How it works
Architecture work is time-boxed and evidence-based. We read what exists, ask sharp questions, and document decisions so they survive handoffs.
- Intake & materials. Repos (read access), existing docs, incident history if available.
- Discovery workshops. Short, focused sessions; outputs are written summaries, not meeting theatre.
- Review cycle. You comment in a shared doc; we revise until the narrative is consistent.
- Handoff. Diagrams + written narrative + open questions list for implementation teams.
Indicative pricing
Ranges depend on system size, number of integrations, and how much reverse-engineering is required. Deep compliance regimes or multi-tenant migrations sit at the upper end.
Architecture assessment (focused)
€14,000–€38,000+
What it covers: A bounded slice: one product area or one migration path, with diagrams, risks, and recommendations.
Fit when: You need a clear decision memo in a few weeks.
Discovery & roadmap (full product)
€35,000–€85,000+
What it covers: End-to-end view, multiple options, phased roadmap, and ballpark estimates for build phases.
Fit when: You are funding a large program and need a shared baseline.
Embedded architecture (per phase)
€18,000–€55,000+ / phase
What it covers: Ongoing architecture ownership during delivery: ADRs, review gates, and course corrections as requirements evolve.
Fit when: The build is long enough that architecture must live alongside delivery.
Indicative only. Fixed-fee vs time-and-materials is agreed per engagement. A “+” signals programs that span many teams or regulated environments.