The roadmap math that never picks you
Inside every CRM vendor, features compete for engineering time. The scoring is roughly: does it close enterprise deals, does it demo well at the annual conference, does it justify a price increase. A complete export button scores zero on all three. Actually worse than zero, because friction on the way out is retention, and retention is revenue. No product manager writes "make leaving harder" on a slide. And no product manager gets promoted for making it easier. The export button is not missing. It is unfunded, forever, and nobody has to say why out loud.
The same gaps, every platform
Because the incentives are the same everywhere, the gaps are too. We keep a running map, and it is remarkably consistent:
- Row caps. Salesforce stops list views at 2,000 rows. Other platforms have their own ceilings, all discovered at the worst moment.
- Permission-gated exports. The greyed-out export button on Salesforce reports is a whole genre of its own.
- Exports that drop the valuable part. HubSpot exports contacts without notes. ActiveCampaign does the same. The properties travel. The relationship stays behind.
- Invisible relationships. HubSpot's associations have no report, so the links between your records cannot leave.
- History you can see but not hold. Record timelines with no export for audits, disputes or handovers.
- Suite products that do not talk. Freshsales and Freshmarketer share a vendor and not an answer.
- Missing basics. Exports that time out, deletions with no bulk path, custom fields that vanish in transit.
The part the vendors are right about
Honesty requires saying this: the vendors' priorities are rational. A CRM serving a million customers genuinely should spend its engineers on the platform. A long tail of small utility features genuinely is a distraction from that. The mistake is not theirs. It is the assumption that every feature must come from the vendor. The gaps are real and permanent, and each one is small: a few days of focused work against a documented API.
Small gaps deserve small tools
That is the entire idea behind The Missing Buttons. Each gap above has a matching button in our catalog: single-purpose, read-only wherever possible, priced per fix rather than as another platform to marry. Your credentials are used in memory and never stored on our servers on our servers. Previews are free. Each tool does one job the vendor's roadmap will never fund. We also take requests: the gaps we build next are the ones people vote loudest for.
Vendors build platforms. Users need buttons. The gap between those two words is where your afternoons go.
Why small tools can exist at all
Here is the structural fact this whole catalog stands on: every vendor above ships an API that is far more capable than their screens. That is not hypocrisy. It is a different budget line. APIs serve the integration partners and enterprise customers that roadmap math does love, so APIs get funded even while small UI conveniences starve. The result is a permanent gap: thousands of capabilities that exist behind an endpoint and not behind a button. That gap is exactly the raw material small tools are made from. The vendor built the road. Someone just has to put a bus on it.
How to judge any small tool, including ours
If this article convinces you to try point tools, take the checklist too, because the category has cowboys. A trustworthy gap-filler tells you what it does with your credentials: in-memory use, or clearly labelled opt-in storage, never silent storage. It is read-only unless its entire purpose is writing, and destructive tools lead with dry runs and typed confirmations. It shows you a preview before charging you. And it is priced like the utility it is, not the platform it is not. We hold our own catalog to that list in public, because that is the only place where holding yourself to a list counts.
What to do with this, practically
Audit your own workarounds. Every recurring copy-paste ritual, every weekly export-and-rebuild spreadsheet, every "we just live with it" is a missing button with your name on it. Some of them are in the catalog already. The ones that are not, tell us. The next button we build should be the one you are currently being paid to be.
Frequently asked questions
Why do CRMs make exporting data so hard?
Because export features score poorly on vendor roadmap economics: they close no deals, demo badly, and reduce switching friction. The result is chronic underinvestment in data portability across every major platform.
Is CRM vendor lock-in intentional?
Rarely as explicit policy, but the incentives all point one way: friction on the way out improves retention, so export gaps never get prioritized. The effect is indistinguishable from intent.
How do I get data out of a CRM with poor export options?
Nearly every CRM has a more capable API than UI. Purpose-built tools that read through the API with your own credentials can retrieve full lists, notes, associations and history that the UI export omits.
What is The Missing Buttons?
A marketplace of single-purpose tools that each fix one gap a CRM vendor never shipped: full exports, missing reports, safe bulk actions. Tools are read-only where possible and use your credentials in memory without storing them.