Discovery Deck

The sponsor-facing narrative for the first Provenance Ops conversation.

This route replaces the deck-only artifact with a repo-native presentation page that can be shared, revised, and deployed through the same release path as the rest of the site.

Problem

01

Post-close operations usually fail in the seams

Documentation describes the business you bought, not the business you inherited.
Important workflows often run on memory, side channels, and undocumented approval steps.
Owners inherit software systems without inheriting a usable method for operating them.

Offer

02

A fixed-scope transition sprint

30-day engagement designed to establish the first owner-readable operating system.
Outputs include workflow documentation, weekly reporting structure, and one deployed workflow fix.
Structured as a defined deliverable rather than open-ended consulting.

Delivery

03

How the work gets done

Senior operators own scope, judgment, and final deliverables.
Structured capture workflows and systematic documentation accelerate delivery.
Targeted tooling is applied where it improves control, speed, or documentation quality.

Outcome

04

What the owner gets

A documented map of workflows, dependencies, approvals, and failure points.
A weekly operator brief that shows what changed, what is stuck, and what to ask next.
A clear roadmap for the next 90 days after the sprint closes.

Related Route

Need the compact shareable version instead of the deck flow?

Open One-Page Overview