Most companies buying engineering help for the first time default to hourly or monthly billing. It feels flexible and familiar. You can start quickly, change direction freely, and stop whenever you like. For genuinely open-ended work, that flexibility has real value.
But a great deal of engineering work is not open-ended. A marketing site with a booking flow. An integration between a storefront and an ERP. A security assessment of a defined application. A cloud cost review. A retrieval chatbot pilot on one set of documents. These are bounded problems with recognisable outcomes, and for bounded problems, the hourly meter is usually the wrong instrument.
Who carries the risk?
Under hourly billing, every surprise is paid for by the buyer. If an estimate was optimistic, if a task took longer than expected, if the team spent a week on a detour, the invoice simply grows. The vendor has no financial reason to be efficient, and occasionally a quiet reason not to be.
A fixed scope at a fixed price moves that risk to the party best placed to manage it: the people doing the work. They know how long things take, where the traps are and how to avoid them. If they underestimate, they absorb the cost. That changes behaviour in useful ways. Scope gets examined more carefully up front, reusable patterns get used, and nobody is rewarded for going slowly.
When you pay for hours, you are buying effort. When you pay for a defined outcome, you are buying the result you actually wanted.
Fixed scope forces better thinking
The real benefit of fixed-scope work often shows up before a single line of code is written. To price something, you have to define it. That discipline forces questions that hourly engagements tend to postpone:
- What exactly is included, and what is explicitly not?
- What does "done" mean, in terms both sides can check?
- Which inputs, such as content, access or decisions, does the buyer need to provide, and by when?
- What happens if requirements change halfway through?
Answering these is uncomfortable, but it is far cheaper to have the conversation at the start than to discover the disagreement in week six.
What a good fixed-scope engagement looks like
Fixed price is not the same as vague price. A well-run engagement typically includes:
- A written scope listing deliverables, assumptions and exclusions in plain language.
- Acceptance criteria that describe how each deliverable will be checked.
- Milestones with visible progress, such as working software in a staging environment rather than status reports.
- A change process that treats new requests as new, separately agreed work rather than silent scope creep.
- A handover covering code, credentials, documentation and a walkthrough for your team.
The change process deserves emphasis. Requirements will evolve; that is normal. The difference is that under a fixed scope, changes are visible and deliberate. You decide whether a new idea is worth its cost now, or whether it waits for the next phase.
When hourly still makes sense
Fixed scope is not a universal answer. It fits poorly when the problem itself is unknown, such as early product discovery, research spikes or debugging an unfamiliar system with no clear boundary. It also fits poorly for ongoing capacity, where you need a team embedded for months and priorities shift weekly.
A practical approach is to split the work. Use a short, time-boxed discovery or advisory phase to turn an unclear problem into a defined one, then run the build as a fixed-scope engagement. For the ongoing care of a live system, a managed support plan with a clear service level often suits better than either.
How to tell if your project is ready
A quick test: can you describe the finished result in a paragraph, list who will use it, and name the systems it needs to connect to? If so, your project is probably ready to be scoped and priced. If not, an hour with an experienced engineer or architect will usually get you there faster than a long exploratory contract.
That is the model Notepoint is built around: clearly scoped, fixed-price engagements you can buy online, and short paid advisory sessions for when the problem still needs shaping before it can be priced.
