Questions first. Code later.
We talk to the people who will use the system and look at what you already run. You leave with a clear scope, a plan split into releases and a price you can plan with.
What an analysis is
An analysis is the part of a project where we find out what exactly to build, for whom and why. It ends with a document you can make decisions on: scope, priorities, plan and price.
It does not always start with a new system. Sometimes the question is what to do with the old one.
A new system
Before development of something that does not exist yet.
What to keep in mind
The first release. Everyone has ideas for a new system. The analysis picks the smallest part that is useful on its own, so people work in it soon and the rest follows from experience.
An existing system
When the current system is slow, old or hard to change.
What to keep in mind
Fix, rebuild or replace. We read the code and the data and talk to the people who use it. Then we say openly which option makes sense and what each one costs.
A process
Work that runs on spreadsheets, email and memory today.
What to keep in mind
The exceptions. The usual case is simple. What takes the time are the exceptions nobody wrote down, so we sit with the people who handle them every day.
Connections
Systems that need to share data without retyping.
What to keep in mind
Who owns which data. When two systems keep the same record, one of them must be the source. We check what the older systems really allow before anyone promises a date.
It starts with a pile of requests
Emails, spreadsheets, meeting notes and ideas from the corridor. Each makes sense on its own. Together they are hard to plan or price. The analysis sorts them into the first release, what follows and what can wait. Here on the example of a patient zone.
A first release that can go live
A small scope that works on its own and is useful from day one. You know its scope and price before development starts.
What comes right after
Builds on the first release and adds what users will ask for next. Its scope is checked again against what the first release taught us.
What can wait
Written down and estimated separately, so nothing gets lost and nothing is rushed. Some of it may turn out not to be needed at all.
What the system does and what it does not. Management, users and developers read the same thing.
An order by value and risk, agreed with you. The riskiest parts are checked first.
A plan split into parts that each work on their own. Your people can use the first one while the next is being built.
An estimate for each release, with its assumptions. You can build a budget on it.
Where we look for answers
A good analysis does not come from the brief alone. It comes from how the work is done today, by whom and in which systems. With 10+ years of experience we know which questions to ask.
How the work really runs today, workarounds included. They show where the system must help most.
Those who will use the system, not only those who order it. Reception and management need different things.
What already runs and what has to stay. Nothing has to be switched off overnight.
Where data comes from, who changes it and where it goes next.
If we build it
The people who did the analysis stay on the project, through development and later through maintenance. Nobody has to explain your processes a second time, and there is no hand‑off to strangers.
Working software to try regularly, not status reports
Training for your people when a release goes live
After launch, a dedicated developer for a fixed monthly fee
If someone else builds it
The analysis is yours. We write it so that any development team can work with it, and it does not depend on our stack or on us.
Specification, architecture and estimates in one place
Open questions and risks written down, not kept in one head
A second look at offers you receive for it
How an analysis runs
For a smaller system it takes a few weeks, for a core system longer. Thanks to AI we work much more efficiently: it turns notes into a first draft, and a developer checks every line.
- 01
Interviews
Workshops with the people who do the work and someone who can decide.
- 02
Map
Processes, roles, systems and data written down, exceptions included.
- 03
Design
Key screens and architecture. Risky parts are tested right away.
- 04
Plan and price
Releases, priorities and a price. Programming can start from here.
What comes after the analysis
Once the scope is clear, design, development and later care follow.
- UX/UI designInterfaces tested with the people who will use them every day.
- Software developmentOne team from analysis to maintenance, at an unbeatable price thanks to AI.
- Internal systemsOne system instead of spreadsheets and email, built from smaller services.
- System rebuildsReplacing an old system step by step, without stopping the work.
- ConsultingA conversation with a developer about an offer, code or an idea.
Tell us about your project or problem
What you are planning or what you already run, in a few sentences, and any documents you have. We reply with questions and a proposal of what the analysis would cover, who would take part and what it would cost.