An audit before a large build
A short paid audit costs less than an estimate drawn from a conversation, and it tells both sides whether the collaboration will work. If it does not, you keep the report.
Approach
Approach
How an engagement actually runs, what we promise and what we refuse to promise. Read this before the call and the call gets shorter.
A written scope, including the exclusions
Deliverables, price, dates, and a list of what we are not doing. Scope changes are priced when they appear, not argued about at the end.
Weekly, openable progress
Every week there is a build you can open in your own staging environment. A status report is not progress.
No lock in
Your repository, your cloud accounts, your keys, from day one. Handover documentation is written for whoever comes after us, including a team that is not us.
How an engagement runs
- 01
A call
Thirty minutes. What you have, what you need, whether we are the right studio for it.
- 02
A written scope
Deliverables, price, dates and what is explicitly out of scope. Fixed price where the scope allows it.
- 03
Weekly shipping
Something you can open every week, in a staging environment of your own.
- 04
Handover
Your repository, your accounts, your keys. Documentation written for whoever comes after us.
Why you will not find a client list here
Work we do for clients belongs to them, and most of it is under confidentiality. Rather than publishing logos, we walk you through the parts of our experience that match your problem, in detail, on a call.
What we will not do
- Promise a fixed price for a scope nobody has written down.
- Start a rewrite in the first week because the existing code is unfamiliar.
- Hold your accounts, domains or keys as leverage.
- Take a project we do not have the capacity to finish.
Tell us what you are building
Write a few lines about the product and the deadline. You get an answer within one working day, from the people who would do the work.
Get in touch