How old was Jason M. Lemkin when he founded his first company?

If you’ve ever Googled this question at 1:00 a.m. while doom-scrolling founder war stories, welcome. You’re in the right place. And yesthis is one of those rare internet questions with an unusually clean, human-sounding answer (no vague “in his early thirties” gymnastics, no suspicious math, no “sources disagree” chaos).

Jason M. Lemkinthe SaaS community builder behind SaaStr and the co-founder most people associate with EchoSign/Adobe Signhas publicly answered the “how old were you?” question himself. The punchline is simple, and it comes with a surprisingly relatable side dish: he felt “too young” even then. (Which is hilarious, because at 33 you’re old enough to have opinions about office chairs and young enough to still believe you can survive on coffee and adrenaline.)

The quick answer (with zero drama)

Jason M. Lemkin says he was 33 years old when he co-founded his first start-up. That first company is widely described by Lemkin as NanoGram Devices, a nanotechnology-focused venture he later said was acquired for roughly $50 million about 12–13 months after founding.

So if you came here for the number: 33. If you came here for the story behind the numberwhat “first company” really means in his timeline, why that age matters in enterprise, and what you can steal for your own playbooklet’s keep going.

Who is Jason M. Lemkin (and why people keep quoting him)?

Jason M. Lemkin is best known in B2B software circles for a few connected chapters: founding and scaling companies, selling into the enterprise, exiting, then turning those battle scars into unusually practical advice. He’s often described as the CEO/co-founder of EchoSign (later acquired by Adobe and eventually branded into Adobe’s e-signature offering), and the founder behind SaaStr, a blog-turned-community-turned-events machine that became a go-to resource for SaaS operators and founders.

But the key point for this article is that his “first company” story isn’t a SaaS story at all. It starts earlierbefore the e-sign boom, before “product-led growth” was a term people used unironically, and before your CRM could auto-generate follow-ups that sound like a polite robot.

What counts as “his first company”?

The phrase “first company” is where the internet gets messy, because different people mean different things:

• First company you ever worked for? (Nope.)
• First company you joined as an employee? (Also no.)
• First company you co-founded as a start-up? (Yesthis is how Lemkin frames it.)
• First famous company you founded? (That’s where EchoSign often hijacks the conversation.)

Lemkin’s own wording matters here. He describes his timeline roughly as: starting work with startups in his mid-20s, joining a start-up full-time later, and then co-founding his first start-up at 33. In other words, he’s not counting “early career hustle” as “founding.” He’s counting the moment he became a founder with founder-level risk.

NanoGram Devices: the first start-up chapter

According to Lemkin, his first start-up was NanoGram Devices. He characterizes it as a “white space” opportunityspotting an abandoned or underused technology and building a company around a clear gap in a fast-growing market. The story he tells is classic founder folklore, but with unusually specific mechanics: he licensed technology, recruited a team with a co-founder, raised VC funding, and then sold the business to a competitor for around $50 million after about 12.5 months.

If you’re wondering why this matters to the “how old” question: it anchors the age to a real milestone. This isn’t a vague “I had a business in college” anecdote. It’s a real company, in a real category, with a reported acquisition outcomemeaning his “33” is tied to a specific founding era, not a fuzzy memory.

You’ll sometimes see a slightly different dollar figure referenced in deal summaries and finance pages (for example, cash purchase numbers can be listed differently than a founder’s rounded headline figure). That’s normal in M&A storytelling: founders remember the big, clean number; deal documents remember the precise structure. The important part is that the first company was a real venture with a real exitnot a side project that “totally could have been big if I’d stayed with it” (the universal anthem of abandoned domains everywhere).

EchoSign: the company most people mean when they say “Jason Lemkin founded…”

EchoSign is the name that shows up in more interviews, profiles, and retrospectives because it sits at the intersection of: (1) SaaS, (2) enterprise workflows, and (3) the modern e-signature market that later became mainstream.

EchoSign’s early visibility was boosted by tech media coverage and launch-era buzz. It’s frequently described as launching publicly in 2006, and it’s also listed in some company databases as founded in 2005. That difference is common: “founded” can mean incorporation or first building months, while “launch” means the first time the market sees it.

EchoSign later became notable for its acquisition by Adobe in July 2011, a move widely covered in tech press and business outlets. Post-acquisition, Lemkin is commonly described as taking on a VP role tied to web services/document services growth, and SaaStr’s own bios and profiles frequently reference milestones like scaling document services revenue/ARR into nine-figure territory in the years that followed.

In other words: NanoGram is the first-founder chapter; EchoSign is the brand-name chapter; SaaStr is the community chapter. The “33 years old” answer is about the first of those chapters.

Why 33 is a fascinating founder age (especially for enterprise)

There’s a startup myth that goes something like: “If you’re not a 19-year-old in a hoodie building the next universe in a weekend, investors will escort you gently into the waiting room labeled ‘corporate.’” Reality is much less cinematicand much more forgiving.

Lemkin’s own commentary adds color here: he’s joked that at the time he felt “too young” to be taken seriously by big customers and even wanted to look more mature. That’s not vanity; it’s enterprise psychology. In enterprise buying, credibility isn’t a nice-to-havesometimes it’s the whole product.

Enterprise customers buy certainty, not just features

When you sell to larger organizations, your product competes against fear. Fear of switching. Fear of risk. Fear of the vendor disappearing. Sometimes the feature list is fine. The real question becomes: “Will this company still exist when my boss asks me about it next quarter?”

Being 33 doesn’t magically solve that, but it often correlates with things that help: having seen a few cycles, knowing how procurement works, understanding how legal teams think, and having the stamina to run a real sales process without treating every “we’ll get back to you” like a personal insult.

The research on founder age is… not what movies promised

Here’s the fun twist: even though 33 can feel “late” in startup mythology, large-scale research and business analysis often suggests the most successful founders skew older than people assume. Multiple widely cited analyses have pointed to outcomes where high-growth entrepreneurship correlates with founders in their 40s, and some research frames the average age of founders behind the most successful high-growth startups around the mid-40s.

That doesn’t mean “older is better” in some simplistic way. It means the advantage often comes from experience: industry knowledge, networks, pattern recognition, and the ability to navigate messy execution without melting down. Lemkin founding his first company at 33 sits right in the zone where you have meaningful experience but still have the appetite to sprint through walls.

How Lemkin’s early timeline shaped the later SaaS playbook

A founder’s first company tends to hard-code their instincts. If your first business forces you to sell complex value, you develop a muscle for positioning. If your first business forces you to hire under pressure, you learn quickly what “culture” really means (hint: it’s what people do when your calendar is on fire).

Lesson 1: “White space” is a cheat codeif you can actually see it

Lemkin describes NanoGram as a “white space” start-up: clear gap, clear tech angle, clear why-now. The advantage of white space is focus. The danger is that markets don’t always reward being early. If you’re too early, congratulations: you invented a category that someone else will monetize later.

The more interesting part of his story is not the romance of the ideait’s the execution sequence: license tech → recruit talent → raise capital → sell strategically. That’s not just “build and hope.” It’s a set of moves that look a lot like an operator playing chess instead of a founder playing lottery.

Lesson 2: EchoSign shows how “boring” workflows can become huge businesses

E-signature sounds boring until you realize how much money sits on the other side of a signature. Contracts drive revenue. Contracts drive hiring. Contracts drive compliance. If signatures are slow, everything is slow.

EchoSign’s early pitchmaking signatures and approvals easierfits a classic enterprise wedge strategy: start with a painful, universal workflow; land fast; then expand into broader document processes. It’s the kind of business that can scale quietly until suddenly it’s everywhere, and you wonder how you ever lived without it. (Like cloud storage. Or noise-canceling headphones. Or the “unsubscribe” button.)

Lesson 3: Content and community aren’t side queststhey can be the go-to-market

One reason people associate Lemkin with practical SaaS growth advice is that he didn’t just build companies; he narrated the learnings afterward. SaaStr itself began as a blog and Q&A-style knowledge-sharing project and then expanded into meetups, podcasts, and major conferences.

From a marketing perspective, it’s a master class in compounding trust: publish insights → attract the right audience → build relationships → turn attention into a platform. The lesson for founders is not “start a conference.” The lesson is: if you consistently teach your market, you become the default reference pointand default wins deals.

SEO note: why this question gets traffic (and why people care)

Searches like “Jason Lemkin age when founded first company” aren’t just trivia hunts. They’re identity questions in disguise. People ask because they’re trying to locate themselves on a timeline:

• “Am I too late to start?”
• “Did I miss my ‘founder window’?”
• “Do serious entrepreneurs start at 22… or is that just social media cosplay?”

The reason this particular answer resonates is that it’s simultaneously ordinary and encouraging. Thirty-three isn’t a magical age. It’s just an age at which a lot of smart people finally feel readyand then promptly realize they were never going to feel fully ready anyway.

What founders can learn from a “first company at 33” timeline

1) Use your pre-founder years like a training montage (minus the sad violin)

Lemkin’s timeline implicitly argues that the years before founding aren’t “wasted.” They’re where you accumulate pattern recognition: how customers buy, what budgets look like, how legal slows deals, how product and sales fight, and what “urgent” really means.

If you’re building a B2B or enterprise company, those patterns are not optional. They are the sport.

2) Don’t confuse “young” with “fast”

Speed comes from clarity and focus, not birth year. Some founders are fast at 22. Some are fast at 42. “Fast” usually means: you know the customer, you know the pain, and you can ship without turning every decision into a ten-person debate.

Founding at 33 can be an advantage because you’ve probably already watched a few train wrecks in slow motionand you’d prefer not to buy that ticket again.

3) The best “first company” problems are the ones people already pay for

Both NanoGram (deep tech with clear commercial value) and EchoSign (workflow that touches revenue) connect to a simple principle: build around a pain that already has budget. Not “it would be nice if…,” but “we currently spend money and time on this, and it’s still awful.”

For your own first start-up, the least glamorous problems can be the most profitablebecause the buyer’s motivation is already alive and screaming.

So, how old was Jason M. Lemkin when he founded his first company?

Circle back to the headline and keep it clean: Jason M. Lemkin says he was 33 years old when he co-founded his first start-up. In his telling, that first start-up was NanoGram Devices.

The bigger takeaway is not that 33 is “the right age.” It’s that founder timelines are real life, not a movie montage. You build skills, you take swings, you learn what you didn’t know, and eventually you start the thingoften right around the moment you stop trying to look “ready” and start trying to be useful.

Extra: of experiences that feel suspiciously familiar if you start your first company at 33

Starting your first company in your early thirties tends to come with a particular flavor of “founder experience.” It’s not better or worse than starting at 22 or 42it’s just different, like ordering the same burrito with a new salsa and realizing the real risk was always the salsa.

First, you often have a stronger instinct for what doesn’t matter. In your twenties, it’s easy to mistake motion for progress: redesign the logo, rewrite the homepage, “reposition” the product every time someone on Twitter uses a new acronym. In your early thirties, you’re more likely to ask: “Will this help us close a customer or build something customers will renew?” That bias toward outcomes is an underrated superpower.

Second, credibility games change. You may still feel youngespecially if you’re selling into conservative industriesbut you’re less likely to be treated like a science fair project. Meetings shift from “Aw, cute idea” to “Okay, walk me through security, pricing, and implementation.” That’s not always fun, but it’s real buying intent. And once buyers treat you like a real vendor, the path to revenue becomes clearer: build trust, reduce risk, show proof, repeat.

Third, you probably have a mental library of “company mistakes” you’re allergic to repeating. You’ve seen hiring mistakes, priority thrash, confusing pricing, and the classic tragedy of “we built a thing nobody budgeted for.” That memory can make you faster because you avoid dead ends. It can also make you cautious. The trick is using experience to stay focused, not using experience to talk yourself out of taking the leap.

Fourth, your relationships are more usable. Not in a cynical waymore in a practical way. You know people who can advise, introduce, sanity-check, and sometimes even become early customers. In B2B, distribution is often the hardest part. Starting at 33 means you may already have the beginnings of distribution simply because you’ve existed in the professional world long enough to be someone other than “that person who just added me on LinkedIn.”

Finally, there’s the emotional experience: you’re old enough to recognize that building a company is stressful, but young enough to still try anyway. You take the leap with clearer eyes. You’re less surprised that hard things are hard. And you’re more likely to design a company you actually want to run, not just one that looks good in a launch tweet. If you’re asking the “how old was Jason Lemkin?” question, chances are you’re really asking, “Is my timeline okay?” It is. The only timeline that fails is the one where you never start.