Start with a conversation, move into a focused technical assessment when needed, or keep NoRewrite involved through ongoing Care. Larger modernization programs are scoped separately around the application, risk and delivery requirements.
Public pricing makes the first decision easier. Larger programs sit outside these packages because pretending every inherited application has the same scope would be misleading.
A short first conversation to understand the application, what changed and whether NoRewrite is the right fit.
A focused technical analysis of an agreed application area, with concrete findings and sensible next priorities.
Ongoing technical ownership for applications that need continuity, maintenance and senior engineering context month after month.
The assessment scope is agreed before access is provided. A smaller application may be reviewed broadly; a large platform may need one workflow, risk area or technical question selected for the initial assessment.
The target repository, subsystem, workflow or decision is written down before technical work starts.
Findings are tied to code, query plans, dependencies, runtime behavior or other observable technical evidence.
Issues are ranked so critical risks are not buried under generic technical-debt commentary.
You receive enough context to continue with NoRewrite, brief another engineer, or decide that no immediate project is justified.
For larger organizations, complex applications and substantial modernization programs where a fixed package would be artificial.
No. The consultation is for context and fit. The Analysis & Assessment is paid technical work and produces a concrete written technical deliverable.
Yes. The assessment is useful on its own and is intended to leave you with a clearer technical picture regardless of who performs the next piece of work.
Care preserves senior technical context across maintenance, incidents and agreed improvement work. The expected workload, response expectations, support window and project-sized work are agreed before the relationship starts rather than being hidden behind an “unlimited support” promise.
Material project work or sustained workload beyond the agreed Care boundary is scoped separately before it is undertaken. The retainer is intended to make ownership predictable, not make capacity ambiguous.
When the number of systems, workstreams, delivery horizon or business risk makes a tailored engineering program more appropriate than a standard package.
Prefer email instead of live chat?
If you want a reply after closing the chat, leave an email address below.