How I work

Choose the right way to work together

Start with a Revenue Operations Blueprint, a defined implementation project or retained consulting. The right model depends on how clear the problem is, how quickly you need to move and who will do the work.

  • Clear scope and responsibilities
  • Hands-on delivery where needed
  • Direct senior access
Choosing a starting point

The engagement should match what is known

If the outcome and work are clear, a fixed implementation can make sense. If several systems or teams are involved and the real scope is uncertain, define it first. Retained consulting suits priorities that will develop as the team implements, learns and makes decisions.

I will recommend the simplest model that gives the work a realistic chance of succeeding.

Clear outcome

You know what needs to change

Use a defined implementation when the required result, boundaries, access and dependencies can be agreed before work starts.

Developing problem

You need clarity or ongoing judgement

Use a Blueprint when scope is unclear, or retained consulting when priorities will evolve through regular working sessions.

Three engagement models

A defined start, build or ongoing working relationship

These models can follow one another. A Blueprint may lead to implementation, and a completed project may move into retained improvement. Start with the smallest engagement that matches what is known now.

Define

Revenue Operations Blueprint

Map the current process, agree the future process and system ownership, record risks and dependencies, and produce a prioritised implementation plan.

Explore the Blueprint

Build

Fixed-scope implementation

Configure platforms, clean or migrate data, build automation and reporting, test exceptions and support launch and handover against an agreed outcome.

View implementation work

Improve

Retained consulting and mentoring

Work through developing priorities with regular decisions, direct implementation, actions and accountability between sessions.

View retained consulting

How the models connect

Start with what is known now

A Blueprint may lead to implementation, and a completed project may move into retained improvement. The next scope is agreed only when the evidence supports it.

How the work runs

Working sessions are for decisions and progress

Working sessions are used to make decisions and move the work forward. We work through evidence, test the process and remove blockers. Actions between sessions are explicit, with an owner and a reason.

My responsibility

Analysis, design and implementation

Prepare the work, challenge weak assumptions, configure agreed changes where appropriate and keep the technical and commercial detail connected.

Your responsibility

Access, context and adoption

Provide the right people, examples, system access and timely decisions. Internal ownership matters because your team must use the result after the engagement.

Shared responsibility

Testing and decisions

Review real scenarios, test exceptions, record what was agreed and change direction when evidence shows the original assumption was wrong.

Scope and change control

Clear boundaries without pretending nothing will change

Every engagement records the intended outcome, included work, assumptions, dependencies and client responsibilities. If new information changes the work materially, we decide what to stop, defer or re-scope before continuing.

At the start

Outcome and included work

Agree what success means, what is in scope, which systems and teams are involved, and who owns each dependency.

During delivery

Evidence and changes

Track decisions, surface constraints early and distinguish a correction within scope from genuinely additional work.

At review points

Next sensible phase

Close completed work properly, identify what remains and agree the next phase only when it can be scoped responsibly.

A good working fit
  • You can give the work an internal owner
  • The right stakeholders can make decisions
  • Real examples and system access are available
  • Your team is prepared to test and change the process
Direct and practical

You work with me, not a rotating delivery team

I combine strategic decisions with detailed system and process work. That is most useful when you want senior judgement without handing the project through several layers.

Frequently asked questions
How do we decide which engagement model to use?

Start with what is known. A fixed implementation suits a clear outcome and scope. A Blueprint suits a cross-system problem that needs definition. Retained consulting suits priorities that will develop through regular work and decisions.

Do you publish fixed packages or prices?

No. Public package names and fixed prices would create false precision because the effort depends on scope, system condition, access, dependencies and the amount your team will own.

What happens between working sessions?

I may analyse data, configure agreed changes, prepare designs or tests and document decisions. Your team may need to supply examples, complete actions, test changes or make an internal decision before the next session.

Can an engagement change shape?

Yes. A Blueprint can lead to a fixed implementation, and a project can move into retained improvement. Material changes are discussed and re-scoped rather than quietly added to the original commitment.

Discuss the most sensible place to start

Share the problem, what you already know and how involved you want your team to be. I’ll help you choose a proportionate first engagement.