How To Land Enterprise Clients As An Early-Stage Company With Hugo CEO & Co-founder Simone Bartlett (Video)

Landing your first enterprise client as an early-stage company can feel like trying to get into a members-only club… without being sure what the “members” even wear. Enterprise buyers have bigger budgets, surebut they also have bigger committees, bigger checklists, and a legendary ability to disappear into “internal alignment” for three weeks.

In a SaaStr Workshop Wednesday, Simone Bartlett (Hugo CEO & co-founder) lays out a practical, surprisingly human playbook for breaking into enterpriseespecially when you don’t have a logo wall the size of a billboard. Below is a fully rebuilt, field-ready guide based on those core ideas, plus proven enterprise selling practices used by early-stage teams that win big accounts without losing their minds.

Why enterprise is worth it (and why it’s hard)

Enterprise deals can compress your revenue goals: fewer customers, larger contracts, and (when you deliver) strong retention. The tradeoff is complexity. Enterprise buyers don’t just “buy.” They evaluate, compare, cross-check, secure-approve, legal-review, procurement-negotiate, and occasionally ask you to fill out a security questionnaire that seems to have been written by someone who deeply mistrusts computers.

The good news: early-stage companies can win enterprise. The better news: you don’t need to “act big.” You need to act prepared.

The Simone Bartlett framework: 5 tactical moves that open enterprise doors

Simone’s advice can be summarized as five moves that compound: move with urgency (but don’t rush), become an insider, master process, remember enterprise people are people, and keep the conversation alive even when you don’t have “enterprise references.” Let’s turn those into actionable steps you can actually run this quarter.

1) Operate with urgency, but be patient

This is the enterprise paradox: you need momentum, but forcing the close too early often creates a faster “no.” Early-stage teams sometimes sprint into enterprise conversations like it’s a speed-dating round. Enterprise is more like a slow dance… while three other people judge your footwork.

What urgency looks like (the useful kind)

• Fast follow-ups: same-day recap emails, clear next steps, and calendar holds.
• Rapid learning loops: every call produces one new insight you bake into your deck, demo, or pricing narrative.
• Time-to-value planning: you can explain how a buyer gets real value in weeks, not “after the implementation phase.”

What patience looks like (also useful)

• Not taking the “big intro” too early: if your product, security posture, or delivery capability isn’t ready, you politely delay the moment of truth until it can become a “yes.”
• Reading the room: what’s happening in the market, in the company, and in society that changes their appetite for new vendors?
• Building credibility quietly: small wins, pilots, and internal advocates before the big meeting.

Practical example: If you’re selling workflow software into a regulated industry and you don’t yet have SOC 2 (or equivalent controls), pushing to security review too early can stall the deal. A better move is to run a limited-scope pilot with non-sensitive data, while you build the security program needed to pass the “real” gate.

2) Become an insider (without being weird about it)

Enterprise companies have their own language, priorities, and internal politics. “Become an insider” doesn’t mean pretending you work thereit means learning how they describe their problems and reflecting it back with precision.

How to become an insider in 2–3 weeks

• Talk to more than one person. Not every stakeholder holds budget, but many can become your champion or guide.
• Mirror their vocabulary. If they say “ticket deflection,” don’t pitch “support automation.” If they say “vendor rationalization,” don’t pitch “another tool.”
• Ask better questions than your competitors. Great discovery feels like therapy with a spreadsheet.

The “lingo map” exercise

Create a shared doc with three columns:

1. What they say (exact phrases from calls, emails, internal docs you’re given)
2. What it means (your translation)
3. How you respond (your pitch line, proof point, or demo moment)

Why this works: enterprise buyers are constantly filtering for risk. When you sound like you understand their reality, you reduce perceived riskand you make it easier for internal stakeholders to repeat your message.

3) Process, process, process (enterprise runs on checklists)

Enterprise buying is a process marathon. Even the person who loves your product may be blocked by procurement steps designed to prevent exactly what you are trying to do: introduce a new vendor. Your job is to treat process like a product requirement, not an inconvenience.

What “process-first selling” looks like

• Know the gates: security review, legal review, procurement, data privacy, and sometimes architecture review.
• Reduce buyer effort: provide answers, docs, and templates in a format they can reuse internally.
• Plan for time: enterprise timelines are shaped by quarter ends, budget cycles, and internal approvals.

Your early-stage enterprise readiness kit

Even if you’re tiny, assemble these assets so you feel “easy” to buy:

• One-page security overview (controls, data handling, access management, incident response basics)
• Architecture diagram (simple, readable, honest)
• Standard legal starting point (your MSA, DPA, and a clear redlines process)
• Implementation plan (what happens week 1–4, who does what)
• ROI model (how they justify purchase internally)
• Reference substitutes (pilot results, quantified case studies, testimonials from credible operators)

Notice what’s missing: “We’re too early for that.” Enterprise doesn’t reward excuses. It rewards preparedness and clarity.

4) Enterprise people are people too

It’s easy to treat enterprise like a machine: “Procurement did this,” “Security said that,” “Legal won’t budge.” But behind every step is a person trying to avoid risk, protect their time, and look competent in front of their peers.

Three things enterprise humans tend to like

• Familiarity: they prefer known patterns, known language, and known categories.
• Checking boxes: clear criteria, clear compliance, clear requirements met.
• Not doing the heavy lifting: if they have to “translate” you internally, the deal slows down.

Make your champion’s job ridiculously easy

Write the forwardable email for them. Provide a short internal blurb they can paste into Slack. Include two crisp proof points and one clear ask.

Template: “If we can get 30 minutes with the security reviewer + the ops owner, we’ll confirm feasibility and propose a low-risk pilot that delivers value in 2–3 weeks.”

When you do this well, your champion doesn’t have to “sell” you. They can simply introduce youand enterprise loves introductions.

5) Don’t let the conversation die before it begins

The classic enterprise question arrives early, usually right after a good demo:

“So… who else are you working with?”

If your honest answer is “not many enterprises yet,” you’re in good company. The goal isn’t to fake credibility. The goal is to build credibility in ways that feel safe to the buyer.

How to answer the “who else” question without panic-sweating

• Use credibility ladders: name relevant mid-market customers, well-known advisors, or partners that reduce perceived risk.
• Offer comparison anchors: “Teams like yours typically use X approach; we replace that with Y and reduce Z.”
• Propose a low-risk pilot: limited scope, success criteria, and a clear mutual plan to expand if it works.
• Quantify outcomes: early results matter more than big names.

Design pilots that don’t trap you in pilot purgatory

A pilot should be:

• Time-boxed (2–6 weeks)
• Measurable (success metrics agreed up front)
• Owned (one buyer owner + one vendor owner)
• Expandable (clear path to production contract)

If a pilot has no decision date and no expansion plan, it’s not a pilot. It’s free consulting with extra steps.

Putting it together: a simple enterprise motion for early-stage teams

Here’s a motion that respects how enterprise actually buyswithout requiring a 40-person sales org.

Step 1: Pick a narrow wedge

Enterprise doesn’t buy “general tools.” They buy outcomes in specific contexts. Choose one high-pain workflow, one department, one integration environment, and one buyer persona. Your wedge is your story.

Step 2: Build an “insider narrative” deck

Make your primary deck feel like it was written with your target customers, not about your product. Lead with their problem framing, their constraints, and their success metrics.

Step 3: Over-invest in champions

Your first enterprise wins often come from people who want you to win. Find them, respect them, and make them look good. Give them assets that travel well inside the organization.

Step 4: Run a Mutual Action Plan

Use a shared plan to align on stakeholders, timeline, requirements, and close criteria. The plan isn’t for youit’s for consensus and momentum.

Step 5: Execute with speed where it counts

Even when the buying cycle is long, the moments between steps should be fast. Enterprise remembers who is easy to work with.

Common enterprise objections (and what to do instead of arguing)

“You’re too small.”

Response: show process maturity. Small teams can be highly reliable if they have clear controls, clean execution, and explicit support commitments.

“We don’t add new vendors.”

Response: position as consolidation, replacement, or measurable cost/risk reduction. Tie your wedge to fewer tools, fewer steps, or fewer incidents.

“Security needs more.”

Response: run a security-forward path: share policies, clarify data flow, answer questionnaires fast, and show a roadmap for compliance milestones (without overpromising).

“Legal will take months.”

Response: start legal earlier, provide reasonable fallback positions, and use a pilot agreement if appropriate. Enterprise doesn’t hate legalthey hate surprises.

Field Notes: ~ of real-world experience patterns (what early-stage teams usually learn the hard way)

Early-stage teams that successfully land enterprise clients tend to discover a few “unofficial rules” that never show up on the buyer’s website. First, enterprise buyers rarely reject you because your product isn’t goodthey reject you because your risk story is incomplete. A founder might give a strong demo, get enthusiastic nods, and still lose momentum the moment security or procurement enters the chat. The teams that win treat risk like a first-class feature: they prepare a simple security overview, clearly explain data handling, and respond to questionnaires quickly with consistent answers. They don’t try to sound perfect; they try to sound accountable.

Second, early-stage enterprise deals are often “sold” in meetings you aren’t in. A champion takes your idea to their director. A director brings it to a budget meeting. Procurement asks, “Why this vendor?” If your message can’t survive forwardingif it requires your live storytellingyour deal slows down. Winning teams build a set of copy-paste assets: a one-paragraph internal summary, a short slide the champion can reuse, and a crisp list of outcomes the buyer can repeat without accidentally inventing new promises. This is not marketing fluff; it’s buyer enablement.

Third, founders learn that enterprise stakeholders don’t all want the same thing. The end user wants relief. IT wants stability. Security wants control. Finance wants predictability. Legal wants liability bounded. If you pitch the same benefits to everyone, you look inexperienced. The teams that close do “multi-threading” early: they ask, “Who else will care about this?” and then proactively schedule time with the people who can accelerateor quietly killthe deal. It feels slower at first, but it prevents the classic enterprise trap: one enthusiastic stakeholder who can’t get consensus.

Fourth, enterprise pilots are a double-edged sword. Teams love pilots because they feel like progress. Buyers love pilots because they feel safe. But pilots fail when they’re vague (“let’s try it”) and succeed when they’re specific (“if we hit these three metrics by this date, we move to production pricing”). High-performing early-stage companies structure pilots with a shared plan, a weekly check-in, and a decision meeting on the calendar from day one. They also protect themselves from “pilot sprawl” by limiting scope: one department, one region, one workflow, one integration. If value is real, expansion becomes easier; if value is fuzzy, expansion becomes political.

Finally, teams that land their first enterprise client usually discover that confidence is contagiousbut only when it’s paired with humility. They don’t pretend to be a Fortune 100 vendor. They say, “Here’s what we do exceptionally well, here’s what we don’t do yet, and here’s how we’ll make sure you’re never surprised.” That toneclear, calm, preparedmakes enterprise buyers feel safe choosing the “new” vendor, because it sounds like you’ll behave like a grown-up when something goes sideways. And in enterprise, something always goes sideways. The question is whether you handle it like a partner.