Problems worked backwards from the outcome.
Business problems, operating-model questions and architecture situations. Each starts from what had to become true and crosses more than one discipline.
Cases focus on architecture and decision-making. Contexts are generalized and, where necessary, combined to protect confidential information.
Operating model & process
How work, decisions and adoption are designed
3 cases
Digital Operating Model · Process Architecture · Revenue Operations · Change & Adoption
Designing a global commercial operating model for fundamentally different sales motions
- Each way the business really sells runs on its own operating path—qualification, stages, evidence, approvals and cadence—inside one frame leadership can compare.
- Seven kinds of commercial work, from a two-week reorder to a three-year OEM programme, were all called “opportunity” and run through one process.
Standardizing RFQ governance across commercial, technical, compliance and project decisions
- Every complex request is classified, assessed by the functions its class requires and decided Go / No-Go by a named owner on recorded evidence.
- Commercial, engineering, quality, plant, finance and compliance each held part of the judgement on OEM and private-label requests; none held the decision.
Moving a commercial team from parallel trackers to CRM
- The team plans, reviews and forecasts from the CRM, and the parallel trackers are retired on agreed dates.
- The spreadsheets held real value, and the management routine still depended on them.
Commercial systems & revenue
The CRM, ERP and pipeline that run it
2 cases
Systems & CRM Architecture · Data & Integrations · Revenue Operations · Process Architecture
Designing a CRM–ERP customer lifecycle
- An approved commercial relationship becomes an operational customer reliably—without duplicate identity or hidden failure.
- Two systems with different authority, an ERP that may be unavailable, and timeouts that do not prove failure.
Designing account management as a performance, development and recovery system
- Every relevant deviation creates an owned obligation, and every obligation ends in a recorded outcome—recovered, escalated or accepted.
- Account plans, performance dashboards and recovery actions lived apart; underperformance was visible every month and nothing was obliged to follow.
Data, automation & AI
Signals, orchestration and bounded agents
3 cases
Data & Integrations · Revenue Operations · Automation · AI & Agentic Workflows · Process Architecture
Designing a governed commercial performance data model
- Orders, invoices and targets become one reproducible performance model whose definitions can be trusted across decisions and systems.
- Facts arrive at different grains, periods and versions; corrections, target phasing and currency can change the result unless their semantics are governed.
Designing stateful orchestration for a long-running commercial process
- One durable run per period that can wait, resume, retry safely and finish with a definitive outcome—and that an operator can read.
- Dependent steps, external waits and effects a rerun cannot undo; a failure half-way must not mean starting again.
Redesigning RFQ processing around AI without moving commercial authority to the agent
- Every RFQ drafted in minutes with evidence for each value—and nothing consequential without a named person’s approval.
- Unstructured requests, ambiguous products and customers, and an agent that must never be the one to commit.
Operating Model & Process Design
Business complexity first. Process and technology second.
How different commercial realities become different processes, decisions, ownership models and operating rules.
Flagship transformations
Organizational complexity, cross-functional analysis and decision design
- 01Designing a global commercial operating model for fundamentally different sales motionsOne “opportunity” concept was hiding seven fundamentally different ways of selling. The work started by understanding them, separated genuine operating motions from superficial variation, kept one shared frame where leadership compares—and only then encoded the model in systems, with ownership, transition and measurement designed for real operation.
- 02Standardizing a global commercial operation before scaling the CRMDeciding what must mean the same everywhere, what may legitimately differ locally and who decides—then governing the difference—before one CRM is scaled across subsidiaries.
- 03Standardizing RFQ governance across commercial, technical, compliance and project decisionsTurning dispersed commercial, technical, compliance and project judgement on complex RFQs into one reproducible decision model: classification, required assessments, Go / No-Go, decision rights, clocks, escalation and a decision record.
- 04Designing account management as a performance, development and recovery systemOne management system for existing customers: understand the account, measure, detect deviation or opportunity, diagnose, decide, commit, act, follow up and reassess—with performance states that change who must do what.
Operating foundation
Getting the basic operating semantics right
Commercial-motion deep dives
Where the operating model becomes specific process logic
- 06Separating aftermarket sales motions by intent, customer maturity and commercial riskWhy “sell more” in the aftermarket is four processes: acquiring a customer, introducing a range, developing an account and expanding a sale need different evidence, qualification and management attention.
- 07Designing indirect demand generation when the originator is not the sellerSeparating demand creation from sales fulfilment when different actors perform them: origination, qualification, assignment, acceptance, fulfilment and attribution as explicit responsibilities.
AI-enabled redesign
Dividing work and authority between people, rules and AI
Execution models
Operating design carried into day-to-day work
- 09Designing the operating cycle behind field commercial executionVisit planning, preparation, the visit itself, capture and follow-up as one commercial loop—so field time goes to the right accounts and every conversation leaves a next step someone owns.
- 10Standardizing customer service from intake to resolution—and back into commercial actionDesigning the service operation—intake, identification, classification, severity, ownership, routing, service levels, escalation, resolution and closure—and the loop that turns what service learns into commercial action.
Systems Architecture & Integration Design
Responsibilities first. Interfaces second.
How commercial capabilities become clear system boundaries, identities, authority models and resilient interactions.
Flagship architectures
Responsibility, identity, authority and interaction across CRM, ERP, integration and data
- 01Designing a CRM–ERP customer lifecycleA premise-led architecture: from commercial intent to a legally valid, operationally recoverable customer.
- 02Designing the system boundaries behind a global commercial platformDeciding which platform owns each commercial capability—and which boundaries stay in place even when the experience feels like one application.
- 03Designing customer and master-data identity across CRM and ERPSeparating commercial, legal and transactional identity—with one issuer, explicit cardinality and governed merges—and giving authority to concepts and attributes rather than whole records.
- 04Designing product, pricing, stock and transaction visibility without turning CRM into ERPDeciding, domain by domain, which ERP information the CRM should replicate, read on demand, summarize, derive or simply reference—so sellers see what they need without a second ERP.
Platform governance
Keeping one global platform coherent across countries, roles and people
- 05Designing a global CRM with a stable core and controlled local variationSeparating the global CRM core from configurable variation, integration mapping and rare local extensions—so the platform stays upgradeable, testable and comparable.
- 06Designing access and visibility for a global commercial organizationSeparating accountability from visibility and edit authority—so shared, global and specialist access is explicit instead of accidental.
Data, Analytics & Decision Intelligence
Define the meaning. Then design the decision.
How operational facts become governed metrics, decision surfaces and actionable signals without duplicating analytical truth.
Decision architectures
Semantic models and decision surfaces: what the numbers mean, and which decisions they serve
- 01Designing a governed commercial performance data modelA governed commercial performance model: orders, invoices, targets and customer context conformed at a declared grain, with explicit time, version, correction and currency semantics—so every metric is computed once and reproduces the same business meaning everywhere.
- 02Designing embedded commercial analytics around management decisionsAn embedded decision layer for commercial managers: organised by management question rather than by system object, with one filter semantics, governed metric definitions, a path from overview to the record where action happens, measured usage—and no analytical truth of its own.
Analytical activation
Governed signals carried back into the systems where commercial work happens
Automation & Orchestration Design
Design the state. Then automate the execution.
How deterministic business rules become safe, observable and recoverable execution across steps, time and changing conditions.
Core automation architectures
Long-running orchestration and closed-loop automation: explicit state, safe reruns, designed exits and recovery
- 01Designing stateful orchestration for a long-running commercial processOne durable run per period with an explicit state machine, start-once steps, waiting as a state, a lightweight continuation that wakes unfinished runs, retry classified at the step boundary and a run record that answers the operator's questions—so a failure in step seven resumes at step seven.
- 02Designing closed-loop automation from signal to action and exitAutomation as the maintenance of an expected downstream state: entry, update, exit and re-entry designed per transition, system-managed and human-owned work told apart, reruns that converge instead of adding, and reconciliation as the control loop that repairs only what is safe.
Applied AI & Agentic Workflow Design
Ground the evidence. Bound the authority.
How AI prepares decisions, structures unstructured work and assists stewardship while context, tools, evaluation and human authority remain explicit.
Applied AI architectures
Where AI reasoning sits inside a governed operating system—with its context, tools, evidence, authority and evaluation designed around it
- 01Designing evidence-grounded AI preparation for commercial decisionsOne architecture used before a customer visit and before an account review: governed context assembled deterministically, a context contract per source, every statement typed and cited, bounded read-only tools, explicit behaviour when context is stale, conflicting or missing—and the decision left with a person.
- 02Designing AI-assisted intake for unstructured commercial workA shared commercial entry point turned into structured, owned work: a taxonomy written before the model, mixed intent decomposed into work items that share one source reference, entities offered as evidence-backed candidates, owners and clocks assigned by deterministic rules, review placed where ambiguity becomes consequential—and no external commitment without a person.
- 03Designing AI-assisted data stewardship without moving master-data authorityAI that makes stewards faster without becoming the steward: candidates found, ranked by impact and explained with evidence and differences; a governed steward queue; identity, merge and consequential classification decided by accountable people; accepted decisions executed by the system’s own processes; and outcomes that improve evaluation and rules—never the model’s permissions.
Every other case, once—filter by the discipline it needs.
Designing customer ownership in a multi-subsidiary organization
- Every level of the customer has a named owner with defined rights; the global relationship is coordinated through one plan; local transactions stay local; conflicts go to a named arbiter with a time limit.
- A group customer buys from several subsidiaries; three teams call it “my account” and nobody can resolve the disagreements.
Disciplines: Digital Operating Model · Systems & CRM Architecture · Data & Integrations
Owning and evolving the operating model after go-live
- Every responsibility the project held has a named operating owner before go-live; recurring friction and requests are classified into one governed backlog; every change is decided by its domain owner with evidence and within a time limit, released as a versioned change and reviewed for effect; and adoption and the model itself are reviewed on a schedule that decides.
- The project team disbanded at go-live. Support tickets pile up one by one, workarounds spread, every change arrives as a ticket to the platform team—and nobody decides whether it changes the operating model, so the configuration drifts.
Disciplines: Digital Operating Model · Change & Adoption · Systems & CRM Architecture
Designing adoption for a multi-subsidiary CRM rollout
- Each subsidiary goes live when it is ready, with role-based enablement, a named champion, dated tool retirement and first-weeks support—and adoption is compared by level, read in local context.
- A global CRM is deployed across subsidiaries with different maturity, roles, historical processes, data quality, local tools and management habits.
Disciplines: Change & Adoption · Digital Operating Model · Systems & CRM Architecture
Replacing mandatory fields with data people use
- Fewer fields, each used by a named decision; values derived or prefilled where they exist elsewhere; required only where known; and a view that gives the entering role something back.
- To force adoption, most opportunity fields were made mandatory. Records are complete—and full of placeholder values nobody trusts.
Disciplines: Change & Adoption · Process Architecture · Data & Integrations
Designing forecast governance and pipeline coverage that trigger action
- A forecast built in the system from stage semantics, with recorded judgement, a named owner of the final number, weekly snapshots and measured accuracy—and a coverage contract that starts pipeline generation below its threshold.
- The forecast is rebuilt every Monday in a spreadsheet, overrides are invisible, and coverage is reported without anyone being asked to generate pipeline.
Disciplines: Revenue Operations · Data & Integrations · Systems & CRM Architecture
Running commercial management cadence from the CRM
- Every recurring forum has a purpose, participants, evidence, decision rights and outputs—and runs from one CRM view built for it. Adoption is measured by whether the forums actually use the system.
- Sellers are asked to keep the CRM current, but every management meeting runs from spreadsheets—so the system is maintained for nobody.
Disciplines: Revenue Operations · Change & Adoption · Digital Operating Model
Reusable patterns behind the cases
- RA / 01Global B2B commercial platformA bounded CRM–integration–ERP topology that separates commercial, legal and analytical truth.
- RA / 02AI-assisted RFQ processingA human-controlled path from unstructured email to a reviewable commercial record draft.
- RA / 03Commercial performance managementOperational and analytical signals joined without turning the CRM into a data warehouse.