S8 Bonus: Stop Reinventing the Wheel: Dropping Full-Stack Collaboration Building Blocks Into Any App with Rickard Hansson, Founder & CEO of Weavy

Episode Summary

Executive Summary: Ricard Hansen describes Weavey’s pivot from an all-in-one collaboration product to developer-focused embeddable building blocks. The company learned that collaboration is best sold as a feature inside existing apps, not as a standalone app. Since 2019, Weavey has prioritized developer experience, scalability, and a small, high-trust team while working to educate the market and shift from older licensing models to modern usage-based SaaS.

Main Topics: Origin and pivot from Incentive to Weavey: The company began as Incentive, a collaboration platform, but pivoted in 2019 after realizing customers responded better to embedded collaboration features added on top of existing products. Developer-first product strategy: Weavey shifted from optimizing only end-user experience to making the product easy for developers to consume, with better authentication, APIs, tokens, webhooks, UI kits, and documentation. MVP creation and early customer validation: The MVP reused prior product components and was converted into an embeddable experience, allowing the team to launch in about six months and win an early customer late in 2019. Roadmap and technical maturity: The roadmap focused on behind-the-scenes architecture improvements for almost two years while the original product kept running, using customer feedback and Shape Up-style processes to refine developer experience. Team culture and hiring philosophy: Ricard emphasizes long-term trusted collaborators, small engineering teams, human-centered hiring, and culture built on openness, individuality, and psychological safety. Scalability and go-to-market challenges: Weavey was built to scale technically and commercially from day one, but the main challenge is awareness: getting developers to find and understand why they need embedded collaboration features. Leadership lessons, mistakes, and future vision: Ricard reflects on pricing mistakes, the need to adapt faster, and the goal of making Weavey a verb in product teams everywhere while staying a nimble company.

Key Arguments: Collaboration should be treated as a feature inside existing software, not as a standalone app, because users want contextual productivity within the tools they already use. The best product opportunities often come from adding value to an existing ecosystem rather than selling a broad all-in-one platform. A strong end-user experience is not enough; developer experience must be equally strong or better if the product is meant to scale. Roadmap decisions should prioritize the hardest-to-spot but most important layer: consumption, integration, and infrastructure, even if it is invisible to end users. Small engineering teams can build better products than large ones when the goal is quality and nimbleness rather than brute-force output. Hiring should prioritize good people over merely talented people, because talent can be trained but character and collaboration are harder to change. The company’s biggest commercial challenge is market education and discoverability, not technical scalability. Fixed/perpetual licensing was the wrong business model for this category; customers expected subscription-based pricing.

Data Points: Founded/pivot year: 2019 - The hard pivot from Incentive to Weavey happened in 2019. Time to build first version: about 6 months - Ricard says the first version of the embeddable experience took roughly six months to create. Early customer date: late 2019 - Weavey landed its first real customer, Tioco, in late 2019. First customer company size: 300 mil software company - Tioco was described as a software company selling telecom billing systems. Team tenure: 15+ years - Ricard says the core engineering team has been with him for almost 15 years or more. Industry experience: 25+ years - He notes he has been hiring and working with people for more than 25 years. Founder age: 48 - Ricard states his age while discussing his background and experience. Future goal horizon: 4 or 5 years - He wants Weavey to become a natural verb in product teams within four to five years.

Pivotal Quotes: "collaboration is not an app, collaboration is a feature." — Ricard Hansen: He explains the core thesis that drove the company’s pivot and product strategy. "Weavey should be a verb within any product team in four or five years." — Ricard Hansen: He describes the long-term vision for product adoption and category ownership. "I rather have happy to be wrong, but I want to be proven that I'm wrong." — Ricard Hansen: He frames his decision-making style and openness to adapting after mistakes.

Implications: The episode suggests embedded features and developer experience are becoming the competitive moat in SaaS. Companies that make integration simple, visible, and scalable can win by fitting into existing workflows rather than replacing them.