Engagement Path

Why this page exists

Database work fails when the room cannot agree on order: which tables move first, which statements must stay fast, and who owns the rollback. This page describes the engagement path we reuse so visitors know what they are commissioning before they write to us.

Stage 1 — Intake

You send engine version, schema exports, slow-query samples, and the commercial dates that constrain the work. We confirm whether the ask fits a schema assessment, a query review, or the flagship refactor engagement.

Stage 2 — Diagnosis

We map hot tables, lock patterns, and naming debt. For query reviews this stage is most of the work. For refactor engagements it becomes the blueprint for migration order.

Stage 3 — Delivery

Scripts and recommendations land in your staging environment. Review sessions walk through risks with the engineers who will run the cutover. We do not push production changes without your written go-ahead.

Stage 4 — Handoff

You receive migration notes, known risks, and a short list of queries to retest after each stage. Ownership stays with your team; we remain available for a limited follow-up window defined in the statement of work.

Natural next actions

• Browse Consultations if you are still choosing a format
• Request a review if you already know the schema that needs attention