FnExec

The What and the How

When you hire a builder, you decide the house: how many bedrooms, where the kitchen goes. You do not decide how the framing is nailed. The first is the What. The second is the How.

Software is the same. What it must do is yours to say. How it is built is ours.

The What and the How Two lines run left to right. The upper line is yours, the What; the lower line is ours, the How. They touch twice: at the description, before any code, and at the checks, at delivery. Between the two, your line is dotted, with nothing to manage, while ours carries the build. The What yours The How ours the description the checks nothing to manage
The two meet twice: at the description you sign off on, and at the checks you watch pass.

The What yours

We sit down with you and write out what the software has to do, in plain words, one item at a time. Where something is unclear we ask before we quote, and the answer goes into the description. You read it and sign off.

You do not need any technical knowledge. If a spreadsheet, a prototype, or a written procedure already does part of the job, bring it. It is a good place to start.

The What takes weeks. Then we quote one price for the build, and the price holds for what you signed off on.

The How ours

AI writes the software, but not from a conversation. It writes from your description, and it writes tests as it goes, so that what it builds is checked against what you asked for.

Where the description left a question open, the choice is written down with its reason before any code is written, and added to your description so you can see it.

The How takes days. The build is not finished until every one of its tests passes.

Where they meet again

At delivery we sit down with you again and go through the checks, one at a time. Each one passes or fails, and you can see which without reading code. You get the software when the list passes.

You also get a written record of the build: your description exactly as the build received it, what each step produced, and the result of every check. It ties each line of the description to the tests that confirm it and lists the few that no test can confirm, with the reason. It is what you hand to whoever asks how the software was checked.

If you want something different later, we write the change down, price it before any work on it begins, and then make it and check it against the new description. A change takes days as well.

A few things, such as where the backups live, depend on where the software runs, and no test of the code can settle them. We go over hosting and where it will run when we talk.

We take on a small number of builds at a time. To begin, write to how@fnexec.com with a short description of what you want the software to do.