Custom CRM
When your sales process does not fit any licence on the market and the team has quietly gone back to the spreadsheet, the problem is not the team.
Book your Diagnostic ↗You are paying for a CRM your team works around.
A custom CRM at Sell with Marketing means a system built to the process you actually sell with: configurable products and calculated prices, multi-stage approvals, the fields your industry needs, integration with the ERP and the quoting engine, and permissions that reflect who is genuinely allowed to see a margin.
The commercial CRMs are good, and for most companies one of them is the right answer. They stop being the right answer at a specific point: when the process has a rule the licence cannot express, and the team starts keeping the real information somewhere else. A CRM that everyone works around is worse than no CRM, because now the data is split in two and nobody trusts either half.
The first thing we do is try to avoid this build. If Zoho, HubSpot, Salesforce, Pipedrive or Dynamics can be configured to your process, that is cheaper for you and we will say so. Building is the answer for the cases where the licence genuinely cannot get there.
The process first. The software second.
- The process written down before anything is built: Who does what, in which order, with which approval, and where it currently breaks. Most CRM projects fail here: they automate a process nobody had agreed on, and the disagreement survives inside the software.
- Configurable products and calculated prices: When the price depends on material, dimension, volume, finish and freight, no licensed pricing field will hold it. The logic lives in the system, so a quote stops depending on one person's spreadsheet.
- Multi-stage approvals with a real audit trail: A discount above a threshold goes to whoever authorises it, and the record shows who approved what and when. This is usually the actual reason the licence stopped fitting.
- ERP, inventory and quoting integration: The CRM reads the stock the ERP holds and writes the order back. Without that link it becomes a second version of the truth, which is precisely how the previous one lost the team.
- Permissions built for a real company: A rep sees their accounts, a manager sees a region, and margin is visible only to those it should be visible to. Configured up front, because retrofitting permissions is where confidential data leaks.
- Migration, training and handover: Bringing the historical data across, training the people who use it daily, and documenting the system so it can be operated and modified without depending on us to exist.
When the real pipeline lives in a spreadsheet.
- Manufacturers whose price depends on a calculation no CRM field can hold
- Companies paying licences for a CRM the sales team quietly works around
- Businesses whose approvals happen in WhatsApp and leave no record
- Teams with a CRM that cannot see the ERP, so stock and orders disagree
- Distributors managing account-specific price lists by hand
- Companies where the pipeline lives in the head of the person who has always sold
We work with Zoho, HubSpot, Salesforce, Pipedrive and Microsoft Dynamics, and configuring one of them is the cheaper answer whenever it fits. The Diagnostic tests that first and says so plainly, because a build you did not need is the most expensive software there is.
Before you sign.
Why build when HubSpot or Salesforce exist?
For most companies you should not, and we start by testing whether a licence fits, because that is cheaper for you and faster to stand up. Building becomes the right answer at a specific threshold: when the process has rules the licence cannot express, when per-seat pricing outruns the value at your headcount, or when the integration your operation needs has no supported path. The Diagnostic states which of those applies to you, or that none of them do.
What happens if we stop working with you?
You keep the system, the source code and the data, and it runs in infrastructure that is in your name. That is the point of building rather than renting. The handover includes documentation and a walkthrough for whoever maintains it next, and we would rather that be a real handover than a hostage situation.
How long does a build like this take?
It is a project with a defined scope and an end, and the length depends on how many processes it has to cover and how clean the data being migrated is. What we do not do is quote a timeline before seeing the process written down, because every CRM project that ran late was quoted before anyone agreed what the process actually was.
Our team never adopted the last CRM. Why would they adopt this one?
Because the usual cause of that is not resistance, it is that the software asked them to work in a way the job does not allow. When the system matches how the sale actually happens, adoption stops being a training problem. We also build the migration and the training into the scope rather than treating them as an afterthought, since that is the other half of where adoption dies.
Can it work alongside the CRM we already have?
Often that is the right shape: the licence keeps doing what it does well, and the build covers the part it cannot express, with the two connected. Replacing a working system wholesale is rarely the cheapest path, and the Diagnostic will tell you when it is not.
SOFTWARE THAT FITS
HOW YOU SELL.
It starts with the Diagnostic: what standing still is costing you, what fixing it costs, and what gets fixed first — in your own data. Paid work, credited 100% against the fix if you move within 90 days.
Book your Diagnostic ↗