Why Groundbase won't build social media management

Groundbase will not get a social media scheduler. No posting to LinkedIn, X or Instagram from inside the CRM, now or on the roadmap.

People ask about it often enough that the reasoning is worth writing down. It is also a fair summary of how I decide what goes into Groundbase at all.

A sinkhole for one developer

Hootsuite and Buffer are whole companies doing one job: keeping posts flowing to social platforms. They are not big because they are inefficient. They are big because that job never stops needing work.

Here is what building a scheduler actually involves:

• APIs that keep changing. X has changed its API access and pricing more than once in the last few years. Instagram puts most of what a scheduler needs behind app review. LinkedIn keeps much of its posting access behind partner programs. Every platform moves on its own timetable, and each move breaks something.
• Sign-in at scale. Token refresh, scope changes, suspended accounts, people with several accounts on one platform. Every platform does it differently, and a token can stop working because someone signed out of an app on their phone.
• Rate limits everywhere. Some count per user, some per app. Hitting one is routine. Explaining to a customer why their post didn't go up is not.
• Rules that differ per platform. Image formats, character limits, what can be scheduled, what gets flagged. What worked yesterday gets an account flagged tomorrow.
• Maintenance forever. This is not a feature you ship once. It is a standing commitment to integrations owned by companies with no reason to keep them stable for you.

For one person, a credible first version is months of work, followed by permanent upkeep. My guess is that a minority of people running a one-person business would use it. That is a bad trade.

Why most CRMs that add it do it badly

If you've used a CRM with a social tab, you probably ignored it.

That is not an accident. A CRM that bolts on social posting ships a thin version, because the CRM is the product and the social tab is a checkbox. It exists so the feature grid looks complete.

If you post enough for it to matter, you already use Buffer, Hootsuite, Typefully, or the platform's own scheduler. A worse copy inside Groundbase would not help you. It would just be one more screen for me to keep working.

What I do instead

Groundbase has an MCP server. It lets Claude, ChatGPT, Cursor and other assistants connect to your CRM and do nearly everything you can do in the app: search and filter contacts, update records, send texts and email, book meetings, send invoices and quotes. What an MCP server is covers the idea in plain terms.

That means Groundbase doesn't need a scheduler. If your assistant is also connected to your scheduling tool, you can ask:

"Look at the deals I closed this month. Draft five LinkedIn posts about what I learned, and schedule them in Buffer."

Groundbase supplies the facts: who you worked with and what happened. Your scheduler does the posting. The assistant does the stitching between them. Each tool does its own job, and none of them has to pretend to do the others'.

The broader principle

I would rather do 50 things well than 500 things badly.

The all-in-one pitch usually turns into separate products sold separately. HubSpot sells hubs, each with its own tiers. You end up paying for breadth, and much of that breadth is shallow, because nobody ships an excellent version of everything.

Groundbase makes the opposite bet. Do the job of a CRM for a one-person business properly, and let the rest of your stack be whatever you already like.

What I said I'd build, and what shipped

When I first wrote this post, in June, I listed what I would build instead of social. Most of that list is done:

• Lead capture forms. Shipped. Each form gets its own link, starts from a template or blank, and every submission finds or creates the contact, tags them, adds a note with the answers and creates a follow-up task. Landing pages, the other half of that line, did not ship.
• Email A/B testing. Shipped, and for texts too. A draft campaign can be split into up to four versions. The audience is split evenly, and results show per version. Groundbase doesn't pick a winner; it shows the numbers.
• More AI coverage. Shipped. The assistant can now do nearly everything you can do in the app. What stays in the app is mostly connecting accounts: Twilio, Google, your mailbox, Stripe.
• Better booking. Shipped. Booking links with confirmation emails, reminders by email and text, Yes, No or Maybe buttons, and reschedule and cancel links. Two-way Google Calendar sync.
• More ways in and out. Shipped as webhooks in both directions, which is how Zapier, Make, Typeform and your own website talk to Groundbase.

Things that weren't on the list shipped too: invoicing with card payments through your own Stripe, quotes, documents and e-signatures, newsletters, and workflows. Every one of them is about you and a particular customer. Social posting is about an audience that isn't in your CRM at all, which is the clearest way I can put why it doesn't belong.

What I won't build

• Social media scheduling. Use Buffer or Hootsuite.
• Ad platform management. Use the Meta and Google Ads dashboards.
• A CMS or blog engine. Use Ghost, WordPress or Webflow.
• SEO audit tools. Use the tools built for it.
• Enrichment. No job titles or company logos pulled in from third-party data services.
• A built-in AI chat panel. Your own assistant connects through MCP instead, on the subscription you already pay for.

These are real products with real teams behind them. Groundbase plays well with them through webhooks and your AI assistant, and stays out of their lane.

The trade-off, stated honestly

Saying no to social means Groundbase is not one login for everything. If you post a lot, you will have a scheduler open alongside it, and the bridge between them is either your assistant or you. Some people want one vendor for all of it, and for them a suite is the better fit.

What you get in return is a smaller product where the parts are finished. Groundbase is one plan, $19 a month or $199 a year, and every feature in the app is in it: no tiers, no add-ons to unlock workflows or campaigns or invoicing. Texts and calls go through your own Twilio account and campaign email through your own Resend account, billed by them, with no markup from me.

If you want to know whether that fits how you work, who Groundbase is and isn't for is the straight answer. Social posting will stay in the tools built for it.

---

Questions about this one? Email me directly: blog-social@groundbasecrm.com — I read every one.