Status. Proposed design only. Nothing in this vault is DG client approval. No application, service or test has been executed; every scenario is Not executed. Fees and dates are open.
Delivery options — Optimized, Balanced (recommended), Comprehensive
DG-facing document; fees and dates open. Original: HTML.
| Optimized | Balanced | Comprehensive | |
|---|---|---|---|
| Purpose | Prove the core journey | Run it the way busy teams work: approvals, email alerts, daily tracking | Full proposed Release 1 |
| Fee | To be confirmed | To be confirmed | To be confirmed |
| Schedule | To be confirmed after staffing, scope and DG dependencies are agreed | same | same |
Lower price means less scope, not weaker security: access control, confidentiality and recovery requirements are the same in every option.
Proposed payment milestones (all options, percentages are a proposal): 40% booking; 40% when the agreed staging build is ready for DG testing (tests pass, no blocking defects); 20% at acceptance after the agreed review period with written reasons for any rejected item. Production launch is a separate written approval. Review rounds are bounded, but fixing and re-testing against the signed baseline is not a change request. Enhancements and ongoing support are priced separately.
Before agreement: option selected; budget and payer; D01–D06 and D08–D10 as they affect the option; named acceptance reviewer, launch approver and review turnaround; hosting region, identity, retention, processors, support-access policy; representative sanitised examples; IP position; support, warranty and defect-correction window; whether deemed acceptance is acceptable (needs legal review); whether any staff work across several companies (would force a Balanced re-scope).
See Scope-Balanced-Manual-Additional, Tier-Differences, Acceptance-Gates-A01-A11.