SAMPLE · ILLUSTRATIVE

Sample 14-Day Challenge packet

An anonymized template showing how Day-1 acceptance checks and a Day-14 go/no-go readout look for an FP&A variance / board-narrative workflow. Not a real client case — illustrative only.

Workflow example: Monthly variance commentary → board narrative Buyer: FP&A / Controller (illustrative) Challenge price: $9,500
01 · Day-1 acceptance checklist

Written pass/fail before the build starts.

Locked on Day 1 with the buyer. Every item is observable. Vague outcomes ("faster close") are rewritten into checks the system can demonstrate.

Check Pass condition (SAMPLE) Status
Source inputs available Pulls prior-period actuals + budget from agreed export (CSV/API) without manual re-key for the scoped P&L lines. ☐ Pass / Fail
Variance draft generated Produces first-pass variance commentary for ≥ N agreed cost centers within the scoped close window. ☐ Pass / Fail
Human review path Reviewer can edit, accept, or reject each line before anything is marked final — no silent auto-publish. ☐ Pass / Fail
Board narrative pack Exports a board-ready narrative section (markdown/PDF) using accepted variance notes + agreed template. ☐ Pass / Fail
Ownership & deploy Code in buyer's repo; deploy path documented in buyer's cloud; credentials stay in buyer's accounts. ☐ Pass / Fail
Handover usable Runbook + dependency inventory lets another engineer operate or extend without Strata present. ☐ Pass / Fail

SAMPLE / illustrative. Real Day-1 checks are written with the buyer for their scoped workflow. Numbers, systems, and line items above are placeholders — not from a live engagement.

02 · Day-14 go / no-go readout

A real decision — "no" is allowed.

At day 14 the buyer scores the written checks, confirms ownership, and chooses the next step. Retainer is never assumed.

Go

Continue after proof

All critical Day-1 checks pass (or are waived in writing). Buyer wants Growth capacity on the same system.

  • Acceptance scorecard signed
  • Ownership inventory confirmed
  • Growth scope + 28-day billing discussed

No-go

Stop — keep the work

Checks miss, fit isn't there, or buyer chooses to pause. Repo, data, and deploy stay with the buyer.

  • Handover pack delivered
  • No retainer obligation
  • Everything already shipped remains theirs

Ownership checklist (buyer confirms)

  • Repository is in our org / accounts
  • Cloud deploy path uses our credentials and environment
  • Data stores and any AI processing boundaries are documented
  • Handover runbook + dependency list received
  • Third-party / cloud cost ownership called out separately

Next-step options

1 · Growth retainer

Backlog, maintenance, and planned improvements on the proven system — only if you choose it.

2 · Pause / self-run

Operate with the handover pack. Re-engage later if priorities change.

3 · Scope a second workflow

New paid challenge on a different priority — after this one has a clear go/no-go.

Anonymized template. This page is process proof you can inspect — not a case study, logo wall, or claim about a named client. Real packets are engagement-specific.