The 3 Startups You'll Find in Large Companies

Three times in my career I have helped build something new inside a company much larger than the team building it. Samsung Ads inside Samsung. SalesforceIQ inside Salesforce. Salesforce Essentials inside Salesforce again. Each time the work looked like a startup from the inside and looked like a feature from the outside. Each time the same forces showed up. Each time the work taught me something specific about how to lead at the seam where a small team is trying to build a real business inside a much larger one.

This is not a celebration of intrapreneurship. It is a description of the pattern.

The three anchors

Samsung Ads. Zero-to-one new business inside a global hardware company. Samsung had massive smart TV reach and no ad business. I co-founded the initiative as part of a four-person team and led design and front-end engineering. We built the advertiser platform, the data visualization layer, the standards posture, and the team itself. In its first year the business generated $20M in profit. We filed a patent for AI-powered visualization of global TV viewership behavior and contributed to IAB standards for smart TV advertising. This was building a category, not a feature.

SalesforceIQ. An acquired AI-assisted CRM absorbed into Salesforce and re-shipped. The back-end was ahead of the front-end. Users could not trust or act on the intelligence the product surfaced. I redesigned the Contact Gallery, introduced a master contact model and multi-merge capability, and consulted on early UX foundations for what became Einstein. The Contact Gallery redesign increased daily active users by 40% and duplicates merged by 34%. Different startup, different stage: a product that already existed had to find its place inside a platform that already existed.

Salesforce Essentials. SMB packaging inside an enterprise platform. Salesforce was too complex for small businesses to adopt. Essentials was the answer. A focused entry point for teams of ten or fewer that preserved a path into the broader ecosystem. The work was figuring out which Einstein capabilities belonged in Essentials, how onboarding should actually work, and how to align customer learning experiences across the company. A startup again, this time defined by what to take out, not what to add.

What is the same across all three

The work is real. The container is borrowed.

A few patterns showed up every time.

Oxygen is the scarce resource. Not money. Not headcount. Oxygen. Executive attention, calendar time, a clear lane that other teams cannot drift into. Inside a large company there are always teams that have been there longer, have more relationships, and want the surface you are trying to build on. You spend a non-trivial part of your week defending the existence of the work, not doing the work.

Credibility is earned in the first month, not the first quarter. The team you are inside of has already decided whether you can build. Show up, close a known problem fast, and the rest of the work gets easier. At SalesforceIQ that meant resolving three long-standing customer issues in the first month before touching the Contact Gallery redesign. At Samsung Ads it meant shipping the early platform at production quality even when the temptation was to ship rough and polish later. License is earned by shipping, not by framing.

You are accountable to two different customers at once. The external customer, who has to find value. The internal customer, who has to find a reason to keep funding the work. The product has to land with both. A startup outside the building only has the first one. A team inside the building forgets about the second one at its peril.

You move between levels constantly. A specific UI pattern in the morning. A product principle by lunch. A standards conversation in the afternoon. A staffing decision before you log off. The luxury of one altitude at a time does not exist inside an internal startup. The job is to be coherent across all of them.

You inherit constraints you did not pick. A brand. A platform. A sales channel. A reporting line. Some of these constraints are gifts. Some of them are taxes. The work is figuring out which is which fast, then designing inside the gifts and around the taxes without complaining about either.

What is different from a clean startup

A startup outside the building decides what to build. A startup inside the building decides what to build and what to defend.

You do not get to pick the cap table. Your investors are your executives, and they are also your competitors for attention with other internal teams. You cannot fire them. You cannot dilute them. The political layer is not a distraction from the work; it is part of the work.

The exit is not an exit. A clean startup is built to be acquired or to go public. An internal startup is built to be absorbed, integrated, or quietly wound down. The endgame is integration into the parent, and the integration almost always changes the product. If you do not design for that future you will get a worse version of it imposed on you.

Speed is bounded by the slowest dependency you cannot replace. Legal. Security. Brand. Procurement. A clean startup can route around almost any internal bottleneck by hiring or by changing tools. An internal startup has to negotiate with the existing organism. The leadership skill is knowing which fights are worth picking, which are worth losing on purpose, and which are worth routing around without making it personal.

You do not get to pretend the parent does not exist. Samsung Ads had to fit into Samsung TV. SalesforceIQ had to fit into the Salesforce platform. Essentials had to fit into the enterprise pricing and packaging story. The pretend-we-are-a-startup posture works for about a quarter, and then the parent shows up. Designing for the eventual handshake from day one is cheaper than retrofitting it.

Talent dynamics are inverted. A clean startup hires people who want autonomy and equity. An internal startup hires people who want autonomy without leaving a stable company, which is a smaller pool and a more specific personality. You spend more time finding the right small group of people than you would in either pure context.

What this builds in a leader

A leader who has built three startups inside large companies has learned how to make new things happen inside organizations that are not naturally built for new things. That is not a generalist skill. It is a specific one. It looks like:

• Building credibility with skeptical executive sponsors quickly, without performing certainty you do not have.
• Holding a quality bar at startup speed, because trust inside the parent and trust from the customer are won by the same thing: work that looks like it knows what it is doing.
• Designing for the eventual handshake with the parent organization from day one, so the integration is something the team shaped rather than something done to it.
• Moving fluidly between a UI decision, a packaging decision, a standards decision, and a staffing decision in the same week.
• Knowing the difference between a constraint and a gift, and not wasting energy fighting the wrong one.

This is the skill that makes a senior design and product leader useful in an inflection-point company. The kind of company past pure-startup but not yet a steady-state machine. A company with a real business and a new bet inside it. A company that needs someone who has done this before, can read the room, and can ship the work.

Close

I did not set out to build a career of internal startups. The pattern accumulated. Looking back, the through-line is clear: I am most useful at the seam where a small team is trying to build something real inside a much larger thing, and where design, product, business, and politics all have to be held in the same hand. Three times now I have done that work and watched what it produced. The fourth time, whenever it shows up, will look like the same job in a new container.