Skip to main content

Platforms & products

The platform we run our own company on

Live

We run our own company on a platform we built ourselves, which is the clearest proof that we build the kind of software we describe.

Formulation Labs runs on a platform we built ourselves: a public website, a client portal where clients see their projects, proposals, invoices, and contracts, and a shared package layer underneath. A crew of six AI agents plans, builds, checks, and reports on it, handing work to each other through the codebase.

Client
Formulation Labs (internal)
Engagement
Architecture and build
Status
Live
Discipline
Platform engineering
What we built
  • Public website
  • Client portal
  • Shared packages
  • AI build crew
  • Release checks
Stack
  • Turborepo
  • Next.js 16
  • TypeScript
  • Supabase
  • Drizzle
  • Resend
  • PostHog
  • Playwright

Before

The most honest case study a builder can show is the one it runs itself. Rather than stitch together off-the-shelf tools, we put the firm on a custom platform of our own: one codebase that powers both the public website and the private client portal, sharing one design language, one data layer, and one set of tested building blocks. It is the same architecture we bring to client work, which means we feel every decision before we recommend it.

What made it hard

01

Two very different surfaces, a public website and a private client application, had to share one codebase, one design language, and one set of components without bleeding into each other.

02

Each client's data in the portal had to stay invisible to every other client, enforced in the database.

03

The public site is live and must never break, so every change passes required checks and a preview deploy before it merges.

04

It had to prove the firm's own standards, not cut corners, which meant real tests and real architecture.

What we built

01

Built a monorepo that runs two live apps, the public website and the client portal, on eleven shared packages for design tokens, UI, data, domain logic, integrations, jobs, AI, widgets, auth, workflows, and testing.

02

Built the portal clients sign into, with their projects, proposals, invoices, contracts, performance, and contact, each client walled off in the database, plus an admin side for leads, scope briefs, and billing.

03

Connected the website's forms to the portal with signed requests, so every application lands as a lead without retyping.

04

Put every change behind required checks (typecheck, lint, unit tests, and both production builds) and a preview deploy before it merges.

05

Run the build with a crew of six AI agents (director, watch, engineer, QA and security, design, and analyst) that hand work to each other through the codebase: 153 handoffs and 145 reports since September 2026.

06

Measured the website's own funnel with consent-based product analytics, the way we measure a client's.

Results

300Commits in six months

73 merged pull requests from April to October 2026, each through the same required checks.

33Portal screens

18 for running the firm and 7 for clients, plus sign-in and onboarding, on database rules that keep each client's data apart.

6AI agents on the crew

They plan, build, test, design, and report on the platform, with a person approving the riskiest changes.

Where it stands

Live. The website and the client portal are both online, and changes ship most weeks.