What we take on
Engagements centre on relational data stores that back customer-facing applications: normalisation fixes, index design, view and procedure boundaries, and driver-level fetch patterns. Typical inputs include slow API endpoints, risky migrations, or reporting queries that bypass the ORM.
We do not sell subscription software or managed hosting. Each project is defined in a written scope with milestones, acceptance criteria, and fees agreed before billable work.
Scoping inputs we need
- Engine and version (for example PostgreSQL 15 on RDS, or SQL Server on-premises)
- Approximate table count in scope and whether production read access is available
- Representative queries or ORM traces showing latency pain
- Change-management rules (maintenance windows, replication topology)
Deliverable examples
| Output | Purpose |
|---|---|
| Annotated ER revision | Aligns entities with how services actually read and write |
| Index and constraint DDL | Targets measured predicates instead of generic templates |
| Migration sequence | Orders additive changes before destructive steps |
| Explain-plan brief | Gives developers a checklist before merging data-access code |
Fees and timing
Fees are quoted per statement of work after discovery. Duration depends on environment access and review cycles; small schema audits may complete within two weeks, while multi-schema refactors run longer with staged milestones.
Next step
If you have a concrete schema or query problem, use the contact form or call 6000 1909 so we can see whether a fixed-scope engagement fits.