Engagement model
How Data Vista Consulting structures discovery, delivery, and handover for programming work.
1. Intake
You submit the inquiry form or email with repository links (read-only), warehouse vendor, and the failure mode you see—late loads, broken tests, or analytics code nobody wants to touch.
2. Discovery call
A 45-minute MYT call with your technical lead. We confirm constraints: data residency, on-call expectations, and whether contractors may access production. No code changes happen in this step.
3. Written scope
We return a statement of work listing tasks, assumptions, timeline bands, and acceptance checks. Fees are fixed for the module or capped for advisory hours. You sign electronically or by email confirmation.
4. Delivery
Work happens in your Git remotes or a scratch repo you own. Stand-ups are optional; async updates use your ticket system. We flag scope creep early rather than absorbing it silently.
5. Handover
Merge requests, runbooks, and a short recorded walkthrough if requested. Warranty covers defect fixes on delivered code for fourteen calendar days—logic errors, not new features.
6. Optional retainers
After handover, monthly advisory retainers can reserve two half-day blocks for review and planning. Retainers roll month to month with seven days’ notice to cancel.