No surprises
in the invoice or the timeline
Below is how we run projects, what you pay for and what happens when something goes wrong. Read it before the call — it saves both of us an hour.
Four rules we do not bend
You own everything
Code, infrastructure, accounts and documentation are yours from day one, in your repository. No lock-in, no hostage situations.
Weekly demo
Every Friday you see working software, not a status report. If a week produced nothing worth showing, we say that too.
Tests before speed
Risky parts get covered first. It looks slower in month one and pays back from month two, when changes stop breaking things.
Direct contact
You talk to the engineers doing the work, not through an account manager who relays questions.
Three ways to work with us
Pick by how well the scope is defined, not by budget size.
Fixed scope
We estimate the whole thing, fix the price and the deadline. Changes go through a short change request, so the budget never moves quietly.
- Fixed price and date
- Payment by milestone
- Best for MVPs and integrations
Dedicated team
A team works only on your product, monthly rate, priorities set by you every sprint. Scale up or down with two weeks of notice.
- Monthly rate per engineer
- You own the backlog
- Best for long-term products
Support retainer
Monitoring, on-call, small changes and security updates for a fixed number of hours per month. Unused hours roll over one month.
- Agreed response times
- Monthly health report
- Works on someone else's code too
Questions we get before signing
How much will it cost?
Nobody can answer that before discovery, and anyone who does is guessing. After a call and a couple of days of analysis you get a range with the assumptions written down.
What if we stop halfway?
You keep everything produced up to that point and owe nothing for the rest. Notice period is two weeks on a retainer and per milestone on fixed scope.
Will you work with our existing team?
Often that is the best setup. We agree who owns which part of the codebase and share the same board and review process.
Our previous contractor left a mess. Will you take it?
Usually yes, but we start with a paid audit — a week or so — and then tell you honestly whether it is cheaper to fix or to rewrite. Sometimes the answer is rewrite, and we say so.
Who owns the intellectual property?
You do, fully, from the first commit. It is written into the contract, not promised on a call.
Still have questions?
Send them over. A short answer costs us nothing and saves you a month of the wrong direction.