Before hiring a CRM software development company, settle one question: do you need a custom CRM at all? Most businesses do not. HubSpot, Zoho, Pipedrive and Dynamics cover the ordinary case, and the right developer will tell you so. If you have checked and the answer is still custom, this guide covers what to put in the brief, how to compare developers, what the contract must say, and the Australian privacy obligations that come with holding customer data in a system you own.<\/p>\n
A custom CRM is worth building when your sales or service process is unusual enough that an off-the-shelf product fights it: a quoting process with many steps and approvals, records that have to link to jobs, assets or sites in ways a standard contact-and-deal model cannot, a regulated workflow that must be followed exactly, or integration with a core system that no CRM vendor supports. It is not worth building because the subscription feels expensive, because a vendor’s layout is annoying, or because someone wants “our own system”. Those are configuration problems, and they are much cheaper to fix than a build.<\/p>\n
Ask any developer you talk to whether they would configure an existing CRM instead. If they never say yes, they are not advising you.<\/p>\n
One to two pages. Who uses the system and how many of them. The records it holds (contacts, companies, deals, jobs, assets) and how they relate. The five to ten things people do in it every day, in plain words: “log a call”, “send a quote from a template”, “see every job for a customer”. The systems it must connect to, with the accounting package named. The reports the owner needs. What is wrong with whatever you use now. And the two or three things that make your process different, because those are the reason you are building.<\/p>\n
Leave out technology choices. A good developer will propose those from the brief, and the proposal tells you whether they have understood it.<\/p>\n
Ask for a CRM they built that is still in daily use.<\/strong> Two or more years old, and a phone call with the business that uses it. Not a case study; a conversation about what broke and how it was fixed.<\/p>\n Ask how they handle the first version.<\/strong> A custom CRM should launch with the five daily tasks working well and nothing else, then grow. A developer who proposes building everything in one go is proposing a longer, riskier project.<\/p>\n Ask about data migration.<\/strong> Your contacts and history live somewhere now, probably in spreadsheets and an old system. Moving them cleanly is a project inside the project, and a developer who has not mentioned it has not thought about it.<\/p>\n Ask who owns what.<\/strong> Code, database, hosting account, documentation. The answer is you, from day one.<\/p>\n Ask what happens after launch.<\/strong> Response times, who fixes a bug on a Friday afternoon, how new features are priced, and what you would need in order to take the system to another developer.<\/p>\n Developers price custom work in one of three ways, and each suits a different stage. A fixed price suits the first version, once the scope is written: you know the cost, the developer carries the risk of estimating badly, and changes are priced separately. Time and materials suits work that cannot be scoped in advance, such as untangling old data or integrating with a system nobody fully understands; insist on a cap and weekly reporting. A monthly retainer suits the period after launch, when the business wants a steady stream of small improvements and someone on call. A proposal that is time and materials with no cap for the first version is a proposal to find out what it costs after it is built. Ask for the first version fixed, exploratory work capped, and support on a retainer you can cancel.<\/p>\n The scope, in the same plain words as the brief. A fixed price for the first version, or a clearly bounded time and materials arrangement with a cap. Milestones you can check. Ownership of all code and data by you, with the source code delivered to a repository you control. Where the system is hosted and where the data sits, which for most Australian businesses should be an Australian region. Security requirements: multi-factor authentication, access per person, backups, and access removed when the engagement ends. Handover: documentation, a walkthrough, admin credentials. Support terms and prices for after launch. If any of these is missing, ask before signing.<\/p>\n A CRM is a database of personal information, and in Australia the Privacy Act’s Australian Privacy Principles govern how it is held. APP 11 requires an organisation to take reasonable steps to protect personal information from misuse, interference, loss and unauthorised access, and to destroy or de-identify it when it is no longer needed. The OAIC’s guide to securing personal information<\/a> is explicit that outsourcing the build or the hosting does not move the obligation: if you hold the data, you are responsible for how the developer and the host protect it. That is why the security clauses above belong in the contract. The Australian Cyber Security Centre’s small business cyber security guide<\/a> covers the practical minimum.<\/p>\n Want this as a one-page checklist?<\/strong> Ten things to settle before you hire a CRM software developer, on one A4 page.<\/p>\n Download the checklist (PDF)<\/a><\/p>\n<\/div>\n This is a hypothetical, not a client. Take an equipment hire company in Townsville with 25 staff. Its process links customers to hire contracts, to individual machines, to service history and to invoices in MYOB. Two off-the-shelf CRMs were tried and both treated a machine as an afterthought. The brief describes the records and the eight daily tasks. Three developers respond: one proposes a full build with every feature in six months; one proposes configuring an existing CRM, which the business has already tried; one proposes a first version with the eight tasks and the MYOB link in ten weeks, then monthly additions. The third is the right shape. The contract names the business as owner of the code, puts the data in an Australian cloud region, and sets support terms. Migration of the old spreadsheet data takes a fortnight of the ten weeks and is the part the staff remember.<\/p>\n High10 builds custom CRM systems<\/a> for Australian businesses whose process does not fit the standard products, and configures HubSpot<\/a> and connects CRM automation<\/a> where an existing product will do. We start by telling you which you need. Every project is quoted in writing after a scoping call, you own the code and data from day one, and the first version launches with the daily tasks working rather than everything at once.<\/p>\n Use an existing product unless your process is unusual enough that it fights you: complex quoting and approvals, records that link to jobs or assets in ways a standard model cannot, a regulated workflow, or a core system no vendor connects to. Configuration is far cheaper than a build, and a good developer will say so.<\/p><\/div><\/details> A first version covering the daily tasks and one integration typically takes eight to fourteen weeks, including data migration and testing. Larger systems with several integrations run six months or more. Launching a small first version and adding to it monthly is faster and safer than building everything at once.<\/p><\/div><\/details> That you own the code and data, where the data is hosted, security requirements written into the contract, a scope in plain words, milestones, support terms, and a live system they built two or more years ago that you can ask the owner about.<\/p><\/div><\/details> It depends on the number of record types, integrations and users, and on how much data has to be migrated. We quote each project in writing after a scoping call rather than publishing figures. Our guide to custom CRM development costs<\/a> covers the market ranges.<\/p><\/div><\/details><\/div>\n Want this as a one-page checklist?<\/strong> Ten things to settle before you hire a CRM software developer, on one A4 page.<\/p>\n Download the checklist (PDF)<\/a><\/p>\n<\/div>\n Before hiring a CRM software development company, settle one question: do you need a custom CRM at all? Most businesses do not. HubSpot, Zoho, Pipedrive and Dynamics cover the ordinary case, and the right developer will tell you so. If you have checked and the answer is still custom, this guide covers what to put […]<\/p>\n","protected":false},"author":2,"featured_media":108,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[18],"tags":[],"class_list":["post-109","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-business-systems"],"yoast_head":"\nFixed price, time and materials, or retainer<\/h2>\n
What the contract must say<\/h2>\n
Privacy obligations in Australia<\/h2>\n
A worked example<\/h2>\n
How High10 helps<\/h2>\n
Frequently asked questions<\/h2>
Should I build a custom CRM or use HubSpot or Zoho?<\/h3><\/summary>
How long does a custom CRM take to build?<\/h3><\/summary>
What should I check before signing with a CRM developer?<\/h3><\/summary>
What does custom CRM development cost in Australia?<\/h3><\/summary>
Related reading<\/h2>\n
\n