Procurement memo, architecture & residual-capacity pack
Single printable pack for evaluation boards: problem/solution alignment, data architecture map, residual-capacity / sole-source skeleton, and package specification. Use Print / save PDF to download. Not a consumer checkout receipt.
Focus package: Multi-country — Multi-Country Portfolio · From ~$45k Year 1 — MERL product + multi-country configuration
1. Problem / solution alignment
Problem. Multi-country and multi-partner programmes still run people, consent, delivery evidence, and claims across spreadsheets, email, and disconnected tools. Manual triangulation before central dashboards creates delay, audit risk, and weak residual capacity when staff turn over or projects close.
Solution. IMP is a multi-tenant decision-grade system of record — people, purpose-based consent, programmes, activities, milestones, evidence, staff expenses, and vendor invoices — under Altamont’s Implementation Integrity standard. Cleaner evidence trails reduce reconstruction risk for funders and secretariats while keeping methodology judgement with human advisors where required.
Why this matters for funding risk. Governed consent history, audit trails on financial claims, and export-ready structure for Power BI / federation layers reduce the chance that regional or donor reviews fail because source data cannot be reconstructed after the fact.
2. Data architecture map (evaluation view)
High-level architecture for legal and ICT review. Final deployment diagrams are issued with the security pack (especially Package 7).
┌─────────────────────────────────────────────────────────┐
│ BUYING INSTITUTION (tenant boundary) │
│ Org A never sees Org B · strict tenant isolation │
├─────────────────────────────────────────────────────────┤
│ Roles: Programme · MEAL · Finance · Leadership · Admin │
├──────────────┬──────────────┬───────────────────────────┤
│ People & │ Programmes & │ Delivery · Evidence │
│ Consent │ Enrolment │ Activities · Milestones │
├──────────────┴──────────────┴───────────────────────────┤
│ Accountability finance: expenses · vendor AP · audit │
├─────────────────────────────────────────────────────────┤
│ Optional: country/office partitions (multi-country) │
│ HQ roll-up ──► authorised portfolio views only │
│ Country A ✗── read ──✗ Country B │
├─────────────────────────────────────────────────────────┤
│ Encryption in transit (TLS) · access controls (RBAC) │
│ Purpose-based consent · grant/revoke history │
│ GDPR-aligned stewardship · export / exit pathways │
│ Hosting: shared multi-tenant · regional · or sovereign │
└─────────────────────────────────────────────────────────┘
│ structured exports
▼
Snowflake / Power BI / NetSuite / federation dashboards
- Tenant isolation: each customer organisation is a separate tenant; no cross-tenant data access.
- Multi-country (where scoped): office-level partitions; HQ sees only authorised roll-ups; Country A cannot see Country B.
- Consent stewardship: purpose badges, grant/revoke history — not free-text spreadsheet cells.
- Hosting options: standard multi-tenant cloud; regional residency-oriented configuration (e.g. Africa / SE Asia); sovereign / high-isolation path under Package 7 with pen-test and handback pack.
3. Residual capacity clause (Implementation Integrity)
Upon completion of implementation and throughout the licensed period, the configured IMP workspace, imported and generated programme data, consent history, evidence attachments held in-system, and operational methods documented for the buyer’s roles remain with the buying institution. Residual capacity is designed so that close-out of an Altamont delivery engagement does not remove the system of record or strand the institution without operable access pathways under the licence terms then in force.
This residual-capacity model supports continuity arguments under limited-competition or sole-source policies where re-procuring an equivalent operational layer would create material risk to consent history, audit trails, and staff continuity. Full sole-source narrative: sole-source justification packsee Altamont sole-source justification pack.
4. Selected package specification
Multi-country: Multi-Country Portfolio
IMP MERL for federated / multi-office programmes — shared product, country isolation patterns, HQ roll-up discipline.
From ~$45k Year 1 — MERL product + multi-country configuration
Commercial track: hybrid · Preferred path: invoice / PO (or LTA call-off)
Includes
- IMP MERL Workspace product (results, evaluation, learning)
- Multi-office / multi-programme configuration guidance
- Country/office partition patterns (Country A cannot see Country B)
- HQ portfolio views and export discipline for regional reporting
- Implementation & training across offices in Year 1 footprint
Deliverables
- MERL product with multi-office pattern. Same IMP tenant model with configured office/programme partitions and role design.
- Portfolio operating model. Who enters data where; HQ export and report cadence documented.
- Roll-up readiness. Consistent indicators and consent purposes across countries in scope.
Out of scope
- Custom software outside IMP product boundaries
- Unlimited country onboarding beyond Year 1 footprint without change order
- Sovereign isolated infrastructure (see Sovereign Compliance engagement)
5. Recommended institutional entry
90-day IMP Pilot Sandbox — $3,500 – $4,500 engagement fee. 100% of pilot fee credited toward Year 1 Core or MERL licence if you continue within 60 days of pilot end. Validates workflows, vendor onboarding, and data governance under real constraints before full Year 1 commitment.
6. Internal routing checklist
- Programme lead confirms footprint, modules, residual capacity requirement
- Finance confirms budget line and PO / invoice entity
- MEAL / data stewardship confirms hosting and GDPR posture
- Legal / ICT review architecture map and isolation claims
- Optional: attach sole-source justification where limited competition applies
- Complete Needs Designer for tailored Year 1 line items (not catalogue floor alone)
7. Next step
Circulate this pack. Then design scope for a tailored estimate and invoice/PO request.
Altamont Digital · AltamontDigital.ai · Document date: 2026-08-13 · Confidential when completed with organisation details