India
Quick answer
Custom fields hold the parts of your process a CRM did not come with, like visa type, unit status or dealer tier; workflows act when those fields change. Find them by listing the spreadsheets and registers your team keeps outside the CRM. Configure a generic CRM when you need a few extra fields and simple triggers; consider a custom system when you need new kinds of records, rules that depend on rules, outsiders taking part, or workarounds that cost more than the tool.
Key takeaways
- Side spreadsheets and registers show exactly which fields and workflows your CRM is missing.
- Fields hold the process, workflows run it; write every workflow as one sentence first.
- Configure when you need a few fields and simple triggers on existing records.
- Build when you need new record types, dependent rules, outside users or costly workarounds.
Every business that uses a CRM for a few months reaches the same moment. The standard fields are filled in, the pipeline works, and yet the team keeps a side spreadsheet, a WhatsApp group or a paper register for the part of the work the CRM does not understand.
That side system is a signal. It is the part of your process the CRM was not shaped for.
This lesson is about closing that gap with custom fields and workflows, and about how to tell when configuring a generic CRM is enough and when your process deserves a system of its own.
Two Words, Defined
Fields hold your process. Workflows run it. A field without a workflow is a box someone fills in. A workflow without the right field has nothing to react to.
Find the Side Systems
Before adding anything, list every place your team tracks work outside the CRM. Ask each person: “What do you keep somewhere else, and why?”
An immigration consultancy found three: a spreadsheet of document checklists per client, a calendar of visa decision dates, and a register of agent commissions. A real estate agency found a unit inventory in Excel and a site-visit diary on the front desk. A manufacturing distributor found a sample tracker and a sheet of dealer price lists.
Each side system becomes one of two things: a few custom fields with a workflow on the existing record, or a new kind of record linked to the customer. Most become the first.
What a Custom Workflow Looks Like
Take the consultancy’s document checklist. As custom fields it becomes one checkbox per required document on the client record, plus a “documents complete” field. The workflow is a sentence, like every automation rule in this module:
When a client enters “Documents collection” ā create the checklist for their visa type ā every 3 days, remind the client of missing items on WhatsApp and the coordinator in the CRM ā when all items are ticked, move the case to “Application filed” and notify the consultant.
Three things changed. The spreadsheet disappeared. Chasing documents, the stage where Module 2 found most enquiries were lost, now happens on its own. And the owner can see every stuck case on one screen instead of asking each coordinator.
Examples by Industry
Notice what these have in common. In each one, the custom field is the reason the workflow can exist. “Visa type”, “unit status” and “dealer tier” are not extras. They are the business.
When Configuring a Generic CRM Is Enough
Most subscription CRMs let you add custom fields and some workflows. That is the right route when:
- You need a handful of extra fields on the contact or deal, not new kinds of records.
- Your workflows are “when this field changes, create a task or send a message”.
- Nobody outside your team needs to see or update the data.
- The tier that allows it fits your budget at your team size, three years out.
If all four are true, configure. It is faster and cheaper, and Lesson 4 of Module 1 showed how to budget it honestly.
When the Process Deserves Its Own System
Configuration starts to strain when the process itself is what makes your business different. The signs:
- You need new kinds of records, like units, cases, samples or projects, each with its own stages, linked to customers.
- Rules depend on rules: the checklist depends on the visa type, the price on the dealer tier, the next task on the visit outcome.
- Outsiders take part: clients uploading documents, brokers seeing their leads, dealers placing re-orders.
- The workarounds cost more than the tool: add-ons, connector tools and a person whose job is to keep the CRM and the spreadsheets in step.
Two or more of these and you are no longer configuring a CRM. You are building one inside someone else’s product, within their limits, at their price per seat.
What a Custom CRM Project Looks Like
If you choose to have one built, a well-run project for a small business follows a predictable shape:
- Discovery. The three pages from Module 2 (stages, customer record, follow-up rules), plus your list of side systems and the roles from the last lesson.
- A first version on your real data. The pipeline, the record and the one workflow that hurts most today, used by the team for a couple of weeks.
- Adjust from use. Fields removed, workflows changed, based on what the team actually did, not what anyone guessed.
- The rest, in order of hours saved. Integrations, portals, reports, mobile.
- Handover you can live with. You own the data and the system, and changes later are a request, not a migration.
The pages you wrote in this course are most of step one. If you want to see what they look like as a working system, this is what we build, starting from exactly those pages.
Next lesson, the last in this module: measuring whether the CRM is paying back.
Check what you learned
3 quick questions. Pick an answer and see why.
What is the best way to find the custom fields your CRM is missing?
Which situation suggests configuring a generic CRM is enough?
In a well-run custom CRM project, what should come first after discovery?
You finished Lesson 3
Up next Ā· Lesson 4 Measuring CRM ROI: Is It Paying Back? Read the next lesson Previous: Lesson 2 Ā· Roles, Permissions and Keeping Customer Data Safe
Planning a CRM for your business?
We design and build CRMs around the way your team already works. Tell us about your process and we will suggest the simplest setup that fits.
