A client asks whether you can “sort out onboarding in a day”. You can probably make progress in a day. What you cannot responsibly promise is to repair every process, change every system and train every colleague before the calendar slot ends.
For your Birmingham consultancy, define a narrower intensive: inspect one client handover, agree the main failure points and produce a practical operating plan. The buyer should know what they will receive, what they must provide and which work remains outside the engagement.
Gbeya’s service structure can hold the audience, outcomes, duration and price of an offer. The substantive work is deciding what those fields mean. A well-written service page is useful, but the scope, client agreement and acceptance process still need to be operated deliberately.
Is this intensive genuinely bounded?
Review the offer before making it bookable.
- What specific decision will the client be better able to make?
- Which evidence and people are required before the session?
- What exact outputs will be delivered and reviewed?
- How much preparation and follow-through does the price include?
- What happens to new requests and unresolved questions?
Narrow the offer or use discovery when a critical answer remains undefined.
This is a scoping method, not a contract template, legal advice or promise of commercial results.
Step 1
Inputs
Agree the records, people and preparation needed to begin.
Step 2
Investigation
Inspect the defined operational problem within the agreed time and scope.
Step 3
Map and action plan
Deliver the specific decision support promised in this example.
Step 4
Acceptance
Review the agreed output and decide the appropriate next step.
In this example, implementation and ongoing supervision sit outside the intensive. If the buyer needs them, scope that next engagement explicitly.
1. Start with the decision the buyer needs to make
Choose one operational question that can be investigated within the available time. For this intensive, it is where responsibility breaks between a signed project and delivery starting. Keep the promise close to evidence you can inspect and a decision the client can use.
Separate your deliverable from the business result the client hopes for. You can commit to a documented handover design and an agreed action plan. You cannot guarantee that the client’s team will implement it correctly or that revenue will rise as a result.
- Why this matters
- A decision-shaped offer creates a useful boundary. It prevents a time-limited session from being sold as an undefined transformation.
- Work through the example
- Suppose the client receives a current-state handover map, a recommended ownership rule and a thirty-day implementation sequence. The offer does not include rebuilding their software or supervising every future project.
- When the approach changes
- If the real problem is still unknown, a discovery engagement may be more honest than a fixed intensive promising a predetermined answer.
- Your decision
- Sell the intensive when the question is sufficiently bounded and the evidence can be made available. Use discovery when that boundary is not yet clear.
2. Make the client’s preparation part of the scope
List the minimum inputs needed to do the work: a recent handover example, the relevant role holders and permission to inspect the necessary records. Ask for the smallest useful sample and avoid collecting unrelated confidential material.
Set a preparation deadline and a rule for missing inputs. Decide whether the session proceeds with a narrower scope, moves to another date or becomes an evidence-gathering discussion. Explain that rule before the client pays, not after you discover that the person with the answers cannot attend.
- Why this matters
- The quality of a focused engagement depends on its inputs. Making dependencies explicit protects both sides from treating missing evidence as a failure of effort.
- Work through the example
- For this proposed handover intensive, request three redacted examples and attendance from the person who sells and the person who accepts delivery. If only one perspective is available, mark the unverified part of the map.
- When the approach changes
- A confidential environment may prevent sharing documents in advance. Agree a supervised review or anonymised example rather than demanding unnecessary copies.
- Your decision
- Accept the booking only with a workable evidence plan and an agreed response to missing preparation.
3. Describe the outputs and how they will be accepted
Name each output in language the buyer can inspect. “A handover map showing the trigger, required information, accepting owner and exception route” is more testable than “strategic clarity”. Agree who reviews it and what counts as a correction within scope.
Include a short walkthrough or explanation so the client can use the work. Public-sector commissioning guidance and an industry response both emphasise clear deliverables and knowledge transfer; apply that principle proportionately rather than importing an elaborate procurement process into a small engagement.
- Why this matters
- Acceptance criteria turn a deliverable into something both parties can evaluate. Knowledge transfer makes it usable after you leave rather than leaving the client with an attractive file they cannot apply.
- Work through the example
- Suppose the client accepts the map when the named role holders can follow one real project through it and identify what happens when information is missing. One correction round addresses inaccuracies in that agreed map.
- When the approach changes
- Acceptance is not a promise that every stakeholder will agree with every recommendation. Distinguish factual correction, an agreed revision and a new request.
- Your decision
- Define the output, review owner and correction boundary before delivery. Keep the acceptance record separate from proof of later business impact.
4. Price preparation, delivery and follow-through
The visible session is only part of the work. Include preparation, analysis, the live intensive, documentation, the walkthrough and the agreed correction window. Record which costs are internal planning assumptions and which are actual cash expenses.
A fixed price can make a bounded offer easier to understand, but it does not make the work unlimited. State the scope and any separately agreed additional work. If a client asks for implementation during the session, pause to define the change rather than silently expanding the original promise.
- Why this matters
- Pricing the complete job exposes an intensive that looks attractive on the calendar but consumes several unplanned days. A clear change boundary preserves the original agreement.
- Work through the example
- For this proposed intensive, budget two hours of preparation, four hours together, two hours documenting and one hour reviewing. That is nine hours of work before sales, administration or any extra support.
- When the approach changes
- An urgent or unusual case may need a different commercial arrangement. Do not force every engagement into the same package because the service form supports a fixed price.
- Your decision
- Choose a price and scope you can explain together. Revisit the model with actual effort after delivery, without inventing a return-on-investment claim.
5. Finish with ownership and a separate next decision
Close the intensive by identifying the first action, its owner and the evidence that will show it happened. The client should be able to start without needing to buy another engagement simply to interpret your recommendation.
If implementation support would help, offer it as a separate decision with its own scope. Keep unresolved questions visible. A useful intensive can conclude that more evidence is needed; it should not manufacture certainty to make the delivery feel complete.
- Why this matters
- A practical handover preserves the value of the work while avoiding dependency disguised as follow-up. It also gives a later review a concrete starting point.
- Work through the example
- Suppose the client agrees to trial the new handover on the next three projects, record missing information and review the result after thirty days. That is a proposed test, not a claim that the new process already works.
- When the approach changes
- A high-risk change may require specialist approval before a trial. The correct next step can be review rather than immediate implementation.
- Your decision
- Close when the agreed outputs are accepted and the next action is understood. Measure implementation and outcomes later as separate evidence.
A short engagement needs a particularly clear boundary
The intensive works as an offer when the buyer can understand the question, inputs, outputs and finish line. That design is supported by commissioning principles, but its usefulness for this client still depends on the actual evidence and delivery.
Gbeya can present the service and support its operational context. It does not turn an ambiguous promise into an accepted scope automatically. Keep the agreement, delivered work and later business effect distinct.
Medium for the proposed method; no intensive delivery or buyer-demand experiment conducted.
Public-sector guidance is applied proportionately to this proposed small-consultancy engagement. No legal contract validation or revenue effect claimed.
Calculation with stated assumptions
Price the nine-hour job, not only the four-hour session
Assume a £1,500 intensive, nine hours of planned work valued internally at £80 an hour and £100 of other direct costs. These are planning assumptions, not market prices or Gbeya fees.
9 × £80 = £720 of planned effort. £1,500 − £720 − £100 = £680 before tax, acquisition, administration and omitted costs. Four additional unplanned hours reduce that figure by £320 to £360.
The calculation is not profit or proof the client will buy. Internal time value is not necessarily cash expenditure.
Use the example to test scope sensitivity, then replace assumptions with actual effort and costs.
Assumptions worth checking
An intensive sells a number of hours.
Time bounds the engagement; the useful decision and deliverables explain the offer.
A confident consultant can work without preparation.
Expertise cannot replace missing client evidence or decision-makers.
Fixed price means unlimited revisions.
Define the correction window and change process.
An accepted report proves business improvement.
Acceptance, implementation and impact are separate observations.
The next engagement should be necessary to use the first.
The intensive should provide a usable outcome within its agreed scope.
Your next 30 days
Days 1–7
Define the bounded decision
Write the audience, problem, exclusions and useful outputs.
Ready for the next step: One inspectable offer rather than a broad transformation claim.
Days 8–14
Prepare the delivery method
Create the input request, session structure and output acceptance checklist.
Ready for the next step: A realistic evidence and review plan.
Days 15–21
Rehearse the complete job
Use a clearly fictional case to test timing, documentation and scope changes.
Ready for the next step: A revised effort model and no invented client result.
Days 22–30
Publish the accepted offer
Verify the listing, booking, payment and delivery handover, then track actual effort.
Ready for the next step: A dated offer record and specific improvements from real delivery.
Questions before you proceed
How long should an intensive be?
Long enough for the bounded decision and its preparation, not a universal number of hours. Include the work around the live session.
Can I guarantee an outcome?
Commit to deliverables and processes you control. Do not guarantee implementation or financial results you cannot substantiate.
What if the client brings a new problem?
Record it and agree whether it replaces, narrows or adds to the scope. Do not silently expand the engagement.
Should I charge a fixed price?
A fixed price can fit a well-bounded offer. Model the whole job and clarify what changes require a separate agreement.
Does Gbeya automatically approve milestones?
Do not assume a service listing approves milestones. Define who reviews each output and verify the acceptance process separately before relying on an automated approval.
What should happen after delivery?
The client should have accepted outputs and a clear owned next action. Further implementation support is a separate choice.
Sources and further reading
Prepared by Gbeya · Sources reviewed 30 October 2026.