Database Cost & Reliability Review — Pilot Assessment

Why a pilot: we're running a limited number of pilot reviews to validate the framework with real engineering teams. Scope is deliberately small so the value is easy to judge — and easy to say yes to.

Scope

• One database platform (e.g. your primary Aurora/PostgreSQL cluster).
• Read-only review — replica, snapshot, or read-only role. No write access, ever.
• Cost, reliability, and observability assessed against our standard checklist.
• Top findings — the highest-impact items, with evidence.
• A 30-day action plan.
• A 60-minute walkthrough with your team.

What you receive

• Executive summary — the picture a non-DBA can act on.
• Findings register — each finding with evidence, impact, effort, and fix risk.
• Action plan — sequenced by impact, effort, and risk.
• Recommended next steps — including whether a deeper Standard/Deep review is warranted.

See the Acme SaaS sample report for the format and depth — the pilot delivers the same structure, scoped to one platform.

How it works

1. Scoping call (30 min) — confirm fit, platform, and access model.
2. Mutual NDA + read-only access — replica/snapshot/role + a metrics window.
3. Review — a senior engineer runs and interprets the diagnostics.
4. Delivery + 60-min walkthrough — report, register, plan, next steps.

Good fit / not a fit

Good fit: a team running PostgreSQL/Aurora at meaningful scale (roughly $5k+/month on the platform) that wants an outside, senior read before a budget cycle or a suspected problem becomes an incident. Not a fit: pre-product environments with negligible spend, or teams wanting a managed service rather than a diagnostic.

Engagement note: pilot terms (availability, scheduling, and any fees) are confirmed on the scoping call. Formal paid engagements proceed once the appropriate legal and tax structure is in place; the scoping call and framework discussion carry no obligation.