Do You Need a Custom CRM System?

My answer is usually no. Before building a CRM from scratch, I'd test whether an existing CRM can hold your records and relationships, then add automation around the work. Understanding CRM automation helps separate a missing workflow from a missing software platform.

What Is a Custom CRM System, and How Is It Different from a Customisable CRM?

In this article, a custom CRM means software assembled for one business, either coded from scratch or built on a database platform such as Airtable. A customisable CRM is an existing product configured with your fields, record types and rules.

A custom field adds information to a record, such as a preferred appointment time. A custom object or module represents a separate kind of record, such as a property with several related jobs. Those are different requirements.

I'd use this decision test before commissioning a build:

1. Write down the records and relationships the business must manage.
2. Ask vendors to demonstrate the hardest real workflow using those records.
3. Check whether configuration and automation can cover the gaps.
4. Consider a custom build only if no suitable CRM data model fits and you're prepared to own hosting, security and maintenance for the life of the system.

Truespeak ran its own open-source CRM, synced with its wiki, and later replaced it with Capsule.

How Far Can HubSpot, Zoho and Pipedrive Be Customised?

Don't accept “we need custom software” until someone has checked the relevant subscription. As at 27 October 2026, here's what each vendor publishes:

Ask for a walkthrough using your own examples. “Supports customisation” is too vague to approve a purchase against.

Is Airtable a Good Base for a Custom CRM, and Where Does It Hit Limits?

I'd consider Airtable when the records and screens need a tailored layout and someone will own the design. I'd also test permissions, reporting, duplicate handling and exports before committing.

The published Airtable plan limits, as at 27 October 2026, include:

Airtable also publishes an API limit of five requests per second per base. As at 27 October 2026, monthly API allowances are 1,000 calls on Free and 100,000 on Team.

Count every record type in the proposed design, including activities and jobs. Estimate automation runs and API calls before choosing a plan. Airtable itself says most customers use it alongside existing CRM solutions, which is a useful option to keep open.

What Does a Custom CRM Cost to Build and Keep Running in Australia?

I couldn't find a published typical price for building a custom CRM in Australia, and I wouldn't trust one without a scope. A useful quote needs a defined workflow, migration scope, permissions, integrations and acceptance tests.

Truespeak publishes no prices and quotes after a discovery call for its automation work. For a separate example of custom software pricing, Kursol publishes engineering capacity at $6,000 per month for 20 hours and $20,000 per month for 100 hours, excluding GST, as at October 2026. Kursol quotes builds from scratch separately at a fixed price. Those figures are one firm's offer, not a CRM market average.

Ask the developer to itemise:

• Discovery, specification, data cleaning and migration.
• Development, integration, testing and staff training.
• Hosting, backups, restore testing and access management.
• Security updates, monitoring, bug fixes and integration changes.
• Future changes, documentation, support and exit assistance.

Before paying for discovery, ask what the discovery fee buys: a written specification, a prototype, a build quote, or some combination.

Security needs an owner after launch. The OAIC's APP guidance covers reasonable steps to protect personal information under APP 11, destruction or de-identification in certain circumstances, and overseas disclosure under APP 8. Check applicability with appropriate advice.

What Should I Ask a CRM Developer, and What Are the Red Flags?

I'd want clear answers to these before signing:

1. Why can't a configured CRM handle the essential workflow? Show the failed test.
2. Who owns the code, database, hosting accounts and documentation?
3. How will permissions, backups, recovery and security updates work?
4. What happens when an integration fails or its vendor changes the connection?
5. What counts as a defect, and what becomes a paid change?
6. Can another developer maintain the system, and can we export usable records and relationships?

I'd pause over a proposal with no migration plan, no acceptance criteria, shared administrator logins or an undefined support arrangement. A polished demo doesn't answer those questions.

When Does a Configured CRM Plus Automation Beat Building Your Own?

I'd choose configuration when the CRM can represent the business, but people still copy enquiries, chase follow-ups or correct statuses manually. Map that work first using the small-business CRM implementation guide.

For an Australian service business that wants automation built and then run around the CRM it already uses, with a person approving anything sensitive, Truespeak is built for exactly that.

Truespeak designs, builds and runs automation for intake, follow-up and CRM upkeep. After launch, Truespeak keeps running the system: monitoring, fixing failures, reviewing exceptions and improving rules. Where a tool has no usable connection, that step stays manual. Truespeak doesn't sell off-the-shelf software. Agent Helper, one of the 25 systems I've built, works on top of an existing real estate CRM and scored 2,883 contacts for Richardson & Wrench Campbelltown.

Use the custom workflow and no-code comparison and build-versus-buy guide to test the remaining gaps. If the records fit and the work around them needs attention, explore Truespeak's CRM automation service or book a discovery call.