How we work: from written assessment to a system your team can run
The process is designed so that you can stop after any step with something useful in hand, and so that the expensive decisions are made before the expensive work starts.
- 01
Written assessment
Free · 2 business days
You submit the project enquiry. We read it, look at anything you link to, and reply in writing: whether it is a fit, two or three ways to approach it, the main risks, and an indicative range. If we are not the right partner, we say so and, where we can, point you somewhere better.
You receive- 1–2 page written reply
- Fit, options, risks, indicative range
- Optional: a 30-minute call to clarify — your choice
- 02
Discovery sprint
2–3 weeks · fixed fee
Workshops with the people who own the process and the systems; interface and data review; a thin technical spike where there is uncertainty (e.g. “can the ERP actually expose this?”). The result is a plan with a price, not a slide deck.
You receive- Scope with prioritised user journeys
- Target architecture and integration map
- Risk register and build-vs-buy recommendation
- Fixed price and milestone plan for the build
- Documents you own — usable for an RFP elsewhere
- 03
Build in milestones
1–9 months depending on scope · fixed price
Foundation first (identity, integration layer, environments, pipeline), then journeys in priority order. Every milestone has acceptance criteria you sign off and a demo on real data. Payments follow milestones, typically 30/40/30.
You receive- Working software after each milestone
- Automated tests, CI/CD, monitoring
- Documentation kept current as part of the work
- Change requests priced before work starts
- 04
Handover and evolution
Warranty included · retainer optional
Go-live with a runbook, a defect-warranty period, and a handover to your team if you want one. After go-live you choose: a small monthly retainer for support and evolution, or a handover to your own team. We build for either from day one.
You receive- Runbooks, admin guides, architecture documentation
- Defect warranty
- Optional support/evolution retainer with response times
Rules we work by
You own everything, always
Repositories, cloud accounts, domains, documentation — created in your name from the start. No escrow needed because there is nothing to escrow.
One senior engineer is accountable
The founder leads architecture, reviews every significant change and is your technical counterpart. The engineering team in India implements under that review.
Written before verbal
Decisions, scope changes and assumptions are written down the same day. Meetings are short because the documents do the work.
Production data stays where it belongs
Your Swiss/EU environments hold production data; development uses masked or synthetic data. Restrictions on who may access what are agreed in writing.
No surprises on invoices
Fixed prices for fixed scope. Change requests are estimated and approved before they are built. Retainers are monthly with 30-day notice after a three-month minimum.
Communication during a project
- Weekly written status (done, next, risks, decisions needed) — no status meetings unless you want them.
- A shared issue tracker and chat channel you can read at any time.
- Demo at each milestone on real data.
- CET working hours for all client contact; engineering team overlaps CET mornings and early afternoons.
- English or German, your choice.
Common questions
Do we have to do the discovery sprint?
For anything beyond a small integration, yes — it is what makes a fixed price honest. For small, well-defined work, the written assessment can go straight to a fixed quote.
What if requirements change during the build?
They will. Changes are estimated, priced and approved before they are built; the milestone plan is adjusted in writing. Because journeys ship incrementally, you can reprioritise what comes next without renegotiating everything.
Can our own developers work alongside you?
Yes, and it is the best way to make handover real. We agree on review rules and who owns which areas; your developers work in the same repositories and pipeline.
Have a system that needs building, connecting or replacing?
Describe it in a few sentences. You get a written, engineer-level reply within two business days — no sales call required.