A simple CRM for a new business: stop losing enquiries between inboxes

The first problem is usually coordination

An enquiry arrives through Instagram, another through a form, and a referral reaches the founder's phone. Each person assumes someone else replied. A CRM begins by making that work visible. The software matters less than the rule that every opportunity has an owner and a next action.

Keep opportunities separate from individual contacts. One customer can have more than one project, and several people can be involved in the same buying decision. For a very small operation, start with one opportunities sheet and add a contact table when duplication becomes difficult to manage.

Use a minimal record

The following operating pattern is a dotSuper proposal. Adapt the fields to the information needed for your actual service.

• Opportunity ID and date received.
• Business or customer name and permitted contact channel.
• Source and relevant landing page or campaign.
• Requested service and short qualification note.
• Stage, owner and dated next action.
• Quoted value, outcome and reason when the opportunity closes.

Define stages by observable events

Start with New, Contacted, Qualified, Proposal sent, Won and Closed without sale. 'Contacted' means a response was actually sent. 'Qualified' means the request fits agreed criteria. 'Won' means the acceptance condition was met, such as a signed order or received deposit, according to your process.

Avoid stages such as 'Warm' unless the team can explain them consistently. Track waiting time separately from the stage. A proposal can be both valid and overdue for a follow-up.

A fictional enquiry walkthrough

A manufacturer requests a product photography quote through the website. The form creates an opportunity ID, assigns an owner and records the requested product count. The owner checks whether the deadline is feasible, replies with the missing questions and sets a next action. The record moves when the conversation progresses.

If the business receives the same request by email, update the existing opportunity rather than count two leads. If the request is outside scope, close it with a reason. A smaller accurate pipeline is more useful than an inflated list of unresolved contacts.

Automate only after the handoff works

First test the manual route. Then automate form capture, owner alerts and overdue reminders. Keep a visible failure path if the integration stops. Do not put sensitive customer details into analytics events or campaign URLs; the CRM and analytics have different jobs.

Control access, make backups and define a retention policy appropriate to the business. A shared spreadsheet with a public link is not a suitable customer database. Use individual accounts so ownership survives staff changes.

A daily and weekly review

Each day, inspect new and overdue opportunities. Each week, compare suitable enquiries, accepted proposals and reasons for loss by source. Response time is useful only when measured consistently; an automatic acknowledgement is different from a helpful human response.

Start with ten real records and test whether another team member can identify the next action without asking the founder. That is a stronger first milestone than purchasing a large CRM and leaving the inboxes disconnected.