What It Costs
The conversation most technology companies avoid.
We would rather you knew roughly what this costs before you speak to us than discover it three meetings in.
Why we talk about this openly
Cost is one of the main reasons smaller organisations delay work they know they need. Research by the OECD into UK technology adoption lists it alongside perceived relevance and trust in vendors as a primary barrier. Refusing to discuss it until someone has filled in a form does not remove the barrier. It only moves it.
Figures cited are drawn from published sources and are correct at the date of publication. The source is named alongside each figure.
What actually drives the cost
- 01
Scope
How much there is to build, and how much of it is genuinely necessary.
- 02
Complexity
Whether the logic is straightforward or full of exceptions and edge cases.
- 03
Integration
How many other systems this has to talk to, and how cooperative they are.
- 04
Compliance
Whether the sector brings obligations around consent, audit, accessibility or data handling.
- 05
Design depth
Whether this needs a considered experience or a functional interface.
- 06
Support expectations
What happens after launch, and how quickly you need issues resolved.
How we price each type of engagement
Discovery is priced as a fixed piece of work, because the scope is known. Project delivery is priced per phase, so you commit to the next stage rather than the whole programme. Retained partnerships are priced as agreed monthly capacity. Support and maintenance is priced against defined response expectations.
How you stay in control of it
- We deliver in phases, so you can stop at the end of any one.
- Scope is written down, so “that was not included” conversations do not happen.
- Changes are quoted before they are made, never after.
- There are no open-ended commitments and no automatic renewals you have not agreed.
- You own your data and your code, so you are never locked in by dependency.
What we will tell you
If you do not need what you have asked for, we will say so. If an off-the-shelf product would do the job for a fraction of what a custom build costs, we will name it. If your budget is not realistic for what you are describing, we will tell you that too, before you spend anything, not after.
Cost questions
Can you give me a figure over the phone?
Usually a range, yes. A precise figure needs enough detail to be meaningful, and we would rather give you a considered number than a fast one you cannot rely on.
Do you charge for the first conversation?
No. The first conversation carries no charge and no obligation. If it turns into discovery work, that is quoted separately and agreed in writing first.
What if the project goes over budget?
Changes are quoted before they are made. If something we missed causes an overrun, that is our problem, not yours. If you change what you want, we will quote it and you decide.
Is there an ongoing cost after launch?
Usually, yes: hosting, maintenance and support. We will tell you what that is before you commit, not afterwards.
Are you cheaper than a larger firm?
Generally yes, and generally more expensive than a single freelancer. What you are paying for is documentation, testing, process and someone still being here in a year.
What is the smallest project you will take?
There is no formal minimum. What matters is whether we are genuinely the right people for it. If we are not, we will tell you.
Tell us what you are trying to do.
We will tell you roughly what it costs, and whether we are the right people to do it.
No charge, no obligation.