Audit. Replace.
Optional run.
Three engagement models for evaluating, delivering, and operating modernization work. Commercial terms follow the scoped workflow, risks, operating model, and acceptance checks rather than a generic website range.
- Scope firstModernization discovery
- ✓ Scoped inventory of workflows, costs, risks, and retained systems
- ✓ Keep, improve, or replace recommendation for the agreed decision
- ✓ Documented assumptions, acceptance checks, and operating model
- ✓ Commercial terms agreed only after the relevant scope is understood
The starting point when the workflow, operating risk, or economics are unclear.
Request a consultation → - Agreed scopeScoped modernization build
- ✓ Workflow, integrations, data treatment, and ownership defined in scope
- ✓ Acceptance checks, migration sequencing, and rollback decision agreed before production change
- ✓ Phased rollout or parallel run where the workflow risk warrants it
- ✓ Support, handoff, and change responsibilities specified in the engagement terms
The build approach follows the risks and operating requirements identified in discovery.
See replacement offers → - Agreed termsSupport or handoff
- ✓ The agreed changes, monitoring, and operating support
- ✓ Named ownership and escalation path for the scoped service
- ✓ Documentation and access for internal handoff where appropriate
- ✓ Change control and continuation terms defined in writing
Choose an operating model that fits the client team and the workflow risk.
Talk about retainers →
Model the current state before pricing a change.
Current vendor cost is only one input. The decision also includes retained systems, internal effort, integration work, migration risk, and ongoing operating responsibility.
A useful model separates up-front delivery cost from retained software, infrastructure, internal effort, migration, training, and ongoing operating responsibility. The discovery record identifies which inputs are available, estimated, or still unknown before commercial terms are proposed.
Agree terms that fit the scoped work.
The billing approach follows the verified scope, risks, dependencies, and operating responsibilities. It is not inferred from a generic savings estimate.
Discovery separates build work, migration, retained systems, internal effort, and ongoing ownership. The proposed billing method and any performance-linked terms require a written definition of the relevant measurement, dependencies, and limits.
When commercial terms are not supported by the available evidence, the decision record identifies what must be verified before a proposal is made.
What should be made explicit.
- ✓
Named team
The delivery roles and decision owners are named for the agreed engagement.
- ✓
Communication
The update rhythm, working channels, and review points are agreed in the delivery plan.
- ✓
Support terms
Response, escalation, monitoring, and continuity responsibilities are written into the scope where needed.
- ✓
Decision records
The project records the material decisions, assumptions, and acceptance checks that affect the workflow.
- ✓
Access and handoff
Repository, access, documentation, and operating responsibilities are agreed before launch.
- ✓
Runbooks
Operating documentation is included where the agreed scope requires it.
Commercial details in the written scope.
The working model is selected after the relevant workflow, risks, ownership, and acceptance checks are understood.
- → Engineering · QA · DevOps · design · product direction
- → Rate, billing method, and engagement length are quoted in the written scope
- → Time-and-materials or another commercial structure may fit selected work