Adam S.

My life thesis: execution > strategy. Compounding FTW. I'm an optimistic skeptic. Curiosity is the most important quality in life.

I enjoy pattern matching and read widely. The opportunity to learn every day is a gift. Time is precious. The ability to improve what and where I focus and delegate the rest is ideal. 

I [of course] love my family and friends. I believe I am a logical, thoughtful adult and therefore accept my choices. I am content and therefore I have won.

Founder and CEO @Chore. We are a founder's back-office (HR, finance, compliance, equity) operations team. Back-office operations are an undifferentiated tax on success. Focusing on your superpower enables success. Chore handles the rest (i.e. we specialize in ops so you never have to) so you can achieve your dreams. 

Host of the Entrepreneurial Excellence podcast. I dive deep with multi time founders about their key decisions, actions, hires, drivers and more that they use to achieve "excellence." 

General Partner at the Autopilot Fund. We invest in early stage startups. We love obsessed founders who have a history of breaking through walls. I have invested in over 200 startups across multiple funds. 14 are unicorns (8 from seed).

In previous lives, I founded 3 other companies, been a product leader on a big co API team, Chief Revenue Officer (CRO), Chief Operating Officer (COO), and do-it-all janitor. 

I enjoy building great teams, processes, and stories that unify a company around a shared mission. Helping others build successful businesses brings me joy. More successful startups = a better, more dynamic world.

People describe me as energetic, positive, creative, detailed and optimistic. I enjoy rational, logical, data driven debate built on mutual trust and respect. I'm not an engineer but people view me as "technical" and have built companies with the brightest PhDs and brilliant engineers. The best compliment I received was "you ask great questions."

Honesty, trust, fun, a sense of urgency and mission are what I look for in colleagues and places I work. Passion about my product, my company and my team is what drives me. I work hard and enjoy being surrounded by people who do the same. 

"Leave the world (and your business) better than when you arrived..."
"The greatest risk is not taking one!"

Always curious and learning. Subscribe to Entrepreneurial Excellence to learn.

General Partner

The Autopilot Fund focuses on early-stage companies that serve and accelerate how companies operate. 

More about us: https://autopilot.fund/

Operations span various “departments”: could be in engineering, operations, sales, finance, product, customer success… the questions we ask ourselves are:

1. Is this a founding team so capable that others should be afraid to go against them?
2. Do they understand the problem better than anyone, and have special “founder-market” fit?
3. Will they rest until they have dragged the world kicking & screaming into their vision of the future?
4. Is the product “infrastructure” in a manner of speaking: structured data, deeply embedded, sticky?
5. Does the advent of AI exponentially increase or decrease their defensibility?

Our portfolio includes some pretty special companies like AngelList, Pulley, Puzzle, Levels, Disco, among others. 

Smart founders focus. Bad founders distract themselves with all the small, non-product, non-customer work that can easily take up hours but not move your startup forward.

We are sector agnostic and focus mostly on early stage. Our thesis is simple: the best founders come from anywhere, with any background, working in any industry. Focus, joy, dogged determination, and deep knowledge about your product and how you're changing the world is what leads to success.

If you're interested in learning more, drop me a note on LinkedIn.

My team and I at Chore have worked on this for months, and now we're excited to announce that Chore is launching a product we're very proud of; our AI Document Classification System. But first, let me tell you a little story.
 
Years ago, every Sunday I used to sit with QuickBooks receipts while my wife watched Netflix. Then she'd say "Really? This is what you're going to spend your Sunday night doing?". I'd think, "Fair point."
 
When we first started Chore, we were drowning in the same problem, spending 15+ hours weekly just sorting documents for our clients. Tax forms, contracts, invoices, HR paperwork, and more.
 
So we built something to fix it.
 
It's an AI document classifier that's trained on 20,000+ real documents from actual operations. We set confidence thresholds where anything below 90% certainty gets a human review, and created a super cool interface where team members see flagged documents instantly.
 
Our document processing dropped from 15 hours to 2 hours weekly, with zero critical errors in 6 months.
 
We spent months building this, but now the payoff is permanent.
 
Now when I upload 50 random documents, I watch AI sort them in seconds with confidence scores. The human review queue shows flagged items, and our time savings dashboard shows hours reclaimed.
 
The truth is, you raised $5 million to build your product, not to become a filing clerk. Every hour saved on document sorting is an hour invested in your growth.
 
So let me know if you'd like to try it out. Send me a DM to take a look.

CEO @Chore | Founders shouldn’t do their own HR, finance, and compliance. That’s what Chore is for.

When I started my first company, I made a hire at employee #7 that I regret to this day. We'd just closed our seed round, and we felt like we were supposed to start "building the team for real."
 
So I hired a full-time office manager / HR person.
 
Pretty nice person, and good at their job, but at 7 employees, there wasn't enough work to fill their week. They ended up doing a little bit of everything and not enough of anything. Meanwhile, I still didn't have enough engineers on the team.
 
That one hire cost us roughly $85K fully loaded and probably 3 months of product velocity.
 
I think about this every time a founder asks me who to hire after they raise. Here's the framework I wish someone had given me:
 
At 5–10 employees, only hire people who build your product or generate your revenue.
That's it. Engineers, a founding salesperson and marketer, and maybe a product designer if your product is consumer-facing.
Everything else, like HR, payroll, finance, compliance, equity management? Outsource it. And this isn't because it doesn't matter as much as the other functions. It's because it matters too much to do badly with a generalist hire who's also ordering office supplies.
 
At 10–25, hire your first ops or people lead.
Your outsourced layer should be doing amazing by now. The mistake I see here is founders hiring a Head of People at employee 12 and that person immediately drowning in benefits admin, state registrations, and 409A valuations. You don't need them yet. You need another engineer or another AE.
 
At 25–50, start hiring where institutional knowledge genuinely matters.
This is the danger zone. You feel like a "real company" now. The board might even ask why you don't have a Head of Finance or a People lead yet.
The answer is because your outsourced partners are still handling it better and cheaper than a single hire could. One ops person at this stage can't cover finance, HR, compliance, and equity management well. So you'd need two or three. That's $300K+ spent every year that doesn't even directly contribute to your bottom line.
 
After 50 employees, maybe you can start hiring where institutional knowledge genuinely matters.
This is when the complexity justifies dedicated headcount. Not before. The founders who scale their companies successfully know this difference early.
 
The ones who over-hire into back-office functions before they're ready spend 18 months unwinding it. I've seen it over and over, a startup with 15 people and 3 of them are in ops roles that could've been handled by one good outsourced partner.
 
The rule I follow now: if the role doesn't build the product or bring in revenue, the default answer is outsource until you hit 50. Then hire.

I got a text from a founder a couple of weeks ago at 11:47pm.
"Quick question: do you know what expense category to use for..."

I knew exactly where this was going. Another founder deep in QuickBooks, reconciling March expenses in May, thinking they're "being scrappy."

And here's what I tell founders in this situation:

Founders who are personally in charge of their company's bookkeeping functions think they're saving money. They're not.

The math I walked them through:
- 15 hours/month on bookkeeping
- Founder time worth ~$250/hour in enterprise value creation
- 15 × $500 × 12 months = $45,000/year

They were burning $45K of runway to feel "in control." I asked them one question: "What did your competitor ship while you were categorizing Uber receipts?"

The silence said everything.

Today he messaged me: "Just hired fractional help for ops and it's the best $3,000/month I've ever spent. I used those 15 hours for 3 customer calls and finally shipped that feature."

Sometimes the best advice is about doing less of the wrong things.

What's the one operational task you wish you didn't have to do?

I was going through our legal bills from one of my earlier startups and nearly fell out of my chair. We paid $4,000 to update three employee stock grants after promotions.

The lawyer sent me a nice PDF invoice, breaking it down. Each grant update was between $1,000 and $1,500. For clicking buttons in Carta and changing some numbers.

So I started asking other founders what they pay for cap table stuff. The numbers are insane. One founder paid $750 for their lawyer to export a cap table PDF for an investor. Another paid $2,000 to adjust a vesting schedule. These are literally five-minute tasks if you know where to click.

The thing that gets me is that most lawyers don't even do this work themselves. They have paralegals handle it, but they still bill you at lawyer rates. Sometimes they bill at paralegal rates, which sounds better until you realize that's still $350 an hour for data entry.

I think lawyers know that founders are scared of messing up equity stuff, so they position all cap table work as this complex legal work that requires their expertise. But honestly, once your equity plan is set up, maintaining it is mostly just keeping track of numbers and dates.

The whole thing reminds me of when accountants used to charge thousands to do tax returns before TurboTax came along. Except somehow we're still living in the pre-TurboTax era for cap tables.

What's the most ridiculous legal bill you've gotten for routine work?

Yesterday we launched our AI document classification product. Within a few hours, my inbox filled up with lots of people telling me this one thing 👇🏻
 
“This is what AI is actually supposed to be used for.”
 
What they meant is, we used AI to do something practical. Automatically organizing the messy, unstructured documents that quietly slow companies down.
 
It's the kind of work nobody brags about, but everyone feels.
 
The best AI use cases make you say, “This saves me hours.” AI should integrate into your workflow and make your life meaningfully easier.
 
And day one feedback tells me we’re building in the right direction.

Jack Dorsey just laid off over 4,000 people from Blocks. Every founder should read Jack’s memo. Here's what I think about it:
 
What stood out to me in Jack’s note was the framing. He’s saying the way companies operate is changing, and changing fast, because intelligence (read: AI) tools are fundamentally altering what it means to build and run a company.
 
That’s the real headline here.
 
For years, we’ve talked about AI as a productivity enhancer. Now we’re seeing leaders treat it as an operating model shift. We're seeing smaller teams with AI embedded into workflows, and more and more founders are admitting that the same output can come from fewer people if systems are stronger.
 
There are two uncomfortable truths here:
1️⃣ Technology always compresses labor somewhere.
2️⃣ As Jack said, leaders will eventually have to choose between gradual drift or decisive restructuring.
 
Jack chose decisive.
 
You can debate whether it was the right call. You can question timing, scale, or execution. But I do respect one thing: clarity. A single hard reset is brutal for everyone, but at least it’s honest about the direction.
 
The bigger question for founders watching this isn’t whether Blocks was right or wrong.
It’s: if intelligence tools genuinely enable smaller teams to operate at a higher level, how should you be structuring your company today? Are you building a headcount-heavy company optimized for the past? Or are you redesigning how work gets done based on how things are shifting?
 
This also doesn’t mean “replace people with AI ASAP” That framing is way too simplistic. It means you should redesign your workflows so humans do judgment, creativity, and strategy, and machines handle repetition, pattern recognition, and scale.
 
Let me also be clear on this: transitions like this are painful. The people leaving built real value. Severance and healthcare extensions may help a little, but it still feels like shit. But my note to founders is that how you treat people on the way out is part of leadership too.
 
Moments like this are a signal that the definition of “efficient” is changing. If you want your company to win, you have to rethink how your team is structured from the ground up. And you'll have to do it without losing their humanity in the process.
 
What do you think about Jack's memo?

A software engineer I know lives in Birmingham in the UK. Her company decided everyone had to come into the London office. Monday to Friday.
She can't afford to move, and the commute isn't realistic. She even offered to come in 3 days a week instead, but they said no.
 
There is no version of the world where that decision helped the company.
 
She writes code. The code she writes at home is the same code she writes in an office. Except at home, she starts work at 9. In the office, she arrives at 9, after two hours commuting, and spends the first 30 minutes recovering.
 
Now, to be fair, there's a real argument for being in person when you're early stage. When you're 4 people still trying to find PMF, being in the same room every day can genuinely speed things up and create a better culture. I'll admit that it helps.
 
But this company isn't 4 people figuring things out. They have a product, lots of customers and a software engineer who's been doing the job well from home for years.
 
This is what office mandates actually cost you:
— Your office sits empty more than 50% of the time, even when "everyone" is in.
— You're paying fixed overhead on a depreciating asset while your competitors pay nothing.
— Every hour spent commuting is an hour your team isn't working, isn't rested, and isn't at their best.
— And you've just limited your talent pool to whoever happens to live within driving distance, instead of hiring for the best.
 
And beyond the math, to me, it signals something about how you manage people. If you need to physically see your people to know they're working, you haven't defined outcomes clearly enough. I'd say that's a leadership problem.
 
We're moving into a world where autonomous systems operate 24/7 with zero overhead. The humans competing alongside them need the same operating model, trusted to deliver outcomes, and not managed by proximity.
 
If your team can't be trusted to work remotely, you have a hiring problem. Or maybe an incentives problem. Or even an outcomes problem.
 
And none of those get solved by a commute.
 
I've seen lots of companies enforcing office mandates recently, and I'm curious. What exactly are you trying to achieve by making everyone come in? If you're a founder who disagrees with me, what has changed between when you were remote and now when you see everyone IRL?

Our friends at Stable surveyed 250+ companies and there's one surprising blind spot they all share.
It's sitting in the corner of your office operations looking completely harmless, and it's quietly costing your team more than you'd think. In time, in compliance risk, and in the kind of low-level reactive work that pulls people away from things that actually matter.
 
It's mail. Not email, it's physical mail.
 
Stable's data reveals exactly what's happening inside these workflows. How much time is being lost, where the bottlenecks are, and what changes when you actually modernize it.
 
Next Monday, March 24th, I'm joining Stable's Andrea Paul Salerno to unpack what 250+ businesses revealed about the real operational cost of mail, and what it looks like when you fix it.
 
If you're an operator, founder, Chief of Staff, or finance/compliance lead who's ever thought "we really need to sort out how we handle mail", this one's for you.
 
📅 March 24th | 1pm ET / 10am PT
🔗 Link to register in the comments

A $2M ARR company with 8 employees just raised a Series A at a better valuation than a $2.4M ARR company with 22. They're in the same space with a similar growth rate. So what was the difference?
 
ARR per employee.
 
The first company was generating $250K per person. The second was generating $109K. To a Series A investor pattern-matching across hundreds of decks, those are two completely different businesses regardless of what the top-line number says. One is a lean, efficient revenue machine. And the other is a company that's going to need a lot more capital to get to the next milestone.
 
Most founders don't track this metric until they're already in a term sheet conversation and it's too late to do anything about it.
 
I have a hot take. This is quietly behind a lot of the layoffs you're seeing right now. Founders overhired during a window when headcount felt like a proxy for momentum, then looked up one day and realized their ARR per employee was way too low. Then layoffs happened as a course correction. I'm not saying it's right, but sometimes layoffs don't happen because the business is struggling, but because someone finally ran the numbers and understood they didn't make sense.
 
And the lever that moves this metric the most is where you're putting that headcount. A full-time hire comes with a 6-month ramp before they're fully productive, with benefits, severance exposure, and a cost that hits your ratio immediately before you see any output. A contractor or vendor relationship is a 30-day out, no overhead, and faster time-to-value for scoped work. Back-office functions especially finance, HR, compliance, equity management, none of these need to live on your payroll at the early stage.
 
If you're raising in the next 6 months, divide your ARR by your current headcount right now. What number are you looking at?

Something weird happened last month. I had a call with a founder who's doing about $2 million in revenue, growing fast, and has a great team. But during our conversation, he casually mentioned he still does the company's bookkeeping himself every Sunday.

I asked him why. He said it only takes an hour, and he likes staying close to the numbers. I did some quick math in my head. That's 52 hours a year he's spending on QuickBooks instead of talking to customers or working on product. At his growth rate, each of those hours could be worth tens of thousands in company value.

I told him I couldn't invest in his startup.

This probably sounds harsh, but I've learned that founders who won't let go of basic operations tasks are usually the same ones who become the bottleneck for everything else. They're the ones approving every expense and touching every decision. Their companies hit a ceiling, and they can't figure out why.

I remember working with three different founders who all had this problem. One would literally do payroll during board meetings because "it had to be done right then." Another missed important customer calls because she was dealing with state filing deadlines. The third spent his entire fundraising prep week managing expense reports and then wondered why his pitch was underprepared.

All of them were smart people. All of their companies struggled to scale. The pattern is pretty clear once you see it enough times.

The weird part is that these founders usually know they should delegate. They just can't do it. They tell themselves they're being responsible by staying involved in everything, but really, they're slowly suffocating their own company.

So be honest. What task are you doing for your startup that you know you need to delegate?

New flex: tiny team, insane output. Headcount is last decade’s vanity metric. Why Jack's 40%+ headcount cut at Block is what every team should be doing.
 
Jack Dorsey just cut ~4,000 people at Block (close to half). This is the way.
 
Smaller teams + intelligence tools + ruthless focus beat bloated org charts.

The metric you should obsess over isn’t headcount. It’s ARR per employee (or gross profit per employee).

Every full-time hire you add early comes with hidden costs:
- coordination debt
- slower decisions
- more management
- permanent fixed burn

Hence, STOP HIRING. A bigger team is not a flex. It's a sign you're undisciplined. It's a sign you're still thinking like it's the 2010s [when the only way to scale was with more people].
 
I probably beat a dead drum but the idea of a Seed or Series A founder doing their own back-office operations is as insane as you trying to build your own power plant to keep the lights on or building your own servers instead of delegating to AWS. Both are critical and if you mess them up, your business is screwed, yet...you outsource the work. 
 
Why would you NOT want experts - who also don't require recruiting, management, equity or severance - running your operations? 

It's insane to think you should spend any time on back-office overhead. You are being penny-wise and pound foolish.

Some of Chore's clients are just two founders who outsource everything non-product and GTM to us. Other of our clients are over 100 FTEs and are gutting their back-office teams as they realize they don't need non-specialized headcount.

Block just became way more lean. Are you doing the same?

2026 mantra: tiny team, massive output, zero busywork.
 
[Note: this is my second post on this topic because, well, the fact that founder's dont get this kills me. Wake up!]

Every week I notice a handful of startups that are making moves most people aren't paying attention to yet. I'm going to start writing them down and sharing them here.
 
It's pretty much my list of founders and operators doing interesting things that I think deserve more visibility in this feed.
 
Here's week one:
1. Sandbar — AI smart ring that transcribes voice notes and enables conversational interaction on your wrist. The wearable AI race is heating up fast, and Sandbar is one of the few betting on a clear, specific use case rather than trying to do everything.

2. Mind Robotics — It's a Rivian spin-out building industrial robots for dexterous factory tasks. They just raised a $500M Series A. When your training data comes from a real manufacturing plant, you have a moat most robotics startups can't buy.

3. Standard Kernel Co. — They're building AI systems that generate GPU software & just raised $20M in seed funding. The problem they're solving is very real. Every new model architecture can require months of specialized engineering to optimize performance-critical code blocks, and kernel engineers are scarce. So they're using AI to automate that process entirely.

4. Jazz — A data loss prevention startup that emerged from stealth with $61M just raised. It's enterprise data protection built for the AI era, and I think this category is going to matter a lot.

5. XBuild — The first AI platform purpose-built for construction. It generates detailed job estimates, supplier pricing, and reports in a fraction of the time. Industries that have been underserved by software are finally getting the products they need to be more efficient.

6. PactFi — A platform for managing complex private credit transactions and deal closing. They just raised a $25M Series A. Back-office for private credit is a real problem and they're going after it.

7. Gangkhar — An AI-native embedded insurance infrastructure for carriers and distributors. Just raised a $4.25M seed round.

8. Risotto — An AI-native autonomous help desk founded by operators from Dropbox, HelloSign, and Gusto, raising $10M seed and backed by Y Combinator. It sits between ticketing tools like Jira and the internal systems that actually resolve requests, rather than bolting AI on top of legacy infrastructure. Risotto autosolves 60% of monthly support tickets for Gusto, saving 1000s of hours/month.

9. Sequence — An accounts receivable automation using AI agents to handle contract intake, collections, and revenue journals. The reviews are strong and the use case is super obvious.

10. Factors.ai — B2B demand-gen and account intelligence platform. It helps teams identify intent and prioritize the right accounts. If you're a founder trying to make your sales motion smarter, it's worth a look.
 
That's all folks. If you're building something worth watching (or know a founder who is), drop it in the comments. I had a lot of fun curating this list so I'll be doing this every week.

Your new hire's first week tells them everything about your company. And most founders are accidentally telling them: "We have no idea what we're doing."
 
You spend weeks getting the recruiting right. The sourcing, the interviews, the offer negotiations. All the energy goes into getting someone to say yes. Then they start, and everything behind the scenes is messed up.
 
Payroll isn't set up yet, the state registration you need to even hire them legally never happened, the equity grant is stuck because the 409A expired, or some other stuff. They're asking where to submit their banking info and nobody give them a good answer.
 
Their first impression of the company they just bet their career on? That nobody has their act together.
 
I talk to founders all the time who are scrambling to figure this stuff out the week someone accepts. Here's what I've noticed about the ones who hire well:
 
They treat all of this as pre-hiring infrastructure. Not something to figure out during onboarding.
Before they ever extend an offer, they already have:
→ Payroll configured and actually tested (not just signed up for)
→ State registration complete if hiring in a new state (this takes weeks, not days)
→ Equity grant templates ready in Carta or Pulley so they can issue the grant week one
→ Onboarding docs ready to send automatically instead of built from scratch each time
→ Benefits enrollment figured out so new hires don't miss their 30-day window
 
The major difference is timing. If you think of these as onboarding tasks, you start working on them when someone accepts. And by then, you're already behind.
 
If you think of them as infrastructure, you set them up once and they work for every hire. The offer goes out, the new hire gets a great experience, and you're not spending their first week apologizing for the mess.
 
Most founders have never set up payroll or HR processes before. Why would they? It's not their thing.
 
But that's exactly why it gets pushed to "we'll figure it out when we need to." By then it's too late.

Everyone has been panicking about the SaaSpocalypse. SaaS stocks are getting crushed and AI is killing the per-seat model. Here's what I think ➡️ the panic is real but most people are drawing the wrong conclusion from it.
 
The narrative is "AI will let companies build their own software, so why pay Salesforce?" Which sounds scary until you think about it for more than five minutes.
 
Yes, you think you can now vibe-code a basic CRM in a weekend. But here is what that overlooks: shipping a v1 is not the hard part. The hard part is maintaining it, iterating on it, and keeping pace with what a dedicated company with hundreds of engineers is shipping every month. You are not replacing Salesforce. You are becoming Salesforce's competitor. And that is not a good use of a founder's time.
 
At Chore, we use Pipedrive. Could we build our own version? Probably. Would we save money on seats? Yes. But if I value my team's time honestly, it would take days or weeks hours to build, then an hour every month to maintain, and I would always be chasing what Pipedrive just shipped. The math is negative ROI before I have written a single line of code.
 
You need to stay obsessively focused on what you are uniquely good at and pay other people to do everything else really well. That principle has not changed. AI just made the build vs. buy question louder.
 
The SaaSpocalypse is real for companies that were already coasting on weak product and legacy pricing though. This doesn't apply to them, but for everyone building something genuinely valuable, this is noise. Don't pay attention to it.

I’ve always been drawn to the different, the audacious, and the unconventional. That curiosity led me straight into the startup ecosystem - where I spent my early years growing and scaling early-stage startups, thriving on the thrill of the 0 to 1 Journey. 

Eventually, I bootstrapped my own venture, Bluwave, where I wore every hat: sales, growth, operations, logistics, finance - you name it! 

It was during those Bluwave days that I discovered the real time sink: dealing with vendors, endless email follow-ups, phone calls,  the constant invoice mistakes… It felt so robotic, so painstakingly manual.

I remember thinking, “It’s 2024 - why are we still working like this?”

So TL;DR: out of Bluwave came a new obsession, mission, idea.  Because if ten truckloads were enough to make me swear off manual processes, imagine what thousands do to a large enterprise. 

That question sparked a new beginning, leading me to finding others who were equally obsessed and had the deep industry knowledge of complexities logistics.

taplio

The Battle

Adam S.

Yash Tiwari

Followers

Posts

Engagements

Likes

Performance ScoreAdam S.'s LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Adam S.

Yash Tiwari

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Adam S.'s LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreAdam S.'s LinkedIn Performance