How pricing and value measurement work

Start with the diagnostic

The Workflow Value Diagnostic is paid, fixed-scope work. TightShip quotes a fixed fee after workflow triage, once the evidence boundary, systems, stakeholders and required access are understood. It remains useful when the right decision is to stop.

Implementation is separately scoped and approved.

Ways to price implementation

Fixed fee

Use a fixed fee when outputs and effort can be bounded but business-value attribution is weak, delayed or too expensive to administer.

Hybrid

Use a fixed implementation fee plus shared upside when part of the benefit can be narrowly attributed and Finance-verified.

Outcome unit

Use a price per verified unit when the unit is stable, observable and agreed before work starts.

Shared savings

Use shared savings only for net realised cash or P&L benefit that can be attributed and Finance-verified against the agreed baseline.

The signed schedule defines the percentage or fee, cap, period, costs, exclusions and dispute path. TightShip does not publish one universal percentage because contribution, risk and client effort vary by workflow.

Four benefit states

1. Forecast: modelled with stated assumptions.
2. Validated: the baseline, mechanism, owner and measurement method have passed review.
3. Realised: operating or financial evidence shows the outcome occurred.
4. Finance-verified: Finance has accepted the amount, attribution, costs and classification.

Only Finance-verified value supports a final shared-savings fee.

Measurement terms follow the workflow

Capacity, cash reduction, cost avoidance, working capital, risk and revenue are different benefit classes. TightShip does not relabel one as another to improve a business case.

The follow-up proposal and measurement schedule define the workflow boundary, baseline, evidence, costs, counterfactual, attribution, exclusions, measurement dates and sign-off authority. That detail is agreed for the specific engagement rather than presented as a universal website formula.

Data handling

Access is least privilege and limited to the agreed workflow. TightShip discloses providers and data locations where client data is processed. Retention and deletion are agreed before access. Client data is not used to train public models.

A proposal states the actual architecture and controls. TightShip does not promise a residency or isolation pattern that the delivery design does not provide.