A practical guide for investors, funders and venture teams

How to scope technical assistance that gets implemented

A useful technical-assistance brief connects a business priority to work the team can adopt. Start with the change you want to enable, then agree the people, resources, decisions and evidence needed to put it into practice.

By Kuza Collective Published

Read online or download. The Word brief is editable. No email required.

01Priority

Name the business change.

02Work

Scope outputs and responsibilities.

03Adoption

Check how the team uses the work.

04Progress

Review evidence and decide what follows.

Technical assistance can take many forms: commercial analysis, financial planning, operating improvements, technology, specialist advice or management support. A report, workshop or new dashboard may be useful. The commissioning question is what the business will do differently because of it.

Use this guide before appointing a specialist, approving a delivery budget or extending an existing assignment. Work through it with venture leadership and the person commissioning the support. For a small assignment, a short shared brief may be enough; a portfolio programme needs an overall delivery framework and a separate scope for each venture.

The approach below is Kuza Collective’s practical commissioning framework. It is designed for discussion and adaptation, rather than a promise that every assignment will produce a particular commercial or impact result.

1. Define the business change

Describe the opportunity or constraint in the business’s own terms. Identify the decision it needs to make, the people affected and why the timing matters. Separate observed facts from assumptions about the cause.

A broad request such as ‘improve financial management’ leaves too much open. A more useful brief might ask for a weekly cash forecasting routine that the finance lead can update and the owner can use before committing to stock purchases.

  • What is happening, and what evidence supports that view?
  • What would the business do differently if the assignment worked?
  • Which single priority matters most now?
  • What can this assignment realistically influence, and what depends on capital, demand or another decision?

2. Check whether the business can use the support

Confirm leadership interest, a practical implementation owner, access to relevant information and time to work with the specialist. A sponsor’s priority and a venture’s priority may differ; resolve that before appointing the team.

When the starting evidence is weak, commission a short diagnostic or data-reconstruction stage. Agree what it must establish and the decision that will follow. If a missing approval, unavailable manager or essential capital item blocks implementation, make that dependency explicit.

  • Name the venture decision-maker and the person who will use each output.
  • Agree access to records, staff, customers or systems, with appropriate permissions.
  • Reserve time for testing, decisions and handover; record who supplies it.
  • State the conditions that must be met before delivery starts.

3. Specify work outputs and how they will be used

Define the deliverables, activities and boundaries together. An output should have a named user, an intended use and a completion check. ‘Build a dashboard’ becomes more useful when it specifies the decision, data inputs, refresh routine and person maintaining it.

Record what is outside the assignment and how a proposed extension will be assessed. For equipment, software or regulated specialist work, specify the relevant technical requirements and who is qualified to approve them.

  • Output: what will exist at the end?
  • Use: who will apply it, and in which routine or decision?
  • Acceptance: what test or evidence shows it is fit for the agreed purpose?
  • Boundary: what remains the responsibility of the business, sponsor or another provider?

4. Make responsibility and decisions clear

A sponsor may commission and pay for support while the venture owns the operational change. Name both roles. Give the engagement lead responsibility for coordinating specialist contributions, progress and unresolved issues.

Agree who approves scope, accepts deliverables, supplies information and makes operating decisions. Set an escalation route and a decision turnaround that fits the business. Confirm how commercial information can be shared with the sponsor; access to support does not automatically mean unrestricted access to company records.

  • Sponsor: authorises resources and agrees the reporting purpose.
  • Venture lead: owns business decisions and implementation commitments.
  • Engagement lead: coordinates delivery and raises risks or dependencies.
  • Specialists: deliver their agreed contributions and transfer usable knowledge.
  • Output owners: maintain the tools, processes and information after handover.

5. Distinguish delivery, adoption and results

Choose a small set of measures that helps people make decisions. Record the definition, starting point, source, owner, review frequency and intended direction. Set targets after checking the baseline and assumptions, rather than inventing a precise improvement figure at commissioning.

Separate what the team delivers from whether it is used and what changes in business performance. Where a sponsor expects social or environmental outcomes, describe the pathway, affected people, risks and evidence needed. Revenue growth or a count of installations alone does not establish wider impact.

  • Delivery: the agreed forecast, process, experiment or system exists and passes its acceptance check.
  • Adoption: the responsible business team uses and maintains it in the agreed routine.
  • Business outcome: a relevant operating, commercial or financial measure changes over a defined period.
  • Wider outcome: customers, workers, suppliers or the environment experience a relevant change, supported by suitable evidence.

A worked measurement example

A cash-forecasting assignment might use the three measures below. Agree baselines and targets with the business; these are measure definitions, not claimed results.

Delivery

Cash forecast passes the agreed test

Agreed input reconciliation, visible assumptions and working scenarios are checked by the nominated reviewer.

Evidence
Forecast file and acceptance record
Owner
Engagement lead / finance lead
Review
At the delivery milestone

Adoption

Finance team maintains the routine

Updates are completed and reviewed on the agreed schedule; record missed cycles and reasons.

Evidence
Update log and management review notes
Owner
Venture finance lead
Review
Weekly during the agreed review period

Business outcome

Unplanned cash shortfalls

Agree what counts as a shortfall, the review period and relevant context before comparison. Baseline may need reconstruction.

Evidence
Cash records and forecast variance review
Owner
Venture finance lead
Review
At agreed review points

6. Resource the whole assignment

Budget for the work required to make the change usable: specialist and engagement-lead time, venture staff time, data preparation, testing, travel, tools, implementation costs and post-handover review. Specify the currency, applicable taxes, reimbursables, payment milestones and who pays for each item.

Discuss the potential business value and its assumptions. Consider costs, benefits, downside scenarios and the time over which value might emerge. Keep forecasts separate from realised results. A useful assignment may also improve a decision or avoid an unsuitable expansion; it does not always justify a neat short-term return calculation.

  • Identify missing resources and the party responsible for providing them.
  • Include approvals, procurement lead times and system access in the schedule.
  • Agree a change process for added work, costs or dependencies.
  • Confirm who owns and can use the work products and underlying information.

7. Use milestones to decide what happens next

Build a delivery sequence around evidence and decisions. Each milestone should identify an output or test, a reviewer and the decision it enables. The sequence below is a starting structure, not a fixed programme duration.

For a portfolio, use consistent reporting categories while allowing venture-specific objectives and definitions. Do not combine revenue, adoption or impact figures across ventures unless their meanings, periods and collection methods are comparable.

  • Start: confirm scope, baseline plan, owners, access and resources.
  • Diagnose: validate the priority and decide whether to proceed or revise the scope.
  • Build and test: try the proposed tools or changes in a bounded setting.
  • Review: compare evidence with acceptance criteria and resolve gaps.
  • Handover: confirm the operating owner, documentation and maintenance needs.
  • Follow through: review continued use and decide whether to close, adapt or extend.

Illustrative assignments

The same discipline. Different work.

These examples describe possible assignments. They are not completed Kuza Collective engagements or promised results.

ManufacturingUnderstand margin before adding volume

Starting point: A production business has orders but limited visibility of product-level costs and delivery performance.

Work: Validate the costing inputs for a selected product group, test pricing or order-acceptance rules, and establish a weekly production and fulfilment review.

Outputs: Costing model, tested decision rules and a documented review routine.

Adoption check: The nominated team updates costs and uses the rules in actual order decisions.

Results to review: Track a consistently defined product margin and on-time delivery measure. Set the baseline and feasible targets with the business.

Dependencies: Reliable cost inputs, production access and authority to test the agreed decisions.

Clean energyMake commercial rollout assumptions testable

Starting point: An energy venture wants to expand a channel or customer segment and needs clearer evidence of the economics and delivery requirements.

Work: Review a defined segment, build a scenario model and test a bounded sales-to-service process with the commercial and operating teams.

Outputs: Segment assumptions, decision-ready scenarios and a pilot operating plan.

Adoption check: The team records pilot evidence and uses agreed decision thresholds before wider rollout.

Results to review: Review contribution economics, conversion and service performance using agreed definitions; assess any customer or environmental claims separately.

Dependencies: Customer access, suitable commercial data and relevant technical approval for any system-related change.

DistributionImprove replenishment in a bounded pilot

Starting point: A distributor wants to understand why stock availability and delivery reliability vary across outlets.

Work: Examine one route or outlet group, test a replenishment routine and clarify the information and responsibilities needed to maintain it.

Outputs: Pilot replenishment rules, stock/delivery records and an operating review.

Adoption check: The responsible staff maintain records and use the rules during the pilot.

Results to review: Review stockout frequency, fulfilment and cost-to-serve with consistent units and periods.

Dependencies: Stock records, route access, working-capital decisions and time from the operating team.

Turn the conversation into a shared brief.

Complete these twelve prompts with venture leadership and the commissioning sponsor. Keep unknowns visible. Add detailed technical specifications where the work requires them.

  1. Business and commissioning context

    Name the venture, sponsor or payer, business stage, assignment purpose and review date.

  2. Priority and intended change

    What decision or action should the business be able to take? Why does it matter now?

  3. Evidence and starting point

    What is known, what is assumed, and what information or baseline must be established?

  4. Scope and boundaries

    List the workstreams, included activities, exclusions and dependencies. Define any required specialist approvals.

  5. Outputs and acceptance

    For each output, name its user, intended use, completion test and approver.

  6. People and decision rights

    Name the sponsor, venture lead, engagement lead, specialists, output owners and escalation route.

  7. Venture participation and access

    Confirm staff time, data/system access, permissions and other start conditions.

  8. Measures and learning

    Define delivery, adoption and outcome indicators, baseline, sources, owners, review frequency and assumptions.

  9. Milestones and decisions

    Set the delivery sequence, reviewers, acceptance points, decision dates and follow-through review.

  10. Budget and payment

    Record fees, currency, taxes, tools, travel, implementation costs, staff time, payer and payment milestones.

  11. Information, ownership and reporting

    Agree confidentiality, access, use of work products and what may be shared with the sponsor or others.

  12. Change, handover and close-out

    Define pause/change triggers, scope approval, maintenance owner, handover requirements and the close/extend decision.

Get the editable brief · Word

Ready to start?

Use this checklist together. An unresolved item should become a decision, dependency or agreed diagnostic task.

Commissioning readiness checklist

0 of 10 items checked.

A discussion aid, not a score or certification. Checkmarks are not submitted or saved and reset when you reload.

Further reading

These sources inform the wider discussion of non-financial support and impact management. The commissioning approach above is Kuza Collective’s practical framework; it does not imply endorsement or certification.

From a useful brief to practical work

What does your venture need to put into practice?

Kuza Collective brings complementary consultants and operators around defined business priorities. Share a concise introduction to the venture or portfolio and the decision you want to move forward.

Discuss a support briefExplore venture and portfolio support