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.
Related Insights
Instead of guarding prototypes, build a library of high-fidelity, interactive demos and give sales and customer success teams free reign to show them to customers. This democratizes the feedback process, accelerates validation, and eliminates the engineering burden of creating one-off sales demos.
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.
Engineering often defaults to a 'project mindset,' focusing on churning out features and measuring velocity. True alignment with product requires a 'product mindset,' which prioritizes understanding the customer and tracking the value being delivered, not just the output.
To keep growth aligned with product, foster a shared culture where everyone loves the product and customer. This isn't about formal meetings, but a baseline agreement that makes collaboration inherent. When this culture exists, the product team actively seeks marketing's input, creating a unified engine.
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.
The V0 team operates with minimal product management oversight, empowering product-minded engineers (often ex-founders) to make 95% of product decisions directly. This sacrifices potentially "perfect" choices for a dramatic increase in development velocity.
Don't force your sales team to learn and sell a completely new product. Instead, integrate the new capability into an existing, successful product, making it "first" or "default" for that channel. This reduces sales friction and complexity, leveraging established momentum for adoption.
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.
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.
