CRM fundamentals

Why it matters

Every business has a CRM; the question is whether it is a system or the owner’s memory. Memory does not scale, cannot be handed to a new hire, and forgets to follow up. A working CRM means no lead is lost because someone was on leave, every quote gets followed up, and the pipeline and forecast come from real data. It is also the foundation for marketing automation, customer service history and the account management that keeps customers paying for years.

What a CRM does, in plain terms

A CRM stores records of people (contacts) and the businesses they belong to (companies or accounts). Against those records it logs activities: calls, emails, meetings and notes. It tracks deals, each attached to a contact and company, with a value, a stage and an expected close date. On top of that sit tasks and reminders, and reports that total things up: pipeline by stage, activity by person, revenue by source.

Modern CRMs also connect to your email and calendar so that correspondence is logged automatically, to your website so that form enquiries create leads, and to your accounting system so that invoices and payments show on the customer record. None of that is necessary on day one, but it is why a CRM eventually beats a spreadsheet.

Spreadsheet, CRM or full platform

A spreadsheet is a legitimate CRM for a sole operator with a handful of live deals and no team. It stops working when more than one person needs to update it, when you have more than about thirty live opportunities, when follow-ups start slipping, or when you want to know how many enquiries you had last quarter and cannot answer.

Entry-level CRMs are inexpensive or free for small teams and cover contacts, deals, tasks and email logging. Full platforms add marketing automation, customer service ticketing, quoting and deep reporting, at a higher price and a much higher configuration cost. Most small businesses should start at the entry level and grow into features as they need them; very few need the full platform in their first two years.

Setting it up without over-engineering

The commonest failure is spending weeks designing custom fields and automations before anyone has logged a call. Start with the default fields, your pipeline stages from your written sales process, and three pieces of information per deal: value, stage and next action date. Import your existing contacts, connect your email, and start using it the same day.

Add only what you will use. A custom field for "lead source" is worth it because you will report on it. Twelve fields for industry sub-categories you will never filter by are not. Rule of thumb: every field should answer a question you actually ask, and every automation should replace something you currently do by hand.

Making it stick

A CRM only works if it is the single source of truth. That means one rule, applied without exception: if it is not in the CRM, it did not happen. Owners have to model this themselves, because a team will not maintain a system the boss ignores. Run your weekly pipeline review from the CRM screen, not from memory or a side spreadsheet, and the data will stay clean because people know it will be looked at.

Make it easy. Mobile apps for logging a call from the car, email integration so nothing is retyped, and templates for common follow-ups remove most of the friction. Review data quality monthly: deals with no next action, contacts with no company, close dates in the past. Fix them in the meeting rather than complaining about them afterwards.

How to choose and implement a CRM

1. Write your sales process first Stages, exit criteria and the questions you want answered. The CRM should fit this, not the other way round.
2. List must-have integrations Usually email, calendar, website forms and accounting. Check each candidate supports them natively.
3. Shortlist two or three entry-level options Prefer tools with Australian support hours, clear pricing and an easy export if you ever leave.
4. Trial with real data for two weeks Import contacts, run your actual pipeline, log real calls. Judge by how it feels on a busy day.
5. Configure the minimum Stages, lead source, a handful of fields, one dashboard. Resist everything else for the first quarter.
6. Set the rule and model it If it is not in the CRM, it did not happen. Run every pipeline review from the CRM.
7. Add automation one piece at a time Each one should replace a manual task you already do: follow-up reminders, enquiry acknowledgements, stale-deal alerts.

Real-world example

A Newcastle signage business gets off the whiteboard

Harbour Signs makes shopfront and vehicle signage for businesses across the Hunter region. Quotes live in the owner’s email, jobs on a whiteboard, and follow-ups in two people’s heads. When a long-term staff member goes on leave, two accepted quotes and a $9,000 fleet job are missed because nobody else knew they existed.

The owner, Sam, writes down the sales process, five stages from enquiry to deposit paid, and sets up an entry-level CRM over a weekend with those stages, a lead source field and email integration. The website quote form now creates a lead automatically. Each Monday the team reviews the pipeline from the CRM dashboard. Within a quarter, follow-ups are happening on time, the business can see that about a third of enquiries come from vehicle signage referrals, and Sam uses the CRM’s customer history to re-contact clients whose signage is three or more years old. Later, with help from SMBH Consulting’s integration team, the CRM is connected to the accounting system so that deposits and final invoices appear on each job record.

Common mistakes

• Buying the platform before writing the process Software will not fix an undefined process; it will just record the confusion. Define stages and rules first.
• Over-configuring on day one Dozens of custom fields and automations nobody uses make the system slow and the team resentful. Start minimal and add on evidence.
• Letting side spreadsheets survive If some deals live elsewhere, the CRM is never trusted. One system, one rule.
• Skipping integrations Retyping emails and enquiries is why people stop logging. Connect email and web forms from the start.
• Ignoring data hygiene Duplicate contacts, missing values and past close dates quietly destroy the value of every report.

KPIs to track

• Logging rate The share of customer interactions recorded in the CRM. Check by sampling a week of calendar and email; aim for close to all of them.
• Deals with a next action Percentage of open deals with a next step and date. Should be 100 per cent after every weekly review.
• Stale records Open deals past their close date or with no activity for a set period. Trend this down to near zero.
• Time to first response From web enquiry created in the CRM to first logged contact. Use the CRM timestamp to measure it honestly.

Frequently asked questions

When is a business too small for a CRM?

Rarely. A sole trader with a few live quotes can use a spreadsheet, but free or low-cost CRMs now do the job with reminders and email logging, and the habit is easier to form early than to retrofit.

How much should a small business expect to pay?

Entry-level tools range from free for very small teams to a modest monthly fee per user. The larger cost is your time setting it up and keeping it current. Check current pricing directly with vendors; it changes often.

Should the CRM connect to my accounting software?

Eventually, yes. Seeing invoices, payments and overdue amounts on the customer record saves time and improves account management. It is usually not necessary in the first few months.

What if my team will not use it?

Usually because it is extra work with no visible benefit. Reduce the work with integrations and templates, make the benefit visible by running every review from it, and apply one rule consistently: if it is not in the CRM, it did not happen.

Key takeaways

• A CRM answers who you spoke to, what was said and what happens next, for everyone in the business.
• Write your sales process first; choose software that fits it.
• Start with an entry-level tool, default fields and your pipeline stages. Add on evidence.
• Connect email, calendar and web forms so logging is automatic.
• One rule, modelled by the owner: if it is not in the CRM, it did not happen.