Home/Process

BNS/P How projects run

No black boxes. Just six steps.

You’ll always know what’s happening, what it costs, and what comes next — because there’s nobody between you and the person building it.

01

Understand

A straight conversation: the business, the customers, what’s actually broken. Free, no pitch.

You get → honest take
02

Define

Scope written down in plain words with a fixed price. If it’s not in the doc, you don’t pay for it.

You get → fixed proposal
03

Build

Clean, tested code on real devices, with updates you can follow without a dictionary.

You get → working system
04

Test

You review a working version and try to break it before it ships. Fixes happen here, not after launch.

You get → approval round
05

Launch

Deployed, checked and indexed. Then watched closely in the first days live.

You get → live + supported
06

Improve

Measured against the original goal and refined. Most value appears after go-live, not before.

You get → ongoing gains

The rules I work by.

PricingFixed before work starts. Changes are quoted, never smuggled in.
CommunicationDirect messages with the builder. Every enquiry read carefully.
OwnershipYou own the code, accounts and data. Documented handover included.
AftercareLaunch isn’t goodbye — fixes and improvements continue.

Timelines, honestly.

A focused website typically takes two to four weeks. Automation and AI helpers often less. Bigger systems are phased so something useful ships early instead of everything shipping late.

I take on a small number of projects at once — if I’m full, I’ll tell you when I can start rather than squeeze you in badly.