The Management Intelligence Layer for fast-growing businesses

Know every customer's journey. Act on the exceptions.

ASAP Digital Platforms connects the systems you already run, builds one journey for each customer and scores every business process along it. When a customer or a process drifts off target, it starts the engagement or retention workflow that brings them back.

What is a Management Intelligence Layer? It sits above the systems you already run. It joins their data, scores every process and tells managers only what needs a decision.

Built on A Customer Data Platform (CDP) approach Identity rules designed for your business Balanced Scorecard and management by exception
Customer journeyILLUSTRATIVE EXAMPLE
One profile, matched from 4 systems Repeat customer, 14 months
emailmobileloyalty IDinvoice account
  1. First contactCampaign to first enquiry92On target
  2. First orderOrder to delivery88On target
  3. ServiceTicket resolved in 3.1 days, target 2 days71Watch
  4. Repeat order41 days since last order, usual cycle 28 days54At risk
Retention workflow started

The score fell below the threshold of 60. A personalised win-back offer goes out today. If there is no response in 3 days, the account owner gets a follow-up task.

Scores run from 0 to 100. Figures are illustrative.

The problem

Your customer is split across systems

Growing businesses add a system for every new channel, site and team. Each one holds part of the customer and part of the process. Managers end up building reports by hand and finding problems after the customer has gone.

Every system reports differently

Sales, operations, service and finance each have their own formats and their own numbers. Putting them together by hand takes days, and the result is out of date when it arrives.

One customer looks like several

The same customer appears under a different record in each system. Repeat buyers, lapsing accounts and renewals at risk stay invisible.

Nobody owns the end-to-end process

Each team sees its own step. The delays between steps are where customers are lost.

How it works

From scattered business data to automated customer retention, in six steps

The platform follows the same six steps for every business. The data, the identity rules and the targets are agreed with your team and configured by us.

  1. Connect your business data

    Sales, point of sale (POS), e-commerce, customer relationship management (CRM), enterprise resource planning (ERP), service and marketing data feed one Business Data Platform. Your systems stay where they are.

  2. Resolve customer identity

    Records from every system are matched into one profile per customer or account, using rules built around how your business knows its customers.

  3. Build the customer journey

    Each profile becomes a timeline: first contact, orders, service, payments, renewals and engagement, in the order they happened.

  4. Score every business process

    Every stage of the journey is a business process with a target. Each one gets a score, so you can see which process helped or hurt each customer.

  5. Monitor behaviour by exception

    The platform watches for drift: a longer gap between orders, a slow resolution, a missed payment. Only breaches of your thresholds reach a manager.

  6. Trigger engagement and retention

    An exception starts a workflow automatically: a message, an offer, a call task or an escalation. Then it tracks whether the customer or process recovered.

Who it's for

Built for businesses that are growing faster than their reporting

Sales, operations, service and finance each run their own system, and nobody sees the whole customer or the whole business in one place. Pick your industry to see the systems we connect, the processes we score and an exception that starts a workflow.

Signs it's time for a Management Intelligence Layer

  • Customer and order data spread across 3 or more systems
  • Growing faster than the finance and operations team
  • An ERP, accounting or operations system already in place
  • Repeat business or renewals matter to the model
  • Management reports still built in spreadsheets
  • Managers who want to see only what needs a decision
Customer identity resolution

Matching rules designed around how your business knows its customers

A distributor knows customers by account number. A retailer knows them by loyalty card and phone. An insurer knows them by policy number. We design the identity model around the identifiers your business already trusts.

  • Your identifiers, ranked. Each one gets a confidence level, and you decide which ones can merge two profiles on their own.
  • People, accounts and sites. We link people to the companies, households, branches or sites they buy for, so business customers work as well as consumers.
  • Every merge is traceable. Each match records the rule that made it, so a wrong merge can be found and reversed.
Example identity rules (illustrative)
IdentifierComes fromMatch strength
Invoice accountFinance, ERPExact: can merge alone
Loyalty or policy numberPOS, policy system, appExact: can merge alone
Email (cleaned)E-commerce, CRMExact: can merge alone
Mobile number (international format)POS, service deskStrong: needs one more match
Name and postcodeDelivery, billingSupporting only
Balanced Scorecard

A Balanced Scorecard for every process, across four perspectives

Customer and process scores roll up into one Balanced Scorecard, so leadership sees growth, customer health and operational quality on one page instead of in four separate reports.

Financial

Are we growing profitably?

Revenue per customertarget +8% · actual +6% Watch
Cash conversion cycletarget 45 d · actual 41 d On target

Customer

Are customers staying and spending?

Retention ratetarget 85% · actual 78% At risk
Repeat-order intervaltarget 28 d · actual 31 d Watch

Internal process

Are our processes on target?

Order to deliverytarget 3.0 d · actual 2.7 d On target
First-contact resolutiontarget 75% · actual 69% Watch

Learning and growth

Are we improving how we work?

Processes digitisedtarget 12 · actual 9 Watch
Exceptions closed on timetarget 90% · actual 93% On target

ILLUSTRATIVE EXAMPLE · d = days

Management by exception

Your managers see what needs a decision, and nothing else

Every measure has a target and a tolerance, agreed with your team. While processes run within tolerance, the platform stays quiet. When one breaches, it raises an exception with an owner, a severity and a workflow already started.

  • Thresholds per process. Set per process, channel, site or customer segment.
  • Severity with a clear response time. Red needs action today. Amber means watch it this week.
  • Closed loop. Every exception is tracked until the measure is back within tolerance.
RedHigh-value customers past their usual reorder dateCustomer · 23 profiles · threshold 1.4 × usual cycle
Win-back running
RedOrder to delivery above target at one siteInternal process · 4.6 days against a 3.0-day target
Escalated
AmberInvoices to key accounts paid later than usualFinancial · days to pay up 9 against a tolerance of 5
Reminder sequence on
AmberNew customers with no second order at 30 daysCustomer · onboarding journey
Nurture series on

38 other measures are within tolerance and are not shown. Illustrative example.

The One Platform model

One data model, one customer identity, one scorecard

Growing businesses usually add a separate tool for each new problem, and nothing connects them. On One Platform, every capability is built on the same data and the same customer, so a new channel, site or product line plugs into what is already there.

  1. Engagement and retentionWorkflows that message, offer, assign and escalate, then measure whether they worked.
  2. Exception managementThresholds, severity, owners and follow-up for anything that drifts off target.
  3. Process scorecardsEvery business process scored against its target and rolled into the Balanced Scorecard.
  4. Customer journey analyticsJourneys mapped from real events, showing where customers stall or leave.
  5. Identity resolutionOne profile per customer or account, matched with rules designed for your business.
  6. Business Data PlatformConnectors, cleansing and one governed model of customers, orders, products and processes, read from the systems you already run.
Why us

Where this sits next to the systems you already own

Keep your ERP, your dashboards and your marketing tools. The Management Intelligence Layer reads from them, joins the customer, scores the processes and acts on the exceptions.

QuestionERPBusiness intelligence (BI) dashboardsTypical CDPASAP Digital Platforms
Holds transactionsYesReads themReads themReads them and leaves your ERP as the system of record
One customer across systemsWithin the ERP onlyOnly if modelled by handYes, mostly marketing dataYes, across sales, service, finance and operations, using identity rules designed for your business
Scores each business processNoCharts measuresNoEvery journey stage scored against a target and rolled into a Balanced Scorecard
Tells managers what needs actionStandard reportsSomeone has to lookAudience segmentsExceptions with an owner, a severity and a workflow already started
Acts on itNoNoMarketing campaignsEngagement, retention and internal escalation workflows, tracked until closed
For your role

What each member of the leadership team gets

Chief Executive Officer (CEO)

One scorecard for the whole business

Growth, customer health and process quality on one page, with exceptions that already have an owner.

Chief Operating Officer (COO)

Process scores by stage, site and channel

See which process is costing customers. The escalation starts on its own.

Chief Financial Officer (CFO)

Margin and cash, customer by customer

Margin by channel and customer after fees, returns and service cost. Cash and collection exceptions raised before month-end.

Chief Marketing Officer (CMO)

One profile per customer

Every system joined into one customer. Retention workflows triggered by real behaviour, with results measured against a control group.

Higher customer retention

At-risk customers show up while there is still time to act, and an automated workflow reaches them before they leave.

Data-driven digitisation

Process scores show which manual processes cost you customers, so digitisation goes where it pays back first.

Fewer surprises at month-end

Cash, margin and service exceptions are raised while they can still be fixed.

Growth without more tools

New channels, sites and product lines plug into the same platform, identity model and scorecard.

How an engagement runs

Start with one journey, then extend

  1. Phase 1

    Walkthrough

    30 minutes on your systems, identifiers and priorities.

  2. Phase 2

    Discovery

    We map your systems, agree the identity rules and pick the first journey.

  3. Phase 3

    First scorecard

    One journey scored on your own data, against targets you agree.

  4. Phase 4

    Exceptions live

    Thresholds, owners and the first automated workflows switched on.

  5. Phase 5

    Extend

    More journeys, channels and sites on the same platform.

What we ask from you

  • Access to the systems in scope
  • A process owner for each journey stage, to agree targets
  • A manager who owns each type of exception

What you do not need to do

  • Replace your ERP, CRM or any other system
  • Clean all your data before you start
  • Connect anything before the walkthrough
FAQ

Questions leadership teams ask us

We already have an ERP and a BI tool. Why add this?

Keep both. Your ERP records transactions and your BI tool charts them. The Management Intelligence Layer joins customers across systems, scores each process against a target and starts a workflow when one breaches. Neither of the others does that on its own.

Do we have to replace any systems?

No. The platform reads from the systems you already run, and they remain the systems of record.

How is this different from a Customer Data Platform?

Most Customer Data Platforms focus on marketing data and audiences. We resolve identity across sales, service, finance and operations, and we score business processes, so the same platform serves the CFO and COO as well as marketing.

How long until we see something useful?

The first milestone is one customer journey scored on your own data. The timing depends on how many systems are involved and how clean the identifiers are. We agree a date with you after discovery.

How much effort is needed from our team?

Access to the systems, a process owner for each journey stage who agrees the targets, and a manager who owns each type of exception. We do the connection and configuration work.

Our customers are businesses, not consumers. Does it still work?

Yes. Identity rules link people to the accounts, branches or sites they buy for, and the journey follows the account.

What happens in the walkthrough?

Thirty minutes. You tell us your industry, systems and priorities, and we show how your journey, scorecard and first exceptions would look. Nothing needs to be connected beforehand.

Get started

See your own customer journey, scored

In a 30-minute walkthrough we show how the Management Intelligence Layer would map, score and monitor your business, using your processes and your identifiers. No system changes are needed for the walkthrough.

Book a walkthrough

Tell us who you are and how your business runs. We reply by email to arrange a time and come prepared with a first journey map.

Where do you sell? (tick all that apply)

We use these details only to arrange and prepare your walkthrough.