How every engagement runs.

Phase 01 // AUDIT

Audit

Duration // One week

Discover, assess, eliminate, scope

Every engagement opens with a structured audit. We map the operation, identify the cost lines worth addressing with AI, eliminate the noise, and scope a build that pays for itself inside thirty days. The audit is its own deliverable: even if you decide not to proceed, you keep the document.

Deliverables

• //Operating-model map
• //Cost-line shortlist with conservative ROI estimates
• //Build scope, priced and timeboxed
• //Risk register and POPIA position

Phase 02 // BUILD

Build

Duration // Two to three weeks

Data foundation, model layer, integration, ship

Build runs in tight weekly cycles against the scope set in the Audit. Senior practitioners on the work, no juniors learning on your account. We architect the data foundation first, choose the model layer second, and integrate against your existing systems third. Production-grade from day one.

Deliverables

• //Data foundation aligned to POPIA
• //Model selection memo (vendor, residency, fallback)
• //Integration into existing operational systems
• //Production deployment, observability, runbooks

Phase 03 // OPERATE

Operate

Duration // Ongoing, monthly cadence

Live tuning, monthly notes, thirty-day proof

Implementation without operations is theatre. Every Impart engagement has an Operate phase priced in. We tune the system against live data, write you a monthly note on what moved, and hold ourselves to the thirty-day guarantee. The system either earns its keep, or we keep working at no further charge until it does.

Deliverables

• //Weekly tuning against live data
• //Monthly written note on movement
• //Quarterly review against the original cost line
• //Thirty-day proof or continued work, no further charge