For agencies and fractional CTOs

Bring me a client whose Postgres is slow.

I'll do the first review free, under your name, so you can see the work before deciding anything.

You keep the client relationship. I review the read-only output you have permission to share and write up what stands out.

Who this is for

  • Development agencies that build and run SaaS products on PostgreSQL but don't have a database specialist on the team.
  • Fractional CTOs who need a second opinion on a client's database before recommending spend, a rewrite or a hire.
  • DevOps and cloud consultancies handling RDS or Aurora estates where the open question is the database, not the infrastructure.

When it makes sense to bring me in

  • A client reports slow pages or a rising RDS or Aurora bill and your team can't point to the cause.
  • A client is still on PostgreSQL 14 or planning another major-version upgrade and needs the risks written down.
  • A migration, backfill or schema change is about to ship and nobody has checked what it locks.
  • A SQL Server client has a plan regression or blocking problem that Query Store should explain.

How the first review works

The free first review uses the same read-only snapshot script and format as the public snapshot review: one database, the output your client has authorised you to share, and three written findings. It counts toward the same monthly limit. Anything beyond that is scoped and priced before it starts.

Roles and confidentiality

  • Authorisation. You confirm that your client has agreed to share the output with a subcontractor. I don't need credentials for the first review.
  • Client communication. By default you talk to the client and I talk to you. I join client calls only when you ask.
  • White label. The free first review goes out under your name. For paid work, a white-label report is agreed in writing per engagement; otherwise it names me as the reviewing engineer.
  • Confidentiality. Send your NDA or your client's for review before any evidence is shared. Output is used only for that client's report and deleted after 30 days unless the engagement says otherwise.
  • Production changes. Your team or the client's team makes them. My reports include the risk, rollback and validation for each change.

Paid work you can resell or refer

Each engagement has a written scope, a fixed fee and a delivery date before work starts. You can see the format in the sample report, built on a demo database.

Who you'd be working with

I'm Kiran Sabne. I work alone, with about 8 years in database and backend engineering. WalStack is listed in PostgreSQL.org's Professional Services directory, and I built PlanReader. The partner kit has a one-page summary you can share internally.