[ How we work ]
Predictable, in writing, and yours at the end.
Most software projects go wrong commercially before they go wrong technically. Our process exists to remove the ambiguity that causes it.
[ Process ]
Four steps, every engagement.
From a two-week build to a six-month project, the shape is the same.
- 01
Discovery
We start from the outcome you need, not the technology. A scoping conversation, then a written summary of what we understood - so any misunderstanding surfaces before it costs money.
- 02
Proposal
A fixed scope, a fixed price and a target delivery date, in writing, before any work begins. Changes are quoted separately and agreed in writing.
- 03
Build
We work in short increments, usually with something you can look at from the first week. One named point of contact, regular written updates, and no silent periods.
- 04
Handover & support
You own the code, the repositories and the hosting accounts. We hand over documentation and a walkthrough, and stay available under a support agreement if you want one.
[ Commitments ]
What you can hold us to.
These are not aspirations. They are what the services agreement says.
Written scope, fixed price
Nothing starts without a signed proposal stating what will be delivered, for how much, and by when. Changes to scope are quoted separately and agreed in writing before they are built.
One named point of contact
You always know who is working on your project and how to reach them. No account manager relaying messages to an anonymous team.
Regular written updates
At regular intervals you get what was done, what is next, and anything that has become a risk. If a date is going to slip you hear it from us early, not on the deadline.
Confidentiality by default
Everything you share is confidential under our services agreement from the first conversation, and we never name clients or describe their systems publicly without written permission. Where an NDA is useful, or your own process requires one, we sign a mutual NDA — ours or your template — before the detail is shared.
You own everything
On final payment the intellectual property in the deliverables transfers to you. Repositories, hosting and third-party accounts are created in your name wherever possible, so nothing is hostage to us.
Documented handover
Every project ends with documentation and a live walkthrough, written so that another developer could pick the work up without calling us.
[ Practicalities ]
The operational detail.
The answers that usually come up on the second call.
- Working languages
- English and Spanish. Contracts, documentation and written updates are delivered in English unless agreed otherwise.
- Where we work
- Remotely, with clients across the United States and Europe. On-site training and workshops are available by arrangement, with travel quoted separately.
- Availability
- Monday to Friday, 09:00 - 14:00 CET. Enquiries are answered within one business day. Support-agreement response times are defined in the agreement itself.
- Subcontracting
- Where a project needs a specialist we do not have in-house, we say so before it is agreed, and any subcontractor is bound by the same confidentiality terms. We do not subcontract work silently.
- Data handling
- We work on the minimum client data needed for the task, prefer anonymised or synthetic data in development, and delete working copies on completion. Detail is in our Privacy Policy .
Ready to scope something?
A short description of the problem is enough to start. We reply within one business day, and if it is not a fit we will say so.