From a first call to your own engineering team.
Four steps. Most clients start with one small project and stay for years. Nobody signs a long contract at the beginning.
You own the code, the accounts and the documents from the first invoice.
GuideDoc worked this way for eight years. WoonWijzerWinkel, four.
Read the storiesYour morning is our afternoon.
If you are in Amsterdam, Madrid or Barcelona, the team is online for about six hours of your working day. Ask in the morning, get an answer before lunch.
Outside Europe the window is shorter. We say so before you sign, and we agree the hours in writing.
- Amsterdam · Madridabout 6 hours
- Londonabout 5 hours
- Sydneyabout 4 hours
- New Yorkabout 2.5 hours
Releases and incidents are covered outside these hours.
Four things we do not change.
A senior engineer designs and reviews every engagement. It is the same person you can call.
Nothing reaches production without a second engineer reading it and QA checking it.
Your code, your accounts, your IP. Assigned in the contract from the first invoice.
A small team with low turnover. The engineers who start on your product are usually still on it years later.
For your technical teamEnvironments, pipeline, testing, review, production and handover. If that is not you, skip it.
Show detailsHide
Environments, pipeline, testing, review, production and handover. If that is not you, skip it.
- Separate local, staging and production, in your own cloud accounts.
- Infrastructure described in code where it earns the effort.
- AWS by default. We are an AWS Consulting Partner.
- Every merge builds and runs the test suite.
- Automatic deploy to staging, one approved step to production.
- Rollback path checked before a release, not after.
- Unit tests on business logic, integration tests on APIs.
- Manual QA on every release, by someone who did not write the code.
- We cover what breaks and what costs money, not a coverage number.
- Every change reviewed by a second engineer before merge.
- Small changes, short-lived branches, readable history.
- Architecture decisions written down in your repository.
- Error tracking and alerts from the first release.
- A named engineer responsible during your working hours.
- Dependency and security updates handled as normal work.
- Repositories, accounts and documents are yours throughout.
- A current README and architecture document, not a final report.
- Any engineer leaving your product writes a handover note first.
Questions founders actually ask.
Can you give me a price now?
On the first call we give a rough range and tell you what it depends on. A price you can plan with needs the Discovery Sprint first.
What if it is not working?
After the first three months the agreement runs month by month, with a short notice period. You keep the code, the documents and the accounts.
How do I judge you if I am not technical?
Working software shown to you every sprint, a senior engineer who explains decisions in plain language, and clients who stayed four, five and eight years. We will connect you with them.
Is English a problem?
No. Most of our clients are not native English speakers either. We write short and plain, and we put decisions in writing.
Step one is a 30-minute call.
We name your biggest technical risk, give you an honest range, and say clearly whether we are the right team.
Free · 30 minutes · with a founder · no deck, no pressure