The first time you sell something, you assume that selling is convincing. You book the meeting, you demo the product, you walk the buyer through the roadmap. Build a better mousetrap, the old line goes, and the world beats a path to your door. It does not.
When nobody has heard of you, the buyer is not really evaluating your product. They are pricing a risk, the risk that you will cost them a year. That caution is earned. More than 70% of companies that attempt a digital transformation get stuck in the pilot stage, often for years on end, and in one McKinsey survey 85% spent more than a year in pilot and 28% spent more than two. Gartner has a name for the reflex this produces, a "risk bias" toward established vendors, where a young company's chance of failing weighs more heavily than its chance of paying off. So a roadmap from a company with no track record is just a promise, and a promise is the one thing this buyer has already learned to discount. That is where feature-led selling stalls.
The way through is almost backwards. You stop selling the product, and you put a single outcome on a clock instead. Credibility is the one thing you cannot borrow when you are unknown, so you manufacture it, one measurable result at a time. That result is the only asset you can build before you own a single logo.
Getting the first meeting
Before you can prove anything, you need the meeting. In industrial accounts, the meeting often comes through a relationship, not a cold email. A COO will not take a call from a company they’ve never heard of, so the first real conversation arrives through someone who vouches for you: a design partner, an operator who already trusts you, an introduction from a person the buyer respects.
This is the part most first-time founders underestimate. You may have the product instinct, but you almost certainly do not have standing relationships with plant directors and heads of operations, and you do not have the years it takes to build them one dinner at a time. That is the gap a studio closes. An OSS co-founder starts with the industrial network already in place, so the introduction that would take a solo founder years to earn becomes the starting position rather than the reward.
Why a measured result beats a feature
A feature list does not answer the buyer's real fear, that you are the fourth pilot who fails. A measured result does. That is the whole shift: a feature is a promise, while a result, inside a fixed window, is the one thing an unknown founder can offer that the buyer can check without trusting you.
Paul Graham made the point in Do Things that Don't Scale: "you have to do sales yourself initially." Pick a single user, he writes, and treat them as if you were "consultants building something just for that one user," because that user "serves as the form for your mold." The polish you lack matters less than you fear. You can give someone "an insanely great experience with an early, incomplete, buggy product, if you make up the difference with attentiveness." Stripe understood this. When someone agreed to try the product, the founders did not send a signup link; they said "give me your laptop" and set the person up on the spot.
So the shift is easy to say and hard to do: stop selling the software, and start selling what it changes in an operator's day, the work that gets faster and simpler, and then put that change on a clock. A result, delivered by an agreed date, on the buyer's own site, is something they can verify without trusting you at all. That is why it carries weight when nobody knows your name.
None of this makes the job easy. Selling into a large industrial account as an unknown founder is hard, and harder still with no one alongside you who has done it before. Closing that gap is the reason the co-builder model exists.
Setting the success gate with the customer
The instinct, when you are unknown, is to over-promise. Do the reverse. You tell the buyer, up front, what would make the project fail, and then you build the trial together: one measurable result, a fixed deadline, a named owner on their side, a shared definition of pass or fail, and the conditions under which you walk away.
This is the go/no-go gate OSS runs on its own ventures, only turned outward and agreed with the customer. It feels backwards. Naming how you could lose, before you have won anything, sounds like weakness, and it is the opposite of weakness. Hide the downside and you look like a salesman; hand the buyer a clean way to call the whole thing off, and you look like proof.
Proving in one place before scaling
McKinsey's deeper finding is that the hard part is not running a pilot, it is scaling one, and pilots die when they are run as one-offs that never plan for the rollout. The founder-side version of that discipline is the anchor-client rule. Validate in roughly three sites before you scale, and start with one site, one workflow, one number, because the surest way to stall is to try to prove everything at once.
Founders reasonably doubt that a real result can land in weeks. The deployment data says otherwise. Bonx deploys in three to ten weeks, while Juno runs its pilots in six weeks. And one validated result compounds: at Teknor Apex, a stack of OSS portfolio companies proven on a single Rhode Island site is now scaling across the rest of its footprint. You prove it in one place, and you earn the right to the next ten.
The playbook for success
- Lead with the value. Open with the outcome in the operator's own words, translated into the one number the COO already cares about, and leave the roadmap out.
- Pick one site, one workflow, one number, because trying to prove everything at once is how projects stall in pilot.
- Set the success gate with the customer up front: the result, the deadline in weeks, the owner on their side, what counts as pass or fail, and how you walk away.
- Over-deliver on the experience. Do by hand what the product cannot do yet, because showing up makes up for the polish the product does not have.
- Hit the number before you expand. Hold the roadmap until the first result is on the board, then move from the anchor client to about three sites and then to scale.
What makes you sellable when you are unknown, proving one result before you ask for commitment, is the same discipline OSS runs by default: lead with the outcome, set the gate with the customer, prove before you scale.
Proof is the part you can build without a track record. The relationships that get you into the first meeting are the part you cannot, and they are what OSS brings on day one.
