Frame
Agree on the decision
Confirm the business question, participants, evidence required and what the final recommendation must answer.
The first paid engagement
Readiness & Roadmap.
A bounded Discover-phase engagement that turns the initial conversation into a documented decision about what to do next. It can end with a recommendation to proceed, address prerequisites first or pause.
Decision at the end
Proceed, address prerequisites or pause.
The work establishes whether your data, operating model and decision rights can support the transformation you are considering — before a larger commitment is made.
- Proceed with a defined first slice
- Address prerequisites with named owners
- Pause with the reason documented
- Purpose
- Test readiness and define the responsible path into pricing transformation or software delivery
- Your team
- An executive sponsor plus the people who own pricing, finance, sales or operations, and IT or data
- Inputs
- A representative data extract, current price rules or lists, approval paths, architecture context and available reporting
- You receive
- Findings, a readiness and gap register, current-state and decision-rights maps, business-case assumptions, and a phased roadmap with a recommended first slice
- Boundary
- No software configuration or enterprise-wide data remediation; those are scoped only after the findings are agreed
Diagnose
Establish what is true
Review representative data, map the process that actually runs and surface gaps in ownership, authority and adoption.
Decide
Leave with a commissioned next step
Review the findings, agree the roadmap and identify the first slice — or the prerequisites that must come first.
What the first two weeks look like
Frame, then start diagnosing. Nothing is configured.
- Day one A working session with the sponsor and the owners of pricing, finance or sales, and IT or data. We agree the business question, who decides, and what evidence the recommendation needs.
- Week one The data extract and the current price lists or rules arrive in whatever form they exist today. We read them as they are; nothing is cleaned for us.
- Week two The first process-mapping session: the pricing process that actually runs, not the one in the policy manual. Interviews on who approves what, and where the informal agreements live.
- After that Diagnose continues until the findings hold up, then the Decide session closes the engagement with a documented recommendation.
What we need from you
A checklist your IT lead can act on.
- A representative extract of invoiced transactions with cost, customer and product identifiers, in whatever format exists today
- The current price lists or pricing rules as they are actually used, including the spreadsheets
- The approval paths for discounts and exceptions, written down or described — including the informal ones
- A one-page picture of the systems involved (ERP, CRM, BI) and how a price travels between them
- The reports pricing, finance and sales look at today, in whatever state they are in
- An executive sponsor who can settle a disagreement between two business units
Describe the business question only when you first write to us. Data extracts are exchanged only under the statement of work, never through the website. How we handle data →
Commissioning it: after the consultation, you receive a statement of work naming the participants, inputs, working sessions, deliverables, exclusions, schedule and fee. Nothing proceeds until those are agreed.