A CRM shaped around how you actually sell
You are paying per seat for a CRM that models somebody else's sales process. Half of it does not apply, the half you need does not quite fit, and the delivery data that would tell you what a customer is genuinely worth lives in a different system entirely.
Replace our CRM with something that fits how we actually sell.
You are probably here because
- Your pipeline stages are a rough translation of the vendor's defaults.
- Important information lives in a custom field called "Notes 2".
- Half the licence cost is for modules nobody has ever opened.
- Sales sees the deal; nobody sees what happened after it closed.
- The same customer exists three times because three routes created them.
- Marketing consent lives in a separate tool, so an opt-out does not reach the CRM.
- Nobody can say where deals actually stall — only where they are lost.
- Reporting means exporting to a spreadsheet, every time.
- The real pipeline is a spreadsheet one of the sales team maintains privately.
What is actually going wrong
Mainstream CRM is genuinely good software for the sales motion it was designed around: a repeatable, transactional pipeline with defined stages and comparable deals. If that is how you sell, use it — a bespoke CRM would be a poor use of money.
The friction appears when your sale is not that. Long consultative cycles, bids and frameworks, multi-party deals, tenders with their own gates, or anything where the qualification questions are specific to your industry, all end up expressed as custom fields bolted onto a model that assumes something different. Adoption suffers, because the system is asking questions that do not match the conversation the salesperson just had.
The deeper problem is the boundary. A CRM stops at the closed deal, so everything about how the work actually went — delivery, support, renewals, the cost of serving a customer — sits in another system. That means the most valuable question you could ask, which customers are actually worth having, is one nobody can answer without a data project.
What we build
Contacts, organisations, opportunities and activities as linked datastores using your stages, your qualification fields and your rules. If your pipeline has a bid/no-bid gate, a framework qualification and a clarification round, that is what the system has, rather than a stage called "Proposal" that everyone silently reinterprets.
The pipeline itself is a board over your opportunity records. Each stage carries its own win probability and forecast category, so the pipeline totals as a weighted figure rather than a hopeful sum — and every stage move is recorded automatically with how long the record sat there and who moved it. Where deals stall stops being an opinion and becomes a report.
Marketing runs from the same records. Segments select an audience from any datastore by criteria, and campaigns go out by e-mail, SMS or WhatsApp with per-recipient tracking. Consent is held per topic rather than all-or-nothing, and an opt-out recorded once holds on every channel — so somebody who unsubscribes from an e-mail topic does not then receive it by text.
The part that off-the-shelf cannot do is the one that pays for it: because delivery, support and invoicing can live in the same application, a customer record shows the whole relationship. Sales, delivery and revenue on one record means margin per customer is a report rather than a project.
How it goes together
- 01
Model the pipeline you actually run
Your stages, your gates and your qualification fields, agreed with the people who sell rather than inherited from a template. This is a conversation about how you sell, and it is worth having properly — most CRM adoption failures are really this conversation never happening.
Built fromDatastores40+ field typesRow validation - 02
Weight the stages honestly
Each stage gets a win probability and a forecast category, set from your own history rather than from optimism. The board then totals by weighted value, and stage duration is recorded on every move — so a stage that quietly takes six weeks is visible rather than suspected.
Built fromPipelinesStage historyBoards - 03
Capture activity without relying on discipline
Inbound e-mail fetched automatically and filed against the matching contact or opportunity, including attachments. A timeline built from what happened beats one built from what people remembered to log.
Built fromE-mail inboxesInbox processingActivity stream - 04
Keep one record per customer
A weighted match policy decides what a duplicate is for your data — a matching e-mail address counts for far more than a matching first name — and a nightly sweep raises candidates for review. Merging keeps a full copy of both records, so a merge made in good faith and later found wrong can be reversed.
Built fromMatch policiesDuplicate detectionMerges - 05
Market from the same records
Segments built from your own data, campaigns by e-mail, SMS or WhatsApp, and consent held per topic across every channel. Throttled sending and a pause control, because the useful half of bulk sending is the part that stops messages going out.
Built fromCampaignsSegmentsConsent & preferences - 06
Put process around the sale
Discount approval as an authorisation step, handover to delivery as a workflow stage rather than a conversation, and renewal dates watched by scheduled tasks instead of by memory.
Built fromWorkflowsElectronic authorisationScheduled tasks - 07
Report without exporting
Pipeline by stage, conversion by source, days-in-stage by owner, forecast and margin per customer, built in the report builder and put on dashboards. The spreadsheet export stops being the reporting layer.
Built fromReportsSummary reportsGraphsDashboards
The platform features doing the work
Nothing here is written specially for this use case — it is the same platform every ActiveManage application is built from. The full feature list is on the platform page.
| Feature | What it does | Why it matters here |
|---|---|---|
| Datastores & 40+ field types | Your own entities and fields — linked dropdowns, AJAX search, conditional fields, dates, currency. | Your qualification questions, in your language. This is most of why adoption succeeds or fails. |
| Pipelines & stage history | A board over your own records, with per-stage win probability, forecast category and won/lost flags. Every stage move records its duration and who made it. | A weighted forecast instead of a hopeful total, and hard evidence of where deals stall rather than where they are lost. |
| Campaigns & segments | Audiences selected from any datastore by criteria; e-mail, SMS or WhatsApp; throttled sending, a pause control and per-recipient results. | Marketing runs on the same records as sales, so an unsubscribe and a deal are not in two systems that disagree. |
| Consent & preferences | Topic-level opt-outs with signed unsubscribe links, plus a suppression list fed automatically by bounces and complaints. | An opt-out recorded once holds on every channel — the alternative is somebody who asked to stop still hearing from you, with evidence they asked. |
| Duplicate matching & merging | Weighted field comparison with review and block thresholds, swept nightly. Merges keep a full snapshot of both records and can be reversed. | Every CRM accumulates duplicates. Merging that cannot be undone makes people avoid the decision, so the duplicates stay. |
| Inbox processing | Inbound e-mail fetched automatically and passed, with attachments, to extraction or a custom function. | The activity history stops depending on salespeople logging things after the fact. |
| Workflows & electronic authorisation | Multi-stage processes with e-mailed approve/decline links. | Discount approval and handover become steps in the system rather than favours asked over Teams. |
| Reports & dashboards | A builder that joins related tables automatically, with graphs and dashboard elements. | Pipeline reporting without the export-to-spreadsheet step that every CRM conversation eventually reaches. |
| No per-seat licensing | Users are an operational decision, not a purchasing one. | Everyone who should see the customer can, including delivery and support — which is exactly the visibility per-seat pricing discourages. |
| API engine | Permission-aware endpoints with token-based clients and call logging. | Marketing automation, your website and your finance system all need to reach this. An API that respects the same permissions is the safe way to let them. |
What you end up with
- Your stages and qualification fields, not a vendor's defaults
- A weighted forecast, with stage durations recorded automatically
- Activity timelines built from real e-mail, not from logging discipline
- One record per customer, with merges that can be undone
- Marketing consent that holds across every channel
- Sales and delivery visible on one customer record
- Reporting without an export step, and no per-seat licence to grow into
Whether this is for you
A good fit when
- Consultative, bid-based or multi-party sales that mainstream CRM models awkwardly.
- Businesses where what happens after the sale determines whether the customer was worth winning.
- Teams where per-seat pricing is actively preventing the right people from seeing the customer.
- Anywhere sales and marketing hold separate contact lists that quietly disagree with each other.
- Anywhere the real pipeline is a private spreadsheet, which is always a sign the CRM does not fit.
Probably not, if
- A standard transactional pipeline that a mainstream CRM already fits. Buy it — this would be an expensive way to get something worse.
- Teams whose problem is that nobody updates the CRM. New software does not fix that; it just gets blamed next.
- High-volume outbound marketing as the main requirement. Campaigns here serve a CRM; a dedicated marketing platform will out-feature them.
- Organisations wanting the ecosystem — the marketplace, the integrations, the certified consultants. That is a real asset and you would be giving it up.
How a project like this runs
First
The pipeline model and one team using it against live opportunities. Sales teams tell you very quickly and very clearly when a field is wrong.
Then
Stage weighting from your own conversion history, e-mail capture, duplicate matching, approvals, reporting, and the join to whatever happens after the deal closes.
Handover
Stages, probabilities, segments and reports are configuration. Sales processes change more often than most software allows for, which is much of the argument for building it this way.
Questions we get asked
Should we really replace a mainstream CRM?
Often not, and we will say so. If your pipeline is transactional and repeatable, mainstream CRM fits it well and is excellent value. The case for building is when your sale genuinely does not fit that shape, or when the answer you need spans sales and delivery.
How accurate is the forecast?
As accurate as the probabilities you set, which is why they should come from your own conversion history rather than from instinct. Because every stage move is recorded with its duration, you can compare actual conversion from each stage against the figure you configured and correct it — most pipelines are set up once with estimates and never revisited.
Can we import our existing CRM data?
Yes. The Data Import System handles files with field mapping and translation, and the Update Existing method means a load can be re-run after corrections without creating duplicates. Set a match policy up before the import rather than after — duplicates are far cheaper to prevent than to merge.
What happens if we merge two records by mistake?
A merge keeps a full copy of both records as they were, so it can be reversed. Activity recorded since the merge sits against the surviving record and would need reassigning by hand, but nothing is thrown away.
Can we run marketing campaigns from it?
Yes — e-mail, SMS and WhatsApp, to audiences selected from your own records, with throttled sending and a pause control. Consent is held per topic and an opt-out applies across every channel. If high-volume outbound marketing is your main requirement, a dedicated platform will do more; if you want marketing that shares the CRM's records and consent, this is the point.
Does it capture e-mail automatically?
Yes. Inbound mail is fetched over IMAP, Microsoft Graph or SES and filed against the matching record, attachments included, so the timeline reflects what actually happened.
What about per-user cost as we grow?
There is no per-seat licence. That changes behaviour more than it sounds: delivery, support and finance can all see the customer, because letting them is no longer a purchasing decision.
Can it connect to the tools we already use?
Yes, through the API engine, linked external databases and datastore sync — with the same permission rules as the interface rather than a back door around them.
Sound like your week?
Tell us what you are trying to fix and we will tell you whether this is the right shape for it — including when it is not.