Systems
“Airtable → custom software”
6,400+
● Leads migrated · zero loss
~70%
● Tool cost reduction
5
● Role-specific views
What was
broken.
Airtable was working — until it wasn't. The team had outgrown its row limits, role-based access was a tangled mess of shared views, and per-seat pricing was scaling faster than headcount. Field ops were running on screenshots and Loom videos.
What I
shipped.
- 01
Audited every Airtable base, identified what was actually load-bearing vs. legacy.
- 02
Designed a Postgres schema mirroring the working data model (no "rebuild from scratch" trap).
- 03
Built a Next.js front-end with role-based access — buyers see leads, ops see pipeline, leadership sees rollups.
- 04
Migrated 6,400+ records with zero data loss using a staged dual-write window.
- 05
Wrote the SOPs the team uses to operate it, plus a 4-page admin guide for me-replacement.
“We stopped paying per seat and started paying for outcomes.”
Custom CRM Build · main view
The primary screen — what users see when they open the systems system. 16:9, PNG or WebP, around 2400px wide.
Detail / workflow shot
A specific feature or workflow up close.
30–60s walkthrough
Loom, screen capture, or MP4 showing it running.
Secondary view
Mobile, dashboard, or alternate screen.
Before / after
The mess before vs. the clean version.
Extra detail
Anything that adds context.
Need a marketing
operator?
Reply within 24 hours. No discovery calls. Send the real problem, get a real answer.
24h