Big-company ideas, one-person company
Product consultant & builder
I spent ten years inside a large industrial company, managing product portfolios that averaged over €100M a year. Then I became a company of one. The surprise: most of the big-company machinery scales down beautifully. The parts everyone complains about — committees, sign-off chains, meetings about meetings — turn out to be costs of headcount, and the useful ideas underneath survive the shrinking.
Here is what I kept, what it looks like at one-person scale, and the one thing that refuses to scale down.
Portfolio thinking, scaled down
At Atlas Copco, portfolio strategy meant deciding where investment goes across product lines: which line gets pushed, which gets held, which gets wound down, and being honest about the difference. I run the same review across my five products. Toogi gets active investment because it serves a real paying audience. Moo-ving is held. North For Nomad taught its lesson and idles. The discipline is identical — allocate deliberately, revisit on a rhythm, and say the quiet part in writing.
The one-person version has an advantage the corporate version lacks: zero politics. A big company holds dying products alive because someone’s title depends on them. A company of one kills a product in an afternoon and reallocates the week.
A platform team of one
Big companies run platform teams so product teams inherit shared infrastructure — analytics, auth, compliance — from a single proven implementation. My fleet works the same way. The build logs show improvement waves: analytics rolled across every product in one sitting on March 8, consent handling on March 15, SEO hardening across five repos on April 8. Prove the pattern once, roll it everywhere.
This was the machinery agents made affordable. The first implementation carries all the cost; the rollout costs about a code review per product. A platform team used to need ten engineers. Mine is a pattern library, a set of agents, and a habit.
Ops reviews, with yourself
The other big-company ritual worth keeping is the operations review: a fixed rhythm where the numbers get looked at whether things feel fine or they feel busy. Every product in my fleet ships with the same measurement setup — funnel events, revenue tracking, public report pages — so the review is cheap and the data is already there.
The discipline matters more alone, because there is nobody to catch what you skip. A founder who checks numbers only when worried is running on vibes with a dashboard for decoration. The fixed rhythm is the point: the calendar owns the review, and feelings get overruled by charts.
What refuses to scale down
One big-company asset has no one-person equivalent: institutional distribution. Atlas Copco could put a new compressor in front of every existing customer through a sales force that took decades to build. A company of one starts every product at zero reach, which is exactly why audience-building has become the core discipline for small companies — the subject of its own piece here.
Everything else made the trip: portfolio allocation, platform leverage, operating rhythm, honest kill decisions. Big companies are bad at speed and good at systems. A company of one is the reverse by default. Borrow their systems, keep your speed, and you get an unfair share of both.
The takeaway
The useful machinery of a large product organisation — portfolio allocation, platform teams, ops rhythms — scales down to one person, and agents pay for it. Institutional distribution is the exception, and audience-building is its one-person replacement. Borrow the systems, keep the speed.
My time is for hire.
Two ways to work with me: a full project build, where I design, build, and ship your product with these methods, or consulting inside your team.
Keep reading
Sprints are dead for prototyping
A working prototype is now quicker to build than the meeting to discuss it. That kills the sprint as a prototyping tool, and it changes how product decisions get made.
The MVP is the easy part now
I have shipped five MVPs since February. Building them was the quick bit. Technology stopped being a moat, users are settling into fewer apps, and audience is the asset that decides who wins.