The autonomy community does not suffer from a shortage of good ideas. It suffers when companies cannot turn those ideas into products customers will buy before the money runs out. That distinction drove a recent Dawn of Autonomy podcast conversation with Lori DeMatteis, consultant and strategic advisor at Lavin Holdings. Drawing on experience at companies including Honeywell, GE, Emerson, Iris Automation and MatrixSpace, DeMatteis challenged founders to stop treating technical achievement, investor interest and enthusiastic demonstrations as substitutes for revenue. Her closing advice captured the approach: “Let’s take the complex, make it simple and move it out.” For drone, robotics and autonomous systems businesses, that means simplifying more than the pitch. It means clarifying the customer, the buying process, the integration requirements and the financial path to a sustainable business.
Autonomy Startup Revenue: Don’t Mistake Need for Purchase
A prospective customer loves your demonstration. A military user sees a mission application. A conference organizer invites you to another event. Encouraging? Yes. A sale? Not yet.
“Don’t mistake need for purchase,” DeMatteis cautioned. She continued, “You must ask yourself, ‘Is there a need for it AND would they buy it?’” Founders must establish both, rather than assume that interest will eventually produce an order.
The reality is that a user may genuinely want your product but lack purchasing authority. Or an organization may recognize the problem but rank other needs higher on their “to do” list. A solution may deliver value but cost more than the customer can justify.
The practical lesson is to qualify the opportunity before committing scarce resources to yet another demonstration. Identify the mission problem, the person who controls the purchase, the available budget and the steps between interest and an order. Then test the economics.
DeMatteis urged founders to explain what they sell, how they price it and whether the business model combines an upfront purchase with recurring software revenue. The product must support the customer’s return on investment and the company’s profitability. Technical excellence cannot rescue a price that makes no business sense.
The Golden Rules for Making Money in Autonomy
DeMatteis identified several golden rules throughout the conversation. Together, they offer a framework for turning promising technology into a viable business:
Understand The End User And Speak In Their Terms
Start with the customer’s mission, not your feature list. Explain how the product solves a specific problem within that customer’s operational and financial constraints.
Know The Customer’s Budget Cycles
A customer who wants to buy cannot necessarily write a check tomorrow. Learn when the organization plans, approves and spends its money.
Choose Your Initial Investors Wisely
The first investors influence what happens several years later, not just whether you can hire next month. DeMatteis warned that investors who expect an early exit can push a company toward a sale before the founder considers it ready. Discuss growth expectations, timelines and exit priorities before accepting the money.
Keep The Business Explanation Simple
“Make sure you talk as a non-technical person,” DeMatteis advised. She described reviewing a one-page explanation that required deep scientific expertise to decipher. Translate complexity into business language including what the product does, who needs it and why it matters. A clear 30-second elevator pitch gives buyers and investors a starting point. Save the technical depth for the audience that needs it.
Tell The Truth About What Works..And What Does Not
DeMatteis closed her do’s and don’ts with a direct warning, “Please don’t lie. Please don’t over exaggerate.” Describe the product’s current capabilities and limitations honestly. Credibility matters when customers depend on autonomous technology in consequential environments, and inflated claims create expectations the company may never meet.
Drone Commercialization: Budget for the Entire Customer Lifecycle
A working product does not automatically equal a deployable solution. DeMatteis illustrated that gap with an unnamed Estonian company that, according to her account, gained selection through NATO’s DIANA accelerator but failed to advance to the next phase. The company generated interest, yet it did not secure a buyer or complete the integrations customers needed. Her slide framed the lesson as an implementation and support problem, to understand the entire user lifecycle:
- Where does your product fit into the customer’s existing operation?
- Which systems must exchange information with it?
- What must happen after installation for the customer to use it effectively?
DeMatteis recalled similar challenges at Iris Automation. Different customers required different integrations, and she said those efforts could cost $1 million to $2 million. Each custom integration raised another question: how would the company earn back that investment?
For autonomy founders, integration belongs in the business model from the beginning. Map the operational workflow, identify the interfaces and account for implementation and support. Otherwise, a product that looks profitable in isolation may lose money every time someone buys it.
Startup Funding: Raise Enough to Reach the Next Real Milestone
Undercapitalization can trap a company in a cycle of constant fundraising instead of product development and sales.DeMatteis urged founders to build an initial financial foundation that supports meaningful progress. The uncomfortable tradeoff is that founders may need to surrender more ownership to secure enough capital, rather than preserve a larger share of a business that cannot move forward.
Budget beyond engineering. DeMatteis specifically identified patents, legal fees, export-control considerations and travel as expenses that accumulate quickly.
Also, distinguish funding for development from money available to build the commercial operation. She warned against treating Small Business Innovation Research awards and other award dollars as an unrestricted sales and marketing budget. Her underlying business lesson is to plan how to finance customer acquisition and other business needs rather than assume a development award will cover everything.
Finally, valuation deserves equal discipline. A headline-grabbing number can create expectations the company cannot support. DeMatteis warned that an overly ambitious initial valuation can lead to a later down round, with consequences for employees and investor confidence. Choose financing terms that support the next stage of growth, not just today’s announcement.
Autonomy Sales Cycles: Plan for Cash, Not Promises
DeMatteis offered a solid planning rule: allow twice the time you expect for sales, product development, manufacturing and hiring. Her point was not that every task always takes twice as long. It was that optimistic schedules leave little protection when contracting, delivery or payment slips.
An end user’s approval may still require a contracting officer and additional paperwork. After the order, the company may need to perform before it receives payment. DeMatteis described walking a founder through that sequence and discussing whether an upfront payment might help bridge the gap.
Build the forecast around when cash arrives, not when someone says yes. Include procurement steps, performance obligations and payment terms. A promising order does not pay payroll while it remains an unpaid promise.
Manufacturing and Startup Ecosystems: Find Help Without Losing Focus
Founders do not have to build every capability themselves. DeMatteis identified supportive organizations that can assist small businesses with manufacturing from prototype to scale, office space, executive mentoring, financing and introductions. She pointed to resources including Capital Factory in Austin and the Youngstown incubator.
The lesson is to seek help against a defined business gap. If manufacturing limits delivery, look for manufacturing capacity. If the team lacks commercial experience, seek leadership guidance. If testing conditions matter, find an ecosystem that matches the operating environment.
DeMatteis encouraged founders to arrive with a product they can explain and an honest assessment of its maturity. Different organizations support different development stages, so target the help that fits where the company actually stands.
The opportunities, in her view, are real. Capturing them requires founders to replace vague enthusiasm with a customer, a workable deployment and a financial plan. “I don’t want people to be discouraged,” DeMatteis said. “I just want you to be smart.”