At Voltaic Coatings, we had university technology, non-dilutive funding, and large-company interest. We still had not answered the manufacturing cost, supply-chain fit, and buyer's reason to switch. The technical milestones made us look further along than the commercial evidence supported. That is the risk I look for first in a hardware startup.
What a hardware startup actually buys when it buys GTM help.
When revenue is below plan, hiring a head of sales feels like a direct answer. But if the company has not defined the buyer, business case, qualification standard, sales stages, and proof, the new leader has to discover all of that while carrying a quota. Several jobs are hidden inside one title.
Good GTM consulting should leave the eventual hire with clear work: who to sell to, why the customer changes, how the financial case is explained, what qualifies an opportunity, what decision advances each stage, and how the CRM records it. The team should own those answers and the documents behind them.
Do not ask the first sales leader to discover the market, build the process, and hit the number at the same time.
Why the SaaS playbook breaks the moment you scale it.
Software sales methods are easy to find, so hardware founders often inherit them without making a deliberate choice. A physical product can require financing, technical validation, procurement, installation, training, and support. Why hardware doesn't sell like SaaS explains how that changes budgets, pilots, buying groups, timing, and risk.
The forecast has to reflect the actual math. At a 19% win rate, the starting point is roughly 5.3 times the revenue target in qualified pipeline before allowing for timing slips or changes in deal size. The team also needs a common definition of qualified; otherwise the coverage number is only a larger version of the same uncertainty.
Start by understanding the customer decision. That tells the team which activity can move a real opportunity and which activity only creates motion.
The proof does not travel by itself.
A pilot can prove the technology to the engineers who ran it and still produce no order. The people who approve production may never have agreed to the success criteria, budget, implementation plan, or decision date. Pilot to production explains how to define those items before the hardware ships.
The champion needs a result they can carry without the founder: the line ran faster, defects fell, capacity returned, energy cost dropped, or labor changed. The number has to be the customer's result and connect to a financial decision. That is the second stage of Proof to Pipeline.
The technical result matters when the customer can connect it to a funded business decision.
The competitor you are actually losing to is no decision.
Founders usually compare themselves with other vendors. In many hardware deals, the harder competitor is no decision. The committee can delay because nobody has shown that the cost of waiting is greater than the risk of buying.
The sales case therefore needs both sides of the decision: why this product and why act now. The second question is often missing from a technically strong pitch.
What the engagement looks like in practice.
I use four stages in order and document the work as we go. The full walkthrough is in Proof to Pipeline.
Interview customers and lost prospects, map the technical and financial buyers, and separate qualified opportunities from promising conversations.
Connect the engineering advantage to cost, payback, implementation risk, and the reason to act. Give the champion evidence they can forward.
Define qualification, CRM stages, ownership, follow-up, proof, and the customer decision required to advance each deal.
Use the process on live opportunities, fix what breaks, and transfer it to an internal owner who has already run it.
When it is not the right spend.
Outside GTM help is the wrong purchase if the product has not shipped or the current sales process already works and simply needs more coverage. The choice between a fractional operator, a consultant, and a full-time hire is compared on cost, speed, accountability, and fit in fractional CRO versus consultant versus full-time hire.
The Diagnostic is built to tell you no. It scores your engine across twelve dimensions and names the next move. Sometimes the next move is a Sprint. Sometimes it is a specific internal fix. Sometimes it is no outside help at all.
That last answer is a valid outcome and it is priced the same. A consultant whose diagnostic cannot return "you do not need me" is not running a diagnostic.
Read the thinking first.
The method is published before the first conversation. Start with the piece that matches the problem you are seeing.