tioga.ai — sample artifact
5-Day Discovery Sprint — Scope Document
What you get for the $5,000 flat discovery sprint, before any larger engagement — credited toward the project price if you move forward.
SAMPLE — illustrative structure and content. Client name, systems, and figures below are fictional; this is not a real engagement record.
01 — Engagement summary
| Client | Meridian Steel Supply (illustrative) |
|---|
| Systems in scope | Oracle EBS R12.2 (Purchasing, Payables) |
|---|
| Target workflow | Accounts Payable three-way-match exception handling |
|---|
| Duration | 5 business days |
|---|
| Price | $5,000 flat — credited toward the project price |
|---|
02 — What we do each day
- Day 1 — Discovery. Shadow the current AP exception process, interview the buyer/AP team, pull a sample of real exception volume and type from the last 90 days.
- Day 2 — Scope the write path. Identify the one sanctioned application-logic write path (not a database shortcut) an agent would execute through, and the approval/escalation policy that already governs it today.
- Day 3 — Build a working prototype. A governed agent that reads an exception, proposes a resolution, and routes it through policy — against a scoped, synthetic dataset shaped like the real one.
- Day 4 — Governance mapping. Map every decision point in the prototype to NIST AI RMF (or your applicable framework) so the evidence trail is audit-legible from day one, not bolted on after.
- Day 5 — Readout. Live walkthrough of the working prototype, a written ROI estimate (hours reclaimed, error-rate impact), and a production build plan with price and timeline.
03 — What you leave with
| 1 | A working prototype against your actual workflow shape, not a slideware demo |
| 2 | An ROI estimate with the assumptions shown, not just a headline number |
| 3 | A production build plan — price, timeline, and what's explicitly out of scope |
| 4 | A governance-mapping worksheet for the one write path assessed |
04 — What this sprint does not include
- Production deployment or a live connection to your real systems
- A multi-workflow rollout plan (scoped to the one workflow assessed)
- Security/compliance sign-off — that's a deliverable of the production build, not the sprint