The Founder in the Corp: How Entrepreneurial Thinking Survives Inside a Software Company

There's a moment, and if you've ever built something from scratch and then stepped into a corporate role you'll know exactly the one I mean, where you're sitting in a meeting, watching a problem get discussed to death, and something inside you quietly screams: I could have built the solution by now.

That's the founder's curse. And also, as it turns out, the founder's superpower.

I've spent the better part of my career straddling two worlds: the scrappy, high-stakes world of entrepreneurship and the structured, process-driven world of corporate software. What I've learned is that the entrepreneurial mindset doesn't have to die when you join a company. It just needs to find a different expression. And at some point, you stop trying to suppress it entirely.

The Founder's Curse (and Gift)

Entrepreneurial thinking isn't really about owning a business. It's a cognitive style: a pattern of seeing problems before others do, feeling a compulsion to solve them, and having a frustratingly low tolerance for the gap between 'identified' and 'fixed'.

In a startup or a business you've built yourself, this wiring is celebrated. In a corporate environment, it can feel like a liability. You spot inefficiencies that nobody else seems bothered by. You want to move faster than the process allows. You find yourself mentally solving problems in meetings that are still at the agenda item one stage.

But here's the reframe: organisations don't suffer from too many people like this. They suffer from too few. The founder mindset, curiosity, bias to action, pattern recognition, and a refusal to accept 'that's just how it's done' as an answer, is genuinely rare inside most corporate structures. That's not a reason to suppress it. It's a reason to direct it.

My Two Worlds

I co-founded and scaled a home services business from a £5k investment to £15M turnover, before exiting in 2023. That journey taught me everything the classroom never could: how to make fast decisions with incomplete information, how to build teams that move with urgency, and most importantly, how to turn an idea into something real without asking permission.

Stepping into a corporate tech leadership role after that was a genuine psychological adjustment. Early on I needed some data to progress a piece of work. In a previous life I'd have had it on my desk within the hour. Instead I made the request, waited, chased, waited again, and eventually just went and found it myself. No drama. Nobody's fault. Just a completely different operating rhythm to the one I was wired for.

That moment taught me something useful: the instinct to just go and sort it isn't arrogance. It's just how I'm built. The adjustment isn't to kill that instinct. It's to know when to use it and when to let the process work.

No Fear, No Permission, No Problem

If I had to name the single trait that has made the biggest difference in how I operate, it's this: I'm not afraid to try things.

Not recklessly. Not without judgement. But I have a naturally low threshold for experimentation, and I'm comfortable being technically curious in public. Most people in corporate environments ask 'is this allowed?' or 'who do I need sign-off from?' I tend to ask 'why wouldn't I just try this?'

The approach I've settled into looks something like this: identify a real problem, go and explore it quietly, build something that proves the concept, then bring people along once there's something tangible to show. Prove it first. Pitch it never.

Demonstrated value is the ultimate permission slip. You don't need authorisation to be curious. You need results to earn trust.

This approach has shaped everything I've built in my current role. Rather than writing business cases or sitting in alignment meetings, I built functional prototypes. I showed, rather than told. And once there was something real to demonstrate, the conversation changed entirely.

Finding the Outlet: Build Inside the Machine

The entrepreneurial energy doesn't disappear in a corporate role. It needs a channel. For me, that channel has been building AI-powered tools that solve genuine operational problems, things that create real, measurable value for the business and the people inside it.

The one I'm most proud of right now is an Auto Triage engine that classifies incoming support tickets and routes them without human intervention. It's running at 99.8% accuracy in production. That result didn't come from a project plan or a committee. It came from the same curiosity and bias toward proof over theory that built a £15M business from a £5k starting point. The tools are different. The wiring is the same.

The satisfaction of watching something you built go from an idea to a live system, one that colleagues are actually using, that customers are actually benefiting from, is no different whether you're a founder or an employee. The same spark. The same sense of having made something from nothing.

The Show and Tell That Actually Works

Here's the part nobody really talks about: the show and tell isn't just a presentation. It's a leadership act.

When you've proved something works, you have two audiences. The first is your team, the people who work with you directly. Bringing them along on the journey, showing them what's possible, and inviting them into the process doesn't just build enthusiasm. It builds capability and belief. It shows them that the space between 'idea' and 'done' is smaller than they thought.

The second audience is your peers and senior leadership. And this is where demonstrated value does something that a pitch deck never can: it changes the conversation from 'should we do this?' to 'how do we scale this?' You're no longer selling an idea. You're presenting evidence.

Influence without authority is one of the hardest things to build in a large organisation. The most reliable way I've found to do it is to make the work speak first.

The Rules of Survival

If you're a founder-minded person inside a corporate structure, here's what I've learned the hard way.

• Pick your battles. Not everything needs disrupting. Save your energy for the things that genuinely move the needle.
• Build allies, not audiences. The loudest voice in the room rarely has the most influence. Find the people who get it and bring them along early.
• Deliver first, challenge second. Credibility opens doors that ideas alone never will. Be the person who ships, and the room starts listening differently.
• Find the white space. Every organisation has problems nobody owns yet. That's not a gap. That's your invitation.
• Stay curious without asking permission. Curiosity is free. Experimentation is cheap. Fear of looking foolish is the only real cost, and it's one you can choose not to pay.

The Corps Need Us. Now More Than Ever.

Large organisations aren't the enemy of the entrepreneurial mindset. They're arguably where it's needed most, and right now the stakes have never been higher.

AI is not coming for SaaS businesses. It's already here. Across every sector, software companies that have spent decades building moats around their functionality are watching those moats fill in, as general-purpose AI tools start doing in seconds what once required a specialist platform. The disruption is real, it's accelerating, and no vertical is immune.

But here's the counterintuitive truth: vertical SaaS businesses, the ones deeply embedded in a specific industry with years of domain knowledge, proprietary data, and trusted customer relationships, are actually extraordinarily well-placed to win this moment. Not despite their focus, but because of it.

General AI is broad. Vertical AI is precise. A horizontal tool can summarise a support ticket. A vertically-trained AI engine, built on years of domain-specific data and workflows, can triage it, resolve it, and learn from it in the context of an industry it actually understands. That's not a feature difference. That's a strategic moat that deepens over time.

The companies that will emerge from this AI disruption stronger are the ones that move now. Not with a twelve-month AI transformation programme, but with curious people who spot the easy wins, prove them fast, and create momentum that others can follow. The first proof of concept changes the conversation. The first result changes the culture.

The Honest Ending

I used to think the goal was to find a way to operate differently inside a corporate structure. To slow down, follow the process, be more patient. I've stopped trying.

Not because I'm incapable of it. But because I've realised the restlessness isn't a flaw to manage. It's the thing that produces the results. The 99.8% accuracy engine. The tools that went from idea to production in weeks. The conversations that shifted from "should we explore AI?" to "how do we scale what we've already built?"

I can't operate any other way. And at some point, I stopped pretending I could. If you're reading this and you recognise that feeling, I'd suggest you do the same.