Mar 6, 2026
Every founder is being told to stay lean. Most are hearing it wrong.
You've seen the narrative.
AI-native startups hitting $100M ARR with 20 people. Solo founders replacing entire departments with agents. Three engineers doing the work of fifteen.
Some of it is true. Most of it doesn't apply to you.
Those stories come from AI-first, product-led SaaS companies with very specific models and very specific funding. If you're a Seed-to-Series B founder building something that requires trust, domain knowledge and real customer relationships - the playbook looks different.
Lean isn't about having fewer people. It's about having fewer of the wrong people.
Here's what I'm actually seeing right now - and what I think you should do about it.
The hiring market has shifted. Again.
The talent freeze is thawing.
For the past 18 months, most people sat tight. "Job hugging" - staying put, avoiding risk, waiting for signals. That's changing. Candidates are starting to move again. Employers are cautiously opening up.
This cuts both ways for you.
Your pipeline should improve. Strong people who were previously locked in are now open to the right conversation. But your own team is exposed too. If you've been relying on a flat market to keep people, that safety net is disappearing.
My advice: have the retention conversations now. Comp, progression, ownership. Don't wait until someone hands in their notice.
AI talent is not what you think it is.
There's a version of "AI hiring" that involves $1.5M comp packages and bidding wars with OpenAI. That's not your fight.
What I'm seeing founders actually need is AI-literate builders. Engineers who can integrate and ship with AI tools - not researchers publishing papers. That distinction matters, because the person who'll have the most impact in your business probably costs half of what you think "AI talent" costs.
Stop chasing the headline job title. Hire the person who builds things.
Credentials are fading. Output is winning.
Skills-first hiring isn't a talking point anymore - it's the default. Portfolios, bootcamps and proof of what someone has actually built are overtaking degrees and years-of-experience filters.
If your scorecard still says "5+ years experience" or "degree in Computer Science" as hard requirements, you're screening out some of the strongest candidates in the market. Rethink what you're actually filtering for.
Work model ambiguity is still the silent offer killer.
I keep watching this happen. A founder writes "flexible" on the job post. The candidate assumes two days in office. In the final round, it turns out it's four. Candidate drops out. Two months wasted.
Remote and hybrid roles fill faster than on-site. That's just the data. But the real issue isn't which model you choose - it's whether you're honest about it from the start.
One line of specificity on day one saves you weeks of dead pipeline.
3 things to do this month
1. Audit every open role against one question: what outcome does this hire deliver?
Not tasks. Not responsibilities. One clear business outcome. If you can't name it, the role isn't ready. If the outcome could be solved by tooling or restructuring an existing role, it probably should be.
This is how you stay lean without being reckless about it.
2. Run a 30-minute retention check on your three most important people.
When was the last time you had a real conversation about what they want next? If you can't remember - that's your priority this week. In a thawing market, your best people are the ones most likely to get tapped.
3. Read your own job posts like a candidate would.
Specifically the work model section, the comp section and the "about us" section. Is it clear? Is it specific? Does it match reality? If there's any gap between what you've written and what actually happens day-to-day - fix it before you run another pipeline.
What I'm seeing from my desk
I'm deep in hiring cycles right now across the Netherlands, wider Europe and the US - mostly technical, data, AI and leadership roles for Seed to Series B.
Three patterns keep coming up.
Founders who define the role around one outcome are closing faster. Less noise, better shortlists, fewer rounds. The ones trying to hire a "senior engineer who also does DevOps, data and maybe some product work" are stuck in month three of the search.
AI-literate generalists are the most in-demand profile I'm placing right now. People who can build with AI tools, not just talk about them. They're still findable - but not for long. If this is on your roadmap for Q2, start the conversation now.
The biggest reason founders lose candidates is ambiguity. Not comp. Not competition. Just unclear expectations. Unclear work model. Unclear reporting line. Unclear what success looks like. Clarity closes. Every time.
Tools
I've built a few lightweight tools to help founders move faster on hiring. DM me on LinkedIn with any of these and I'll send them straight over:
SCORECARD - A 5-line role scorecard template. Forces clarity on what the hire actually needs to deliver.
LOOP - A structured interview loop framework. Who interviews, what each stage tests, how to avoid asking the same thing four times.
OFFER - A checklist for making offers that stick. Comp, work model, timeline, and the soft stuff most founders forget.
Built Different - Because great teams are built different
Hiring question? Building a key team? DM me - always happy to think it through with you.
Brought to you by Will Aldred, Founder @ Built Different