A tool for Salesforce admins wrestling with field sprawl — smart idea, real problems.
Every Salesforce org older than three years has the same skeleton in the closet. There's a field called `Account_Type__c`, another called `AcctType__c`, and somewhere buried in a 2019 campaign object there's `Account_Category__c` that nobody remembers creating. Some junior admin built a monthly loader in Google Sheets to reconcile them. Their coworker inherited it. Nobody knows what breaks if you delete any of these fields. Nobody wants to find out.
This is real. The Trailblazer Community threads, the r/salesforce posts, the G2 reviews that say Gearset is great but "doesn't touch schema bloat upstream" — this isn't manufactured pain. Salesforce admins are not a vocal Twitter audience, which means when they're complaining publicly, it's bad enough that they finally bothered to write it down.
So the idea makes sense at first glance. Build a tool that ingests field metadata, runs semantic similarity clustering ("Account_Type" and "AcctType" are 94% the same thing), maps every workflow and formula that references each field, and generates a merge plan you can preview before touching production. The "aha moment" they describe — connecting your org and seeing "34 semantically similar field clusters" with fields you recognize — is genuinely good product design. Free audit, prove the pain exists, then sell the solution. The wedge is clever.
The moat argument also isn't crazy. Every new org that runs an audit adds labeled examples of field synonyms. After 50 orgs you have a pattern library nobody else has. After 200, your cold recommendations are accurate enough to feel almost spooky. That compounding effect is real, it just requires surviving long enough to build it.
Here's the problem I keep coming back to: this is a project tool, not a workflow tool.
A Salesforce org does a serious schema cleanup once every 18-36 months. That's not a SaaS business, that's a consulting engagement with a subscription wrapper. The retention hooks they've proposed — monthly drift alerts, quarterly health scores — are reasonable ideas, but they're speculative. You need to validate that admins will actually open those emails and care between major cleanups. Right now that's an assumption, and it's the most dangerous assumption in the model.
The LTV math shows $10,800 assuming 18-month average retention at 5% monthly churn. If that churn spikes to 8% after customers complete their cleanup, the LTV drops to $7,200 and the unit economics get uncomfortable fast. More importantly, you might see a usage cliff at month 3-4 that no amount of email drip campaigns will fix if the admin literally has nothing left to do in the product.
The Salesforce AppExchange security review takes 8-16 weeks and has a real rejection rate for anything touching Metadata API writes. Until you have that listing, you cannot close a deal with any security-conscious buyer, which is most mid-market buyers. That's a 4-6 month gap after MVP where you're either selling to early adopters willing to skip security review, or you're stalled.
This doesn't kill the idea but it murders the runway assumptions. If your break-even is 13 customers at $799/month, and you can't credibly sell to your target buyer for the first 6 months post-launch, you need either more runway or a cheaper version of the first few months. The "free audit" approach might actually be the right move here — use those 6 months to do manual audits, charge nothing, and treat it as paid research. But you have to go in knowing that's what you're doing, not discovering it after you thought you were 8 weeks from revenue.
The Accentures and Slaloms of the world are both a channel and a competitor, but mostly a competitor in this context. A mid-large enterprise with serious schema debt almost certainly has an SI on retainer. When the RevOps VP finally decides to deal with the field chaos, their first call is to that SI, not to the AppExchange. The SI builds a custom cleanup script in two weeks and bills 40 hours. You never enter the conversation.
The companies most likely to buy self-serve are Series B SaaS companies with a single overworked Salesforce admin and no SI relationship. That's actually a better target segment than "mid-large enterprise" — faster sales cycles, more autonomy for the admin to just try something, and a lower security review bar. The pitch document gestures toward this with "200-1,500 employee SaaS companies" in the channel section, but then talks about enterprise features and $2,000/month tiers as if that's the real prize. Pick one.
This is the counterargument I find most uncomfortable. If semantic field cleanup was a durable, well-monetizable problem, and the Metadata API has been available for 14 years, why hasn't a well-funded team built and scaled this? The most honest answer is probably: they tried, discovered the episodic use case problem, and the category didn't work as a standalone SaaS. That doesn't mean the AI angle changes nothing — it genuinely changes the UX from "six-week consulting engagement" to "10-minute self-service audit." But it doesn't change the fundamental usage pattern.
And then there's Salesforce itself. Einstein for Admins is opaque, Salesforce has the metadata access, the distribution, and the AI infrastructure. A single product release — "Health Check now detects semantically similar fields" — could neutralize the entire core feature. You'd be left selling the dependency graph and the merge execution layer, which is closer to what Gearset and Copado already do.
I think this is worth exploring but not in the form described. The enterprise angle and the AppExchange-first strategy feel like founder wishful thinking. The real path, if there is one, starts smaller and cheaper.
Do the manual audit thing first, seriously. Not as a marketing tactic but as a genuine learning exercise. Find 10 admins, pull their metadata with Workbench, run GPT-4 clustering in a spreadsheet, deliver a PDF. Charge nothing. At the end of every call, ask two questions: "Would you pay $300/month for this automated?" and "How long ago did you last do a cleanup like this?" The answers to the second question will tell you everything about your churn problem before you write a single line of product code.
If you do build, target the solo Salesforce admin at a 100-500 person SaaS company, not the enterprise RevOps team. Faster sales, fewer security hoops, and honestly more likely to become a champion who refers you to other admins. Price at $199/month and optimize for volume. The $2,000/month enterprise dream is a distraction that will burn your runway on a 12-month sales cycle before you've validated that anyone stays subscribed past month 4.
The unfair insight buried in the pitch is actually the most interesting thing here: admins aren't buying a technical tool, they're buying political cover. A data-backed report they can show their CRO. That's a real insight and it suggests the product might be less of a technical utility and more of a reporting and documentation tool that happens to also do migrations. That framing changes what you build, what you charge for, and who you sell to.
Score it a 7 and call it "worth exploring" — that's exactly right. Not a clear winner, not a clear pass. Worth three months of free audits and genuine curiosity, with an honest willingness to discover that the episodic use case problem is fatal and this needs to be repositioned as a one-time audit service, not a subscription.