Why I Replaced Our SaaS Sprawl With One Postgres System

Nexrena is my client studio for B2B web design and SEO. For a while the company ran on a pile of subscriptions: CRM in one product, project status in another, invoicing in a third, files and messages wherever they landed.

Every new client meant reconciling three UIs by hand. There was no single record for “where is this engagement.” I was the person doing that reconciliation, so I built the system I wanted to operate.

I am the sole engineer. I designed it, I shipped it, and I still run it in daily production.

What had to live in one schema

Contacts, projects, invoices, subscriptions, and the service catalog. If an upgrade (pages, SEO, forms, automations) cannot hang off the same project row, you are back to copy-paste between tools.

The stack is the boring one I already use for client work: Next.js for the client portal and admin, Express REST on Heroku, PostgreSQL with Prisma. Validation is against live client data, not demo fixtures. Schema changes go through migrations without taking the business down.

What I refused to bolt on as another vendor

A multi-site public form API (site-key routing, sanitization, dedupe, ops inbox). AI chat intake with a knowledge profile per site. A Gemini sales assistant with lexical retrieval and lead scoring. An OpenAI ops copilot that can propose writes and waits for confirmation.

Those are modules on the same database. New service types are schema plus UI, not a new monthly bill.

What changed

Published outcomes, not a vibe:

• CRM, project management, invoicing, and the client portal are one system.
• It runs live client delivery every day.
• Multiple SaaS seats for core ops went away.
• The case study lists 5+ tools replaced.

This is the same muscle I take to a product team: own the data model, ship the API, keep it running. The public writeup with architecture (no production source) is nexrena-platform. The long form is the work page.

What this is not

It is not a claim that every company should build an internal platform. It is a claim that I will, when the cost of the sprawl is my time, and I will operate what I build.