Frontier software

Setup

A coordination product for an industry running on email, spreadsheets and phone calls. No comparable vendor, no analyst category, no line in anyone's budget, and therefore no way for a champion to buy it without inventing a justification from scratch.

What happened

Sales were slow and the pipeline looked terrible for a year. The turn came when the company stopped selling software and started quoting the cost of the specific coordination failure it removed — a number the customer's own operations team already tracked and hated. The category name arrived after the first ten customers, invented largely by those customers, not before them.

Where it stands

It is now the reference vendor in a category with three named competitors and an analyst quadrant. That is validation and also the point at which pricing power begins to erode, so we watch discounting and win rate against the new entrants rather than category growth.

Quarters before category emerged

4

What unlocked sales

cost of the failure removed

Named competitors today

3

Categories are lagging indicators. Give a thesis about four quarters to produce a category name before you treat it as a hobby — and start watching price the moment the name exists.

Setup

A simulation tool sold into hardware engineering teams whose prototyping budget was a visible, painful, separately reported line item. Pricing started as per-seat, which put it in the same procurement conversation as CAD licences.

What happened

Adoption tracked the cost of a single physical iteration almost exactly. Where a prototype cost a few thousand dollars, the tool was a nice-to-have that lost to inertia. Where an iteration cost millions and took a quarter, it sold itself in one meeting and the seat count was irrelevant to the buyer.

Where it stands

Expansion is targeted by iteration cost rather than team size, pricing is anchored to iterations avoided rather than seats, and win rates in the high-iteration-cost segment roughly doubled. The low-cost segment was deliberately abandoned.

Adoption predictor

cost per physical iteration

Win rate after re-segmentation

~2x

Pricing basis

iterations avoided

Developer and engineering tooling is priced against the cost of the thing it removes, not against headcount. Segment the pipeline by that cost before you read any conversion rate.