How we work
A four-phase engagement pattern that adapts to new builds, modernization, AI integration, retainers, and government RFP delivery. The same team across every phase. Documented, predictable, and built to last past launch.
The four phases
Every engagement runs through the same four phases. The depth of each phase varies by engagement type, but the structure is consistent so you always know what comes next, who is responsible, and what gets delivered at the end of each phase.
Before we sign anything substantial, we map the actual work. Stakeholder interviews, technical review of the existing stack (or whiteboarding the new one), risk identification, and a written scope with milestones, exit criteria, and a budget bracket you can take to procurement.
Two-week sprints with a working demo at the end of each. The senior person on your kickoff call is the senior person on every sprint review. We do not bring in a different team to build what we sold. Code reviewed by a second set of eyes before merge, accessibility checked against WCAG 2.2 AA + Section 508 by default.
The riskiest part. We run the new system in parallel with the old one for as long as your business needs. Documented rollback path. On-call coverage during the cutover window. We do not declare victory and disappear. Stabilization continues for two to six weeks past go-live until daily incident rate trends to zero.
Most clients move into a retainer relationship after launch. The same team that built the system runs it, adds features, and handles incidents. Quarterly review of priorities, monthly check-ins, on-call coverage with documented response times. The default is multi-year because that is what produces the lowest total cost of ownership.
Engagement-type variations
The four phases stay the same. The depth and emphasis shift based on the kind of work. Six common engagement shapes appear below, each adjusting which phase carries the heaviest weight and which compliance gates apply.
New build from scratch
Heaviest in Discovery (2–4 weeks). We invest early to map the user, the data model, and the business rules before writing code. Build phase is longer (6–12 months typical). Cutover is lighter because there is no legacy to migrate.
Inherited or existing system
Discovery focuses on code review, test coverage assessment, and risk identification before committing to any forward roadmap. We will tell you straight if the existing build is salvageable, needs heavy intervention, or should be replaced.
Modernization or migration
Cutover is the heaviest phase. Parallel-run windows can stretch to months for high-traffic systems. We prioritize zero-downtime cutover and bidirectional data sync during the parallel window. Calculator for budget bracket.
AI integration
Discovery includes a knowledge base audit (depth, freshness, structure) because it sets the deflection ceiling. Build includes prompt engineering, evaluation harnesses, and human-review workflows. Operate phase has heavier ongoing tuning. ROI calculator.
Ongoing retainer
Skips Discovery and Cutover entirely. Sprint-based delivery with a quarterly priority review. Same team continuity rules apply. Most retainers run $50K to $200K annually depending on team size and on-call coverage.
Government RFP delivery
Adds compliance gates inside each phase: WCAG 2.2 AA + Section 508 conformance audits, FERPA or HIPAA review where applicable, and a designated MPO point of contact (Manish Mittal). Documentation is heavier and audit-ready by default. Capability statement.
How we collaborate
Engagements fail more often from communication breakdown than from technical surprise. The protocols below are non-negotiable defaults. If your organization needs different cadences (security cleared environments, regulated industries), we adapt without losing the underlying accountability model.
Decision rights are written down. Every engagement starts with a one-page RACI: who is responsible, accountable, consulted, and informed for each major decision type. Architecture decisions, scope changes, security exceptions, accessibility waivers all have named owners.
Escalation paths are written down. When something needs to go above your day-to-day contact, the written path tells you who to reach and how fast they will respond. Defaults: production incidents within 1 business hour, scope conflicts within 1 business day, contract questions within 2 business days.
Why our clients stay
Most agencies treat the build as the deliverable and the relationship as a side effect. We treat it the other way around. The build is the entry point. The years of operate-and-evolve work that follow are where the partnership actually pays off, for you and for us.
Healthcare directory client since 2014. Same team, multiple platform refreshes, continuous engineering across 12+ years. Reference call available during procurement.
Our six anchor engagements span education, nonprofit, healthcare, real estate, e-commerce, and manufacturing. Each has been with us five years or longer.
The senior person who signs your kickoff is still on the engagement at year five. We staff for tenure, not for utilization optimization.
A 60-minute scoping call covers the discovery questions, names the team that would deliver, and produces a written scope you can take to procurement.
