Architecture review: know where you actually stand.
We analyze your system and write down what we find, free and independent of any follow-up engagement.
Starting point
Sound familiar?
You want to grow
But you do not know whether your system can handle the next stage.
A previous vendor is gone
Nobody on your team can explain why certain decisions were made.
You are planning a larger project
And want to know where the risks are before you invest.
Before money goes into the next decision, nobody has honestly assessed the system.
The result
You then have a document you can decide from: what comes first, how much effort it takes and what can wait.
- A document listing your system's biggest technical risks
- An effort estimate for the most important next steps
- A recommended sequence for tackling them
- An assessment of whether your system needs modernization or a rebuild
Client feedback
From client work
A hands-on mentality paired with broad technological know-how. This is what makes IT projects fun.
Process
How we go about it
01 / REVIEW
We look at the system.
We look at the architecture, code and operations of your system.
02 / CONVERSATIONS
We talk to your team.
We talk to the people who run and build on the system today.
03 / DOCUMENT
We write down the findings.
We write down risks, effort estimates and a sensible sequence for next steps.
04 / HANDOVER
You get the document.
You get the document and a conversation about it, regardless of whether we work together afterward.
Team shape, cadence and handover in detail are covered on the How we build page.
Questions
Frequently asked questions
Yes. You get the document even if no further engagement follows.
A few days to two weeks, depending on system size. We clarify scope in the first conversation.
No. The document is yours and usable without us.
Running software that has grown without its architecture growing along with it. From individual services to entire platforms.
No. We do not estimate work we have not understood. An analysis always comes first.
No. Whoever starts stays until handover.
No. After handover you decide when we lose access to your systems. There is no spare key.
The code is yours and so is the documentation, entirely from day one. We do not build dependency on us as a business model.
Contact
Let's take a look at your system.
Tell us what runs and where it hurts.
André Loreth
Andreas Neugebauer
You talk directly to the founders.
A reply within one working day.
On the call
- 01You describe what's going on: a new system, or one that isn't keeping up anymore.
- 02We ask questions and tell you honestly whether and how we can help.
- 03You get concrete next steps, whether or not we end up working together.