To innovate at scale, Harness treats each new product as a semi-independent entity. These "startups" have a founder-like PM, go through internal seed/Series A funding stages tied to revenue milestones (e.g., $1M ARR), and are responsible for their own initial founder-led sales.

Related Insights

During a transformation from services to product, identify and commercialize the reusable tools that services teams have already built to support clients. Instead of starting from scratch, productizing these existing "mini-products" aligns them with the broader product strategy, saves development time, and leverages proven solutions.

Project-based companies operate on a cash flow mindset, accepting any custom work that brings in immediate revenue. A true product company uses an investment mindset, strategically saying 'no' to short-term revenue to invest in building a scalable asset that can win a market long-term.

Resist hiring quickly after finding traction. Instead, 'hire painfully slowly' and assemble an initial 'MVP Crew' — a small, self-sufficient team with all skills needed to build, market, and sell the product end-to-end. This establishes a core DNA of speed and execution before scaling.

In a multi-product company, horizontal teams naturally prioritize mature, high-impact businesses. Structuring teams vertically with P&L ownership for each product, even nascent ones, ensures dedicated focus and accountability, preventing smaller initiatives from being starved of resources.

Don't expect the parent company's sales force to sell your nascent product. Their focus on core business means they will ignore emerging tech. An internal incubator must have its own dedicated go-to-market team to find new personas and develop sales plays before a handoff.

To launch new products and compete with agile startups, embed a small "incubation seller" team directly within the technology organization. This model ensures tight alignment between product, engineering, and the first revenue-generating efforts, mirroring the cross-functional approach of an early-stage company.

Stripe's Experimental Projects Team discovered that embedding its members directly within existing product and infrastructure teams leads to higher success rates. These "embedded projects" are more likely to reach escape velocity and be successfully adopted by the business, contrasting with the common model of an isolated R&D or innovation lab.

The AMP team is small and agile, bypassing traditional processes like code reviews to ship 15 times a day. They leverage Sourcegraph's customer trust, revenue, and platform teams (e.g., security), allowing the core team to focus purely on product velocity and radical innovation.

An internal incubator’s biggest mistake is acting like an external startup. Finding product-market fit is insufficient. Lasting success requires achieving "product-company fit" by deeply understanding and aligning with the parent company's internal business units, strategic goals, and unique challenges.

Contrary to typical platform strategy, Harness sells its modules separately. This prevents weak products from hiding inside a bundle and creates intense internal accountability. It forces each team to compete and win on its own merits, ensuring customers only buy what delivers real value.