Your Salesforce knows the wholesale buyer but not the firing that's making them wait
A custom CRM (Customer Relationship Management) for a Stoke-on-Trent ceramics or distribution business runs $45k to $110k over 3 to 6 months. The trigger is that Salesforce, HubSpot or Pipedrive can track a trade buyer's conversations beautifully but can't tell that buyer's rep that the wedding range they promised is stuck behind two firings, because the kiln schedule lives nowhere near the CRM.
HubSpot and Pipedrive are built for a clean sales pipeline: lead, opportunity, deal, won. A Potteries firm's reality is messier. A long-standing department-store buyer reorders a heritage range, your rep promises a date, and then production tells them the kiln's full until the end of the month. The CRM has no idea any of that happened, so the next call is a guess and the relationship that took three generations to build runs on hope.
Meanwhile your ecommerce customers and your trade accounts sit in separate worlds. The same person who buys a single mug online might run a gift shop ordering by the pallet, but generic CRMs treat those as unrelated records. You lose the chance to spot the gift-shop owner buying retail, and you lose the thread that ties a complaint about seconds back to the firing batch that caused it.
What crm costs in Stoke-on-Trent
| Project scope | Typical cost | Timeline |
|---|---|---|
| Unified trade and ecommerce CRM core | $45k to $75k | 3 to 5 months |
| CRM with live kiln-capacity and quality linkage | $75k to $110k | 5 to 7 months |
| Group CRM across multiple Potteries factories | $110k+ | 7 to 10 months |
The fix: crm built for Stoke-on-Trent, not rented
A custom CRM for a Potteries firm ties the buyer relationship to the floor. When a rep opens a trade account, they see that account's open orders against live kiln capacity, the seconds history for the ranges that buyer takes, and whether the same contact also shops your store. A promise becomes a date the kiln can actually keep. That linkage between relationship and production is exactly what no off-the-shelf CRM gives you, because they were never built to know what a firing is.
- You sell to both trade accounts and direct ecommerce customers and they overlap
- Reps promise dates that production can't keep because they can't see capacity
- Quality complaints need to be traced to specific firings and ranges
- Key relationships live in a retiring rep's head, not in a system
- You sell one channel only and your pipeline is genuinely linear
- Standard HubSpot reporting covers everything you need to know about a buyer
- You have no production-capacity constraint to surface inside the CRM
- A small team can run on Pipedrive without re-keying into other systems
The capability list that earns its budget
CRM services we deliver in Stoke-on-Trent
The engagements Stoke-on-Trent teams bring us most often: marketing automation, Salesforce development, HubSpot integration, Zoho CRM and Pipedrive.
How long it takes, phase by phase
Exactly what you get
You get a CRM where the relationship and the factory finally talk. A rep opens a trade account and sees open orders mapped against live kiln slots, the seconds history for the ranges that buyer favours, and whether that same contact buys from your store. Promises become dates production can keep. It connects to your custom ERP, your inventory management system and your helpdesk software so a complaint, an order and a conversation share one thread instead of three disconnected ones.
How to choose a developer in Stoke-on-Trent
Choose a developer who treats integration as the core of the brief, not an extra. The hard part of a Potteries CRM isn't the contact screens, it's wiring the relationship to live production. Ask how they'll surface kiln capacity to a rep mid-call, how they'll unify a buyer who shops both trade and retail, and how a quality complaint links back to a firing batch. Demand a reference where they connected a CRM to a real manufacturing or fulfilment system, and make sure the contract covers ongoing care of email and marketing integrations.
- Trade reps quote dates against real kiln capacity instead of guessing and apologising later
- One view that unifies a buyer's wholesale orders and any retail purchases they make
- Complaint records linked to the firing batch and range, so quality patterns surface fast
- Automated reorder prompts timed to a trade account's real cycle, not a generic nudge
- Clean handover when a long-serving rep retires, with the full relationship history intact
- You forgo HubSpot's vast marketplace of pre-built integrations and add-ons
- Sales-automation features that come free in Pipedrive must be specified and built
- Reps comfortable with a familiar CRM will resist a bespoke interface at first
- You own the cost of keeping email, calendar and marketing integrations current
- !They pitch a CRM that ignores your production system; ask how a rep sees real capacity before promising a date
- !No plan to unify trade and retail records; ask how a gift-shop owner who also shops your store appears
- !They can't show quality-complaint linkage; ask how a seconds complaint ties back to a firing
- !Heavy reliance on one off-the-shelf platform under the hood; ask what's bespoke versus configured
- !No migration story for relationships in a retiring rep's notes; ask how that knowledge is captured
Most Stoke-on-Trent teams pricing crm end up comparing notes on mobile app, website, pos too; the systems share one data spine.
Rohan advises mid-market and enterprise teams on ERP, CRM and custom software, and has led delivery on dozens of business-software builds.
Writes for Digital Heroes, shipping business software for 2,000+ brands across 55+ countries since 2017.
Frequently asked questions
Why not just use HubSpot or Salesforce?
They're excellent at managing conversations and pipelines, but they have no idea what your kiln is doing. A rep using stock HubSpot promises a date with no view of capacity, then production overrules them. A custom CRM puts live kiln slots and seconds history inside the account so the promise is keepable.
Can a custom CRM unify our trade and ecommerce customers?
Yes, and that's often the strongest reason to build. A single buyer might order a pallet for their shop and a mug for themselves. A custom record links those so you see the whole relationship, spot upsell paths, and stop treating the same person as two strangers.
How does it help with quality complaints?
Every complaint can be linked to the firing batch and range it came from, so when several customers report crazing on the same glaze, the pattern is visible immediately. That turns scattered grumbles into a quality signal your production team can act on.
What happens when an experienced rep retires?
A custom CRM captures the relationship history, the buying cycles and the quirks of each account in the system rather than the rep's head. When they retire, the handover is a login, not a panic. For family firms that have relied on personal relationships for generations, that's a real safeguard.
Will it integrate with our ERP and store?
It should be built to. The whole point is honest promises, which means the CRM has to read live stock from your ERP and inventory system and know what your storefront is selling. Without those links you've just bought a prettier address book.