Start to finish, in writing.
Most of what goes wrong between a business and a software company goes wrong in the gaps: the things nobody wrote down, the weeks nobody heard anything, the invoice nobody expected. So we built the gaps out of the process. Here is the whole journey, in the order it happens.
A call with a person.
Not a form, not a chatbot, not a discovery questionnaire. You talk to a person about what your business needs, and we tell you plainly whether we’re the right people to build it. If we’re not (wrong size, wrong shape, wrong budget), we say so on that call, and we’ll try to point you somewhere better.
Your client login opens.
Within days of that call you get a link to a private page: your client login. The proposal lives there, and so does everything that follows: the scope, the agreement, the invoices, and a dated, plain-English record of the work. There is no password to remember and no account to create. The link is yours to share with a business partner, an accountant, or the colleague who asks the hard questions. The room is written to hold up in front of the most sceptical person you know.
The scope, in writing.
Before we take a deposit, you have a written scope: what we are building, what it costs, what it does not include, and what happens if either of us wants to change it. The price you agree is the price. Changes to scope are agreed in writing, priced in writing, and recorded in the room before any work on them starts. Nothing drifts, and there are no surprises in month three.
A Friday update, written by hand.
Every Friday while your build is live, we write you an update in plain English: what got done, what’s next, and anything that needs a decision from you. It is written by the person doing the work, not generated by a dashboard, and it goes into the room where the whole history stays readable. If a week goes badly, the update says so. You will never learn more from an invoice than you learned from the updates.
Sign-off, on your terms.
A build ends when you say it does: a walkthrough of everything in the scope, against the scope, with anything unfinished named and dated. The final invoice arrives after sign-off, not before. And your client login stays yours: the record of what was agreed, built and paid for doesn’t vanish when the project ends.
If that sounds like the way you’d run things, write to us or go back and read the letter on the front page.