Statement of Work (sample)
PDFWhat our SOWs look like before signature. Fixed scope, fixed price, fixed deposit, fixed deliverables. 8-12 pages, anonymized from a real mid-market healthcare engagement.
Anonymized samples · Real artifacts
Every engagement produces concrete artifacts you can show to your CISO, your board, or an auditor. Here are the real templates and samples — anonymized but otherwise unchanged from production engagements.

What our SOWs look like before signature. Fixed scope, fixed price, fixed deposit, fixed deliverables. 8-12 pages, anonymized from a real mid-market healthcare engagement.
Format we use for every architectural decision: context, options considered, decision, consequences, references. Versioned in Git alongside the code.
How we structure eval suites: input fixtures, expected outputs, scoring rubric, gating thresholds, regression detection, CI integration.
Every model inference logged with: input context fingerprint, retrieval bundle hash, model version, prompt hash, output, downstream action, reviewer disposition. WORM-compatible.
How the reviewer queue operates day-to-day: SLAs, escalation paths, calibration cadence, threshold tuning, drift detection. Used by every production deployment.
The 25-page Discovery output: workflow map, KPI baseline, system access requirements, risk register, architecture recommendation, Build SOW.
The artifact quality is the product. If you can read our SOW template and our audit log schema, you already know whether we're the right partner — without needing a sales call. We'd rather lose a prospect because the deliverables don't match what they need than waste anyone's time.
Ready to receive these on your project?
Every package above $15k produces these artifacts as part of the engagement. The configurator scopes your project in 4 minutes.