Flagship engagement
Schema design review
For product teams and DBAs who want a documented second opinion before locking migrations — not a generic audit checklist.
Who it is for
Engineering leads preparing a greenfield module, or teams untangling a legacy schema before a fundraising diligence round. Typical clients have between fifteen and two hundred tables and use an ORM alongside hand-written SQL for reporting.
What you receive
- Written report (PDF and markdown) with findings grouped by severity
- Annotated ERD notes or comments on your existing diagram tool export
- Suggested migration sequence with rollback considerations
- 90-minute video call to discuss disagreements and implementation order
What we need from you
Current schema dump (read-only), entity relationship diagram if available, list of top ten queries by business criticality, and any compliance constraints (POPIA retention, audit columns, soft-delete rules).
Scope and boundaries
Included: table and column design, primary and foreign keys, indexing intent, enum versus lookup tables, partitioning hints, and obvious ORM impedance mismatches. Excluded: application code review beyond data access layers, infrastructure sizing, and ongoing DBA administration.
Timeline
Standard turnaround is ten business days from receipt of materials and signed statement of work. Rush delivery within five business days is available at the rate listed on our rates page.
Delivery
Remote by default. On-site working sessions in the Western Cape can be arranged for schema workshops with multiple stakeholders; travel is quoted separately.
Pricing basis
Fixed fee based on table count band — see rates. A 40% deposit confirms the slot; balance due on report delivery.
Next step
Send a short description of the schema change and your target release date. We reply with a scope confirmation and available start week.