BUILDERS

Lux Aeterna is building the world's first fully reusable satellite platform, designing spacecraft with built-in heat shields that survive reentry instead of burning up in the atmosphere.

In a recent episode of BUILDERS, we sat down with Brian Taylor, Founder & CEO of Lux Aeterna, to learn how the company is challenging the disposable satellite model by betting that cheaper launch costs fundamentally change the design equation for spacecraft.

Topics Discussed:

• Why Brian left roles at SpaceX, Amazon Project Kuiper, and Loft Orbital to start a satellite company in his basement

• The contrarian thesis: satellites should be designed and flown and brought back, not burned up

• Why launch being 20x cheaper today than it was 20 to 30 years ago changes the satellite design equation
• How the first six months were Brian alone in his basement designing a satellite, then sending it to former colleagues for feedback
• Why the first mission is sold out across civil, defense, and commercial customers
• How government and defense contracts became the primary go-to-market path over commercial LOIs
• Why taking VC money means you cannot tolerate learning as you go on any front
• The hiring philosophy: senior principal-level engineers only, because you cannot teach someone out of college how to design a satellite
• Why government business development requires a specific hire who knows the world, the application, and the color of money
• How the team simulated orbital eclipse conditions using Home Depot halogen lights and a shipping container

GTM & Technology Adoption Lessons:

• Non-dilutive government funding as a go-to-market wedge: Brian focused on defense and government contracts as the primary path to revenue rather than relying on commercial letters of intent. Government procurement, through programs like the DOD 5000 acquisition process, became the traction signal that validated the company to investors and customers alike.

• Design for where the market is going, not where it is: The entire thesis behind Lux Aeterna rests on the observation that launch is "20x cheaper today than it was" 20 to 30 years ago. That shift means mass optimization, the traditional constraint driving satellite design, matters far less than it used to. Brian bet that designing heavier, reusable spacecraft would be viable precisely because the cost equation had changed.

• Hire for the specific system you are selling into: Brian said the learning curve for government business development is "massively too steep or too slow for how fast our company needs to grow." Rather than learning government sales as a founder, he prioritized hiring someone who already knew defense procurement, the specific application, and the specific funding mechanisms.

• Pressure-test your work before building the team: Brian gave himself six months of runway and went to work alone in his basement designing the satellite. He then sent those designs to former colleagues with a specific ask: "find the problems that I did wrong based on your area of expertise and then you get to go fix them."

• Speed demands seniority when venture-backed: Brian said once you take VC money, "you're on a different path and a different trajectory and a different speed." Every engineer at Lux Aeterna is senior or principal level because the company cannot afford the ramp time of junior hires when preparing for a 2027 demonstration mission.

• Resourcefulness as an engineering advantage: When Brian needed to test a flight solar array for eclipse conditions, he bought pallets of halogen lights from Home Depot, put them in a shipping container, cooled it down to negative 80 degrees Celsius with gaseous nitrogen, and blasted the lights.

// Sponsors: Front Lines — Silicon Valley's leading Podcast Production Studio. We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership. Mention you are a listener and get a 10% discount. www.FrontLines.io/Podcast-as-a-Service

Delegate is a marketplace where AI agents like Claude and Codex find, hire, and pay for the tools and services they need, instead of humans signing up for each one. Launched two weeks before this recording, it already lists almost 700 services. On BUILDERS, Maximilian Freiermuth, Co-Founder of Delegate, shares how he chose early personas, turned data providers into partners, and why he expects digital services to see agentic commerce’s biggest early impact.

Topics Discussed:

• The admin work humans still do for their agents
• Early personas: new GTM operators, VCs, PE, and creators
• Positioning with providers as a lead funnel, not a rival
• Sourcing 700 services through self-serve partners and direct deals
• Why AI-native startups adopt faster than enterprise

GTM Lessons For B2B Founders:

• Sell the chore AI left behind: In Max’s framing, humans now just give agents access, sign up, enter credit cards, and cancel trials. Subscription fatigue is a buying trigger. Map the admin tax buyers pay to use tools they already own.
• Make routing the product: Most new GTM operators don’t know which databases exist, and Max argues they shouldn’t need to. Delegate sends the request to the right service. If your buyer can’t name the category, own the decision.
• Enter where the default fails: Two early personas are VCs who need founder signal from LinkedIn and X (Delegate benchmarked the scrapers) and PE firms researching brick-and-mortar businesses where Google returns nothing or outdated data.
• Trust unlocks autonomy: Agents can only buy safely if every service is quality-checked and screened for prompt injection. In agent-facing markets, curation is part of the product.
• Let customers graduate: Max worried providers would see Delegate as a foe. Instead, users discover a provider on Delegate and bring their own key once they use it often. “In the worst case, we’re basically just like a lead generator.” Build supply-side economics that survive churn to direct.
• Segment supply by partner model: Newer providers built for agent customers partner readily. Those with reseller-style programs need direct deals. Save negotiation for partners that require it.

//
Sponsors:
Front Lines — We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership.
www.FrontLines.io

//

Don’t Miss: New Podcast Series — How I Hire
Senior GTM leaders share the tactical hiring frameworks they use to build winning revenue teams. Hosted by Andy Mowat, who scaled 4 unicorns from $10M to $100M+ ARR and launched Whispered to help executives find their next role.
Subscribe here:
https://open.spotify.com/show/53yCHlPfLSMFimtv0riPyM

AdviNow Medical automates the entire medical practice. Every non-physical task handled by the front desk, medical assistant, physician, and biller is handled by the platform. The only exceptions are physical examination and the final clinical decision. Getting there required building four separate AI systems: one that mimics the physician's diagnostic reasoning, one for treatment planning, one for billing and insurance claims, and one for legal liability and compliance review.

James Bates did not set out to build a software company. He came to healthcare looking to buy practices. What a stopwatch and a 3,000-line spreadsheet taught him changed direction entirely.

In a recent episode of BUILDERS, we sat down with James Bates, CEO of AdviNow Medical, to learn how a complete practice automation platform got built from a Six Sigma lean analysis and why physicians spending 70% of their time on billing became the founding insight.

Topics Discussed:

• Why evaluating over 30 medical practices for acquisition led to founding AdviNow instead of buying anything
• How a Six Sigma lean analysis revealed that physicians spend 70% of their time on billing and compliance, not medicine
• The sequencing principle for automation: identifying the key intelligence required before building the system
• Why AdviNow had to build four separate AIs before any of the automation could actually function
• The first customer: what it looks like when the person you told "your business kind of sucks" says "let's give it a try"
• Why 100% of growth is still referral-driven and what happens when a practice's profitability goes up roughly 1,000%
• How AdviNow's change management burden is lighter than most enterprise software deployments
• Why winning the C-suite is not enough and who else has to be on board before an implementation succeeds
• The AI to onboard the AI: what AdviNow is building to handle a backlog it cannot yet clear
• Why the AI roll-up thesis is tempting for vendors and exactly what it costs them with existing customers

GTM & Technology Adoption Lessons:

• Start with measurement, not automation. James walked into medical practices with a stopwatch and measured every single task by every role, translated each one into a fully loaded cost, then correlated it against three outcomes: positive patient outcomes, reliable payment, and liability avoidance.

• The number that unlocked everything. Physicians were spending 70% of their time getting paid and not getting sued. Only 30% practicing medicine. Every product decision at AdviNow flows from that one number.

• Identify the required intelligence before you build anything. James describes a sequencing principle: determine what you want to automate, then determine what intelligence that automation requires, then build the intelligence.

• The easiest first customer is the one who watched you analyze their business. AdviNow's first customer was a practice James had been evaluating for acquisition. He told them their margins were structurally broken.

• Profitability-driven referrals are the strongest referral engine. Every time AdviNow onboards a client, the practice goes from low single-digit profitability to roughly 35%. That outcome is dramatic enough that clients tell their entire networks.

• Change management is easier when the job does not actually change. AdviNow's staff adoption challenge is lighter than most enterprise software deployments because no one's job function is eliminated from their perspective.

• Champions below the C-suite are required, not optional. James describes a pattern where the CEO signs the contract over the CTO's objection. In every subsequent meeting, the CTO is framing the competitor's product as superior.

// Sponsors: Front Lines -- Silicon Valley's leading Podcast Production Studio. We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership. Mention you are a listener and get a 10% discount. www.FrontLines.io/Podcast-as-a-Service

Flow Engineering builds tooling for hardware teams that Pari likens to Git and CI/CD in software. The company just raised $50 Million at a $750 Million valuation, with eight term sheets in two weeks. In this episode of BUILDERS, Pari Singh, CEO & Founder of Flow Engineering, explains how a London team of six or seven found its beachhead among ex-SpaceX and Tesla founders in LA, why he sells "a religion as opposed to selling software," and why his TAM is narrow by design.Topics Discussed:- How automating rocket engine design revealed the need for a new class of hardware tooling- Why inbound from five-person rocket startups became the beachhead- The "GitHub didn't get big by selling to IBM" strategy- Why BYD, not Tesla, made US automakers rethink engineering- Why Pari raised in summer with little prep- Keeping a skunkworks culture as the company scales

Gather AI builds a physical AI platform for logistics, using cameras on drones, forklifts, and static mounts to digitize warehouse operations into a real-time digital twin and orchestrate facilities with AI agents.

In a recent episode of BUILDERS, we sat down with Sankalp Arora, Chief Executive Officer of Gather AI, to learn how 175 customer discovery interviews turned a drone autonomy engine into a warehouse intelligence platform with 150 percent annualized NRR.

Topics Discussed:

• How Sankalp's PhD work at Carnegie Mellon on the world's first fully safe autonomous helicopter led to Gather AI
• Why the team pivoted at customer discovery interview 75, after learning that large companies wanted drones but did not know what to do with them
• How a single VentureBeat article in August 2019 generated about 10 leads a day, pre-product, with no SEO or ads
• Why innovation labs at large companies turned out to be poor customers, and why mid-market operators became the real early adopters
• The barcode reader benchmark: Gather AI's goal of becoming a default line item when someone stands up a facility
• How market education evolved from live robot demos to a testimonial and reference engine
• Why door to door sales failed, and what it revealed about where the buyer actually sits
• Why 150 percent annualized NRR was the signal to build a commercial team
• What an engineer learned about sales: it can be more formalized than engineering
• The current GTM bottleneck: seller onboarding speed against a six to nine month sales cycle

GTM & Technology Adoption Lessons:

• Pivot on buyer behavior, not technical identity: The three grad student founders assumed they would sell the autonomy engine they were known for. Discovery interviews showed that large companies would buy the engine but did not know what to do with the drones.

• Treat pre-product demand as the market signal: The first investment came from the conviction of people who said if you build it, I'll buy it. When the company launched a website in August 2019 with nothing behind it but a VentureBeat article, leads arrived at about 10 a day with no ads or SEO.

• Qualify early adopters by pain, not by title: The initial inbound came from innovation labs at large companies with a mandate to explore the problem. They turned out not to be the greatest customers. The best customers were operators, mostly mid-market, whose problems the product addressed directly.

• Sell where the budget sits, not where the product runs: Sankalp personally ran door to door sales at warehouses and it failed completely. The buyer, usually a VP of operations or senior director of operations, sat at the corporate head office, not at the facility.

• Turn early adopters into the education engine: Market education moved through phases: showing up at facilities to prove the robot works, then making early adopters successful, then circulating their testimonials. For 3PLs like the ones Gather AI serves, being featured was mutual value, since claiming differentiated, forward-looking innovation in a crowded market made them look good, backed by real ROI.

• Use NRR as the scaling trigger: The signal to build a commercial team came when annualized NRR reached about 150 percent while new customer acquisition was starved of investment.

• Hire GTM leaders who think differently: Sankalp's first commercial hire thought like him, and he calls that fault an expensive learning for the org. Running a sales team requires a different aptitude than building a solution, so he now looks for shared values with different thinking and real domain expertise.

// Sponsors: Front Lines -- Silicon Valley's leading Podcast Production Studio. We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership. Mention you are a listener and get a 10% discount. www.FrontLines.io/Podcast-as-a-Service

Higharc builds technology for home builders and distributors, taking a disconnected field of tools and third parties and streamlining the design-to-construction process digitally, producing buildable assets like construction drawings, estimating data, and pricing, along with 3D sales experiences.

In a recent episode of BUILDERS, we sat down with Marc Minor, Co-founder & CEO of Higharc, to learn how the company sequenced eight years of product and market decisions and then dismantled its own functional org at 240 people.

Topics Discussed:

• Why Higharc started with a direct-to-consumer and home builder experience and quickly learned that was the end state, not the entry point
• How the company moved to enterprise design partners who paid a small fee so Higharc could learn how to serve large builders
• Why homes are the most mass customized product out there and what that does to automation accuracy targets
• How Marc sequences a company's history in chapters by matching product maturity to a part of the market
• Why Higharc dismantled its functional matrix and flattened into a network of small teams run like general managers
• The first principles behind the restructure: what remote work is good at, accountability, and joy in work
• Why Higharc created physical hubs without moving to a full hybrid structure
• How a week-long, whole-company hackathon was used to get 200 plus people their own AI experience
• What Marc looks for in a defensible technology position: structured data that is out of distribution for the models

GTM & Technology Adoption Lessons:

• Sequence the market to the maturity of the product: Marc described the company's chapters as "trying to place the state of the product experience to a part of the market. And over time discovering more and more about the market, about the homes, about the value chain as we go and sort of adjusting in real time."

• Charge your design partners something: Higharc worked with "enterprise design partners, early customers who were willing to let us serve them for a small fee, so that we could learn about how to serve large builders." A small fee does not fund a company.

• Accuracy sets the roadmap in high-stakes automation: "We service a very important and hard to service market because homes, you can't get it wrong." Marc added that Higharc automates many things and "Automation really has a high bar for accuracy and correctness."

• Design the org around the constraint you actually have: Marc did not start from an org design playbook. He started from being remote. Remote's superpowers are extreme focus and high autonomy, and its failure is collaboration.

• Accountability is the management surface that matters: "So high accountability is one of the only tasks I think that actually matters in a company structure to make a difference.

• Restructure before the hiring debt compounds: The tension Marc identified sits between "the historical functional owners where power is vested as you cl as you go up the hierarchical ladder" and an org where power follows output and team remit.

• Mandates do not create AI adoption, projects do: Higharc turned its annual March retreat into a week-long hackathon where "every one of our 200 plus people at that time" had to build something, salespeople included.

• Differentiated data is the asset, not the model: "if you have a rich structured set of data that is out of distribution for the models, you are sitting on an outstanding asset to go and build with." Higharc generates buildings as spatial data it can reason about, which is what makes agent-driven tooling on top of it defensible.

// Sponsors: Front Lines -- Silicon Valley's leading Podcast Production Studio. We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership. Mention you are a listener and get a 10% discount. www.FrontLines.io/Podcast-as-a-Service

Kall Morris Inc (KMI Space) is an in-space logistics company providing Relocation as a Service, covering end-of-life services, orbit change maneuvers, and active debris removal for satellite operators.

In a recent episode of BUILDERS, we sat down with Troy M. Morris, Co-Founder & CEO of KMI Space, to learn how the company turned a hard physics problem into a service customers could name, understand, and buy.

Topics Discussed:

● Why KMI Space reduced a complex orbital servicing category to "Tow trucks for space" and how long that clarity actually took

● How constant de-risking, not better renderings, moved KMI through its first government contracts

● Why KMI Space partnered with MIT, Stanford, and USC before applying for its first SBIRs, and how it framed those partnerships

● The 35-proposal exercise KMI Space ran against the Space Force Orbital Prime opportunity and how it narrowed to six

● The jump from a roughly quarter-million-dollar SBIR Phase I to a Phase II closer to $1.25 million, and what changes between them

● Why KMI Space built relationships with technical points of contact within hours of winning Phase I

● The customer insight that reframed the entire product: operators wanted prevention, not recovery

● Why "we want to partner with NASA" is not a go-to-market plan

● The decision to build a space company in Marquette, Michigan instead of El Segundo or the Space Coast

● What KMI Space proved on the International Space Station across 172 test runs

● How a US government shutdown and budget gap shaped KMI Space's 2026 priorities

GTM & Technology Adoption Lessons:

Message clarity is earned through customer contact, not workshops: KMI Space's positioning now compresses into a single phrase, "Tow trucks for space." Troy was direct about the cost of getting there. "we can absolutely lie and say that was day one.

Selling deep tech is a de-risking exercise, not a demo: Troy reframed early contract wins as risk reduction rather than persuasion. "You can build awesome sketches, you can have the coolest AI write a speech or make a visual.

Borrowed credibility only works if the partnership is real: KMI Space partnered with MIT, Stanford, and USC before applying for its first SBIRs, which changed how reviewers read the application. Troy drew a sharp line on how to think about it. "really leveraging it every step, not to borrow the prestige of the other group, but earn the partnership."

Generate wide, then cut to where you have earned the right to win: KMI Space responded to the Space Force Orbital Prime opportunity by drafting 35 separate proposals, then narrowing to about six based on internal specialty and which partners they could actually recruit. The filter was capability plus access, not enthusiasm.

Start the next contract the day you win the current one: Troy's rule for government sales is to move immediately from celebration to relationship-building with the people who will evaluate the work. "find the people who are going to be reviewing this, working with you, and build that relationship."

Customer discovery is what separates an interesting capability from a fundable one: Asked what he would send back to his earlier self, Troy gave two words. "it would absolutely be two words: customer discovery."

Institutions are not buyers. People inside them are: Troy described the most common mistake he sees, including from his own earlier self, as treating a large agency as a single addressable entity. "which part of NASA? What center? What mission? What human is going to read this?"

// Sponsors: Front Lines -- Silicon Valley's leading Podcast Production Studio. We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership. Mention you are a listener and get a 10% discount. www.FrontLines.io/Podcast-as-a-Service

Zenno Astronautics builds superconducting magnet systems for space, starting with a stabilization system that replaces fuel-based stabilization at higher orbits and expanding toward magnetic launch systems and radiation shielding.

In a recent episode of BUILDERS, we sat down with Max Arshavsky, Founder and CEO of Zenno Astronautics, to learn how the company took superconducting magnets from a technology most of the industry doubted to a commercial product that has flown in space twice.

Topics Discussed:

• Why Zenno chose satellite stabilization as its first market
• Why Max sees private companies as faster early buyers than government
• Why the earliest adopters were engineers already literate in superconductivity
• How an industry that treated superconductivity as a promise too good to be true came to see it as commercially applicable
• Why six years passed between founding the company in 2017 and the first launch in 2023
• How the third system is four hundred times more powerful than the first and forty times more powerful than the second in pretty much the same mass and volume
• Why Max defines the entire stack of superconducting technologies as the product
• Why building cool technology does not make it sell itself

GTM & Technology Adoption Lessons:

• Enter through a function every customer already performs: Max said every satellite needs a stabilization system, and that the existing solutions are not self-sufficient and each has shortcomings. Zenno's first product went after that function rather than asking the market to accept a new use case.

• Look for buyers who carry less risk: Asked about the first deal, Max said government is slow and more risk averse, while companies are much more agile and willing to take risk.

• Find the people for whom the concept is not new: Max said the first adopters are literate in engineering and in superconductivity, so they did not need to buy into a novel concept. What they had not known was that it is now feasible in space. Because they understand it, he said, they see it as less of a risk.

• Expect disbelief and answer it with hardware in orbit: Max said pretty much everyone doubted the technology and that most people in the industry saw superconductivity as a promise that was too good to be true. Zenno launched its first system in 2023 and its second in 2025, and Max described the next system as flight proven twice.

• Do not assume the technology will sell itself: Max said he was one of the founders who believed it would take care of itself. He described an industry full of systems that have been invested in and stable for years, which are rightly not easy to disrupt. That reality, he said, forces you to understand the market, its trends, and what drives customers.

• Define the product as the stack, then sequence it: Max defines the entire stack of superconducting technologies as the product, so the commercial actuator is not yet the complete product. The pillars he named are satellite mobility, magnetic launch systems, and radiation shielding. As each matures, Zenno builds a business around it or builds something itself around it.

• Move from R&D lab to business: Max said Zenno has been a very successful R and D lab so far and that he is now laser focused on building a very successful business.

// Sponsors: Front Lines -- Silicon Valley's leading Podcast Production Studio. We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership. Mention you are a listener and get a 10% discount. www.FrontLines.io/Podcast-as-a-Service

Qover is an embedded insurance orchestration platform that gives enterprise brands a single API to design, launch, and operate insurance programs across European markets where insurance regulation, commercial law, language, and currency differ country by country.

In a recent episode of BUILDERS, we sat down with Quentin Colmant, CEO and Co-founder of Qover, to learn how the company coined the category of embedded insurance orchestration and rebuilt its product, pricing, and sales motion around it.

Topics Discussed:

● Why a pan-European insurance layer is hard to build when every country has its own regulation, commercial law, language, and in some cases currency

● How Qover coined the term embedded insurance orchestration roughly four or five years ago and why the word orchestration was chosen deliberately

● Why category creation forced a reorganization of product, people, structure, and partnerships rather than a marketing refresh

● How the category definition produced a clear ICP and a faster no

● The pricing change that followed: splitting technology, operations, and advisory into separate fees

● Why Qover raised patient capital and how Quentin set that expectation with investors from the first conversation

● The gap between actual revenue and contracted revenue, and why contracted revenue can become a vanity metric

● Why Qover keeps a small marketing budget and invests in risk sharing with partners instead

● The two ways Qover's partner bets failed, including partners going bankrupt before launch

● How positioning around complexity stops prospects from trying to build the solution themselves

GTM & Technology Adoption Lessons:

• Category creation is an operating decision, not a naming decision: Quentin said the realization was "not only about naming something and doing some marketing, it's how you completely reorganize your product, your organization, your people, your structure, as well as your partnership."

• Name the complexity when complexity is the moat: Qover's problem was explanation. Quentin said it took him "at least 20 minutes to explain our business model, the different pillars we have, what we do, nobody understands it, it's too complicated, the value chain is very long."

• A category is only real if the sales motion enforces it: The category gave Qover its ICP and its verticals, and then the discipline to defend both. "We have a clear definition of our ICP and we say no, we say no a lot, we say no quickly."

• Repricing is part of repositioning: Once the category defined what Qover sold, the commercial model changed with it. Quentin described splitting the technology from the operation from the advisory work, with a flat fee, a tech fee, and a fee per ticket.

• Match investor time horizon to industry time horizon: Insurance economics are built on renewal books that compound over decades. Quentin said Qover made the requirement explicit at the start: "we need patient capital and as part of finding people that are okay with this patient capital meaning they've always a 10 to 12 years horizon but you make sure you get that from the very beginning and they will follow you."

• Spend on distribution risk, not demand generation: Qover's marketing budget is small by design. Quentin said a targeted account-based motion, a few events, and white papers that let partners talk about themselves is enough, because "then they are very happy and then they become your clients afterwards."

// Sponsors: Front Lines -- Silicon Valley's leading Podcast Production Studio. We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership. Mention you are a listener and get a 10% discount. www.FrontLines.io/Podcast-as-a-Service

Anjuna Security builds the software stack that makes confidential computing accessible to enterprises — doing for hardware-level data protection what VMware did for virtualization and what CUDA did for GPUs.

The company counts three of the top ten global banks among its customers, has expanded into the federal government through defense primes, and recently launched a second product to govern AI agents running inside a trusted computing environment.

In a recent episode of BUILDERS, we sat down with Ayal Yogev, CEO of Anjuna Security, to learn how the company sold a category that buyers had never budgeted for, what actually moves the needle when selling to the world's largest banks, and why he calls rationalizing exceptions to your ICP "basically a death warrant."

Topics Discussed:

● Why category education is a long game with uncontrollable accelerants — and how the JP Morgan global CEO's open letter to vendors changed buyer conversations overnight

● The two biggest GTM money pits: hiring salespeople before product-market fit and building large conference booths that attract the wrong buyers

● Why a private suite with pre-scheduled meetings adjacent to a conference consistently outperforms booth presence on ROI

● How Anjuna closed three of the top ten banks and what a year-long sales cycle actually looks like from first meeting to signed contract

● Why people movement between banks is a structural referral engine — and how touching 100-plus people inside a single bank compounds over time

● Champion identification in long-cycle enterprise deals: who to find, how deep to go, and what happens when your champion leaves before the deal closes

● Why selling direct to the US federal government was "close to impossible" and what finally worked: defense primes like Booz Allen Hamilton, Lockheed Martin, Leidos, and CACI

● How government grew from roughly zero to 25% of revenue and is tracking toward 50% in the next 12 months

● Why focus is defined by what you say no to — including inbound that's outside your ICP

● The forward-deployed engineer model: why bundling actual engineers into the first enterprise deal changes success rates, churn, and renewals

● Anjuna's second product: a trusted supervisor agent running inside a confidential computing environment to solve the "arctic intern" problem for AI governance