How we define the work.
A brief, a project margin, and capability coverage: what each means, how it is computed, and where the numbers come from. No customer data in any aggregate.
Method, sample, date
- Method
- Definitions from the product-content schema and the fixture tenant Meridian & Co.; arithmetic from Flow*form margin cards and Skill*form roster.
- Sample
- Meridian & Co., 24 people across 8 disciplines, 3 clients, 6 projects, week 19 to 32 campaign series. No live customer data aggregated.
- Date
- Published 2026-08-30. Updated when the schema changes.
A brief
Five fields: objective, audience, constraint, deliverables, and source. Spark*form extracts them from a call or notes, flags the vague field, and holds the brief until every field has a check. The checked brief is the artefact, not an email about it.
A project margin
Fee minus burned hours at the blended rate, divided by fee. Flow*form recomputes from fee, committed hours, and blended rate; the card shows the result per project, and Pulse carries a flag in the morning digest when it crosses below zero, where you already look.
Capability coverage
Four capabilities: strategy, craft, analytics, delivery, mapped from the roster in Skill*form at each seniority. Coverage shows which team can field the work and which gap calls for a hire or for training, not a new title.
What this does not claim
No benchmark, no aggregate telemetry, no per-client shape. Customer data is never aggregated for a public figure; until volume makes an aggregate non-identifying and a stated consent basis exists, the only honest sample is the fixture tenant above. A number that drifts between pages is worse than a smaller one that holds.