How an engagement unfolds.
Every iModernizeIT engagement follows the same shape. Here’s exactly what happens, when, and what to expect at each stage.
The five stages.
Fit call.
You describe the application and the pressure you’re facing. I ask questions to determine fit. On the call I walk you through private samples of prior work — engagements I can reference on a call but can’t publish on the public site. No sales pitch. If it isn’t a fit, I say so on the call.
Scoping & SOW.
I review the existing application (read-only access or walkthrough), interview 1–2 of your users (30 min each), and write the Statement of Work: scope, deliverables, timeline, fixed fee, assumptions, exclusions, access requirements, stakeholder contacts, communication channel. You approve in writing before anything else happens. The signed SOW is the kickoff — no separate ceremony.
Build.
I build. Your legacy application is the source of truth — twenty years of translating business intent from legacy code into modern patterns means I rarely need to interrupt your team. One engagement at a time, start to finish: while yours is active, it’s the only rebuild I’m working on, and I’m fully reachable throughout. Staging environment available for your review as the app comes together.
Review & delivery.
Full walkthrough of the rebuilt application with your team. Accessibility conformance report, performance baseline (Lighthouse), and security baseline (OWASP Top 10) delivered. Deployment to your production environment. One-hour knowledge transfer session. Acceptance, or walk-away (see payment structure below).
Warranty.
Bug fixes and minor adjustments during the warranty window. After day 30, the engagement is complete.