What to specify in a custom CRM before development starts

A CRM fails when it copies a generic pipeline that nobody’s day matches. Before anyone builds screens, write down how a lead actually moves in your company.

One lead needs a name, a phone number, a source, an owner, a status, and the last thing that happened. Extra fields are useful only if someone will fill them in. If the team will not type “industry” on a busy call, do not make it required. Empty required fields are how people stop opening the tool.

Replace “Qualified” with the words the team already uses. A coaching institute might use: enquiry, demo booked, demo done, fee discussed, joined, not now. A spare-parts counter might use: asked, quoted, waiting on supplier, sold, lost. A custom status list is the main reason to build rather than rent a generic CRM.

Each status needs one meaning. If “quoted” sometimes means a verbal price and sometimes means a PDF, split it. Reports are only as honest as the words.

• What happens when two people save the same phone number. Keep both and flag them, or attach the new note to the existing lead.
• Whether a lead can sit with no owner. If it can, it will.
• Who can see everyone else’s leads. In a four-person team the owner often sees all of them, and everyone else sees their own.

These three rules cause more rework than the colour of the buttons. Write them in sentences before the first screen is designed.

Pick one report. Examples: leads with no next step, leads untouched for seven days, or leads by source this month. A CRM with fifteen charts and no Monday report will not be opened. The first release is successful when that one list is used, not when the dashboard looks finished.

Leave email sync, a WhatsApp inbox, call recording, and commission maths for a later release unless the business cannot record a conversation without them. Those are products of their own. The first release should make the pipeline trustworthy.

A four-person interior studio. Leads arrive from Instagram, a website form, and walk-ins. Statuses: new, site visit booked, estimate sent, won, lost. Only the owner sees every lead. Each lead must have a next date, or it appears on the Monday list. Version one does not send invoices. Invoicing stays in the accounting sheet until the pipeline has been used for a month.

If your list looks like that — sources, statuses, one visibility rule, one report, and a clear exclusion — a team can estimate the first release without inventing a process you do not have.