How we work

No mystery, no jargon, no invoice you did not see coming. Here is the whole process, including the parts most shops do not show you.

Four application screens in sequence, from a first sketch through a review pass to a finished interface.

01

The call

30 minutes, free

You describe the problem. We ask what it costs you today, who has to use it, and when it has to exist. If the answer is a spreadsheet or a tool you already own, we say so and there is no invoice.

02

The quote

Within 2-5 days

Fixed scope, fixed price, in language you can forward to a colleague. It names what is included, what is not, and what we would do next but are not charging you for yet.

03

The first slice

Two weeks

We build the riskiest part first and put it in your hands. If it is wrong, it is wrong two weeks in, not four months in.

04

Weekly to launch

Then handover

A demo every week. At the end you get the code, the accounts, the documentation and a walkthrough.

Where AI fits, and where it does not

We use AI daily. It is also confidently wrong in specific, repeatable ways: a payment handler that charges twice on a retry, money kept in a float, a check that you are logged in without checking the record is yours.

So AI drafts and a person owns. Every line is read by someone who will answer the phone if it breaks.

The ten things AI gets wrong

Things we will say that you may not expect

“Do not build this.”

If a spreadsheet, an existing tool or a phone call solves it, that is the answer.

“That is cheaper than you think.”

Most integrations are days, not months.

“That is more expensive than you think.”

Usually anything touching money, permissions or old data.

“Not us.”

If it needs a specialism we do not have, we say so and, where we can, name someone.

Working with us, practically

Who you deal withA named engineer, not an account manager
How often you hear from usA demo every week, in writing between
How we billFixed price against scope, in stages
Who owns the workYou do. Code, accounts and documentation
What happens at the endA handover session and a runbook

Custom software, built to fit

Tell us the thing that will not work.

Thirty minutes on a call. We will tell you what it takes, what it costs, and whether you should build it at all.

Book a call What it costs