Purpose and fit

Use this before a workflow grows beyond a small trial, or when its original cost estimate covers only licences or model usage. Build a view of the resources needed to keep the work useful and supported. The aim is a fundable operating plan with explicit assumptions.

Choose a planning period that matches the decision. Keep cash spending, staff effort and capacity constraints separate so that a promising estimate does not conceal an unstaffed responsibility.

Before you start

Use existing authorised invoices, dated rate cards, workload notes or activity estimates. Include the currency, billing unit and period for each amount you have; anonymise sensitive details. Missing rates or volumes can remain unknown and the worksheet can still map ownership and cost drivers. Do not create sample financial data merely to use this resource.

Expect a provisional cost-and-capacity worksheet with traceable assumptions, not verified totals, a forecast or spending approval. Numerical outputs require independent checking against the inputs; where rates or units are missing, return the formula or unresolved field rather than an invented amount.

Required inputs

  • The workflow scope, expected demand and plausible variations in volume or complexity.
  • Current supplier or internal cost information with dates, billing units and relevant assumptions.
  • Expected setup, review, maintenance, support and fallback activities, including who performs them.
  • Existing tools or costs that would remain, plus plans for changes, replacement or retirement.

Practical workflow

  1. Define the unit of work and planning period. Record which costs fall inside the review and which sit elsewhere. Make shared costs visible without allocating the full amount to every workflow.
  2. List one-time work: design, preparation, integration, testing, training and transition. For each item, identify cash expenditure or staff effort, the estimation source and the responsible owner.
  3. List recurring work: usage, licences, review, exception handling, source updates, access administration and service support. Include the effort needed when the assisted route fails and the team returns to its fallback.
  4. Connect variable costs to explicit drivers. Use a range for demand, review effort or retries where evidence is weak. Show low, expected and high-workload scenarios without presenting any one as a forecast.
  5. Check change and exit obligations: replacing a connected system, updating the workflow, exporting permitted records and retiring duplicate arrangements. Include only costs relevant to this scope and explain exclusions.
  6. Review affordability and ownership with the sponsor. Assign unresolved costs to named investigators, identify capacity bottlenecks and agree a review trigger such as changed pricing, sustained volume growth or increased correction work.

Expected output

A cost-and-capacity worksheet plus an ownership decision:

Planning period and unit: [definition] Activity/cost item: [description] One-time or recurring: [type] Cash or staff effort: [classification] Driver and quantity: [volume/hours/other] Rate and source date: [verified input or unknown] Scenario range: [assumptions] Responsible owner: [role] Funding/capacity confirmed: [yes/no/unresolved] Excluded/shared amount: [treatment] Review trigger: [condition]

Hypothetical example: an internal summary workflow has modest usage charges but requires a reviewer and frequent source maintenance. Its sponsor can see that adoption depends on allocating those roles, even if no additional licence is needed.

Human checks

The budget owner checks units, time periods, duplicated amounts and any monetary conversion. Process owners validate effort assumptions against actual work where possible. Do not equate released time with cash savings or assume that an existing employee has spare capacity. Record the owner’s confirmation separately from an estimate.

Limitations

This worksheet is a planning aid, not a return-on-investment claim. It does not establish benefits or replace the organisation’s budgeting process. Estimates can move with task mix, supplier changes and operational learning; keep ranges and review triggers visible.

Starter prompt

Prepare an ownership-cost review for [workflow] over [planning period] using these sanitised cost, demand and activity notes: [inputs]. The unit of work is [unit]. Use supplied prices and rates only, record their dates and leave missing amounts unresolved.

Separate one-time and recurring work, cash and staff effort, fixed and volume-driven items. Include review, exceptions, maintenance, fallback and exit work where relevant. Create a worksheet with these fields: planning period and unit; activity or cost item; one-time or recurring; cash or staff effort; driver and quantity; rate and source date; scenario range and assumptions; responsible owner; funding or capacity confirmation; excluded or shared amount; review trigger. Identify unowned responsibilities and possible double counting. Do not claim realised savings, approve expenditure or convert time into money without an approved basis.

Adapt the requested fields to the authorised inputs actually supplied. Show the source, formula, quantity, unit, currency and period for any calculated amount. Do not combine currencies without an approved dated conversion basis or add staff hours to cash totals. Separate low, expected and high workload assumptions; identify shared costs, recurring periods and possible double counting. Mark conflicting rates unresolved and require independent arithmetic checks before numerical reliance. State the expected output and acceptance criteria before drafting. Ask for essential missing information; where a useful partial draft is possible, label its limits and assumptions. Do not invent facts, evidence, results or approvals.

Data, model variability and your responsibility

Use relevant data that exists or that you provide, with accuracy and completeness sufficient for the task. Different AI models and versions may produce different results, and responses may vary between runs. You are responsible for checking and validating the output against your own requirements, source information and acceptance criteria before relying on it.