Intrapreneurship

New businesses die in fairly predictable places inside a large company. Not for lack of ideas, but because the machinery that keeps the existing business running cleanly turns poisonous around a new one. Requiring approval for every expense is a reasonable way to prevent waste, and it's a two-week wall in front of a team that doesn't yet know what it needs.

When someone at Pagedeck proposed looking into workflow automation, the wall showed up all at once. Mia and Theo took it on, and three things held them down. Wiring up a single external tool meant waiting for the executive meeting that convened once a month. A revenue target was attached from the first quarter, so they had to set a price before knowing whether anyone would buy at all. And whenever the main product broke, Theo was the first person pulled back. Six months produced one deck. The following year a similar product shipped from another company.

Intrapreneurship is what's left when those three are removed. The company's assets — its existing customers, its name, its cash — stay available, and only the way of working gets detached and moved closer to a startup's. It separates starting a new business from building the conditions under which one can be started.

A small team gets money and authority carved out in advance, some of the head office's approval steps waived, and a stretch of time where it will be judged on something other than revenue.

1. The team and the clock. Three to seven people, dedicated, for six months to a year. Dedicated has to hold on the calendar and not just in a document. A team whose members are listed on the new effort while spending four days a week on incidents in the main product is not a team.
2. The budget. A year's amount is fixed up front and handed over whole, with no line-by-line approvals inside it. Given $150,000, the team decides where it goes. What does the work isn't the size of the number but the fact that it was settled in advance.
3. Decision rights. What to build, what to charge, and who to sell to first belong to the team. The obligations that come with using the company's name — legal and security standards — still apply. Leave that boundary unwritten and it gets negotiated case by case, and enough negotiations put the speed back where it started.
4. What gets measured. The quarterly question is what the team learned, not what it earned. It's the same rule the third column gets in three horizons, the framework that splits a business into current, growth and exploratory and manages each differently. How many people saw the minimum viable product (MVP) — the smallest build that can test a hypothesis — and how many of them said they'd pay are the numbers that belong here.
5. The stopping condition. Write down what ends it at the same time you start it: no twenty paying customers within a year, for instance, and the effort closes. One more line goes with it — a guarantee that people return to their old role or an equivalent one when it closes. Without it, the people the company would most want don't volunteer.

The term comes up most in companies whose core business has started to flatten while cash is still on hand. Without money there's nothing to run, and while growth is steep there's no reason to bring it up.

The first place is the resource allocation meeting, where how much headcount and budget goes where gets decided. The size of the exploratory share and the shape it will be run in get settled together. Carve out the share but run it inside the existing organization and all three walls come straight back.

The second is anywhere long-odds work is on the table. A moonshot — an attempt that usually fails but changes the board if it lands — doesn't survive inside a team's quarterly goals. Hand low-probability work to a team measured on goal attainment and that work is the first thing to slip.

The third is about people. It's also a way to give someone who could go and found a company a reason to stay. Some companies attach a share of the upside as equity or separate compensation. Without that, the company carries the risk and keeps the return, which thins out the reason to do it inside rather than outside.

"Let's run this as intrapreneurship. Under the current approval structure we won't ship anything in six months."

Stating that without a waiver from the process, there will be no result.

"If you call it intrapreneurship and still file for approval on every expense, it's just a new business team."

Pointing out that only the label changed and the way of working didn't.

"If it gets shut down after a year, can I go back to my old team?"

Checking where you land on failure before deciding whether to sign up.

Pagedeck changed its approach after the deck. Grace pulled four people out full time for a year, handed over the budget whole, and stopped asking about revenue in the quarterly review. The question instead was how many teams they had talked to that quarter and how many of those wanted to try it first.

In the second quarterly review the team dropped its original direction. Rather than building automation outright, it narrowed to a small feature that finds repetitive work inside documents already in Pagedeck. With a revenue target attached, changing direction would have registered as a miss.

The most common mistake is thinking the label does the work. Stand up a separate team, call it intrapreneurship, and the shape is there, so it feels done. But if even one of the three — budget, decision rights, what gets measured — keeps following head office rules, the other two stop with it. A team still carrying a revenue target can't sit on an unproven hypothesis, so it turns toward whatever can sell this quarter, and what comes out is indistinguishable from a small extension of the existing product.

Assuming it's easier than founding a company outside is the other one. Money and customers being available already is a genuine advantage. What's different is that there are difficulties outside companies don't have. The team competes with other teams for people and budget, and if the new product looks like it will eat the existing product's revenue, the objections come from inside. That's why the waivers get written down at the start. Autonomy that exists only as a verbal promise is the first thing reclaimed in the quarter the core business gets hard.