I have built revenue with a sales team and without one. At SolarCity I sold inside an established organization and finished at 257% of quota. At Energy Fox, we built more than $7 million in contracted work without a dedicated sales staff. At Clean Energy USA, the immediate problem was not headcount. It was lead quality and follow-up. Changing that process moved the company from eight mostly unqualified leads a month to 15 qualified leads a week, with a 70% close rate.
Those experiences did not teach me that salespeople are unnecessary. They taught me that timing matters. A good hire can expand a working process. They should not be expected to invent the market, recover the founder's unwritten knowledge, rebuild the CRM, and close a long-cycle hardware deal at the same time.
A new hire inherits the process you already have.
Before opening the role, make sure the company can answer four practical questions. If the answers change depending on who is in the room, the work is not ready to hand off.
A technical conversation is not automatically a sales opportunity. The customer needs a real problem, a reason to solve it now, a decision owner, a path to budget, and an agreed next step. Write that definition before a new hire inherits a CRM full of names and is asked to call it pipeline.
If the team cannot agree on what qualifies a deal, the forecast is only a list.
Hardware deals usually involve more than the technical user. Operations, finance, procurement, safety, compliance, IT, and an executive sponsor may all have a say. A new seller needs to know which people matter, what each one is protecting, and how the decision moves from interest to an approved purchase.
Performance data proves the product works. It does not tell finance where the money comes from. The seller needs a simple way to connect the product to labor, throughput, downtime, risk, compliance, or another budget the buyer already manages. That case should use the customer's numbers whenever possible.
Preparation, execution, and review all matter. The team needs a clear owner, a dated next step, useful CRM notes, and a regular review of why deals moved or stalled. That is how the company learns. It is also how a founder can tell whether the process works without sitting in every call.
Consultant, fractional CRO, or full-time leader?
The right choice depends on the work, not the title.
Use a consultant when the problem is defined and has a finish line: buyer research, positioning, qualification, CRM stages, a pilot process, or a hiring plan.
Use a fractional CRO when someone needs to build the process, run live deals with the founder, and take responsibility for the commercial work over a period of time.
Hire a full-time leader when there is enough qualified pipeline and day-to-day management work to justify the seat, the company knows what success looks like, and the process is ready for a permanent owner.
Is the assignment specific? If it has a clear deliverable and end date, start with a consultant.
Does someone need to own live deals now? That points toward fractional or full-time leadership.
Is there enough work for a permanent senior seat? Count qualified opportunities, management needs, and operating responsibility—not just the revenue goal.
Can the company explain what the person will inherit? If not, define the process first.
The full decision tree, fractional CRO versus consultant versus full-time hire, with the scoring questions for each path, runs on its own page: Fractional CRO vs consultant vs full-time hire.
When should the founder stop running every sale?
The founder should stay close to early sales. Those conversations expose problems in the product, offer, pricing, and market faster than a report will. The handoff becomes necessary when the founder's calendar limits revenue or deals stall whenever the founder leaves the room.
The trigger is not a single revenue number. It is whether the company has captured what the founder knows. Before stepping back, document the buyer roles, qualification questions, business case, common objections, sales stages, pilot terms, and the reason past deals were won or lost.
If it is not written down, it leaves when the founder leaves the room.
Run the first deals together. After each meeting, compare what the buyer said with what was entered in the CRM. Review why the opportunity moved, why it stalled, and who owns the next action. The founder should step back one account at a time, after the new hire can run the process without losing the technical or commercial context.
Screen for the sale you actually have.
A strong software résumé is not proof that someone can sell hardware, but it is not a disqualifier either. Ask for specific examples. Has the candidate sold a purchase that required technical validation, operations, finance, and procurement? Did they move a pilot into a production order? How did they qualify budget and decision authority? What did they do during a long stretch when there was no contract to close?
Compensation and expectations should match the real sales cycle. If the company rewards only quick closes, the seller will naturally pursue the fastest work. Define what progress looks like before day one: qualified pipeline created, buying-committee access, stage movement, clean next steps, and revenue from opportunities the person had time to influence.
A practical hiring sequence.
First, learn how the customer buys. Second, document qualification, the business case, deal stages, ownership, and follow-up. Third, decide whether the current need is a project, temporary commercial leadership, or a permanent owner. Then hire against that job and run the first deals together.
The Hardware Go-to-Market Diagnostic reviews the buyer, business case, pipeline, team, and founder dependence before you open the role. For a shorter comparison of the three options, see fractional CRO versus consultant versus full-time hire.