Clear ground rules, before we write the first line of code.
How we bill, how a project runs step by step, and what you get at the end.
Three ways to work together
Fixed price
The scope is known and you want to know the cost up front.
- Good for
- Integrations and well-defined stages
- Billing
- Per stage, on acceptance
Time and materials
The product keeps evolving and priorities shift every few weeks.
- Good for
- New products and ongoing development
- Billing
- For hours worked, monthly
Engineers in your team
You have a team and a process, and you need experienced people.
- Good for
- Strengthening a team for the length of a project
- Billing
- Monthly, per person
How a project runs
Call
Half an hour on what should work and why. No strings attached.
Scope
We write down what we will build, in what order, how long it takes and what it costs.
Build
We work in short stages and show working progress.
Launch
We go live with monitoring and a plan for when something goes wrong.
Maintenance
We stay with the system: fixes, updates, further development.
How we build
The same technology and the same habits in client projects and in our own products.
Changes reach users in small pieces, so each one is easy to check and to roll back.
Every change passes the tests before it reaches users.
A second person reads the code. Always.
We write down what we chose and why. The project can be handed over without us.
Rules that always apply
- NDA before the first call, if you want one.
We sign a confidentiality agreement before you tell us about the project.
- The code is yours.
After acceptance the rights to the code pass to you, and the repository is in your hands from day one.
- You see progress as it happens.
Access to the repository, the task board and a test version for the whole project.
Let us talk about your project.
In the first call we will work out which model makes sense.