Status. Proposed design only. Nothing in this vault is GGA client approval. The GGA client documents are supplied drafts: see GGA-Source-Digest. No application, service or test has been executed; every scenario is Not executed. Delivery fees and dates are open.
Delivery plan and options history
Sources: Blueprint pp. 19, 20 (GGA-Requirement-Register); 1.3 delivery options kept as history. Fees and dates remain open until the client sets them; this note proposes how to groom the delivery plan, following the same discipline as 1.3.
GGA delivery stages (Blueprint p. 19)
| Stage | Deliverable | Exit condition |
|---|---|---|
| 1 Confirm and design | User flows, screen sketches, field dictionary, access matrix, configuration defaults, chosen stack | GGA approves rules, ownership, budget and pilot scope |
| 2 Foundation and publishing | Authentication, company profiles, public and member projections, partner intake, operations review | An eligible company can discover a reviewed offer; isolation tests pass |
| 3 Complete the service loop | Interest, scoped consent, introduction, profile reminders, events, outcomes, contribution records | A synthetic company completes the end-to-end journey including a payment decline |
| 4 Pilot with 20 companies | Production monitoring, operational training, staffed support, live country-partner sourcing | Real usage shows profiles stay current and operations can follow through |
| 5 Expand towards 100 | Fix demonstrated bottlenecks; improve search and workflow convenience | Service stays affordable; introductions produce reported value; founder time stays within the agreed cap |
The developer obtains a fixed scope, estimate and support arrangement after the launch decisions are recorded (Blueprint p. 19). Judge the pilot by current-profile rate, active owner-confirmed opportunities, accepted introductions, discussions held, company-confirmed value, cash collected, operating cost and Anand’s total time.
Grooming proposals (improvements on the Blueprint, for client review)
- Treat Stage 1 as its own decision gate: record launch decisions GL01 to GL08 (Blueprint p. 20) before any estimate is fixed.
- Split Stage 2 into two milestones: foundation and policy pipeline with the isolation harness first, then publishing; the harness finding from 1.3 (build isolation tests before feature work depends on them) lowers risk for GA01, GA04, GA09.
- Stage 3 builds the introduction and consent engine before profile reminders and finance, because consent release is the highest-risk transaction (GA05, GA06).
- Sequence payment late and keep the gateway optional: manual invoicing and verified bank reconciliation are first-release and the opt-in, finance-approved invoice, settlement and 12-month-term path must pass GA12 before the pilot with 20 companies. A payment-gateway delay does not block the pilot because the gateway is optional (Blueprint pp. 8, 18, 19).
- Make the restore rehearsal and the performance measurement entry criteria for Stage 4 (GA11).
- Tie each stage payment to named gates, not calendar dates.
Proposed payment milestones (kept from 1.3, a proposal only)
40% booking; 40% when the agreed staging build is ready for GGA testing and has 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; fixing and re-testing against the agreed baseline is not a change request. Enhancements and support are priced separately. These percentages are a proposal and carry no commitment.
Before agreement
Stage 1 scope and pilot budget; launch decisions GL01 to GL08 (Blueprint p. 20); named acceptance reviewer, launch approver and review turnaround; hosting region, identity, email, scanning, backup providers and retention; sanitised examples; IP position; support, warranty and defect-correction window; whether deemed acceptance is acceptable (needs legal review); the funded event and partner budget (Blueprint p. 20).
History: the 1.3 options (superseded)
| Optimized | Balanced | Comprehensive | |
|---|---|---|---|
| Purpose | Prove the core journey | Approvals, email alerts, daily tracking | Full proposed Release 1 |
| Fee and schedule | To be confirmed | To be confirmed | To be confirmed |
The three options priced a private partnership exchange; they do not price the GGA scope. Lower price meant less scope, not weaker security: that principle stays. See Tier-Differences and Acceptance-Gates-A01-A11.