Analytics consulting for businesses with more data than insight.

Method Strategy Consulting is the independent practice of Andrew Valentine, a former Business Analytics Director with over a decade of experience building the KPI frameworks, reporting systems, and pricing experiments that operationally complex businesses run on. Engagements here are defined and scoped up front, with clear deliverables and end dates.

What I do

Four ways I engage with clients, each scoped before work starts. Most prospects land on one of these, though the right shape sometimes emerges from the first conversation.

KPI & Reporting System Build

A defined project that produces an aligned set of KPIs and the reporting infrastructure to track them. Good for companies where every team has its own version of the numbers and leadership reviews keep getting stuck on which figures to trust.

Pricing & Experimentation Programs

A defined project to run an A/B pricing or product test end-to-end, with the test infrastructure left in place to run further experiments after. Good for businesses sitting on a pricing decision they can't make confidently from instinct alone.

Embedded Analytics Leadership

Interim analytics leadership tied to a specific transition or milestone. Good for companies that need senior direction now without committing to a permanent hire yet.

Advisory Retainer

A monthly engagement covering KPIs, reporting, and experimentation strategy. Good for leaders who want senior outside perspective without adding headcount or scoping a larger project.

Where I focus

The work tends to land in retail, CPG, automated retail and operations, logistics, and SaaS. The common theme across these industries is operational complexity - distributed locations, physical inventory, high-value pricing decisions, and customer behavior worth testing. My background is largely in distributed-kiosk retail (Redbox and Automated Retail Technologies), and most of the methods translate cleanly to any business with locations, units, or transactions to optimize.

Clients are typically based in Chicago, New York, Boston, Washington DC, Atlanta, Miami, London, and Birmingham, but anywhere else reachable in US Central, Eastern, or UK working hours works great. All work is fully remote.

Selected results
  • Eight-figure annual incremental revenue impact from a pricing change, built on survey-based elasticity work and test/control market experiments.
  • Significant reduction in kiosk downtime from a predictive failure model built on error code and sensor telemetry data, used to prioritize technician dispatch toward kiosks at risk of imminent failure.
  • Cluster-based cannibalization & accretion model that let leadership target kiosk removals without over-cutting any single trade area, while preserving leaders' qualitative input on the final decisions.

Read the case studies →

Common questions
What if we don't have any analytics tools or infrastructure in place yet?
I can build the reporting layer on top of most existing setups, but standing up a data warehouse from scratch isn't my area of expertise. If that's where you are, I can point you toward BI and data engineering specialists who do that well, and I'm happy to come in once the foundation is in place. If you're unsure about your situation, for example if you have data in operational systems but no real warehouse yet, I can talk through what's actually needed. Sometimes the answer is simpler than it sounds.
Do you work with our existing analytics team, or instead of them?
Almost always with them. Your existing team knows your data and business best, and they're the ones who'll keep the work running after I leave. I tend to act as a senior partner to in-house analysts rather than a replacement, pairing on harder problems and leaving documentation behind that the team can build on. The exception is embedded leadership engagements, where the point is to fill a senior gap that doesn't currently exist on the team.
Do you work hourly or by project?
Most engagements are project-based with a fixed price agreed up front. Retainers are billed monthly. Hourly billing is generally avoided.
How quickly can you start, and what do you need from us to get going?
Typically a week or two between signing and starting active work. I use my own hardware and tooling by default, but can remote into a client environment when security policies require it. To get moving I need read access to the relevant data sources, a point of contact for questions, and an intro to whoever uses the current reporting most. Onboarding friction is almost always on the access provisioning side, so the faster that moves, the faster the work does.

See the full FAQ & get in touch →