Quick answer
A scoped engagement is a fixed piece of work with a written scope, a fixed price and a clear definition of done. Before any work starts, you know what will be built, who does it, when it will be finished and what it costs. It’s done when the outcome is running and your team knows how to keep it that way. If someone won’t give you both the scope and the price before they start, keep looking.
What a scoped engagement is
A fixed piece of work, with the scope, the price and what done means agreed in writing first.
Most outside help is sold by the hour or by the month, with a loose description of the work. You find out what it cost when the invoices arrive, and what you got when it ends. A scoped engagement flips that: the outcome, the timeline and the price are written down and agreed before anyone starts.
That makes it easier to decide, easier to manage, and easier to judge at the end. Either the outcome in the scope is running, or it isn’t.
What’s in the scope
What gets built, what done looks like, who does it, when, and the price.
What will be built.
The process, the system or the handoff, described plainly.
What done looks like.
How you’ll both know it’s finished: running, owned, and used by your team.
Who does the work.
The people on both sides, and what’s needed from your team.
The timeline.
When it starts, the first deliverable, and when it’s done.
The price.
Fixed, before any work starts.
What’s left out
Open-ended advice, management with no defined outcome, and anything not written down.
Open-ended advice.
Calls and recommendations with no deliverable at the end.
Ongoing management without a defined outcome.
Work that could run forever.
Work that hasn’t been written down.
If it isn’t in the scope, it isn’t part of the engagement.
Anything that needs you in every meeting.
The point is to take work off your plate, not add to it.
If something new comes up along the way, it gets its own small scope and price, agreed before it starts. Nothing is added quietly.
How it runs, from first call to handoff
You describe what’s stuck. The scope and price come back in writing. You approve it. It gets built. It’s handed over running.
Describe what’s stuck.
A few lines or a short call: what isn’t working and what you want instead.
Get the scope and the price.
In writing: what will be built, by when, by whom, and the fixed fee. Including whether it’s the right fit at all.
Approve it.
Or ask for changes. Nothing starts until you’ve agreed.
The work gets built.
In your tools, with your team, with plain updates on what moved and what’s blocked.
Handoff.
It’s done when the outcome is running and your team knows how to keep it that way, with the process written down.
Scoped vs hourly
With a fixed scope, you know the cost and the outcome before you start.
A fixed price also makes it simple to decide whether a project is worth paying for: you’re comparing a known cost with what being stuck costs you.
The Blueprint
A paid, two-week look at how your business actually runs. We find where AI and better systems take work off your plate first. You get a written plan, plus a build scope and a fixed quote. If you go ahead with the build, the Blueprint fee is credited toward it.
- About two weeks
- Written plan you keep
- Build scope and fixed quote
- Fee credited toward the build
How to read a proposal
Check for the five parts, then ask the questions that aren’t on the page.
Are all five parts there?
What’s built, what done looks like, who, when, and a fixed price.
Is done specific?
“Improve operations” isn’t done. “Order intake written, owned and running in four weeks” is.
What’s needed from your team?
Hours, access and decisions, so there are no surprises.
What happens if it slips?
Who tells whom, and how it’s handled.
What’s running when they leave?
And who on your team owns it.
For how to choose between different kinds of help, see consultant vs agency vs hire and how to find a fractional COO.
What a Scoped Engagement Looks Like
A written scope, a fixed price and a clear definition of done. One page, ready to print or share with your team.
Your guide is ready.
We also emailed you a link to your library, so you can come back to it from any device.
That didn't go through. Please try again, or email hello@lockhold.com.
FAQ
What is a scoped engagement?
A fixed piece of work with a written scope, a fixed price and a clear definition of done, all agreed before any work starts. You know what will be built, when it will be finished and what it costs.
What should a project scope include?
What will be built, what done looks like, who does the work, the timeline, and the price. Anything not written in the scope isn’t part of the engagement.
Is a fixed price better than hourly billing?
For a defined outcome, usually yes. A fixed price lets you compare the cost to the problem before you start, and it puts the focus on finishing the work rather than on hours.
What happens if the work changes partway through?
New work gets its own small scope and price, agreed before it starts. The original scope stays as agreed.
Want it built and running?
Write down the one thing that’s stuck. Ask for a written scope and a fixed price to fix it. If you don’t get both before work starts, keep looking.
How we work explains our version: tell us what’s stuck, and we’ll tell you what it would take, what it would cost, and whether we’re the right fit.
Related guides and work
How to tell if a project is worth paying for
What being stuck costs, how to compare it to a fixed price, and what makes yes easy.
Read the guide Guide
Consultant vs agency vs hire vs execution partner
What each one does, which stage each fits, what to ask before you sign, and the red flags.
Read the guide Page
How we work
A written scope at a fixed price, then we build it and run it until it’s done.
Read →