Groundbase's answer:

Two things.

First, BYO infrastructure. You connect your own Twilio account and your own Resend account. Your cost per SMS is whatever Twilio bills you, on an invoice with your name on it. I don't mark it up and I don't sit between you and your vendors. Most CRMs that offer SMS set their own rate, and you have no way to audit it.

Second, it has an MCP server. Claude, Cursor, or any MCP client can read your contacts, create deals, send SMS, and build workflows using your real data. I didn't bolt a chat sidebar onto the UI. I exposed the data and let you bring whatever AI you already pay for.

Also $9 a month, flat. One plan. No per-seat, no tiers, nothing gated behind an upgrade.

Groundbase's answer:

Technical solo operators. Solo founders, indie hackers, freelance developers, agencies of one.

Concretely: someone who reads "bring your own Twilio account" and thinks "good, I want control" instead of "ugh, more setup." Someone who already knows what an API key is and where to find it. Someone who'd rather assemble a few sharp tools than buy one bundled platform that's mediocre at everything.

If "Twilio account SID" makes you nauseous, this isn't the right tool and I'd rather say so now. Zoho Bigin or HubSpot's free tier will treat you better.

Groundbase's answer:

I built the CRM I wanted and couldn't find. Everything out there either assumed I had a sales team I don't have, or was the cheap entry tier of someone else's upsell funnel.

The part worth telling is what I removed. Groundbase originally had a credits system. Customers topped up a wallet, sent SMS through my master Twilio account, and I marked up the rate. That was supposed to be platform revenue.

I killed it. A few reasons: A2P 10DLC compliance for a multi-tenant setup is brutal for one person, every credits system generates "where did my $10 go" support emails, and refund accounting on partial balances is miserable.

But the real reason was simpler. I built this to get away from platforms that mark up Twilio, and there I was marking up Twilio. So customers connect their own account now. I lost the markup revenue and got back a product I'd actually buy.

Groundbase's answer:

Cloudflare Workers for the backend and API. Turso (libSQL) for the database. Stripe for billing. Twilio for SMS and voice, though that runs on the customer's own account, not mine. Resend for email, same arrangement.

The web app is React on Vite. Desktop is Electron with a local SQLite store. Mobile is React Native. The MCP server is a separate Worker speaking Streamable HTTP.

No framework on the backend, just TypeScript and the Workers runtime. The marketing site runs on Vercel. Everything else, the API, the app, and the MCP server, is on Cloudflare Workers, mostly for the cost curve. At $9 a month with thin margins, a bandwidth bill that scales on multiple axes is a real problem.

Groundbase's answer:

Depends who you are, and for a lot of people the honest answer is you shouldn't.

If you run a sales team, use HubSpot or Close. They're built for that and I'm not. No lead routing, no approval workflows, no SSO, no SOC 2.

If you're one person, the math changes, because the tier where the useful things live is never the cheap one. HubSpot Sales Hub Professional, where sequences and real automation sit, is $90 per seat per month on annual billing plus a required one-time $1,500 onboarding fee. Close Growth, the tier that unlocks the Power Dialer, is $99 per seat per month annually. Groundbase is $9, one plan, nothing gated behind an upgrade.

Then there's messaging cost. With bundled telephony you pay whatever rate the platform sets and you have no way to audit it. With Groundbase you connect your own Twilio account and the bill arrives with your name on it.