Pricing Strategy Blueprint
How price will be set going forward — what it is anchored to, who ratifies it, and which decisions the platform is allowed to make. The strategy configuration will implement, not a slide that sits beside it.
The RevSeekr method · Phase 2 of 5
Phase 2 — Design & Blueprint
Define the target state and the path to reach it.
Design frameworks
Run with you on engagements — request a session →
Segmentation & Price Structure Design
How customers and products are grouped for price, and the lists, floors and bands that follow. Volume-only A/B/C tiers are redesigned here, or they stay — that is a decision, not a default.
Discount & Approval Architecture
Who can approve what, at which margin or discount, and how an exception is routed. The matrix that has to exist as a decision before it can exist as a workflow.
Price Waterfall Definition
One agreed definition of list, on-invoice, off-invoice and pocket — the fields a deal must carry so margin is visible at the point of decision, not reconstructed later.
Data Model & Integration Design
The objects, identifiers and feeds the platform will read — product, customer, cost, price — and which system is authoritative when they disagree. Target architecture that ERP, CRM and Pricefx can all live with.
Workshop kits
Run with you on engagements — request a session →
Solution Design Workshops
Facilitated sessions where each team maps its current process, then defends its exceptions. Most exceptions turn out to be habit. The genuine ones become parameters in one framework.
To-Be Process Mapping
The process that will run after go-live, written down end to end: quote, approval, exception, agreement, the update when cost moves. Discovery mapped what is true today; this is the target.
Governance Design Session
Requirements governance as its own workstream: who settles a disagreement between two business units, and how a decision is made to stick. Treated as design, not as a byproduct of the build.
Design Review & Sign-Off
A formal pass on the design package — strategy, structure, authority, waterfall, data — so configuration starts from decisions, not from a workshop parking lot.
Templates & outputs
Run with you on engagements — request a session →
Solution Design Document
The written target state: process, authority, architecture, first-slice scope, and the pricing logic — lists, floors, segments, approval thresholds, exception codes — as a section of this document, not a separate file. Configuration is held to it.
Integration Architecture Diagram
How ERP, CRM, the pricing platform and BI will exchange the objects that price depends on — direction, cadence, and who wins a conflict.
Data Migration Plan
What is loaded, from where, in what order, and what “clean enough” means for the first slice. Not a promise to clean the whole book.