How it works

You don't have to commit to a software project to find out whether one is worth it. Each step is small, priced up front, and you can stop after any of them.

The four steps

  1. Step1

    Free call

    20 minutes, no charge

    You tell me which task takes the most time. I ask a few questions and tell you honestly whether it's worth looking at. Sometimes the answer is a setting in software you already own. You leave knowing whether an audit is worth paying for.

    Book the free call

  2. Step2

    Admin automation audit

    £2,450 + VAT, fixed

    A one-hour kick-off to agree up to three processes to look at. Then I spend time on site with the people who do the work, and map where the hours and errors go. You get a written, costed, prioritised plan and a call to go through it. The report is yours to use with anyone.

    What the audit covers

  3. Step3

    Build

    Fixed quote, in phases

    If the report says a custom system is the answer, I build it in small phases. Each phase is quoted before it starts, so you see working software early and can stop after any of them. The audit fee is credited if you go ahead within 90 days.

  4. Step4

    Support

    Monthly, agreed up front

    Once it's live: hosting, maintenance and fixes for a monthly fee, with response times agreed in writing before go-live. Optional.

Why it's broken into steps

Each step stands on its own. You get something useful out of it whether or not you go any further.

The call costs nothing

Most of the time a short conversation is enough to know whether an audit is worth booking. If it isn't, I'll say so.

The audit stands alone

You get a written, costed plan whether or not you build anything with me. Use it yourself, or with another developer.

Builds happen in phases

You see something working early, rather than waiting months for one big release. Each phase is quoted before it starts.

Support is optional

Once a system is live, ongoing hosting and support is a separate agreement, priced and agreed up front.

Why it works this way

Requirements rarely arrive all at once. Why asking for one thing at a time costs more

Most failed software projects are not built badly. They are built to a specification nobody checked against reality.

People rarely bring a problem; they bring a solution already diagnosed. The request already contains an answer

Start with a 20-minute call

No pressure to book an audit afterwards. See what the Admin Automation Audit covers first, if you'd rather read ahead.

Book a free 20-minute call