By Marty Papamanolis / Published 3 May 2026 / 10 min read
Custom CRM vs Salesforce for a 30-person firm
For a 30-person accounting, legal or wealth practice, the choice is rarely a clean “custom CRM or Salesforce.” It is the parts of Salesforce the firm genuinely uses, plus a custom layer for the rest. Salesforce is excellent at large sales orgs with a dedicated admin. The real question is which workflows belong on a per-seat licence at $200 a month and which ones a custom build pays off inside eighteen months. The framework below is what we use.
Where does Salesforce win outright for a 30-person firm?
Salesforce earns its keep in a small number of places. We have not seen a custom build beat it on these.
The first is a genuine sales pipeline with a dedicated business development team. If a firm has two or three people whose job is moving qualified leads through stages, with forecasting up to the partner group every Monday, Salesforce’s pipeline tooling is mature in a way that takes years to build. The reports, the dashboards, the cadence tooling, the integration with email tracking. It is a proper sales product. A custom build can match the database, but matching the surrounding behaviour is a multi-quarter project that most 30-person firms cannot justify.
The second is marketing automation tied to a CRM, where the firm runs scored nurture lists with event-triggered email sequences. Pardot and Marketing Cloud sit cleanly on top of Salesforce. The same workflow on a custom CRM means rebuilding the email infrastructure, the consent tracking, the bounce handling, and the segmentation engine. Doable, but a different scope of work.
The third is the multi-entity firm with a parent and several subsidiaries that need shared client records but separate reporting. Salesforce’s permission model handles this through profiles, role hierarchies, and sharing rules. A custom build can do it, and we have built it, but the configuration burden moves from “Salesforce admin” to “custom code that the team owns.” For a firm without an IT lead, that is a real consideration.
If a firm reads this list and recognises one or more of those three workflows as the centre of how they make money, Salesforce is probably the right call. The licensing is the price of admission to a mature product.
When is a custom CRM cheaper than Salesforce by month 36?
The other side of the line is where most 30-person professional services firms actually live.
Client intake and onboarding for a regulated practice. A new wealth client triggers a fact-find, a risk profile, an FSG, a TFN check, an AFSL compliance hand-off, and a record in Xplan. A new legal client triggers a conflict check, an engagement letter, a trust account record, and a matter in LEAP. A new accounting client triggers a Xero invitation, an XPM record, a CAS360 entry, and a lodgement profile in LodgeiT. None of these is a sales pipeline. They are compliance-aware workflows with branching rules. Salesforce can be configured to do this, but the configuration is custom development inside Salesforce’s framework, paid at platform-developer rates and licensed per seat. A custom CRM that knows the firm’s intake rules natively is usually cheaper inside three years.
Annual review and recurring obligation tracking. Wealth practices run annual reviews. Accounting firms run BAS quarterly and tax annually. Law firms run trust account reconciliations monthly and renewals on a calendar of their own. The data shape is recurring, scheduled work tied to a client, with a partner who owns it and a paralegal or analyst who does the prep. Salesforce treats this as either tasks or custom objects. Both options work. Both options become an admin’s full-time job to maintain. A custom CRM with a domain-specific concept of “annual obligation” is shorter to build than the equivalent configuration debt.
Reporting that draws from the practice management tool, the ledger and the CRM at once. A partner asking “which clients made us money this year, weighted by the cost of serving them” wants a number that combines XPM time records, Xero ledger data, and CRM relationship history. Salesforce can ingest the ledger, but the licensing cost of pulling external data into Salesforce reports adds up. A custom CRM built on its own database can join across systems without paying per-record for the privilege.
Document-heavy workflows where the CRM has to know about files. Engagement letters, fact-finds, SOAs, BAS workpapers, ASIC forms, signed deeds. Salesforce stores documents through Salesforce Files, which works, with limits on storage and search that get expensive at scale. A firm where every client record carries thirty to a hundred documents and where partners search by document content rather than by client name will hit those limits quickly. A custom CRM built around document storage natively, with full-text search and retention rules tied to the regulator’s audit window, is a different tool from a CRM with documents bolted on.
When we look at the firms we have built CRMs for, three of these four are usually present. The fourth is the one that flips the calculation from “configuration” to “different product entirely.”
How much does Salesforce really cost a 30-person firm?
The most common error we see in this comparison is calculating Salesforce’s cost as licence price multiplied by user count. The number is always wrong on the low side.
A Sales Cloud Enterprise licence is in the order of $200 per user per month, AUD, before tax. For 30 users that is $72,000 a year. That is the headline number a firm uses to decide. It is also the number a Salesforce sales rep quotes.
The real cost includes three more components.
The first is the implementation. A 30-person firm’s Salesforce build, done well, sits between $40,000 and $120,000 for the first usable release, depending on integrations and the number of custom objects. This is paid once but it is real. A firm that tries to do this implementation in-house with a part-time admin underspends on day one and pays it back in technical debt over two years.
The second is the ongoing admin. Salesforce assumes someone in the firm owns it. That person spends one to two days a week on it, every week, forever. For a 30-person firm, that is either a paid Salesforce admin contractor at $1,000 to $1,500 a day, or it is the operations manager’s bandwidth that comes off something else. Either way, the figure is six figures over three years.
The third is the integration cost. Connecting Salesforce to Xero, LEAP, XPM, Xplan, HUB24 or Netwealth is not a free feature. The connectors are paid add-ons. The Zapier-style middlewares hit limits at scale. The API governor caps get expensive when a firm grows past the entry tier. Six to twelve thousand dollars a year is normal for the connector layer alone.
Add it up and a 30-person firm running Salesforce well is at $120,000 to $180,000 a year by year three.
A custom CRM at the same scale has a different cost shape. The build is heavier upfront, sitting in the same range as the Salesforce implementation but skewed higher: $80,000 to $200,000 for the first usable release. The licence cost after that is the hosting, which is in the order of $200 to $500 a month for a firm of this size. The admin overhead is real but smaller, because the system is shaped for the firm rather than the firm being shaped for the system. Most of the maintenance is the change requests the firm would have made anyway. Total cost over three years is usually $150,000 to $300,000, including ongoing development.
The two cost shapes laid side by side, for a 30-person firm, in AUD:
| Cost component | Salesforce | Custom CRM |
|---|---|---|
| Build / implementation (first usable release) | $40,000 to $120,000 | $80,000 to $200,000 |
| Licence | Hosting, $200 to $500 / month | |
| Ongoing admin | 1 to 2 days a week, six figures over three years | Real but smaller; mostly change requests the firm wanted anyway |
| Integration / connectors | $6,000 to $12,000 / year | Included in ongoing development |
| Three-year total | $120,000 to $180,000 / year by year three | $150,000 to $300,000 over three years, including ongoing development |
The two ranges overlap. Custom is cheaper when the firm has the four workflows we listed and intends to keep them as-is for at least three years. Salesforce is cheaper when the firm is genuinely a sales-led business, when the marketing automation is core, or when the firm expects to grow past 80 people inside the same horizon. The maths is not “custom is always cheaper.” It is “the line crosses around month 30 to 36 for firms in the middle band.” Where the firm sits on that line determines the answer.
Hybrid: when both make sense
The hybrid pattern shows up often enough to be worth naming. A 30-person firm runs Salesforce for the part it does best, usually the new-business pipeline and the campaign tracking, with seats only for the people who actually use it. A custom layer sits alongside, owning the intake workflow, the recurring obligations, the document store, and the cross-system reporting. The two share data through a tight integration that the firm owns rather than rents.
This works when three things are true. The sales pipeline is genuinely a separate workflow from the operational work, with different people in it. The firm can afford both fixed costs, because hybrid does not save licence fees on the part that stays in Salesforce. And the integration boundary is clear enough that the data does not need to round-trip every five minutes.
It does not work when the firm is trying to use it as a transition step. “We will keep Salesforce for now and slowly move workflows to the custom build” is a plan that almost always stalls at the halfway point, with both systems half-loved and the firm paying for both forever. If the intent is to migrate off Salesforce, do it in one project with a known end date.
For firms already on Salesforce who want the hybrid pattern as an exit ramp rather than a permanent state, the house next door approach is the version we run. The custom layer goes alongside the existing CRM. The data the firm needs gets synced into a database it owns. Salesforce exits when the custom side is genuinely doing the work.
What changes if the firm is closer to 100 people?
The framework above is calibrated for 30 people. The line moves at scale.
At 80 to 100 people, Salesforce’s strengths compound. The reporting infrastructure gets more valuable as the firm has more people generating data. The admin overhead is the same one to two days a week, but it is now a smaller fraction of total cost. The library of pre-built apps on the AppExchange becomes useful, because at 100 people there is usually a need for one or two specialist tools that already integrate.
The custom CRM strengths compound differently. A 100-person firm has more workflows, more document types, more integrations, and more reporting demands. The custom build is more expensive at this scale, sitting in the $200,000 to $500,000 range for the first release, with proportionally heavier ongoing development. The break-even moves to month 48 or beyond.
For most firms above 100 people, Salesforce or a competitor of similar weight (Microsoft Dynamics, HubSpot Enterprise) becomes the default and a custom layer fills specific gaps. For firms below 50 people, custom usually wins on the maths we ran above. The 30-person firm sits in the middle band where the answer depends on the four workflows.
We have written more about how we run custom CRM builds for Melbourne professional services firms, including the diagnostic that produces the firm number before any commitment. The closest case-study analogue we can publish is the wealth management CRM rebuild, where a firm came to us after evaluating Salesforce Financial Services Cloud and choosing custom. It is not a universal answer. It was the right answer for them.
For accounting firms running the same comparison, the accounting industry view covers the practice-management overlap that changes the maths. For wealth practices, the wealth management view covers the platform integrations that often tip the decision either way. The framework on this page is the starting point. The real answer depends on which side of the line each firm’s workflows actually sit on.
