A semiconductor company does not sell a chip. It sells a line item in a bill of materials for a product that does not exist yet, to a customer whose own launch date decides when the money arrives. Everything strange about semiconductor go-to-market follows from that one fact, and almost every instrument a first-time commercial leader imports from software assumes the opposite. The practice behind this note lives at GTM consulting for deep tech and hardware.
Separate the design win from the revenue forecast.
Crunchbase counted roughly $10.7 billion in seed-through-pre-IPO semiconductor rounds by June 10, 2026, on pace to pass 2025. MatX raised a $500 million Series B in February. Ayar Labs raised $500 million in a March Series E. Cerebras went public and raised over $5 billion. Companies using that capital to build sales still need measures that match the way silicon is bought.
That gap is where the generic go-to-market consultant does the most damage. A playbook that works on a software purchase assumes the buyer can decide, buy and deploy inside one budget cycle, and that the seller controls the close. On a socket sale, none of the three holds. The general version of that argument is why hardware doesn't sell like SaaS. This note is the semiconductor case, which is the most extreme case in hardware.
A design win becomes revenue only if the customer's product reaches volume.
Four instruments that break on a socket sale.
One: pipeline coverage. Coverage planning requires a value-weighted win rate measured on the same qualified pipeline and time period as the revenue target. A 20% value-weighted win rate implies 5x coverage before timing and slippage adjustments. Do not use the manufacturing benchmark’s 19% average win rate as a semiconductor revenue-coverage target: its weighting and subgroup are not equivalent to your deal economics. In semiconductors, a design win and the resulting production revenue can fall in different years. Track both against the customer’s ramp schedule. See the coverage calculation and its assumptions.
Two: the comp plan. Design the plan around the customer’s program milestones and expected timing. Define how the seller is recognized for qualification, design selection, and production revenue. Use the manufacturing reference for context, then test the assumptions against the specific segment and program.
Three: the forecast. Converting design wins to revenue on a fixed attach assumption produces a forecast of the customer's execution, presented as a forecast of yours. Sockets get cancelled. Programs slip. End products fail in their own market and take the silicon with them. The number is not wrong because the assumption is too aggressive; it is wrong because it is unexamined and carried forward year over year without ever being scored against what actually shipped.
Four: selling only to the engineer. A semiconductor design-in may also involve firmware, component engineering, quality, procurement, and requirements passed down by the customer's own customer. Map the actual roles and what each needs before treating the opportunity as secure. The broader discussion is in the hardware buying committee.
The evaluation board is a pilot, and it converts like one.
An evaluation board needs a defined commercial next step. Identify the program, the budget owner, the qualification requirements, and the decision that a successful evaluation would unlock. Give the engineer a path from technical evidence to the people who approve the program.
What converts an eval is what converts any pilot, and it is decided before the board ships rather than after it works. A named program the part is being evaluated for, with a start-of-production date attached. A named person who owns the decision to design it in, distinct from the engineer running the bench. The second-source position stated plainly, because component engineering will raise it and the honest answer is better than a surprised one. The qualification burden agreed in writing, including who pays for it and what the schedule is. Non-recurring engineering terms that do not quietly obligate a roadmap. The design rules are in pilot to production; the semiconductor translation is only the vocabulary.
The pattern the good companies run is unglamorous: fewer evals, each one attached to a program. A high eval-board count is a vanity metric with shipping costs. It measures curiosity, and curiosity is free.
What to build instead: four moves.
If you run a semiconductor company between $1M and $20M in revenue, make sure the sales measures match the transaction before adding headcount. Four moves help.
Instrument the design win as a stage, not an anecdote. A design win is only real when three fields are filled: the socket, the customer program it sits in, and the expected start of production. A design win with a blank program field is a relationship, and a design win with a blank production date is a hope. Companies that will not enforce those three fields cannot forecast, and no consultant can fix a forecast built on records that do not exist.
Run two pipelines and never merge them into one board slide. The design-win pipeline is what the commercial team controls: opportunities to be selected. The revenue pipeline is what the customer controls: won sockets moving to volume. They have different conversion rates, different cycle times and different owners. A board shown a single number gets a number that means two things, and the ambiguity always resolves in the optimistic direction. Two charts is not a reporting preference, it is the difference between a company that knows why it missed and one that does not.
Pay on the event the seller controls. Design-win credit at design-win time, with a revenue component that follows the ramp. The exact split is a company decision and depends on runway and on how much of the ramp risk sits inside the customer rather than inside the product. What is not a company decision is the principle: a plan that pays only on recognised revenue makes every seller a volunteer for one to two years, and the good ones will not volunteer twice.
Make the reference design easy to find and cite. Publish the evaluation results, documentation, and integration path in a form an engineer can inspect and share. G2’s software-buyer research gives context for the role of AI-assisted discovery; it does not measure semiconductor purchasing. The method that connects technical evidence to commercial decisions is Proof to Pipeline.
A funded sector is not a buying sector. The $10.7 billion is investor conviction about AI infrastructure, not evidence that design-in cycles have shortened or that the buyers on the other side of the table have more budget. Cerebras raised over $5 billion in its IPO and its shares were down about a third from the first-day close five weeks later (Crunchbase, June 10, 2026). Capital markets and customer markets are different markets and they turn at different times.
Silicon has been bought through a design win, qualification, and customer production ramp for decades. Tracking those events separately remains useful when the funding cycle changes.
Three questions, answered straight.
What does semiconductor GTM consulting actually cover?
The work defines a design win with a named socket, program, and expected start-of-production date; separates design-win opportunities from forecast revenue; aligns compensation with events the seller can influence; and makes the reference design, evaluation data, and integration path easy for buyers to inspect. The firm-level engagement is described on the GTM consulting page; the earlier-stage version is go-to-market consulting for hardware startups.
Why do semiconductor sales forecasts miss even when design wins are up?
A design win depends on the customer's product reaching production volume, and some won sockets never ship. Track design-win opportunities and forecast revenue separately, then compare attach and ramp assumptions with actual results.
Is an evaluation board the same as a hardware pilot?
Yes, when the evaluation is tied to a named customer program, socket, production owner, qualification path, second-source requirements, and decision date. An evaluation board sent without that context may produce useful technical feedback without creating a production opportunity.
Keep reading.
This note sits inside a published method. Start with the page that ties it together, or go straight to the piece that names your stall point.