An enquiry arrives in a shared inbox. One person replies, another prepares the quote, and the agreed date stays in a spreadsheet. When the customer calls, the team searches for the latest message. The problem is not necessarily too few tools, but unclear ownership and a disconnected workflow.
A CRM manages customer relationships and sales opportunities. A custom CRM makes sense when existing software cannot support your important rules, roles or connections. For contacts, statuses and reminders, check a ready made solution first. Custom development is not a required starting point.
From enquiry to delivery handover
An illustrative workflow, not a preview of a client's internal application. Each step needs an owner and a clear condition for moving forward.
- 01
Arrival
Contact, need, source and arrival time. Check whether a record already exists.
- 02
Owner
Who replies, by when, and who takes over during an absence?
- 03
Checked need
What does the buyer need, which information is missing and what is the agreed next step?
- 04
Quote
The current version, required approvals and an agreed next contact.
- 05
Confirmed agreement
What did the customer accept? Record scope, terms and the information delivery needs.
- 06
Team handover
The delivery owner acknowledges receipt. Missing information returns to sales instead of disappearing in email.
“Quote sent” is not enough if nobody knows what comes next. A useful record says who takes the next action and when. Rejected or postponed enquiries also need a clear status rather than staying among open tasks indefinitely.
An existing CRM, an integration or custom development?
These capabilities do not require custom development in every company. For example, Microsoft describes qualifying a lead into a sales opportunity and the journey from opportunity to quote and order in Dynamics 365 Sales. Individual features depend on licensing, configuration and permissions.
- Buy: if a ready made CRM fits your usual sales workflow. Test it on your own examples.
- Configure: if you already have suitable software but need agreed statuses, responsibilities or notifications.
- Connect: if the CRM works but staff copy data into quoting or business software manually.
- Build: if other options cannot reasonably support important rules, permissions or the delivery handover.
Development can be a small addition. Keep the existing CRM and use a custom app for a particular approval or delivery form. For a broader comparison, read the internal business applications guide.
Example: a quote for equipment with installation
A hypothetical company receives enquiries for supply and installation. The salesperson needs dimensions, selected equipment and a requested date. While dimensions are missing, the CRM shows “awaiting information” and a follow up task. It does not turn an incomplete enquiry into a confirmed order.
After calculation approval, the quote is linked to the opportunity. Once the customer accepts, the installation team receives the confirmed scope, contact, location and agreed date. A delivery owner checks readiness. An accepted quote does not by itself confirm availability of materials or staff.
The CRM manages responsibility and next steps. Calculating materials, discounts and document versions is a separate requirement, covered in the quoting software guide.
What to include in the first version
Limit the first release to one sales workflow. A useful agreed scope for this pilot includes:
- company, contact and enquiry records with duplicate checks,
- an owner, status, next action and deadline,
- a link to the current quote and a record of acceptance or rejection,
- handover of the confirmed scope to the delivery owner,
- agreed permissions, a history of important changes and a usable export.
Do not automatically include marketing, warehousing and all accounting in the first version. For each addition, ask whether it is necessary for the chosen process to reach completion. A phone form should support entering the required information without navigating a wide desktop table.
Email and business software need clear rules
Do not automatically copy entire personal inboxes into shared records. Define a business inbox or a selected way to attach messages, the permitted information and who sees it. Failed capture needs a visible status and a way to review it manually.
For an ERP connection, check the exact version, licence, permissions and supported API operations or structured import. Define the authoritative source for customers and price lists, error handling and duplicate prevention on retries. More detail: business system integrations.
Permissions, export and costs after introduction
Sales, managers and delivery staff do not necessarily need the same information. Define who can see individual records, amounts and attachments, and test permissions in search and export too. When an employee leaves, transfer open tasks and revoke access.
Before commissioning, agree exports of contacts, deals, activities, attachments and their relationships. Test a sample export. Separately settle licences, code rights, backups, support and handover to another maintainer. An export feature does not automatically guarantee a simple migration.
Compare licences, configuration or development, data cleaning, integrations and team onboarding. Include agreed maintenance and support. The custom application cost guide provides orientation; a proposal confirms the actual scope.
A CRM is not a promise of new enquiries
A CRM helps organise how contacts are handled. Adding a record does not create a new customer. In the pilot, measure time to reply, enquiries without an owner, overdue next actions and incomplete handovers. Also track actual use, corrections and time spent maintaining the records.
Start with one example: where an enquiry arrives, who prepares the quote and who takes over delivery. Do not send passwords, customer data or confidential messages. Explore custom business applications and how we work together, then describe your process below.
Frequently asked questions
When does a small business need a custom CRM?
When important rules, roles or connections cannot reasonably be handled by existing tools. Test a ready made CRM and its configuration first. Custom development can cover just the missing step rather than replacing the whole system.
Does a CRM generate new enquiries by itself?
No. Recording a contact does not create a new customer. A CRM organises ownership, next actions and handovers. Customer acquisition remains a separate task, and neither a CRM nor an automation guarantees more sales.
Can we connect email and our ERP to the CRM?
Potentially, depending on the software version, licence, permissions and supported interfaces. Define which business messages are included, who can access them, the authoritative data source and how failures and duplicate transfers are handled.
What should the first CRM version include?
One agreed workflow with contact and enquiry records, an owner, status, next action, a link to the current quote and handover to delivery. Include permissions, important change history and export. Add other modules only when the chosen process needs them.
How do we avoid becoming dependent on a single provider?
Agree export contents and formats, including attachments and relationships, and test a sample. Separately confirm code rights, third party licences, access ownership, documentation, support and handover. An export button alone does not prove that migration will be straightforward.