Proof to Pipeline is the name I use for a practical sequence, not a theory. It came from selling residential solar, building a commercial solar company, trying to commercialize advanced materials, mentoring a robotics company through national customer discovery, and advising more than 30 early-stage companies.
The companies and markets were different. The work repeated. We had to learn who could buy, understand why they would change, give them evidence they could use internally, and turn the founder's knowledge into a process the rest of the team could follow.
The four stages keep that work in order. Each one should produce something usable: a buyer map, a business case and message, a working sales process, and a documented handoff.
Why the order matters.
At Voltaic Coatings, we had university technology, non-dilutive funding, and interest from large companies. We still had not solved manufacturing cost, supply-chain fit, and the buyer's reason to switch. Technical progress made the company look further along than the commercial evidence supported.
That same gap appears in sales hiring. A founder sees a flat pipeline and hires someone to fix revenue. The new hire is then expected to identify the buyer, rewrite the message, define qualification, build the CRM process, create demand, and carry a quota at the same time. That is several jobs hidden inside one title.
I want those questions answered before a company adds sales headcount. A good seller can run and improve a defined process. Asking the seller to invent the entire process while being judged on the number makes it difficult to tell whether the problem is the person or the system.
Customer evidence first. Sales process second. Headcount after the work is clear.
Proof to Pipeline follows that order. It starts with customer evidence, turns the evidence into a business case, builds the process around how the customer buys, and tests the process on live opportunities before handing it to the team.
I begin with customers, lost opportunities, stalled deals, and the assumptions inside the company. The questions are straightforward: what problem caused the buyer to act, who first cared, who approved the money, what evidence was required, what slowed the decision, and what almost killed it?
The output is a buyer map for the accounts that matter. It separates the technical evaluator, financial buyer, internal champion, procurement owner, and anyone who can block implementation. It also shows which opportunities have a real approval path and which are still conversations with interested people.
Tric Robotics is a good example. During the NSF National I-Corps program, I served as a formal mentor and advisor while the team conducted interviews across the country. The original low-Earth-orbit drone concept did not produce the commercial evidence the team needed. The interviews helped redirect the company toward UV-C agricultural robotics. The value of the work was not better wording for the original idea; it was evidence strong enough to change the market.
The technical buyer and the financial buyer usually need different evidence. The engineer may care about performance, integration, and reliability. The CFO may care about payback, cash flow, implementation risk, warranty, and what happens if the product fails. The message has to connect those views without flattening the technical advantage.
At SolarCity, East Coast customers resisted an escalating power-purchase agreement. The equipment had not changed, but the offer asked the customer to accept a future payment path that was difficult to explain. A fixed monthly lease made the decision easier to understand. That change helped me reach 257% of quota, maintain a 75%+ close rate, and sell more than $13 million.
The champion needs a business case they can explain when the founder is not in the room.
The output is a clear positioning statement, the financial case, answers to the objections that repeatedly stop deals, and a one-page document the champion can forward internally. Every claim should connect to evidence the company can show.
Once the buyer and business case are clear, I build the operating process: where opportunities come from, what counts as qualified, what decision advances each stage, who owns the next action, what proof the buyer receives, and how the CRM records it.
The stages should describe customer decisions rather than seller activity. "Demo completed" says what the seller did. "Technical evaluation approved" says what changed for the customer. That distinction makes the forecast easier to inspect and gives the team a common definition of progress.
At Clean Energy USA, the inbound channel produced roughly eight mostly unqualified leads a month. After changing the way inquiries were captured, qualified, and worked, the business reached about 15 qualified leads a week and a 70% close rate. Lead source, qualification, ownership, and follow-up had to work as one process.
A process is not proven because it looks complete in a document. We run it against live opportunities, inspect where deals stop, and change the stages, message, proof, or ownership when the evidence says they are wrong.
The main operating measure is qualified-pipeline coverage against the revenue plan. Pipeline coverage is the value of qualified opportunities divided by the revenue target for the same period. The required coverage depends on the company's actual win rate, timing, and deal-size mix. At a 20% win rate, the starting math requires at least 5x qualified coverage before allowing for timing slips or changes in deal size.
I count an opportunity as qualified when the team has identified the technical and financial buyers, confirmed a problem worth funding, understood the evaluation and approval path, and placed a dated next step on the customer's calendar. A conversation can be promising without meeting that standard, but it should not carry the forecast.
Energy Fox shows what this looks like in a complex sale. A commercial solar project had to move through site economics, financing, USDA funding, utility interconnection, engineering, procurement, and construction. We built more than $7 million in contracted work with no sales staff because the three founders could run the same decision process and bring in the right specialist at the right point.
The handoff is successful when the team can explain why a deal is real, what decision comes next, and who owns it.
At the end of the stage, the company has the buyer map, business case, CRM stages, qualification standard, meeting and follow-up process, operating measures, and runbook. The internal owner has used them on live deals before SignalForge leaves.
Where teams get the order wrong.
Starting with the message. The company rewrites the website before interviewing customers and lost prospects. The new copy is cleaner, but it is still based on the same internal assumptions.
Starting with a sales hire. The new leader inherits an undefined buyer, inconsistent qualification, and a CRM that records activity rather than customer decisions. Their first months become discovery work under a revenue deadline.
Starting with more outbound. The team sends more people into a process that has not explained why good opportunities stall. Lead volume rises faster than qualified pipeline.
Any of those moves can be useful at the right time. The problem is sequence. Customer evidence should inform the message. The message and buying process should inform qualification and CRM stages. A sales hire should inherit enough clarity to spend most of the week selling rather than rebuilding the company around them.
What done looks like.
The engagement is done when an internal owner can run the process on live deals without depending on me to interpret it.
The team can name the buyers in each qualified opportunity, explain the business case, show the next customer decision, defend the forecast, and use the same CRM definitions. The founder still joins the deals where founder credibility matters, but no longer has to rescue every follow-up or translate every objection.
The exact conversion rate and coverage will differ by company. What matters is a process the team understands, numbers the board can inspect, and evidence that the process is improving.