You have a slide in your deck. Somewhere between the product overview and the financials, there's a line that shows NRR growing — account by account, division by division, team by team — until the initial deal looks like a seed and the account looks like a tree. Land and expand. The investors nodded. The board accepted it. You built the model around it.
Nobody questioned it. Including you.
That slide is wrong. The expansion you're counting on requires a sales motion you haven't built yet — one you probably haven't thought about building, because the thesis told you you wouldn't need to.
The Good Lie
Your investors have funded this story before. Figma. Slack. Datadog. They've seen the curve — one team buys, the product spreads, NRR compounds. When you said "land and expand," that was the pattern they recognized. They weren't asking whether it holds for deep tech. They nodded. You took the nod as a verdict.
Your board didn't push back because the story sounds responsible. Staged growth, capital-efficient — nobody in that room had enough deep tech field experience to interrogate it. Sounding like a plan is often enough to pass for one. And you read the silence as agreement.
And you — this is the one that stings — you believed it because it let you feel like the hard part was already done. You'd landed. The expansion would come. The thesis is psychologically comfortable because it defers the uncomfortable thing. The work of building a second sales motion, developing a new champion, running a new technical evaluation — that work didn't feel necessary yet. And you read your own relief as confidence.
You built the model by looking at your own enthusiasm. The customer who bought from you thinks "we made a good decision." They are not thinking "I'm going to crusade for this vendor internally." That gap — between your mental model of their excitement and their actual excitement — is where the land and expand thesis lives and dies.
Why It Breaks the Same Way Every Time
Enterprise engineering organizations aren't monoliths. Each team runs its own budget cycle — and budget cycles aren't interchangeable. Your first deal probably came out of a program budget: multi-year, executive-approved, purpose-built for a specific initiative. Large enterprises often fund first-year adoption through innovation departments — groups whose job is finding new tools to try, with targets measured in how many they onboard. Your first deal lived in that budget. The program worked. Year two, the innovation department moved on to the next evaluation. The operational team that now owns the tool has to justify it against their own budget. Different ceiling. Different approval chain. A different number with a different logic. You modeled expansion as though the company's spending capacity traveled from one team to the next. It doesn't. It belonged to one program, at one moment, under one set of conditions.
The warm intro gets you the meeting. It doesn't move the second team's budget.
Your champion from the first deal is tired. Not disinterested. Tired. They staked their credibility on an unproven startup. They survived the implementation. They have value to show for it. Now you're coming back asking them to do it again — different team, same risk, same unproven startup energy. That tiredness reads as "they're less enthusiastic about us" when it's actually "they've spent what they had and haven't refilled." You read their tiredness as a signal about your product. It was a signal about their political balance sheet.
In electronics engineering this fault line runs between RF and analog. RF engineers know which tools they trust and which ones they've already evaluated and rejected. The analog team has a completely different answer to both questions. They've run their own shortlist for years. Neither team buys based on what the other did. Your champion's credibility ends at that line. Your market has an equivalent boundary — hardware and software, simulation and verification, application and infrastructure, platform engineering and product engineering. Write it down. Your champion's credibility ends there, and your expansion motion starts over on the other side.
And then there's the silence. Enterprise engineering organizations are execution systems, not knowledge-sharing systems. Your first customer's success is invisible to the expansion target unless your champion is actively, repeatedly, deliberately broadcasting it in terms the second team finds credible. The adjacent team has never heard the outcome of your deployment. I have watched deals stall for twelve months because nobody told the story across the hallway. The story doesn't travel on its own.
The Window You Keep Missing
Expansion in deep tech is time-gated. The window exists at a specific moment in the adjacent team's program calendar, and almost nowhere else.
Deep tech products prove their value on live programs — real problems, real deadlines, someone's name on the delivery date. Between programs, the value goes latent. The team knows the tool works, but nobody is living the benefit. No urgency. No struggling moment. Nothing to trigger an evaluation.
The window opens in the 4-12 weeks before the adjacent team's next significant program kicks off. Before it: no urgency. Mid-program: no appetite for change. After: retrospective interest with no commercial hook. Miss the window and you're waiting 12-18 months for the next one — and during that window, the incumbent is in the room locking the toolchain without a conversation. In semiconductor specifically, programs run on three-year cycles — and companies run three in parallel, launching a new product each year. Miss the window on one program and the next relevant one may be three years out.
Your CS team needs program calendars. Not health scores and usage metrics. When does their next tape-out happen? When does the adjacent team move from architecture to implementation? That information exists. Customers share it when they've stopped treating you as a vendor.
You've been timing expansion conversations around your calendar. The window is around their program cycle, not your runway. And you only arrive at it ready if you've already built the champion to the point where they carry you into it — which is a different motion entirely from selling.
The Three Signals
Most founders push for expansion at the wrong moment. The tool is installed, the team seems satisfied, time to grow the account. Right? Wrong. A satisfied champion is not an expansion asset. They're a person who made one good bet on an unproven startup and hasn't been paid back yet.
The first signal is dependency, not adoption. If you turned off access tomorrow and the team's current program would survive the week, you're a tool they like. The champion carries the expansion conversation when removing you would break the program. Not because they like you. Because they need you.
The second signal is whether the champion can put a number on the outcome in their language. "63% faster simulation" is a claim you made. "We shaved six weeks off the Raytheon timeline" is a result they own. They need to walk into an internal meeting with the second kind of statement. "The team loves it" doesn't close approvals. A missed milestone does. And if your champion can't get to that number without significant coaching from you, sometimes it's telling you the outcome wasn't significant enough to be visible yet.
And then there's the third signal. The one nobody manages for.
The champion mentioned the product to a colleague without your prompting. The reference program didn't produce this. The outcome mattered enough that they wanted their peers to have it. These organizations run engineering all-hands meetings, technology exhibitions, intern project showcases. In one of those rooms, a champion raised their hand without any briefing from us. The expansion conversation came to us fourteen months later without a single outbound push.
Run this diagnostic against your champions right now. You probably have satisfied users, but not advocates.
You can't ask them for a withdrawal before they've made a deposit.
What a Deposit Actually Looks Like
Engineering leaders build status through program outcomes that other people witness. The champion whose tool hit the milestone — and said so, in front of their VP — just made a deposit. Not because they love your product. Because their technical bet produced a visible result at a moment their organization was paying attention.
Your job in the deepen motion is to be present at those moments. Not QBR. The program review where the milestone got hit. You need to know when their programs hit critical gates — tape-outs, delivery dates, postmortems, leadership offsites. The attribution has to be made out loud, by your champion, in a room that counted. Value delivered when nobody was watching doesn't build political capital.
The CS reflex is a reference call. That turns your champion into a vendor's reference. Different thing. Put them on a stage instead — an industry panel, a session at the conference their peers actually attend, a bylined piece in the publication their VP reads. A champion who stands up in front of their peer community and talks about a result those people recognize walks back into their organization differently. Colleagues start asking them about it. Their boss hears about it from someone else first. You arranged none of it. That's the point. You've got to make it impossible for them not to mention it to a colleague.
And then intelligence. Real signal from their field — what a comparable team just figured out, how their procurement landscape is shifting, what a new compliance requirement means for their next program before their boss has read about it. Not product updates. Not roadmap previews. The champion who gets that from you regularly starts carrying it into their organization. They share it. They source it back to you. Their peers start asking where they get their information. Your name comes up. That's a deposit. It costs preparation. Nothing else. And it pays for years.
Most CS teams are running health scores and NPS surveys. Hygiene, not deposits. When the expansion stalls, they blame timing or budget. The account was thin the whole time.
The mechanics above are the easy part. Knowing which champion has enough standing for the stage to matter, which milestone is worth the trip, whether the attribution has enough weight to spend — those are judgment calls. The ability to make those judgment calls comes from experience. And the cost of getting them wrong isn't a missed tactic — it's a spent champion. You won't get a second chance to use their credibility in that room.
Land and Deepen
Land and expand works when one person's use pulls another person in automatically. Figma. Slack. Someone shares a file and the recipient needs an account to open it. The product spreads because using it once gives someone else a reason to use it. Your product requires a buying committee, a technical evaluation, and a full procurement cycle every time a new team picks it up.
The first deal is a commitment: you are going to make one team's experience so embedded, so quantifiably valuable, so internally championed that the second deal comes to you instead of you going to it.
You have to make a second first sale.
Treat the Adjacent Team as a New Logo
Treat the adjacent team as a new logo.
Same qualification. Same discovery. Same discipline about whether they have a struggling moment, a budget, and someone with authority to decide. Don't approach them because they're in the same building as your best customer. Approach them when you have evidence they have a problem you can solve. Being at the same account earns you a better starting position — the reference is fifty feet away, not a case study PDF — but it doesn't earn you a deal.
This is where most expansion playbooks go wrong. They treat account presence as a signal of intent. It isn't. It's an opportunity to find a signal. Knowing your product exists isn't needing it. Qualification comes first. The account relationship comes second — it's what you lean on once you've found the struggling moment.
When you do find the struggling moment, your position is strong. No competitor in that account has a live deployment fifty feet away. No competitor's reference can be walked to in under five minutes. You close faster because the proof isn't theoretical. But that advantage only activates after qualification. Not before.
The practical implication is two separate pipelines. Internal accounts where your champion is dependent, has a number they own, and has mentioned you without prompting — those go into active expansion. You're looking for the struggling moment, working the timing window, running a full discovery motion. Internal accounts that haven't reached all three signals stay in the deepen motion — you're building the deposit, not making a withdrawal. New logos run independently on their own timeline.
The shared account is an asset. It's not a substitute for a sales process.
What You Had
You didn't have an expansion motion. You had a story built on the right shape — staged, responsible, elegant on a slide.
The innovation budget was someone else's mandate. The warm intro got you a meeting, not a channel. Your champion wasn't patient — they were tapped out. The program silence wasn't time. It was timing you hadn't mapped.
The second deal comes to you instead of you going to it. It comes fourteen months after a champion raises their hand in a room you weren't in.