Skip to content

Reference Workflows & Executable Demonstrations

Explore executable demonstrations across all three workflow families. Project Alder is the deepest native-Word reference workflow; the Investment Research and Wealth Communication examples demonstrate shared evidence maps and review rails using illustrative data.

Executable public exampleIllustrative data — not client workDraft for human review
Three Workflow Families

Reference Deliverables & Downloads

Select an action below to view browser previews or download genuine sample Office files.

Investment Research & Monitoring

Post-Earnings Research Review

Format: Native Word (.docx) & Excel (.xlsx) model verification

Illustrative data — not client workDraft for human review

Browser preview of the generated Word/Excel deliverable.

Transactions & Diligence

Project Alder Investment Committee Memo

Format: Native Word (.docx)

Illustrative data — not client workDraft for human review

Browser preview of the generated Word deliverable.

Portfolio & Client Communication

Portfolio Review Pack

Format: Native Excel (.xlsx)

Illustrative data — not client workDraft for human review

Browser preview of the generated Excel review pack.

What a workflow sprint includes

A typical engagement lasts approximately 4–6 weeks and includes a focused 10-working-day build sprint. Discovery, data access, review cycles, training, and handover make the complete engagement approximately 4–6 weeks.

Concrete Scope & Deliverables
Discover → Map

Understand the last real deliverable, then document templates, approved sources, data boundaries, and reviewer expectations.

Build → Verify

Native Word (.docx), Excel (.xlsx), or PowerPoint (.pptx) where scoped — plus an inspectable evidence report and reviewer checklist.

Train → Handover

User onboarding session, operating runbook, acceptance tests, and full workflow ownership.

Interactive 6-Stage Engagement Map

Discover → Map → Build → Verify → Train → Handover

Click any stage below to inspect its inputs, process, and deliverables:

Stage 01Engagement circuit

Discover

Phase 01 of 06

We learn how the deliverable is prepared today, who signs it, what sources are used, and where review loops break down.

Stage Outputs & Artifacts
  • Last real deliverable
  • Preparer & reviewer roles
  • Pain, timing, and constraints
Architectural Safeguard

The engagement starts by understanding the last real occurrence of the workflow — not a generic AI pitch.

Inspectable Evidence Maps & Deliverables

Select a workflow demonstration below to inspect its source location, material claims, unresolved items, and reviewer checklist.

Project Alder — Investment Committee Memo

Native Word deliverable (.docx)

Illustrative data — not client workDraft for human review
Executive summary

Project Alder is a profitable vertical software business with recurring revenue, a concentrated customer base, and clear cross-sell potential. The first-pass case is credible but depends on retention assumptions and margin progression that require diligence.

Material claims & figures
Metric / ClaimValueSource LocationStatus
Revenue$48.2 millionModel_v12.xlsx · RevenueBuild!C8Sourced
EBITDA margin22.4%Model_v12.xlsx · P&L!D12Derived
Revenue growth17.8% YoY10Q_Q2_2025.pdf · Page 14Sourced
Unresolved items & open questions
  1. Customer-by-customer retention detail
  2. Sales pipeline by stage
  3. Working capital seasonality
Reviewer checklist
  • Confirm revenue ties to model.
  • Validate retention assumption.
  • Separate facts from interpretation.
Sources & Lineage Map
  • Model_v12.xlsxRevenueBuild tab
  • 10Q_Q2_2025.pdfPage 14, ¶3
  • Q2_Call_Transcript.txtPage 7 (Review)

Illustrative Provenance Record

Example Run Record

Digest Matched
RUN_ID: #QVR-2026-0729-01Provenance Log

// Cell Lineage & Input Verifications

Model_v12.xlsxRevenueBuild!C8
$48.2m [Matched]
10Q_Q2_2025.pdfPage 14, ¶3
17.8% YoY [Verified]
Q2_Call_Transcript.txtPage 7 (Q&A)
Top 10 > 40% [Review Needed]
HASH:sha256:8f9b4c2e10a76d3f9b8a7c6e5d4c3b2a10f9e8d7c6b5a4f3e2d1c0b9a8f7e6d5

The digest identifies this displayed run record for lineage tracking. It is an internal snapshot, not an external certification.

Send us the deliverable your team dreads drafting.

We'll map the process, build the first working version, and train your team to run it. The first conversation can use public data only.