Business requirements

“We got a proposal for a $180,000 rebuild. Nobody internally could tell me whether we needed it.”

Three agencies quoted three different projects at three different prices, and none of them asked what your dealers actually do with the site. Your CEO wants a number. Your IT lead wants to know what happens to the integrations. Sales wants the quote form to stop losing leads. Nobody has written down what the site is supposed to accomplish, so every proposal is a guess.

You can’t approve a project you can’t define.

What we do

We interview the people who use the site and the people who suffer when it doesn’t work: sales, inside sales, operations, IT, dealers, sometimes customers. We map how leads and product data move through your business today, including the spreadsheets and forwarded emails nobody documented.

We audit what you have: platform, integrations, analytics, content, technical debt, security posture. We separate what’s broken from what’s merely old.

Then we write it down. A requirements document with functional specifications, integration dependencies, success measures, and a phased roadmap with cost ranges for each phase.

What you get

A document you own. Detailed enough to send to three vendors and get three comparable bids. Specific enough that your IT lead can review it and find nothing missing. Clear enough that your CEO can see what the first phase costs and what it returns.

You also get a defensible answer to “do we need a rebuild.” Sometimes the answer is no, and that’s worth knowing before you spend the money.

What it looks like when it’s working

Your leadership team reads one document instead of sitting through four pitches. The project gets approved in one meeting because the scope is bounded and the phases are priced.

Six months in, nobody has said “we didn’t think about that.”

Start here

Bring us the proposal you’re not sure about. We’ll tell you what it’s missing and what it would take to define the work properly.

[Book a 30-minute scoping call →]