Custom CRM
A CRM that holds your whole sales process, from first contact to renewal, so the pipeline lives in one place and not in side spreadsheets.
Standard CRMs assume one sales process. If yours runs through trade accounts, quotes, site visits or renewals, the steps that don’t fit end up in spreadsheets. We map how deals actually move, then build the stages, fields, entry rules and handoffs to match, with Shopify orders and Stripe payments on each customer record. The console we built on top of HubSpot for a UK consumer brand includes its sales pipeline.
For Founders, sales directors and COOs at B2B and trade-selling companies whose sales process doesn’t fit the stages and fields of a standard CRM.
You need this when
- 01
Half the pipeline lives in a spreadsheet because the CRM has no place for it.
- 02
A deal moves to proposal with no contact, value or close date on it.
- 03
Sales, operations and finance each keep their own list of the same customers.
What’s included.
Pipeline and stages
Your stages, entry rules and required fields, so a deal can’t move forward with information missing.
Contacts and companies
Records that hold what your team needs, such as trade terms, sites, contracts or renewal dates, with duplicates merged.
Tasks and handoffs
Tasks created when a deal changes stage, assigned by role, with reminders when they go overdue.
HubSpot sync or migration
Keep HubSpot as the record and build your views on top, or move the data across with a field-by-field map.
Orders and payments
Shopify and Stripe data on each customer record, so sales sees what each customer bought and what they still owe.
Views by role
Reps see their own deals, managers see the whole pipeline, and finance sees terms and payments.
How it runs.
v1 takes 8–16 weeks; your team works its own pipeline in staging from week 4.
- 01 · Map the sales process
We sit with sales and operations and draw every stage, handoff and field as it works today.
- 02 · Scope and prototype
Stages, fields and screens agreed, then clicked through by the people who will use them.
- 03 · Build on real data
Contacts and deals load into staging, so the team tests on its own pipeline.
- 04 · Switch over
We migrate or sync the data, walk each role through it, and run old and new side by side until the numbers match.
Deliverables
- Pipeline map: stages, entry rules and required fields
- Data model and field list
- Clickable prototype of the pipeline and record screens
- Production CRM on your domain
- Migration or sync from HubSpot or spreadsheets, with a field map
- Role matrix and admin panel
- Staging environment
- Admin guide, runbook and handover session
Works with
What buyers ask.
Why not configure HubSpot instead?
Sometimes that’s the right call, and we’ll say so in week 1. A custom CRM makes sense when your process needs records, rules or screens HubSpot can’t hold without workarounds.
Will sales keep it up to date?
They help design it, so fields nobody fills in don’t get built. Reps try the prototype before the build and work their own pipeline in staging before switch-over.
What happens to the data in HubSpot and our spreadsheets?
It moves across through a field map with duplicates merged, or stays in HubSpot and syncs. Either way, a test import runs in staging and your team checks sample records before anything switches.
Pairs well with
One private screen for the weekly review, each figure traced to its source.
Let’s build your pipeline.
Tell us what you sell, who buys it and roughly what a customer is worth to you. We reply with questions, then a written proposal.