Back to Blog
CRMNext.jsExecutive AssistanceTutorial

Why I Built a Custom CRM Instead of Using Salesforce — and How You Can Too

July 1, 2026 8 min read

The problem every executive assistant knows

You have 200+ contacts across 3 departments. Some are internal stakeholders, some are clients, some are vendors. Each needs different follow-up cadences, notes, and priorities. And somehow it's all in a spreadsheet that nobody updates.

Why Salesforce was the wrong answer

Salesforce is a $150B company for a reason — they solve enterprise CRM. But for a solo executive assistant managing 200 contacts, Salesforce is like hiring a 50-person IT team to manage your personal inbox.

I needed something that:

  • Takes 5 minutes to set up
  • Has exactly the fields I need (and nothing I don't)
  • Sends me a weekly digest of pending follow-ups
  • Cost me ₹0/month in software fees
  • What I built

    A custom CRM with:

  • Next.js frontend (static export, hosted on Vercel free tier)
  • PostgreSQL via Supabase (free tier — 500MB)
  • Tailwind CSS for UI
  • Custom fields: contact type, relationship strength, last interaction date, next follow-up
  • Weekly email digest via a simple cron job
  • The result

    Zero missed follow-ups in 6 months. The executive I support saves 4+ hours per week. Total development time: 3 days.

    Want the exact blueprint?

    I documented the full build — database schema, API routes, and deployment — in a GitHub repo. DM me if you want the link.

    Like what you read?

    I write weekly about building systems, automation, and workflows. If you need something built, let's talk.