Evaluate the marketing funnel and join the systems which make the customer journey quantifiable.

The business problem

The customer journey crosses the business. The data rarely does.

Marketing may know the source of an enquiry. Sales holds the opportunity and quote. Operations manages fulfilment. Service owns what happens after delivery. When those records and handovers do not connect, teams have to reconstruct the customer story before they can act.

Fragmented records

Customer, partner, product, quotation, order, delivery and service information live in different places.

Manual joins

Spreadsheets, re-keying and individual knowledge hold important relationships together.

Weak handovers

The next step, required information, owner or approval is not always clear.

Incomplete visibility

The business cannot confidently see where demand came from, how it progressed or what value it created.

The complete commercial spine

Follow the relationship beyond the lead—and beyond the sale.

The right spine depends on the business. In a complex product or service journey, it may need to connect the source of demand to the organisation, people, opportunity, configuration, order, delivered product and ownership lifecycle.

1. 01

   Source

   Campaign, referral, event, partner or interaction.

2. 02

   Relationship

   Organisation, contacts, customer and channel.

3. 03

   Need

   Enquiry, application, opportunity and requirements.

4. 04

   Decision

   Configuration, proposal, quote and approval.

5. 05

   Commitment

   Accepted order, contract and commercial terms.

6. 06

   Delivery

   Fulfilment, status, handover and commissioning.

7. 07

   Installed product

   Serialised asset, owner, operator and location.

8. 08

   Lifetime value

   Usage, service, warranty, retention and margin.

Evidence discipline

Visibility is not the same as attribution. Attribution is not the same as causality.

Source visibility

Where did this expression of demand appear to begin?

Journey linkage

Which customer, opportunity, order and product records can reasonably be connected?

Incrementality

What outcome would probably not have happened without the activity?

Dark Horse labels direct facts, matched records, assumptions and inference separately rather than presenting every relationship as proven causality.

Define the requirement

Start with the questions and journey—not the systems you happen to have.

Dark Horse first defines the minimum information, relationships and status history needed to improve a priority decision or transaction. Existing systems and data can then be assessed against a clear requirement rather than audited in the abstract.

Questions

What must the business be able to know, decide or improve?

Journey

Which customer and operational workflow matters first?

Schema

Which entities, fields, stable identifiers and histories are required?

Audit

What exists today, what can be joined and where are the material gaps?

Build the data foundation

Create one governed view without pretending one system should own everything.

Identity

Organisations, contacts, roles, partners and stable matching rules.

Demand

Sources, campaigns, interactions, enquiries and opportunities.

Transaction

Requirements, configurations, quote versions, approvals and orders.

Product or service

Delivered item, asset, serial number, owner, operator and lifecycle.

Operational status

Progress, ownership, exceptions, handovers and next actions.

Commercial value

Revenue, cost, margin, service value and retention.

CRM may own some of these records while pricing, finance, production, quality, service or other operational systems retain distinct responsibilities. A governed connected view does not require forcing every function into one source system.

Operationalise the joins

Connected data becomes valuable when it changes what happens next.

Each critical handover should work as an agreed operating rule. The business needs to know what begins the next step, what must be complete, who can decide and how an exception is handled.

Trigger

The event that begins the next stage.

Required evidence

The information, documents and checks that must be complete.

Owner and approval

The person responsible and the limits of their authority.

Next action

The task, communication or controlled system update created.

Exception route

What happens when the normal rule cannot be followed.

Audit record

What happened, why, when and under whose authority.

Operationalising data means joining reliable information to an explicit, accountable way of working.

Improve future capture

Fix the few inputs that most improve visibility and flow.

Governed source capture

Consistent campaign, referral, partner and analogue source records.

Stable identifiers

Keys that allow customer, transaction and product records to stay connected.

Useful status history

A small set of meaningful stages, dates and reasons for delay or loss.

Controlled handovers

Required information and ownership at the points where work changes hands.

The work is proportionate: not every data field or historical record must be repaired before value can be demonstrated.

Make the evidence usable

A data platform is not the product. A better decision is.

The first useful experience often helps a member of staff see the complete relationship, understand what is missing and identify the next valid action—without having to search across teams and systems.

Complete account view

The connected customer, partner, transaction, product and service history.

Blockers made visible

Missing information, disputed records, approvals and stalled stages.

Next valid action

What should happen next, who owns it and what evidence is required.

Source of truth

Where records disagree, show which source should be trusted and why.

From fixed dashboards to answerable questions

Let authorised people ask the next question.

A conversational interface can make governed information easier to find, explain and act upon. It should follow reliable data and controlled processes—not attempt to compensate for their absence.

Evidence-backed answers

Every conclusion traces to governed data and agreed definitions.

Permission-aware access

People see only the information and actions appropriate to their role.

Human control

A named person approves consequential decisions and write-back.

Known limits

The answer states its freshness, evidence status and unresolved uncertainty.

Applied example

From an enquiry to a delivered and supported product.

A generic complex-product journey can begin with marketing, customer, quotation, production and service records that exist but must be reconstructed manually. The intervention is to define the customer-to-product spine, test the joins and turn the key departmental handovers into governed rules. The result is that staff can see the complete transaction, what is holding it up, who owns the next step and what value followed delivery.

The first proof should improve one important end-to-end workflow—not require the business to buy or replace its final enterprise platform.

How an engagement works

A practical route to a useful first proof.

1. Define the journey

   Agree the business question, customer experience and priority workflow.

2. Design the spine

   Define the minimum schema, identifiers, histories and sources of truth.

3. Audit reality

   Test systems, data quality, direct and partial joins, manual work and ownership.

4. Map the operating logic

   Set triggers, evidence, approvals, owners, communications and exceptions.

5. Define the MVP

   Choose the smallest staff-facing experience that proves useful value safely.

6. Plan delivery

   Sequence the roadmap, governance, dependencies, acceptance criteria and measures.

What the client receives

A practical route from fragmented evidence to a working first proof.

Journey and handover map

The end-to-end customer journey and the internal commitments required to deliver it.

Minimum data model

The entities, relationships, identifiers, status history and sources of truth required.

Systems and data audit

What exists, what links, where records disagree and which gaps matter most.

Operating-logic design

Triggers, checks, approvals, owners, customer communications and exception routes.

MVP definition

Priority user journeys, interface concept, controls, failure cases and measures of success.

Implementation roadmap

The phased critical path, decision gates, dependencies and technical delivery brief.

Questions the work should answer

Turn reporting into a commercial and operational diagnosis.

Demand

Where does new demand originate, and which customer, market, product or partner does it concern?

Progression

Where does the journey advance, stall or disappear—and what prevents the next step?

Connection

How reliably can customer, opportunity, order, delivered product and service records be joined?

Ownership

What should happen at each handover, who remains responsible and what needs approval?

Value

Which activity and relationships create orders, margin, retention and lifetime value?

Action

What is the smallest useful intervention, and how will the business know it worked?

Governance and limits

Automate the effort. Preserve the accountability.

Dark Horse treats ownership, permissions, provenance, uncertainty and human approval as part of the product—not paperwork to add later.

No premature platform decision

Prove the required data and operating logic before committing to a final CRM or enterprise stack.

Transparent matching

State where records link directly, partially, probabilistically or not at all.

Controlled action

Keep people in charge of commitments, approvals and consequential write-back.

Proportionate scope

Start with one reusable workflow and expand only when the evidence supports it.

FAQ

Frequently asked questions