Plainly Innovate Start a project
HOW I WORK · NO SURPRISES

how I work

Boringly predictable, on purpose

Most people arrive here having been burned: by an agency that went quiet, a freelancer who vanished, a project that doubled in price halfway through. So here is exactly what happens, in order, and exactly how the money works.

01

The path

Every engagement follows the same four steps. You can enter at any point, but the order exists for a reason: it is cheaper to diagnose before building, and cheaper to build well before running.

STEP 1

Discovery

What happens first: the five-question form, a reply within 48 hours, and a short call if it looks like a fit. Free, no obligation on either side.

begin discovery →
STEP 2

Diagnostic

A written assessment of how the operation actually runs, where it leaks time and money, delivered in two weeks. The deliverable is a document: a process map, findings costed in your own numbers, and a sequenced plan any engineer could execute.

STEP 3

Build

Custom software, integrations and automation, scoped from the diagnostic or directly where the problem is already clearly defined.

Builds span four kinds of work.

Build
The product itself: the thing your customers and staff actually touch.
Automate
The manual steps that stop needing a human.
Connect
Your tools talking to each other instead of through you.
Integrate
Disparate systems behaving as one.
STEP 4

Support

The ongoing arrangement: hosting, monitoring, maintenance and the next improvement, handled monthly, for as long as you want it. Not a package you upgrade to; the same standard, continued.

Engagements typically start at £2,500.

02

A build, step by step

1/4
Build, in the open A staging link from week one, so you watch it take shape. A short written update every week: what got done, what's next, anything blocking. You'll never wonder what's happening.
2/4
Review & fix You test everything against the scope. What's wrong gets fixed, without negotiation; that's what the scope was for.
3/4
Launch Domains, DNS, analytics, monitoring and backups, done properly. Launch day is a checklist, not a drama.
4/4
Handover & aftercare Documentation a non-engineer can follow, a walkthrough call, and a 30-day window for anything that snags. Then you choose: run it yourself, or move to support and have it run for you.
03

Three ways to work together

Not a pricing table; a framework. Which one fits depends on your cash flow, how much you want to own, and whether you want a long-term engineering partner or a finished thing.

MODEL A
Licence

Lower upfront cost, then a monthly fee covering hosting, maintenance and small changes. Plainly Innovate retains the code and IP; you get a system that's always looked after.

suits · cash-conscious starts
upfront · lower
ongoing · monthly
ownership · kept by Plainly Innovate
MODEL B
Buyout

One fee, and everything is yours: code, accounts, IP, documentation. Walk away free, host it anywhere, hand it to any developer. An optional retainer is there if you want it.

suits · companies that want full control
upfront · higher, one-off
ongoing · optional
ownership · yours, outright
MODEL C
Retainer

Ongoing monthly engineering: hosting, updates, maintenance, managed automations, and a standing claim on my time when something new is needed.

suits · systems that must keep running
upfront · none
ongoing · monthly
ownership · per original model

unsure which fits? that's a discovery question, and the honest answer is sometimes "none of them yet".

04

Step one is five questions.

everything above starts the same way.

Begin discovery →