SOVE7GN GTM
Deep tech go-to-market: long cycles, pilots and named accounts
Updated 11 November 2026 · Written by Reyansh Juneja and Naman Dhiman, the co-founders of SOVE7GN, who run inbound, midbound and outbound for founders
Deep tech go-to-market is account-based, not volume-based: when there are 40 to 400 organizations on earth that could buy what you built, every one of them gets researched, named and worked individually, and the sales cycle is measured in quarters. The work is to get a paid or structured pilot with a named sponsor, then convert that pilot into a contract through a procurement process you should map before the pilot starts.
Short answer: write the full list of possible buyers on one page. If it fits, you do not need outbound volume, you need depth. Target a technical sponsor and an economic sponsor at each account, aim for a scoped pilot with a written success measure, and treat procurement, security review and legal as part of the sale rather than paperwork at the end. Expect 9 to 24 months from first conversation to signed contract in most regulated industries, and budget cash for it.
How is deep tech go-to-market different?
| Volume software sales | Deep tech sales | |
|---|---|---|
| Possible buyers | Thousands | Often under 500, sometimes under 50 |
| First contact | Cold email or inbound form | A conference, a paper, a mutual contact, a named cold approach |
| Who you talk to first | A manager with a budget | An engineer, scientist or program lead with no budget |
| Proof required | A demo and a reference | A pilot on their site or data, often with their own test protocol |
| Cycle length | Weeks to months | Quarters to years |
| Deal structure | Subscription | Pilot, then a contract, sometimes a joint development agreement |
| Biggest risk | Being ignored | A champion who leaves, or a pilot with no path to a budget line |
The consequence is simple arithmetic. If 60 organizations can buy from you and you need 6 customers in two years, you cannot afford to burn an account with a bad first message. One careless sequence to a list you bought can cost you 2% of your entire market.
Should a deep tech startup do volume outbound?
No. Run named-account outreach instead. The difference is not the channel, it is the preparation per account.
For each named account, before anything is sent, you should be able to write down: the program or product line your technology fits, the person who owns that program, the person who owns its budget, what they have said in public about the problem, which peer or competitor is already working on it, and their buying route (direct contract, framework agreement, prime contractor, government program).
That is four to eight hours per account, or a quarter of a person's year for 60 accounts. It is also the only version of outbound a chief engineer answers. The general method is on warm outbound vs cold outbound, and the triggers are on buying signals for B2B outbound.
Founders also go wrong treating conferences as marketing. In a market this small, the annual industry conference is your best pipeline event of the year. Go with 15 named people you intend to meet, book half of those meetings before you fly, and follow up the same evening.
Where does non-dilutive funding fit?
In the US, federal research programs can pay for the work that proves your technology to commercial buyers, and the award itself is a credential a technical sponsor can point to internally. SBIR.gov (checked November 2026) describes America's Seed Fund as funded through 11 participating federal agencies, and lists the amounts agencies can award without SBA approval as up to $335,937 for Phase I and up to $2,239,578 for Phase II, as of 16 October 2026. Larger awards need a waiver.
If you intend to sell to the federal government directly, registration comes first. SAM.gov (checked November 2026) states that "if you want to apply for federal awards as a prime awardee, you need a registration", and that registrations must be renewed every 365 days to stay active. Start that early, not the week a program office asks for your details. This is general information, not legal advice, and the rules for your agency and program should be read directly.
The pilot to contract checklist
Most deep tech pilots fail quietly: the technology works, everyone is pleased, and nothing is ever bought, because no budget line existed for the result. Run the checklist below before the pilot begins, not after it ends.
Before the pilot starts
- Named sponsor and named economic buyer. Write both names down. If you only have the technical sponsor, your pilot is a science project.
- The success measure, in writing. One number or one pass/fail test, agreed by both sides, with the method and who runs it.
- Who pays. A paid pilot filters seriousness better than any qualification question. If it must be free, trade it for data, a joint publication, or a reference.
- The budget route to production. Which budget pays for the rollout, in which fiscal year, and who approves it. Ask directly: "If this works, what is the path to a purchase order?"
- The security and compliance list. Ask for their vendor review pack on day one. SOC 2, insurance certificates, export control questions, site access and safety approvals all take longer than the pilot.
- The data and IP terms. Who owns the results, what you may publish, what they may do with your models or designs.
- A timeline with a decision date. Not an end date, a decision date, with the people who will be in that meeting listed.
- A continuity plan. Who inside the account knows about the pilot besides your sponsor. Champions change jobs, and an unwitnessed pilot dies with them.
During the pilot
- A written update every two weeks, in their language, that your sponsor can forward without editing.
- One in-person visit if there is any physical component. Problems show up in a site visit that never show up in a call.
- Log every objection raised by anyone in the building, including the people who are not in the project.
At the decision
- Deliver the results against the agreed measure, including what failed. Nobody in deep tech believes a clean result.
- Bring the commercial terms to the same meeting. Pricing, support, implementation, timeline.
- Ask for the procurement route in the room. Who writes the requirement, whether it goes to competitive tender, how long legal takes.
- If the answer is no, ask what would have to be true. In a market of 60 accounts, a no is a scheduled follow-up, not an ending.
What about the founder who dislikes selling?
This motion suits technical founders better than they expect. In a market this small, the sale is a technical conversation with a peer, not a pitch, and your advantage over a career salesperson is that you can answer the chief engineer's third question. Carry three things: a clear statement of what the technology does and does not do, the number from your last test with its method, and a specific ask at the end of every conversation.
What does not suit a technical founder is the admin: list research, the follow-up on the eleventh day, conference pre-booking, the update emails that keep a nine-month cycle alive. That is the work SOVE7GN GTM takes off a founder, while you keep the technical conversations. Pricing is shared on a call, so book 30 minutes if your account list is built and nothing is moving. If your list is 20 accounts and you know everyone on it personally, do not hire anyone. Go and see them.
For a slightly larger market, see vertical SaaS go-to-market, and for when to hand sales over, founder-led sales. The rest are in the GTM guides hub.
Questions people ask
How long is a deep tech sales cycle?
Usually several quarters, and in regulated or safety-critical industries it can run past two years from first conversation to signed contract. Plan cash around the cycle you observe in your own first three deals rather than a number from a blog.
Should deep tech startups do cold outbound?
Not at volume. Named-account outreach works: a handful of researched messages a week to specific people, with a reason for each one. With a small total market, a bad mass campaign removes accounts permanently.
How do I price a pilot?
Price it so it is a real decision for the buyer but small enough to avoid a full procurement cycle, and find out what their no-tender threshold is before you quote. A paid pilot also tells you whether the sponsor can get money at all, which is the thing you most need to know.
What do I do when my champion leaves?
Assume it will happen, and make sure at least two other people in the organization know what the pilot is for and have seen a written update. If it happens anyway, go back in through the economic buyer and the written success measure, not through a new relationship.
Do we need a salesperson or a technical person doing sales?
In deep tech the first seller is nearly always a founder or an engineer who can hold the technical conversation. A traditional salesperson works later, once the pilot process and the objections are documented well enough to teach.
Want calls on your calendar without hiring five people?
Book a 30-minute call. Tell us who buys from you and we'll show you what inbound, midbound and outbound would look like for your startup.
Book a call How SOVE7GN GTM works- Vertical SaaS go-to-marketCounting a small market, named-account outbound, and the events that matter.
- Founder-led sales: keep or hand offWhat a founder keeps, what to hand off first, and a handoff checklist.
- Warm outbound vs cold outboundThe two outbound motions compared, and how founder posts warm up a cold list.