Return to Serre.app

Strategic Framework

The Value
Model

The connective layer of causal chains between what your business offers and how buyers actually realize benefit.

Choose the example closest to your platform

The claims, conditions, evidence and calculator below all update with your choice.

Now showing: Legal-tech

From contract workflow to faster, more consistent review.

Illustrative model · Contract lifecycle and review platform

Explore the model↓
Solutions→Claims→Conditions→Mechanics→Drivers→Evidence
SolutionsClaimsMechanics+−DriversEvidenceEnablesLimits

01 — Layer One

Solutions

A contract platform brings requests, clause review, approvals, and obligations into a shared workflow. Its value depends on what happens differently in the buyer's team.

Discrete, directly usable capabilities a user can interact with or invoke.

Contract lifecycle and review platform

Structured contract intakeClause extraction and playbook comparisonApproval routing and review historyObligation reminders

02 — Layers Two + Three

Claims & Conditions

A review feature becomes a value claim only when you can explain whose work changes, under what conditions, and how you will measure it.

Select a claim to explore its conditions

03 — Layer Four

Mechanics

Mechanics answer the “how.” They are the specific causal paths through which a solution produces its claimed outcome — making the model falsifiable and defensible.

Solution

Clause extraction and playbook comparison

via mechanism

Impacts Claim

Reduce hands-on effort on eligible contract reviews

The platform prepares a review queue and identifies departures for a qualified reviewer. It supports, rather than replaces, the reviewer's judgment.

Causal path:Agreement received→Clauses compared with playbook→Exceptions routed to counsel→Routine review effort reduced

Solution

Structured intake and approval routing

via mechanism

Impacts Claim

Reduce avoidable approval handoffs

Routing can reduce internal waiting and rework. It does not establish that external negotiations or total contract cycle time will improve by the same amount.

Causal path:Complete request captured→Approval rules applied→Owner notified→Queue delays tracked

Solution

Obligation tracking

via mechanism

Impacts Claim

Improve visibility into upcoming obligations

Visibility supports follow-through; it is not a guarantee of compliance or avoidance of contractual loss.

Causal path:Commitment captured→Owner and date verified→Reminder delivered→Completion or escalation recorded

04 — Layer Five

Drivers

Drivers quantify claims. They translate assertions into arithmetic — each driver has inputs, a formula, and an output metric that lets the buyer test a measurable outcome in their own context.

Claim being quantified

Reduce hands-on effort on eligible contract reviews

Estimate review capacity released

Contracts reviewed per year

1,200

Hands-on minutes saved per eligible review

30

Share using the workflow and eligible for this saving

70%

1,200 × 30 min × 70% ÷ 60

420hours of review capacity released per year

This is capacity, not automatic payroll savings. Measure hands-on time separately from elapsed cycle time.

Example inputs — replace with buyer data. This estimates the selected benefit, not total ROI.

05 — Layer Six

Evidence

Evidence is what separates a value model from marketing copy. Every claim, driver formula, and input assumption must be traceable to proof.

Examples of evidence to collect

Claim Evidence

→ validates Review-effort claim

  • Before/after hands-on review times for comparable agreement types

  • Pilot records showing adoption, exception rates, and quality checks

Driver Evidence

→ validates Hours-released calculation

  • Reviewed calculation with non-overlapping workflow steps

  • Sensitivity analysis across contract complexity and adoption

Input Evidence

→ validates Contract volume, time saving, and eligible share

  • Buyer intake and contract-volume exports

  • Sampled reviewer time records and eligible-workflow usage logs

The complete picture

One connected model

When all six layers are connected and evidenced, the business can make claims with precision, defend them under scrutiny, and review them when new evidence arrives. Connect the legal-tech feature story to the work buyers actually perform: review capacity, clearer handoffs, and visible obligations — with explicit conditions and proof.

Sign up
Solutions→Claims→Conditions→Mechanics→Drivers→Evidence

For the market

A coherent story of how solutions create and deliver value — not just features, but outcomes.

For buyers

A verifiable chain from "what you buy" to "what you gain" — with conditions and evidence to trust it.

For the business

A diagnostic tool: which claims are under-evidenced, which conditions are risks, where to invest next.