← All perspectives

Perspective / Software & CRM

Choosing the CRM boundary: system of record, orchestration layer or engagement interface?

A CRM can hold a customer record without owning every fact about that customer. Define identity, authoritative data and workflow boundaries before committing to a platform or a programme of integrations.

10 min readReviewed

Aerial rail interchange with separate routes connected through a central station.
Conceptual editorial image.

A CRM architecture should assign clear authority for customer information, rather than assume one application must own every customer-related fact. The commercial question is which system can make each decision reliably, and how that decision reaches the people and services that depend on it. This article develops a reference model for separating customer identity, relationship management, transactions and operational status. The worked example is illustrative; its purpose is to expose design choices and failure conditions before a business commits to implementation.

The executive view

  • Assign authority to individual business facts, not to an ambiguous universal customer record.
  • Use stable identifiers and explicit contracts for updates, events and exceptions.
  • Approve consistency limits, migration evidence and operational ownership before implementation.
01

Start with the decisions your systems must support

Begin with an inventory of business decisions: creating an account, qualifying an opportunity, approving credit, accepting an order, issuing a refund and handling a service complaint. For each decision, identify the evidence required, the person or service authorised to act, and the consequence of using stale information. A sales screen and a credit-control process may both display the same organisation but require different authoritative facts.

This creates a more useful architectural starting point than a list of screens. A CRM might be the system of record for relationship ownership, an orchestration layer for a sales process, and an engagement interface for information owned elsewhere. Those roles can coexist, provided their boundaries are explicit.

The first deliverable should be a decision-and-data map. It should reveal which proposed CRM customisations create business capability and which merely reproduce information already maintained by another system.

For a concrete discovery exercise, trace one renewal from the initial account query to contract acceptance and invoice creation. At every step ask which fact is being asserted, which identifier links it to the customer and who can correct it. Record the manual messages and spreadsheet checks as part of the process. These often represent missing policy rather than mere inconvenience.

This exercise also exposes where a new CRM would create duplicate decision authority. A supplier might propose reproducing credit rules inside a sales workflow because it makes a demonstration self-contained. That apparent convenience creates a second place to maintain limits and exceptions. Challenge the proposal against a narrower alternative: the CRM requests a decision from the existing credit authority and records the response with its effective time.

02

Define ownership below the level of a customer record

“Customer” is often an overloaded term. A prospect, contracting entity, invoice account, delivery contact and website user can be related without being interchangeable. Forcing them into one undifferentiated object creates ambiguous permissions, incorrect reporting and difficult migrations.

Assign authority at the level where the business actually governs the information. Finance may own payment terms; sales may own account responsibility; an identity service may own login credentials. Define how changes are proposed and accepted, rather than permitting every connected application to update every field.

Microsoft’s integration design guidance illustrates this distinction between shared data and ownership. The broader lesson is architectural: a consolidated interface does not require consolidated write authority. A useful ownership matrix records the authoritative source, allowed writers, validation rules, distribution mechanism and recovery owner for each significant fact. It should also identify facts that must never be copied into the CRM.

Model relationships explicitly. One corporate group can contain multiple contracting entities, each with several invoice accounts and users who act for more than one entity. A hierarchy is useful for reporting, but inheriting every permission down that hierarchy can grant unintended access. Make group reporting, commercial responsibility and transaction authority separate relationships.

Field-level ownership also needs a correction path. If a salesperson notices an incorrect payment term, disabling the field without providing a route to finance creates shadow records in notes and emails. A change request should identify the old value, proposed value, reason and approving authority; the approved change then returns through the authoritative integration. That mechanism supports a coherent interface while preserving the business control that made the separate finance system necessary.

03

Worked example: one account across sales, finance and fulfilment

Consider an illustrative business selling equipment through a website and an account-management team. It needs a coherent customer view, but the systems perform different jobs.

InformationAuthoritative systemCRM behaviour
Account owner and opportunity stageCRMCreate and maintain
Contracting entity and payment termsFinanceDisplay approved information
Order acceptance and fulfilment statusOrder platformDisplay status and history
Login credentialsIdentity serviceReference the user identifier
Delivery contact preferenceDefined customer-profile serviceSubmit a validated change

The account manager can see overdue invoices without being able to alter the underlying balance. A website user can update a permitted delivery contact without modifying the contracting entity. Customer support can explain an order’s progress without inventing a second order-status model.

The architecture therefore requires dependable references and controlled transitions, not a universal customer table that every application edits.

Suppose an account manager sees a £20,000 credit limit and prepares a £12,000 order. A £10,000 order from another channel may be accepted while the first screen remains open. Rechecking the displayed limit alone would still be insufficient: acceptance needs an authoritative decision about current exposure and the new commitment. The CRM should distinguish a credit estimate from a reserved or approved amount.

The customer-facing message must reflect the same distinction. A quotation saved in the CRM is not necessarily an accepted order, and an accepted address-change request is not necessarily a completed update in fulfilment. Use explicit pending, accepted, rejected and completed states with meaningful reference identifiers. These states give staff something accurate to explain when a downstream service is slow, instead of encouraging an unverified promise to the customer.

04

Make identity and integration contracts explicit

Use stable identifiers to connect records. Email addresses, names and postal addresses are useful attributes but unreliable long-term join keys: they change, can be shared, and may be duplicated. Document how an account is created, matched, merged, suspended and, where appropriate, separated again.

An integration contract should specify both technical structure and business meaning. A field called status needs an agreed vocabulary, permitted transitions, effective time and ownership. Include versioning rules, error responses and a way to distinguish an accepted request from a completed business action.

For events, record an event identifier, entity identifier, relevant version and the time the business change became effective. Decide how consumers handle an older event arriving after a newer one. These details determine whether an integration can be operated safely; they should not be left to informal agreement between two developers after the procurement decision.

Separate commands from facts. A request to change an invoice address asks an authority to decide; an event stating that the invoice address changed reports a completed decision. Giving them the same name and payload makes retries and reconciliation harder to reason about. Record the correlation between request and outcome, and preserve rejection reasons that an operator can act on.

For account merges, retain aliases from retired identifiers and make downstream ownership changes explicit. Do not simply overwrite a foreign key in the CRM and assume finance, documents and analytics follow. A merge can expose one organisation's records to another if entitlements inherit automatically. Test the merge and an incorrectly requested merge separately, including the business's ability to correct the latter without losing historical transaction references.

05

Choose consistency according to commercial exposure

Not every field needs immediate synchronisation. A recently updated relationship note may tolerate a short delay. Credit approval or stock allocation may require a fresh authoritative check before accepting a commitment. Treat that difference as a business rule and record it in the architecture.

For each critical journey, specify the maximum acceptable information age and the behaviour when that limit is exceeded. Options include displaying a timestamp, requesting a fresh check, placing a transaction in review, or temporarily refusing a commitment. “Always available” is not a sufficient requirement if the available answer can be materially wrong.

Do not promise that asynchronous integration makes all views instantly consistent. Instead, design visible pending states and reconciliation. Executives should approve the trade-off between responsiveness, operational continuity and financial exposure, with examples of the decisions that remain possible during a downstream outage.

Use an information-age contract for each view. A relationship note might tolerate a refresh after several minutes, whereas a payment decision must consult the authority at commitment time. The numbers are business choices, not universal architecture defaults. Displaying when information was refreshed helps an operator understand its limitations, but a timestamp alone does not enforce the rule.

During an outage, decide which work can continue without making new commitments. Staff might prepare a quotation, collect missing evidence or queue a validated request while order acceptance remains unavailable. Document how queued work is rechecked when processing resumes, because the customer relationship or credit position may have changed. A recovery backlog should be prioritised and observable rather than silently replayed as though time had stood still.

06

Prove the boundary before migrating the organisation

Test a representative journey across the proposed boundaries before moving every customer record. Include awkward cases: duplicate organisations, merged accounts, a payment-term change during an open order, and a contact who works for two customers. These cases expose weaknesses that a clean demonstration database will hide.

Rehearse migration using a record of source identifiers and transformation rules. Separate genuine duplicates from legitimate relationships. Reconciliation should test business invariants, such as whether every active invoice account maps to the correct contracting entity, rather than merely comparing row counts.

Keep ownership decisions visible in the migration plan. During coexistence, identify the permitted writer for each field and the moment authority transfers. A temporary shared database or two-way synchronisation arrangement needs an expiry condition. Otherwise, transitional convenience can become a permanent source of conflicting information and unplanned support work.

Use two reconciliation layers. Technical reconciliation identifies missing messages and unmapped identifiers; business reconciliation checks whether meaningful totals and relationships agree. In an illustrative migration of 10,000 active accounts, a 99.8% mapping rate still leaves 20 unresolved accounts. If those accounts carry current orders or large balances, the remaining fraction can be operationally material. Rank unresolved records by exposure instead of declaring success from the percentage alone.

Rehearse delta capture between the initial extract and cutover. An accurate snapshot becomes stale while sales and finance continue operating. Decide whether to freeze specific writes, replay an ordered change feed or run another controlled comparison. Each approach needs an owner and a measurable cutover condition, including treatment of records that change during the final reconciliation window.

07

Approve an operating model as well as an application

A viable design names the people responsible for data quality, integration failures, identity exceptions and business-policy changes. It also explains how those people detect problems. Useful measures include unmatched records, rejected updates, reconciliation differences and the age of information used in critical decisions.

The final architecture pack should include the ownership matrix, context diagram, identifier model, integration contracts, exception runbook and migration evidence. It should make a supplier change possible without losing the explanation of how the business operates.

Domain analysis offers a useful vocabulary for distinguishing business boundaries. Those boundaries do not require a particular vendor or a microservice deployment. The test is whether the chosen design makes authority, behaviour and operational responsibility understandable. A CRM programme succeeds architecturally when the organisation can govern those responsibilities, rather than depend on undocumented knowledge inside one platform.

Set service measures around the boundary, not only around application uptime. Track the oldest unresolved identity exception, the proportion of critical decisions using expired information and the time to restore an integration after failure. A CRM can remain available while every account view is stale; uptime would miss the commercial problem.

Make supplier exit a design constraint. Preserve identifier mappings, business vocabularies and integration contracts in a format the organisation can use independently of the selected platform. Check export coverage for relationships and audit history, not merely account names. Before approval, ask the receiving team to explain a complex account from source to displayed view. If that explanation depends on one consultant's memory, the apparent customer-data architecture still contains a significant operational dependency.

08

When a bespoke CRM layer is justified

A bespoke layer is most defensible when the differentiating workflow crosses existing systems and cannot be expressed economically through supported configuration. Examples include complex account relationships, a proprietary qualification process or a controlled operational interface spanning finance and fulfilment. The justification should identify the capability gained and the continuing responsibility for maintaining it.

Compare alternatives at the boundary level. A custom account workspace can display finance-owned facts while leaving invoice decisions in the finance platform. That is a smaller commitment than rebuilding finance functionality inside a new CRM. Conversely, a thin interface becomes misleading if it hides a large body of duplicated business rules.

The procurement question is therefore specific: which decisions will KTE Media or another delivery partner implement, which will remain in existing products and who will operate the connections? A documented boundary gives commercial buyers a stronger comparison than feature counts, while allowing the chosen technology to change without rewriting the business's meaning of a customer.

Further questions

Questions this raises

Does a single customer view require one database?

No. A coherent interface can assemble information from several authoritative systems. The architecture must define identity, ownership, acceptable information age and failure behaviour so that the combined view supports reliable business decisions.

Should every customer update synchronise in both directions?

Only where a defined business process requires it. Unrestricted two-way updates create conflicting authority. Prefer an explicit permitted writer, with requests for change validated by the system responsible for the underlying fact.

What should a CRM architecture review produce?

A decision-and-data map, ownership matrix, identifier model, integration contracts and an operational exception model. For a migration, add transformation rules, reconciliation evidence and the conditions for transferring write authority.

References

Sources & further reading

  1. Choose the right design for your Dynamics 365 apps integration 1 February 2024 (updated)
  2. Use domain analysis to model microservices 25 February 2026 (updated)

Connected capabilities

Software & CRMStrategy & digital transformation

From thinking to doing

What could this mean
for your business?

Your next chapter

What could your
business do better?

Tell us where you want to go, what’s getting in the way, or what you need to deliver. We’ll start there.

Start a conversation

Start a conversation

Tell us what
you have in mind.

Interactive preview. Your information stays in this page and is not sent.