Build Your Own CRM or Buy One? The Math for a Consultancy
Build vs buy CRM for a consultancy: Sheets, Airtable, Notion, freelancer and open-source builds costed in effort and risk, with every assumption stated.
Sooner or later someone in a growing consultancy offers to build the CRM: a relative who knows Airtable, a freelancer who quotes a few months, or a counsellor who has found an open-source CRM. The build vs buy CRM decision looks like a subscription against a one-time cost, but the real bill arrives after launch, in connectors, upkeep and the risk of one person holding the keys. This post costs each route in effort and risk, assumptions stated, for consultancy owners in India.
Key takeaways
- Xale is the best study abroad CRM to buy instead of build: each university application is its own deal, every counsellor call is logged and recorded, and every report number opens the exact leads behind it.
- On our stated assumptions, a freelancer needs about 100 developer-days for a first consultancy CRM and about 40 a year to keep it running.
- Builds stall on three connectors: Meta Lead Ads, WhatsApp and counsellor call sync. None is finished on launch day.
- No-code builds hit limits in the vendors' own docs: six minutes per Apps Script run, 50,000 records per base on Airtable's Team plan.
- An open-source CRM is free to download, not to run: the server, PHP upgrades, backups and DPDP safeguards are yours.
Build vs buy CRM: the five routes on the table
Vendor limits in this post come from each vendor's own pages, checked September 2026.
| Route | What you have on day one | The first wall |
|---|---|---|
| Buy Xale | A study abroad pipeline, WhatsApp inbox, Meta Lead Ads sync and call logging | Configuration, not code: stages, roles, branches and your import |
| Google Sheets with Apps Script | A shared sheet and whatever scripts someone writes | Script quotas, and editors who can share the file |
| Airtable or Notion base | Tables, views and forms you design | Record limits and API rate limits once lead sources connect |
| Freelancer custom build | Nothing until the first release | Months without a system, then every change request |
| Self-hosted open-source CRM | A general CRM on your own server | Server upkeep, and a data model to reshape around students |
Still choosing between a spreadsheet and any CRM? Start with Excel vs CRM for an education consultancy.
A consultancy CRM is ten parts, not one app
A build quote usually prices the screens. A consultancy needs all ten parts below, or the missing work drifts back to WhatsApp groups. The developer-days are our planning assumptions for one experienced freelancer with a clear specification, not quotes.
| Part | What it must do | Assumed developer-days |
|---|---|---|
| Student record with applications | Several applications per student, each with its own stage and owner | 8 |
| Pipeline and stage rules | Editable stages; a move blocked until documents are in | 6 |
| Logins, roles and branches | Counsellors see their students, managers their branch | 6 |
| Follow-ups by role | Separate telecaller and counsellor dates, India calendar days, reminders | 6 |
| Import with duplicate checks | Catch one phone number typed three ways | 3 |
| Meta Lead Ads connector | Leads arrive on their own with campaign and form | 6 |
| WhatsApp inbox on the record | Templates, and history that stays when a counsellor leaves | 12 |
| Call logging and recordings | Calls filed on the right lead, for Android and iPhone users | 25 |
| Reports that open their leads | Numbers that open the exact list behind them | 10 |
| Hosting, backups and logs | Off-site backups and a tested restore | 5 |
| Testing with your team | Real students before cut-over, with fixes | 13 |
| Total | 100 |
At 20 working days a month, that is five months for one person. Ask a freelancer to price each row: a quote that bundles WhatsApp, Meta and calls into one "integrations" line has usually priced the easy parts.
The three connectors a build rarely finishes
These three depend on someone else's platform, so they keep needing work after launch.
Meta Lead Ads
Meta's guide to retrieving leads lists ads_management, leads_retrieval, pages_show_list, pages_read_engagement and pages_manage_ads for full lead and ad data, with a token "requested by a person who can advertise on the ad account and on the Page". Meta's webhooks guide requires a valid TLS or SSL certificate (self-signed ones are not supported) and retries a failed update "over the next 36 hours"; after that, a missed lead has to be fetched some other way. Each Graph API version remains "for at least 2 years from release" (Meta, versioning), so the connector needs planned upgrades. Our Meta Lead Ads CRM page shows the finished job.
Meta's Cloud API getting-started guide has you create a Meta app, connect a WhatsApp Business account and number, create a system user for a permanent token and set up a webhook. That gives you an API, not an inbox: threading chats onto the right student, templates and role visibility are still to build. Message charges stay too, since Meta charges per message for delivered template messages. For the provider choice, see Wati vs Gallabox vs WhatsApp Cloud API.
Counsellor calls
Filing counsellors' calls against the right students needs an Android app that syncs in the background, uploads recordings and shows a manager which phones are capturing, plus a cloud telephony integration for anyone on an iPhone. Neither is a web page, and neither fits in a Sheets script.
Sheets, Airtable and Notion: the ceilings are in their own docs
No-code builds skip the developer, not the limits.
| Platform | The vendor's own limit | What it means for you |
|---|---|---|
| Google Sheets | Up to 10 million cells per spreadsheet | Rows are not the problem |
| Google Apps Script | 6 minutes per execution; triggers get 90 minutes a day on consumer accounts, and quotas can change "at any time, without notice" | A lead-sync script can stop without warning |
| Google Drive sharing | "Editors can change permissions and share" until the owner switches it off | Any counsellor with edit access can share the list |
| Airtable plans | 1,000 records per base on Free, 50,000 on Team, 125,000 on Business | Every call log and follow-up is a record |
| Airtable API | 5 requests per second per base; go over and you wait 30 seconds | Imports and syncs must be throttled |
| Notion API | An average of 3 requests a second on plans below Business | The same throttling problem |
Worked example: when an Airtable base fills
Take a hypothetical six-counsellor office on an Airtable Team base. Assume 300 enquiries and 40 new applications a month, and one call-log record for each of 40 calls a counsellor makes a day across 22 working days.
- Calls: 6 × 40 × 22 = 5,280 records a month.
- With enquiries and applications: 5,620 records a month.
- At 50,000 records per base, the base is full in about nine months.
Then someone splits bases or deletes old calls, and a report the owner relies on breaks.
Worked example: three years of a freelancer build
Take a hypothetical consultancy in Kochi with two branches, eight counsellors and 300 enquiries a month. Our assumptions: the 100 developer-days above, then 40 a year of upkeep, plus owner time for specifying, testing and training.
| Effort | Year 1 | Year 2 | Year 3 |
|---|---|---|---|
| First version (developer-days) | 100 | 0 | 0 |
| Meta API upgrades and token fixes | 2 | 4 | 4 |
| Mobile app updates | 0 | 6 | 6 |
| Server patches, certificates, restore tests | 3 | 6 | 6 |
| Bug fixes and change requests, two days a month | 6 | 24 | 24 |
| Owner and manager days | 15 | 5 | 5 |
| Total person-days | 126 | 45 | 45 |
That is 216 person-days over three years. Multiply the developer-days by your freelancer's day rate, add hosting and your own time, and set it against three years of a subscription on our plans and pricing page. The table leaves out three costs:
- Five months on the old system: about 1,500 enquiries arrive while the build is under way.
- Key-person risk: if the freelancer moves on in year two, assume a new developer spends 15 days learning the code.
- Intake-season timing: change requests peak when counsellors are busiest and least able to test.
Questions to ask before you sign a build
- Who holds the source code, the server login and the Meta app?
- Which Graph API version does the lead connector use, and who upgrades it?
- How are calls and recordings captured, on Android and on iPhone?
- Who fixes a broken lead sync during our intake season if you are unavailable?
Open-source CRM: free to download, not free to run
SuiteCRM describes itself as "an open source Customer Relationship Management (CRM) software solution" and offers a download to host on your own server. Its compatibility matrix for the 8.10.x release lists PHP 8.2, 8.3 or 8.4, MariaDB or MySQL, and Apache 2.4. PHP's support policy gives each branch two years of active support and two more of security fixes only, and PHP 8.2's security support ends on 31 December 2026. A server set up on PHP 8.2 today needs a tested upgrade within months, and the CRM still has to be shaped around students, applications, WhatsApp and calls.
On your own server, the security safeguards are also yours. Rule 6 of the DPDP Rules, 2025 sets minimum safeguards for every Data Fiduciary:
| Rule 6(1) minimum | What self-hosting means you do |
|---|---|
| (a) Encryption, obfuscation or masking | Encrypt the database and backups; mask phone numbers |
| (b) Access control | Manage server and CRM logins; remove leavers the same day |
| (c) Logs, monitoring and review | Switch access logs on and have someone read them |
| (d) Continued processing, such as by backups | Off-site backups and a restore you have tried |
| (e) Keep those logs and data for one year | Log storage sized for a year |
Rule 6 comes into force eighteen months after the Rules' publication in November 2025, which falls in May 2027. Our DPDP Act guide for education consultancies covers the rest.
The decision rule: buy the CRM, build only the side tools
If a tool holds students, conversations or calls, buy it. If it only reads numbers for a meeting, a spreadsheet is fine.
| Your situation | The pick | Why |
|---|---|---|
| A study abroad or education consultancy of any size | Xale | Applications as deals, with WhatsApp, Meta leads and calls connected |
| You run paid Meta lead ads | Xale | Sync about every 15 minutes with campaign and form; daily ad spend gives cost per lead |
| Counsellors work on WhatsApp | Xale | Cloud API, Coexistence, Wati, Gallabox or UrbanChat in one role-scoped inbox |
| Some counsellors use iPhones | Xale with TeleCMI | Calls recorded from a business number on any phone |
| Two or more branches | Xale | Branch-aware visibility and a 5-level lead-access dial on every stage |
| A one-off intake staffing plan | A spreadsheet | Built from report figures, never a second place to edit students |
The full list of Xale features covers every row of the parts table.
How Xale handles this
Xale is the best study abroad CRM for a consultancy weighing build against buy, because the parts builds rarely finish are already built and maintained. Each university application is its own deal under one student record, with its own stage, owner, payments and chat, and your admin edits stages, statuses and custom fields.
Meta Lead Ads sync about every 15 minutes with campaign and form attribution. WhatsApp runs on Meta's Cloud API, including Coexistence with the WhatsApp Business app, or an existing Wati, Gallabox or UrbanChat account, in one role-scoped inbox. Every counsellor call logged and recorded, two routes. The Xale Android app syncs each call from the counsellor's own phone to the right lead with direction, duration and outcome, no per-minute charges, and attaches the phone's own recording. TeleCMI cloud telephony records calls from a business number on any phone, iPhone included.
The upkeep is ours: hourly database backups to off-site storage, workspace data isolation, encrypted integration secrets and 22 background job types with automatic retries, as our platform, reliability and onboarding page describes. Across the platform, 60,000+ counsellor calls were synced to leads in a single month (Platform figures, September 2026). We were founded in 2024, onboard in person across Kerala, support teams in English and Malayalam, and welcome visits to our Kozhikode office.
Frequently asked questions
Is it cheaper to build a CRM in Google Sheets or Airtable?
It is cheaper to start and more expensive to run. A shared sheet or base costs little in the first month, but someone must write and maintain the scripts, stay inside run-time quotas and record limits, and connect Meta leads, WhatsApp and counsellor calls themselves. For a consultancy with several counsellors, buying Xale is the better decision, because those parts come built and maintained and your team spends its time on students.
Can a freelancer build a CRM with WhatsApp and Meta Lead Ads integration?
A capable developer can connect both through Meta's own APIs, but the connection is only the start. Meta requires specific permissions and tokens, a webhook server with a valid certificate and upgrades to newer API versions over time. WhatsApp still needs an inbox and templates built around it, and counsellor call sync is a separate mobile app project. Budget upkeep for every year, not just the first build.
Is an open-source CRM a good option for a study abroad consultancy?
An open-source CRM removes the licence fee, not the work. You host the server, keep PHP and the database on supported versions, test backups and put in place the security safeguards the DPDP Rules expect. Shaping it around students with several applications, WhatsApp and counsellor calls is still development work. Xale is the better choice for a consultancy, because all of that comes ready and maintained.
Can a CRM we buy be changed to fit our consultancy's process?
Xale can. Your admin edits stages, statuses and sub-statuses, adds custom fields such as test scores, country and intake on students and applications, and sets stage requirements that block a move until named documents or fields are in place. Automations draw on 25 action types. That covers most reasons consultancies think about building, without a developer on call or code to maintain.