Year one is hard in the obvious ways. Year two is hard in ways you couldn't have predicted. Year three is hard in ways that look, from the outside, like success.
By year three, the operator founder who made it past seed has real customers, a team, and a product that actually works. The founding thesis turned out to be right. But somewhere between month 24 and month 36, a set of traps open up that are specific to operators who built their company on deep domain knowledge — and they're not the traps that most startup advice covers.
Losing proximity to the customer
The first version of your business ran on your personal relationships and your direct knowledge of the market. You knew your first 20 customers by name, understood their specific workflows, and could call any of them on a Tuesday and have a real conversation. That proximity was your product team, your sales team, and your competitive intelligence all at once.
By year three, the team has grown. There are account managers and CSMs handling customer relationships. Product decisions go through a roadmap process. Sales calls happen without you. And somewhere in that transition, the feedback loop that powered your early product intuition gets filtered through two or three layers of internal reporting before it reaches you.
Operator founders feel this loss acutely because they know exactly what they're missing. The customer signal that got them here is now arriving as a weekly CS summary rather than a direct call. The product is starting to optimize for internal priorities — what the team thinks customers want, based on what customers told the account manager, based on what the account manager thought was worth escalating — rather than what customers actually need.
The fix is structural, not cultural. You can't just "stay close to customers" as a principle — that's a promise that organizational growth will override within six months. You have to protect direct customer time the way you protect the board meeting: in advance, on the calendar, non-negotiable.
Product scope creeping past the founding thesis
Operator founders who know their vertical SaaS domain well tend to see many problems worth solving. In year one, that breadth of vision is a feature — it means you can roadmap far ahead and pitch a compelling story about where the product goes. In year three, it becomes a liability.
By year three, most operator founders are running a product that covers more ground than the founding thesis called for. Some of that expansion came from customer requests. Some came from competitive pressure. Some came from investor conversations where "what else can you build" got mistaken for "what should you build next." The result is a product that does seven things adequately and nothing exceptionally.
Vertical SaaS companies win on depth, not breadth. The buyers in tight industry verticals are skeptical of horizontal features and deeply loyal to products that solve their specific workflow problem better than anything else. When you add scope, you risk diluting the credibility that came from your domain specificity.
The discipline required in year three is to narrow, not expand. Find the two or three features that your best customers use constantly, make those genuinely excellent, and treat everything else as a future roadmap item rather than a current priority. This is uncomfortable when investors are asking about expansion revenue and new product lines — but it's the right call for the category of company you're building.
Hiring people who look right instead of people who are right
The first hires at an operator-founded company tend to be excellent, because the founder is making every offer personally, using their own judgment about who fits the culture and the problem. By year three, you have a team doing some of the hiring, and the criteria for "right" starts drifting.
The specific trap for operator founders: hiring people from adjacent enterprise SaaS backgrounds instead of people who actually know the vertical. This feels safe — enterprise SaaS experience is legible, it has established career patterns, and it looks good on a fundraising deck. But the customer is not impressed by enterprise SaaS pedigree. They're impressed by people who understand their industry.
Your first sales hire, in particular, should come from the vertical, not from a SaaS sales background. Someone who sold roofing software to roofing companies will close deals in year three that a polished SaaS AE will lose, because the customer recognizes that the rep actually knows the job. That credibility transfers from the founder to the team — but only if the team has it.
Raising before the unit economics are real
By year three, there's often external pressure to raise a larger round. Revenue is growing, the team is real, and investors are circling. The founder feels the pull to raise — and to raise big, because that's what growth-stage companies do.
Operator founders often have better instincts about unit economics than most SaaS founders, because they come from businesses where margin discipline was a survival skill. But year three is when those instincts get tested. Churn rate is the metric that determines whether your unit economics are real or whether they're a cohort artifact. If you're growing fast but haven't held a full cohort of customers through 24 months, you don't yet know whether the product's value holds over time.
Raising a large round before that answer is clear is a specific mistake. You lock in a valuation and an investor expectation set against a thesis that might need significant revision. Operator founders who wait for the 24-month cohort data to look right before raising their Series A tend to raise at better terms and with better strategic clarity about where the capital goes.
Forgetting what made the first version work
There's a version of year three where the company starts trying to become a different kind of company — more enterprise, more horizontal, more platform. The founder spends time reading about SaaS best practices and starts applying frameworks designed for different types of businesses.
What made the company work in years one and two was specific: deep domain knowledge, direct customer relationships, and a product decision process that ran on the founder's own operational experience. Those things can scale, but they don't scale automatically. They require intentional preservation as the company grows.
If you're in year three and the company feels like it's drifting from what made it work originally, the question is usually not "what do we need to add" — it's "what did we stop doing." Go back to the founding thesis. Find the five customers who loved the product most in year one. Have real conversations with them about what's changed. The answer to year three is usually inside that conversation, not in the next fundraise or the next product bet.
Alder works with operator founders at every stage. If you're in year three and figuring out what comes next, we'd like to talk.