CRM for Agencies: Configure HubSpot, or Build the Retainer and Margin Layer Your Stack Cannot Model?
Headcount and retainer variety decide this.
On this page
Headcount and retainer variety decide this. Under roughly 15 people with simple retainers and only a few tools, buy: configure HubSpot properly, add a vertical agency tool if you need one, and put the money into new business, because a custom build at that size solves a problem two spreadsheets already solve. Between 15 and 50 people, with margin visibility a genuine and costly problem and your project and time tools locked in, build the integration and reporting layer and keep the delivery tool, at $70,000 to $110,000 over 4 to 6 months. Above 50 people with multiple service lines, a full custom platform is defensible. One rule holds at every size: do not rebuild Asana, ClickUp or Jira.
When is off the shelf genuinely the right call here?
Under roughly 15 people with simple retainers and only a few tools, configure HubSpot or a vertical agency platform and stop. At that size the reconciliation work is hours a month rather than days, and spending $60,000 to remove it is a poor trade against spending it on new business. We tell agencies this regularly.
Buy also if your retainers are uniform. If every client is a flat monthly fee with the same included scope, off the shelf reporting plus a well maintained sheet gets you close enough to margin, and the build will not pay back. The complexity that justifies custom work is retainer variety rather than client count.
Do not rebuild project management at any size. Your delivery team already trusts Asana, ClickUp or Jira and opens it every morning. Rebuilding it adds months, adds cost and loses buy in, and in our experience the agencies who tried spent a large share of the budget recreating features nobody had asked them to change. Replace the delivery tool only if it genuinely cannot model your work, which is rare.
Keep accounting where it is too. Nobody should pay a development team to rebuild a general ledger when Xero or QuickBooks already balances. Push journals, do not rebuild books.
The honest test before anyone writes a proposal: can your owner name the three least profitable clients without opening a spreadsheet. If yes, the seams in your stack are not costing you enough to justify engineering. If the answer is that nobody actually knows, keep reading, because that is the question this whole category exists to answer.
When does a custom build actually pay off?
Off the shelf systems were built for one motion: a representative moves a deal through stages until it closes, and then the tool's job is done. Agencies do not work that way. The moment a proposal is signed the real relationship starts, with a retainer that renews monthly, a scope that creeps, a delivery team burning hours and a margin that quietly erodes. Salesforce and HubSpot treat the closed deal as the finish line. For an agency it is the starting gun.
The pain shows up in the seams. New business sits in one system, delivery in Asana, ClickUp or Jira, hours in Harvest, Toggl or Clockify, and invoices in QuickBooks or Xero. Nobody owns the join, so the account director cannot see that the client paying a $6,000 retainer is consuming $9,000 of team time. Margin per client is the question an agency owner most needs answered and the one no single generic tool answers.
The signals are specific. An operations manager assembles a profitability view in a spreadsheet every month. An account director checks retainer consumption by eye. Somebody reconciles what was contracted against what was billed. And, the number that usually decides it, your owner can name a retainer that ran two thirds over its included hours for a year before anyone noticed. That single relationship is often larger than the whole build, and it is the honest comparison rather than the subscription line.
The second trigger is structural. Once your project and time tools are locked in and will not change, the join between them is permanent work that no vendor has a commercial reason to build, because deep synchronisation into a competitor's ecosystem is not on anyone's roadmap. A permanent gap is a sound thing to own rather than to wait for.
How do they compare on the things that matter in this industry?
- Retainer as a data model. Generic systems model a deal that closes once. A retainer is a recurring relationship with a monthly value, a renewal date, included hours or deliverables, and a consumption rate that can exceed what the client pays. There is no native concept of hours burned against a retainer, so scope creep stays invisible until the margin is gone.
- Retainer variety. Flat monthly with included hours is simple. Tiered retainers with rollover, deliverable based retainers where hours are irrelevant, and media spend percentage arrangements each need their own consumption model, and agencies with several service lines usually carry all three.
- Where hours live. Profitability depends on logged hours mapped to a retainer or project line. That mapping crosses two products, so it exists in a spreadsheet in almost every agency and gets rebuilt monthly by hand.
- Pipeline stages. Abstract qualified, proposal, won stages mean little to a shop whose real steps are discovery call, scope drafted, proposal sent, verbal yes, contract out, kickoff scheduled. Renaming picklists gets you part of the way and does not connect the scope drafted at deal stage to what was sold.
- Integration direction. Reading project status and hours is a scheduled job with error handling. Writing back means reconciling two systems that both believe they own the record, which is roughly double the work and where most agency builds overspend.
- Per seat economics. Your customer relationship management (CRM) seats, delivery seats and time tracking seats all scale with headcount, so growing the team costs you more forever. Compare against your own invoice and your hiring plan rather than a published rate.
What does total cost of ownership look like at your scale?
These bands reflect Digital Heroes delivery experience. An entry build runs $45,000 to $65,000 over 3 to 4 months: pipeline stages that match how you actually sell, client and project records, retainer fields maintained by hand, and one read only integration with your project management tool. It is a real system and it will not answer the margin question yet.
The standard band is $70,000 to $110,000 over 4 to 6 months and it is where most agencies should land, adding time tracking synchronisation, retainer consumption alerts when a client crosses into scope creep, scope and proposal linkage so what was sold becomes the source of truth, and margin reporting per client, per project and per account manager. The full platform is $110,000 to $180,000 over 6 to 9 months with two way synchronisation across project, time and accounting tools, invoicing triggers, multi team dashboards and role based access.
A 38 person agency running Asana, Harvest, Xero and HubSpot lands at roughly $102,000, of which $19,000 is the retainer object with consumption tracking, $26,000 is the two integrations, $13,000 is margin reporting with scope creep alerts and $8,000 is migration plus a four week parallel run. A 16 person agency with one read only integration and no proposal linkage lands nearer $48,000.
Running costs are 15 to 20 percent of build cost a year. Infrastructure is modest at $150 to $400 a month, because agency data is small and traffic is light. The bulk of that figure is integration upkeep: Harvest, Asana, Xero and the rest change their interfaces on their own schedule and each change is a few days of attention. Get a clear answer during selection about who does that work and how it is billed. Add onboarding too, since a custom system has no public documentation and your team writes the training material once.
What does the hybrid look like, and when is it the honest answer?
The hybrid is the recommendation here, not a compromise, and it has two dimensions.
The first is what you build. The custom system owns pipeline, retainers, proposals and profitability. It reads delivery status from Asana, ClickUp or Jira and hours from Harvest, Toggl or Clockify, and it pushes journals to Xero or QuickBooks. Nothing your delivery team touches daily changes, which is what protects adoption.
The second is direction. Start read only. A one way pull of project status and logged hours delivers the margin report you cannot get today, at roughly $10,000 to $16,000 per integration. Two way synchronisation is roughly double and it is a phase two decision you will make better once people are using the reports. Most agencies do not need the write direction in year one, and the ones that buy it up front are paying to reconcile records nobody has yet disagreed about.
There is a narrower version that is underrated. The retainer and profitability layer alone, sitting on top of whatever system you already use, runs $30,000 to $50,000 over six to eight weeks: a retainer object with monthly value, renewal date, included hours or deliverables and live consumption tracking, plus margin reporting fed from your time tool. It answers one question, which is which clients make money, and it leaves your sales tooling untouched. For an agency whose pain is margin blindness rather than pipeline chaos, that is the whole project.
Two rules keep any of these on budget. Integrate project management and time tracking first, because together they produce the report you cannot get. And clean your client list before migration, because most agency data carries the same company under three spellings with contacts attached to whichever one was typed that day. That cleanup is your team's work and it costs nothing if it happens during discovery.
Which should you choose, by operator size and stage?
Under 15 people, simple retainers, few tools: configure HubSpot or a vertical agency platform. Spend the difference on new business and revisit at 20 people.
Uniform retainers at any size: buy. If every client is a flat fee with the same included scope, a maintained sheet closes the reporting gap and the build will not pay back.
Fifteen to 50 people, margin visibility a real and costly problem, project and time tools locked in: build the integration and reporting layer at $70,000 to $110,000 and keep the delivery tool. This is the highest return version of this project and it is what we recommend most often.
Any agency whose pain is specifically margin rather than pipeline: build the $30,000 to $50,000 retainer and profitability layer on top of your existing system. It is the cheapest credible answer to the question that matters and it ships in six to eight weeks.
Above 50 people with multiple service lines where off the shelf reporting cannot model how you make money: the full platform at $110,000 to $180,000 is defensible and usually pays back. Insist on a fixed discovery phase before a fixed build quote, with a one page diagram showing every field moving between every system as the deliverable. Any firm quoting a full price before mapping your data is guessing. A vendor who does not ask about your retainer structures before your technology stack will build a generic system with your logo on it.
When the shortlist is down to two and you need a tiebreaker, Digital Heroes has delivered more than 2,000 projects with a named team you can speak to before you sign, rather than a bench you meet in month two. Nothing about that commits you to the build.
The evidence behind this guide
Independent findings on why this investment pays off. Every link goes to the primary source.
- Nucleus Research's re-examination of 63 case studies found CRM returns an average of $3.10 for every dollar spent, a 37% decline over the prior decade from $4.90. Source: Nucleus Research (2023) →
- The right combination of digital transformation actions can unlock as much as US$1.25 trillion in additional market capitalization across Fortune 500 companies, while the wrong combinations put more than US$1.5 trillion at risk; companies with all three core factors (strategy, aligned technology, and change capability) saw a 5% market-value lift relative to peers. Source: Deloitte (2023) →
- Almost half of all the activities people are paid almost $16 trillion in wages to do in the global economy have the potential to be automated by adapting currently demonstrated technologies. Source: McKinsey Global Institute (2017) →
- The EY survey of 508 payroll professionals at U.S. companies with 250-10,000 employees quantifies the direct and indirect cost of payroll inaccuracy, reinforcing the ROI case for payroll automation; the study is the original source of the frequently cited $291-per-error figure. Source: BusinessWire / EY (Ernst & Young) (2022) →
Frequently asked questions
What does it cost to switch off HubSpot or Salesforce later?
Around 8 percent of a build in the worked example above. Clients, contacts, open deals, active retainers and project history migrate. Closed opportunities from years ago usually should not, and leaving them behind is a decision rather than a loss.
What goes wrong is duplication rather than export. Most agency data carries the same company under three spellings with contacts attached to whichever one was typed that day. Cleaning that is your team's work and it costs nothing extra if it happens during discovery instead of during migration.
What happens if our project or time tracking tool changes its pricing?
Model it against your hiring plan rather than today's invoice, because customer relationship management seats, delivery seats and time tracking seats all scale with headcount. Growing the team costs you more on every line forever, which is the exposure rather than any single increase.
A custom layer does not remove those subscriptions, since you keep the delivery and time tools deliberately. What it removes is the per seat cost of the reporting layer itself, and it means a repricing on one tool becomes a decision about that tool rather than about how you see your business.
How long does an agency CRM build take?
Three to four months for an entry build, four to six for a standard one, and six to eight weeks for the retainer and profitability layer alone. Discovery and data mapping is three to five weeks of that and around 9 percent of the cost.
The build is rarely the bottleneck. Data migration and getting account managers to actually use the new tool are, so plan a parallel period where old and new overlap and treat the first month after launch as part of the project. Adoption depends on account directors seeing their own numbers in it early.
Is HubSpot cheaper than a custom agency CRM?
Under roughly 15 people with simple retainers, yes, and it is the right answer. Configure it properly and spend the difference on new business, because a custom build at that size solves a problem two spreadsheets already solve.
The comparison changes when margin visibility becomes costly. HubSpot treats the closed deal as the finish line, so it has no native concept of hours burned against a retainer, which is exactly the number an agency owner most needs. That is a data model difference rather than a configuration one.
Should the custom system replace Asana, ClickUp or Jira?
No, and this is the clearest rule on the page. Your delivery team already trusts the tool they open every morning, and rebuilding it adds months, adds cost and loses buy in. The agencies who tried spent a large share of the budget recreating features nobody asked them to change.
The stronger pattern is a custom system owning pipeline, retainers, proposals and profitability, reading delivery status and hours from the tools you keep. Replace the delivery tool only if it genuinely cannot model your work, which is rare.
Which integration should we build first, and what does each cost?
Project management first, then time tracking. Project management makes client to project linkage real, and time tracking supplies the hours profitability depends on, so those two together produce the report you cannot get today. Accounting, email and electronic signature are secondary, and agencies that sequence them first end up with an expensive contact database.
Budget roughly $10,000 to $16,000 per integration read only. Two way synchronisation is roughly double, because you are reconciling two systems that both believe they own the record and writing the rules for when they disagree.
Can we build only the retainer and profitability layer?
Yes, and it is underrated. A retainer object with monthly value, renewal date, included hours or deliverables and live consumption tracking, plus margin reporting fed from your time tool, runs $30,000 to $50,000 over six to eight weeks.
It sits on top of whatever system you already use rather than replacing it. What it answers is which clients make money, and that changes how you price and which relationships you renew. Be sceptical of anything cheaper that claims to be a full agency platform.
How do we build the business case if our owner will not fund reporting?
Put a full year on one page: your customer relationship management seats, delivery seats, time tracking seats and any professional services automation module, noting that all of them scale with headcount. Then count the reconciliation, meaning the operations manager assembling a monthly profitability view, the account director checking consumption by eye, and the finance person matching contracted against billed.
Then add the number that actually decides it. Take the clients you discovered late were unprofitable and the retainers where consumption drifted for months. A single retainer running two thirds over for a year is usually larger than the whole build.
How much should a small business budget for its first custom app or website?
For a focused first build, most small businesses land between $8,000 and $60,000: roughly $8,000 to $45,000 for a custom website and $25,000 to $60,000 for an internal tool or simple web app, based on Digital Heroes delivery across 2,000+ projects. Customer-facing products with payments, logins, or a mobile app start around $40,000. Quotes far below these bands usually mean a template with your logo on it, not software shaped around your workflow.
What are the biggest mistakes first-time software buyers make?
Choosing the lowest bid, paying more than 30-40% upfront instead of on milestones, skipping a written specification, and having no maintenance plan for after launch. The most expensive of the four in Digital Heroes rescue projects is the missing spec: without written acceptance criteria, done becomes an argument instead of a checklist, and every disagreement resolves in the vendor's favor. Fix those four and you have avoided most of the ways these projects fail.
Can a custom CRM integrate with QuickBooks, Gmail, and our phone system?
Yes, and integrations are usually the main reason to go custom: QuickBooks, Gmail and Outlook, Stripe, Mailchimp, WhatsApp, and VoIP platforms like Twilio all have stable APIs we wire into CRMs routinely at Digital Heroes. Each standard integration adds roughly $2,000 to $6,000 and one to two weeks to the schedule. The expensive ones are legacy systems with no API, which need file-based syncs or database-level connections, so flag those in the first conversation.
Can we migrate years of data out of our current system into new custom software?
Almost always yes, through CSV exports or the vendor's API, and migration should be scoped as its own workstream with field mapping, a dry run, and a planned cutover window rather than an afterthought. The real time sink is rarely moving the data; it is cleaning it, since years of duplicates, free-text fields, and inconsistent formats surface all at once. Pull a full export from your current vendor before committing to anything new, because some SaaS plans restrict exports on lower tiers.
Is Zoho or Pipedrive good enough for a small sales team, or should we build custom?
For a straightforward pipeline they are genuinely good and cheap: Zoho CRM Standard starts at $14 per user per month billed annually and Pipedrive Essential is priced about the same. They stop being enough when you need custom objects, industry workflows like job scheduling or inventory-linked quoting, or deep hooks into an internal system. If your team exports to spreadsheets every week to do the real work, the tool has already failed and custom is worth pricing.
Who owns the code when an agency builds my software?
You should, completely, through a written intellectual property assignment that transfers everything on final payment; without that clause, copyright stays with whoever wrote the code by default. Insist that the repository lives in your own GitHub organization from day one and that hosting, domains, and third-party accounts are registered to you. Also check for licenses to the agency's proprietary frameworks buried in the contract, because those can make switching vendors practically impossible even when you own your own code.
What tech stack should a custom CRM be built with?
Boring and mainstream wins: React or Next.js on the front end, Node.js, Python, or Laravel on the back end, PostgreSQL as the database, hosted on AWS or a managed platform. Any of those combinations will run a CRM for a decade; what actually matters is that the stack is common enough for other developers in your market to take over. Treat an exotic stack choice as a red flag, because it usually serves the agency's convenience rather than your continuity.
How many developers does it take to build a custom CRM?
A typical build runs with 4 to 5 people at partial or full allocation: a project lead, one or two developers, a designer, and a QA tester, with design and QA tapering after the middle sprints. Teams larger than six rarely make a CRM ship faster and often slow it down, so do not pay for a bench. On your side, plan for one decision-maker spending 2 to 4 hours a week, because slow client feedback delays more projects than slow code does.
How do I vet a CRM development agency before signing a contract?
Ask to see two live CRMs they built for businesses your size and talk to those clients about what happened after launch, not during the sales process. Then pin down three specifics: who owns the code (you should, fully, on final payment), what a change request costs after go-live, and how they plan data migration. An agency that cannot walk you through a migration plan on the first call will improvise yours.
What happens to my software if the agency shuts down or we stop working together?
Nothing dramatic, if the engagement was set up correctly: the code sits in your repository, hosting runs on your cloud account, and a handover document explains how to deploy and operate the system. Any competent replacement team can then take over in days rather than months. If the agency controls the repo, the servers, or the domain, fix that now, because renegotiating access during a dispute is the most expensive place to discover the problem.
Who can build a custom CRM software system?
Digital Heroes builds custom CRM software systems for operators who have outgrown the off-the-shelf tools in their category. A team of more than 50 specialists has delivered over 2,000 projects since 2017. Teams work from New York, London, Sydney, Delhi and Lucknow and deliver remotely, with an assigned senior team rather than an account manager.
Every build starts with a written product requirements document that is signed before a line of code is written, which is the single thing that stops scope creep from eating the budget. Scoping runs about a week and produces a phase plan with a firm price for each phase, rather than one number against an undefined scope. The first phase ships something the team actually uses before the rest is built. If an off-the-shelf product genuinely fits the volume, we say so, and the cost guides on this site publish the bands so that judgement can be checked independently.
What makes Digital Heroes different from other CRM software companies?
Four things that competitors in this bracket cannot simply copy. Digital Heroes runs a YouTube channel with more than 2.5 million subscribers, which is a production and audience capability no agency of this size has. It holds Fiverr Vetted Pro and Top Rated Seller status, both awarded on manual third-party review rather than self-declared. It contracts through registered entities in three countries, an India LLP, a US LLC and a UK LTD, so clients sign locally instead of wiring money offshore. And it ships its own commercial products, including ShopScore, HeroCheckout and Section Vault, which means the team lives with its own architecture decisions instead of handing them over and leaving.
Two more that show up in the work. Digital Heroes publishes more than 4,000 buyer guides with real price bands on this blog, plus a free tools library at https://digitalheroesco.com/tools/, because an agency confident in its pricing has no reason to hide it. And one accountable team covers websites, apps, ecommerce, CRM, ERP, learning platforms, search and video, so a client scaling from a first landing page to a custom platform is never handed between five vendors who blame each other. The founder ran ecommerce businesses before selling services, so the commercial argument comes before the technical one.
How can I check Digital Heroes is legitimate before getting in touch?
Verify it independently rather than taking the site's word for it. The YouTube channel is at https://youtube.com/@DigitalMarketingHeroes, the Fiverr profile at https://www.fiverr.com/shreyanshsin261, and the Upwork profile at https://www.upwork.com/freelancers/shreyanshsingh. Client reviews sit on Clutch at https://clutch.co/profile/digital-heroes-0 and Trustpilot at https://www.trustpilot.com/review/digitalheroes.co.in, and the company page is at https://www.linkedin.com/company/digital-heroes-1/.
Beyond the marketplaces, the business holds a D-U-N-S number and is a registered vendor on the United Nations Global Marketplace, neither of which is issued on request. Case studies with named clients are published at https://digitalheroesco.com/case-studies/. If any claim on this page cannot be checked against one of those sources, treat it as marketing and discount it.
Related guides
More from Olivia.
Performance Marketing Lead · New-york · 4 posts on the site
Published · Last updated .
