Acuity Sourcing The Method
How we work

A playbook,
not a pitch.

Twenty years of enterprise software deals, every stage of every one. The playbook is what twenty years accumulates into. Knowing when to run all of it, and when to compress it, is where the experience comes in.

01 / Premise

The deal is half built before procurement walks in.

A business user gets handed a problem they have not fully defined. They start watching demos. The vendor begins to fill in the requirements. By the time anyone formalizes what the business actually needs, the price is set on the vendor's terms, the integrations are scoped to the vendor's strengths, and the decision criteria match the vendor's marketing.

None of it is malicious. It is what happens when a buyer arrives unprepared and the vendor offers to help.

The Acuity Method is built for the upstream work. The part of the deal that decides the outcome before anyone sees a price. Done well, the negotiation is half over before it starts.

02 / Structure

Three phases. Each does a specific job.

The method mirrors the buyer's actual journey. Each phase produces a written artifact that the next phase depends on. The sequence is not flexible. The depth is.

i.

Define what good looks like.

Establish what the business actually needs from a platform, in business terms, before any vendor is in the room. This is harder than it sounds. Most teams cannot separate what they need from what their current system does. We do that work for them and produce a written, prioritized specification that holds up under scrutiny.

ii.

Make a defensible recommendation.

Compare the real options against the requirements. Model the all-in cost of each path, including the cost of staying where you are. The output is a decision a CFO can sign without losing sleep, and a price position the vendor cannot easily move you off.

iii.

Make the win sustainable.

A signed contract is not the end of the work. Renewals are where most savings get given back. We build the governance and review cadence that keeps the decision strong every year, so the second negotiation is not a starting from zero exercise.

03 / Substance

What is underneath each phase.

Inside each phase sits a set of working frameworks. We are not going to lay them out here. The short version is that they cover the four areas where most software deals are won or lost.

Requirements that survive a vendor demo.

A written, prioritized, system-agnostic specification that does not collapse the first time a salesperson shows up with a slick screen. Built by facilitating the business unit, not by surveying them.

Integration and dependency mapping.

A scored map of every system that touches the platform, with the cost and risk of each connection quantified. The thing that turns "we cannot leave" into a number.

Total cost modeling, both paths.

The cost of staying with the incumbent, modeled honestly. The cost of leaving, including switching friction. The number where the math flips is the negotiating position.

Governance that holds at renewal.

A standing committee with named decision rights, a review cadence, and a documented trigger price. So the next renewal conversation starts from your position, not the vendor's.

04 / Fit

Where this work pays for itself.

  • Decisions where the wrong move costs millions over the contract
  • Renewals where the vendor knows more about your usage than you do
  • New categories where there is no internal precedent to lean on
  • Deals that have stalled because the executives are not aligned
A note on scope The method described here is the full form, deployed when the size and complexity of the deal justifies it. Most engagements are subsets. A renewal under time pressure looks different from a category transformation. The principles are the same. The shape of the work changes.
If you have a software decision that matters, we should probably talk before the vendor does.
Acuity Sourcing See the Opportunity. Seize the Value.