The bit nobody else does

Everything a software team does, done for you

Writing the thing is maybe a fifth of the work. The rest is deciding what to build, checking it, putting it somewhere, keeping it standing and fixing it on a Saturday. That is the part you were never offered separately, and it is the part that decides whether you still have a working thing in two years. Here is all of it, in order.

First, it works out what you actually need

Not what you asked for. A haulage firm asked for a phone list with a box for the company name. What he needed was companies as their own thing, because a haulier has six people at it and you ring whichever one picks up. Typed as a box, that list is wrong within a month. This is the job a good analyst does before anyone writes anything, and it is the reason most software built to a customer's exact words turns out useless.

Then it says what it is about to do, and what could go wrong

Who will be able to see what. Whose information is in here. Which screens a customer could reach if you sent them a link. If something in that looks wrong, it asks you now, in your words, rather than after it is built. Something like: this screen would let one customer see another customer's bookings, shall I lock it to their own?

Then it builds it, and reads its own mistakes

It compiles it, runs it, opens every screen and checks each one actually has something on it. When something fails it reads the error and fixes it, the way a developer would, and goes round again. You are not shown any of that. You are shown the thing working.

Then it checks its own work before the internet ever sees it

Every outside component it used, checked against the list of ones with known problems. Every file checked for a password left lying in it. A written record of every piece that went in, kept, so the day a problem is announced somewhere in the world we can answer in seconds whether yours has it.

If any of that fails, it does not go live. There is no button to say do it anyway, because you should never be the one deciding whether a security problem is acceptable. That is our job and you are not equipped to carry it, which is exactly why you came here.

Then it puts it up properly

A real address, a certificate so the padlock shows, the database shut away where nothing on the internet can reach it. Then it takes the first copy of everything and proves the copy works by putting it back. A backup nobody has ever restored is a rumour.

Then it keeps doing all of that, forever

The daily copy, the watching, the emailing you when something stops. And when one of those outside pieces turns out to have a problem six months from now, it is replaced and your app is put back up on the new one. You find out because we tell you it is done, not because you have to do anything.