Skip to content

How engagements are structured

Five ways to work together, each a different commercial shape rather than a tier of the same one. Every engagement starts with the same conversation about what is actually in front of you, and the scope follows from that rather than the other way round.

See the five models

On prices

Because any number I printed would be wrong for most of the people reading it. A performance diagnosis on a slow Magento store and a headless replatform with an ERP integration behind it are not the same size of work, and one published figure would misprice both.

And because a quote is cheap to get. Describe what is in front of you and you get a real number against a real scope, usually the same day. That is a better use of both our time than a rate card you would have to caveat anyway.

What you get instead

  • A scope written down before anything starts, in terms you can hold me to.
  • A fixed number for fixed-scope work, not an estimate that drifts.
  • A clear hourly rate once I know what the work is, confirmed in writing.
  • A recommendation that no project is needed, where that is the honest answer.

Engagement models

  1. Hourly Technical Consulting

    Time, bought in blocks, against questions rather than deliverables.

    Best for

    A decision you would rather not make alone: a platform choice, an architecture review, a proposal from someone else that you cannot independently evaluate.

    How it is structured

    • Billed hourly, in agreed blocks, with the time logged against what it was spent on.
    • No minimum retainer and no commitment past the block you have bought.
    • Scheduled sessions plus written follow-up, because the reasoning is the deliverable and it needs to survive the call.

    What is included

    • Architecture and platform review
    • Code and infrastructure assessment
    • Written recommendation with the reasoning behind it
    • Second opinion on an estimate, proposal or vendor
    • Direct access, with no account manager in between

    Not for: Implementation. If the answer turns out to be "build this", that is a different engagement and I will say so.

  2. Fixed-Scope Development

    A defined piece of work, a fixed number, an end date.

    Best for

    Work you can describe: a migration, a module, an integration, a checkout rebuild, a performance programme with a target.

    How it is structured

    • Scoped first, in writing, including what is explicitly out of scope.
    • Fixed price against that scope, staged across agreed milestones.
    • Change requests priced separately rather than absorbed quietly, so the number you agreed stays the number.

    What is included

    • Technical specification and architecture
    • Implementation, code review and testing
    • Deployment, with the release process documented
    • Handover documentation written for your team, not for me
    • A defined warranty period after go-live

    Not for: Work nobody can describe yet. If the scope is genuinely unknown, an hourly diagnosis first is cheaper than a fixed price padded for the unknown.

  3. Monthly Retainer

    A reserved block of capacity each month, with priority access.

    Best for

    A live platform that needs someone to own it technically: a steady stream of changes, releases and the occasional thing that breaks at a bad time.

    How it is structured

    • An agreed number of hours each month, reserved rather than sold speculatively.
    • Rolling monthly, cancellable with notice. No annual lock-in.
    • Priority response, and a standing slot rather than joining a queue.

    What is included

    • Platform maintenance, upgrades and security patching
    • Performance monitoring and tuning
    • Feature development inside the monthly allocation
    • Incident response during agreed hours
    • A monthly written summary of what changed and what it cost

    Not for: A large build. A retainer that gets consumed by one project is not a retainer, and the project should be scoped as one.

  4. Contract Engineering

    A senior engineer inside your team, for a fixed term.

    Best for

    A team that needs commerce or full-stack depth for a defined period: a release to get out, a gap to cover, a capability to build in-house.

    How it is structured

    • Fixed-term contract, full-time or an agreed fraction of a week.
    • Working inside your process: your board, your standups, your review cycle, your definition of done.
    • Monthly or milestone billing against the agreed term.

    What is included

    • Hands-on development in your stack and your repository
    • Architecture input and code review for the wider team
    • Mentoring, where the brief includes building the capability
    • Documentation and handover at the end of the term

    Not for: A permanent seat. If that is what you are filling, the remote work page is the right place to start.

  5. Long-Term Development Partnership

    An ongoing technical relationship rather than a sequence of projects.

    Best for

    A business whose platform is the business: a multi-year roadmap, a growing catalogue, and a need for the person who makes the decisions to remember why the last ones were made.

    How it is structured

    • An annual or multi-year arrangement, reviewed quarterly against the roadmap.
    • Blended commercially: a retained base for continuity, with projects scoped on top.
    • Involved in the roadmap rather than handed it, which is the whole point of the model.

    What is included

    • Technical ownership of the platform and its direction
    • Roadmap planning alongside the commercial side of the business
    • Architecture governance as the platform and team grow
    • Everything in the retainer and fixed-scope models
    • Continuity: the context does not get rebuilt every engagement

    Not for: A first engagement. This is where a working relationship ends up, not where it starts, and it should follow a project that went well.

Getting a quote

No charge for any of it, and no follow-up sequence afterwards. If the scope says you do not need the work, that is the end of it.

  1. Tell me what is in front of you

    A few paragraphs is enough. The platform, the problem, and what you have already tried or been quoted.

  2. A short call, or a written reply

    Whichever is faster for the question. Usually within 24 hours, and the call is 30 minutes rather than an hour of discovery theatre.

  3. A written scope and a number

    What the work is, what it is not, the structure it fits, and the figure. Usually within a few days of the call.

  4. Decide, including deciding not to

    No follow-up sequence and no pressure. If the answer is that you do not need this, the scope will say so.

Questions

Why is there no price list on this page?
Because one number would be wrong for most of the work. A performance diagnosis and a headless replatform differ by an order of magnitude, and publishing a single rate would misprice both. A quote against a real scope takes a day or two and is accurate, which a rate card cannot be.
How do I get an actual number?
Describe the work on the contact page or email [email protected]. You get a written scope and a figure, usually within a few days of a short call. There is no charge for the quote.
Which engagement model should I pick?
You do not have to. Describe the problem and I will tell you which one fits, including when the answer is the cheapest one on the page. A decision you are unsure about is hourly consulting; work you can describe is fixed scope; a live platform that needs owning is a retainer.
Do you charge for the first conversation?
No. The first call and the scope that follows it are free, because neither is the work and pricing them would just slow down finding out whether there is any.
Can a fixed-scope project turn into a retainer?
Often, and that is the usual path into one. A platform that has just been built or migrated is the platform most in need of someone to own it, and by then the context is already there.
Do you work with agencies as a subcontractor?
Yes, white-labelled where that is what the arrangement needs. The agency partner page covers how that works and what the commercial structure looks like.

Tell me the platform, the problem and what you have already been quoted. You get a written scope and a figure, and no charge for either.

What I actually do