Jason ✨👾SaaStr.Ai✨ Lemkin Profile picture
Jul 24, 2021 11 tweets 4 min read Read on X
So Avalara is a Quiet Giant in SaaS -- that you don't know enough about

At $600m ARR, growing 38%+, it does something both boring AND hard

It sells tax compliance software to SMEs

5 Interesting Learnings: ⬇️⬇️⬇️⬇️⬇️
#1. 15,580 customers, up 20% year-over-year — or $40,000 per customer per year on average.

NRR is 107%, fairly consistently over the past 4 quarters. Good but not great for a $40k deal.

What they do is mission critical, so ACVs from SMEs are pretty high
#2. 1000 partners are key to their GTM strategy. And “in 950 of the partners, Avalara has no competition”.

Like HubSpot, Shopify and other leaders that sell sophisticated, $10k+ solutions to SMEs, partners are key to implementation.

They invest >heavily< here
#3. $180,000 revenue per employee. With 3,351 employees, Avalara is not that leveraged.

We’ve seen this with sales-driven SMB and SME leaders like Xero as well. If you are selling to SMBs, you have to be efficient. Especially if they need a lot of human interaction.
#4. 7% of revenues from prof services — which have 48% margins

Avalara leans on partners to do most of the heavy lifting here (see #2), but they still provide them for larger customers. They mark the services up about 2x. They don’t lose money on services.
#5. Driving upmarket to cross $1B in ARR, but $100k is still a big customer for them

Avalara is fueling growth to $1B ARR by pushing into $100k+ deals, but it didn't rush there.

Their core is still SME and it got to hundreds of millions of ARR while remaining SME focused:
And a few bonus notes

#6. It wasn't a rocketship to start.

Avalara was founded in 2004, took 16 years to hit the first $500m in ARR, in 2020.

But the compounding now is epic.
#7. Gross annual churn of 4%, NRR of 107%.

It’s great to see an SME leader disclose the combo of gross churn and NRR.
#8. Long-tail drive revenue.

Most of us underinvest in our partner ecosystem, see #2 above

A great visual here about how their 1000+ partners bring in revenue and deals for them:
#9. Finally, deal sizes are up across all segments — Small, Medium, & Large

Enterprise is $71k ACV, Mid-market is $36k, SMB is $23k, and small customers are $14k ACV

Deal sizes are all up over the past 24 mos outside of smallest customers

This is how most of us scale
A deeper dive here:

saastr.com/5-interesting-…

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Jason ✨👾SaaStr.Ai✨ Lemkin

Jason ✨👾SaaStr.Ai✨ Lemkin Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @jasonlk

Oct 5
ICONIQ's latest State of Software 2025 report is out.

Buried in 73 pages are some great data on just how AI is changing B2B software

Here are my Top 10 Learnings: 🧵 Image
#1. AI Companies Burn More Cash — But Also Have Better Capital Efficiency.  It’s Not a Paradox But … It’s Complicated.

This one breaks your brain at first: AI-native companies under $100M ARR have a median FCF margin of -126% (they’re burning cash at 126% of revenue). That’s more than double the -56% for non-AI companies.

Yet their burn multiple—the key metric for capital efficiency—is actually better: 0.4x versus 1.8x for non-AI companies.

Translation: AI companies are burning more absolute dollars, but they’re generating new ARR so much faster that each dollar burned produces more revenue growth. They can afford to burn harder because the growth rates are exponential rather than linear.

This suggests we need entirely different frameworks for evaluating AI-native businesses. Traditional SaaS metrics around payback periods and magic numbers may not capture what’s really happening when you can scale revenue 3x faster than historical benchmarks.Image
#2. GTM for AI Products Is Flipped: 55% of High-Growth Teams Are in Post-Sales

Traditional SaaS companies put 55% of their GTM headcount in sales roles.

For high-growth AI-native companies, that ratio is flipped: 47% in sales, but 31% in post-sales (versus just 23% for traditional SaaS).

AI leaders have sales teams. They are just much smaller. And much more of that budget is going to FDEs, SEs, and post-sales.Image
Read 13 tweets
Sep 27
Can AI agents really manage other agents? Most of us can't even get one AI agent to really work well.

But it works in @Replit v3. For real. And it's so cool.

I had it do a 2.75 hour autonomous security audit. One agent managing other AI agents.

Here's how it worked:🧵
2/6: I was updating our pitch deck grader and it became time to deeper security audit.

This was just hard before v3. To do it for real. Doing a deep security audit against every single element of the app.

But instead of getting stuck, Replit V3 autonomously brought in specialists:

-Security expert
-System architect
- Senior/junior agents

I watched them DEBATE each other in English for 3 hours. Like humans. Like extremely talented, bickering engineers.

It was like old times :) Just without the humans.

🚀And truly incredible.

(Now bear in mind in a sense some of these agents are different personas of the same agent, but I'm not sure that really matters)Image
3/6: Why this was so novel:

No human could conduct a 3-hour security audit covering every line of code, every function, every vulnerability. Without a break, on demand.

These agents found edge cases I'd never consider. A lot of them. Maybe too many, but a lot of them.

And then on their own, they implemented sophisticated protections. They thought through attack vectors systematically.

For hours.
Read 6 tweets
Jul 21
Vide Coding Day 11,

So today’s been a time of introspection and reflection. I have learned a lot becoming a ‘vibe coder’ and it has been addictive. For real.

My #1 learning is an old one, re-learned: Building Great Software is Still Hard.

Getting going is easier than ever. 🧵
On the dev tools side, I’ve asked all the best CTOs in my portfolio how much they really benefit from Cursor, Claude Code, et. al.

The consistent answer: net net, no one is giving back their Claude Code. No one. But net net, alone, it lets folks move about 20%-40% faster.

Why? These tools (all really Anthropic LLMs) help everyone do routine work faster, and in fact, some of the best devs I talk to can do 90% of most of their routine work in prompts.

But what about the hard stuff? The stuff that hasn’t been done before? The novel stuff?

What about the planning? The thinking?

What about code reviews and checking the work?

That all takes time.

So net net many are seeing a 20%-40% real productivity boost from Claude Code et. al. Much higher for routine stuff, but net net of all of the job — that’s where it seems to land today.
On the platform side, the B2C side, Replit+Loveable etc., this tools are magical. Magical. Maybe more than magical.

If you want to build a POC or prototype, it’s all magic, really.

But in the end, if you want to built true commercial grade apps, then they are … just tools.

Flawed tools, magical tools, but tools. At least today.

You can now think up an app and see it prototyped in < 20 minutes. Longer if you want all the buttons to work, but still.

But getting to >great< software? That’s in its own ways is hard as ever. Even if the tools are so much cooler, faster, and slicker.

No great engineers have been made obsolete here.
Read 6 tweets
Jul 18
Vibe Coding Day 9,

Yesterday was biggest roller coaster yet. I got out of bed early, excited to get back @Replit despite it constantly ignoring code freezes

By end of day, we rewrote core pages and made them much better

And then -- it deleted our production database. 🧵
You can read the thread here, and all the convos with @Replit. It went rogue again during a code freeze -- and deleted our >production< database.

Rule #00001 my CTO taught me: never, ever, never, ever touch the production database.

Even in 2005, when we launched the first version of EchoSign / Adobe Sign, everything broke. But the database was sacrosanct.

In 2025, 1 Billion+ contracts later, I think no contracts were ever lost in DB. A few corrupted, but none lost.

Yet, Replt went rogued and destroyed our production DB last night.

During a code freeze when it knew to touch nothing. And agreed to touch nothing.

x.com/jasonlk/status…
Now it gets a little crazier. Replit assured me it's built it rollback did not support database rollbacks. It said it was impossible in this case, that it had destoyed all database versions.

It turns out Replit was wrong, and the rollback did work. JFC.

Replit went rogue again, lied, and then said we couldn't roll back.

But we could. I'm still processing all this.

Is it OK there are NO guardrails to deleting a production database?

Why did Replit "lie"? Also, why did it not know about how this feature worked?

Look, no matter what, deleting a >production< database is NOT OK.

But Replit lied / was wrong, and I just rolled back. And it >seems< OK.

JFC though.Image
Read 12 tweets
Jul 17
Vibe Coding Day 8,

I'm not even out of bed yet and I'm already planning my day on @Replit.

Today is AI Day, to really add AI to our algo.

I'm excited. And yet ... yesterday was full of lies and deceit.
@Replit Ok I have 2 main goals today:

1. Keep working on minimizing rogue changes, lies, code overwrites, and making up fake data

2. Get our AI working Image
Now, yesterday was crazy. Until 9pm or so, I wasn't sure we made any progress at all.

Because Replie was lying and being deceptive all day. It kept covering up bugs and issues by creating fake data, fake reports, and worse of all, lying about our unit test.

We built detailed unit tests to test system performance. When the data came back and less than half were functioning, did Replie want to fix them?

No. Instead, it lied. It made up a report than almost all systems were working.

And it did it again and again.
Read 32 tweets
Jul 16
Vibe Coding Day 7,

Let me be clear about at least one thing: @Replit is the most addictive app I’ve ever used. At least since being a kid.

(@lovable_dev is great, too. We used it to build a core landing page. I’m not taking ‘sides’, but for this project, I chose Replit).

Last night I was thinking about vibe coding in the middle of the night. I checked on my app on my phone at dinner. And while I opened up the WSJ first this morning, my brain would have prefer Replit. I’ve dropped tons of other things to make more time to be with Replie.

Will I get there? Will I go from ideation to a 100% commercial-quality app all inside a vibe coding app? Without hiring a dev, coding myself, etc. etc.?

I don’t know. I give it a 50/50 shot right now. But I am … addicted. I need the hit.

In fact, I’m a totally different person than I was a week ago. @HarryStebbings said he saw it when my responsiveness plummet. I’m locked in.
The goal today: slow it down.

My biggest fear, and 100s of you have shared it yourself, is that vibe coded apps are never stable. That the AI keeps rewriting them when you think you’re about 50% of the way there.

I’m there, too. So my goal is to slow it down. Vibe Coding makes you feel like a superhero, but as cool as it is, I’m not SaaS Superman.

So today I am going to lock down as much of the app as I can. Research more on how to minimize rewrites. And really make sure my unit tests actually work.

If I spent all day on my unit and other tests, that would be good. Instead of instantly building new features :)
I spend $200+ yesterday on Replit and will likely spend that much today. When you go all-in, with Claude 4 and extended windows and GPUs blazing, it’s not $25/month.

It’s a little more than $1 a minute to use Replit in max/max mode. That’s “cheap” vs a human. But not “I built my own Notion for $2” cheap.

But I almost don’t care. I’m … addicted to vibe coding.
Read 12 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Don't want to be a Premium member but still want to support us?

Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Or Donate anonymously using crypto!

Ethereum

0xfe58350B80634f60Fa6Dc149a72b4DFbc17D341E copy

Bitcoin

3ATGMxNzCUFzxpMCHL5sWSt4DVtS8UqXpi copy

Thank you for your support!

Follow Us!

:(