In one sentence
Muse produced an unusually strong product, team, and community, but those strengths could not compensate for weak distribution, an unfocused market, platform constraints, and a prosumer business model too small to support the team. Wiggins’s central lesson is that craft and integrity are valuable but do not replace market focus, business-model fit, and durable customer need.
Overview
Muse began as Ink & Switch research into tablets, styluses, infinite canvases, and digital tools for early-stage thinking. After becoming a company in 2019, the team simplified the product, experimented with messaging, and found traction by positioning Muse as a “tool for thought.” A successful 2020 launch, Apple featuring, short demo videos, and the Metamuse podcast created momentum; 2021 became the company’s high point.
The business nevertheless remained dependent on a narrow Apple-centered audience and a difficult-to-explain product. Users loved Muse, but growth was insufficient. In early 2022 active users and other metrics sharply declined. Wiggins attributes this partly to the macroeconomic downturn and partly to the limited durability of aspirational productivity software: enthusiasm may attract early adopters, but long-term viability requires a deeply embedded, hard-to-replace use case.
Muse 2.0 doubled ARR from roughly $60,000 to $120,000, but that was still inadequate for a seven-person company. The team pivoted toward collaborative B2B software, finding real interest among remote teams. Adoption failed because non-champion teammates resisted learning the tool, the champion bore the support burden, and Muse lacked web, Windows, integrations, permissions, and multi-workspace features. The company ended the team venture in 2023 and transferred the product to engineer Adam Wulf as a smaller indie business, preserving customer continuity.
Core ideas
A research prototype is not yet a product
Lab experiments can validate delight without validating learnability. Muse’s early stylus gestures and unconventional interactions worked in demonstrations but confused new users. Productization required moving closer to familiar platform conventions.
Novel categories create a messaging tax
Muse addressed an important but poorly named activity: unstructured ideation before writing, designing, or planning. “Thinking canvas” was accurate but ineffective as marketing language. A category label such as “tool for thought” helped, but it also connected Muse to a category increasingly associated with backlink-heavy outliners rather than canvases.
General-purpose flexibility can become strategic vagueness
Muse served writers, lawyers, doctors, designers, investors, and others, but never chose a dominant segment or narrow use case. This broadened the product’s appeal while making positioning, feature prioritization, and distribution harder. Wiggins recognizes the tradeoff but is unsure how he would have resolved it.
Distribution came from explanation and demonstration
The strongest channels were unusually well matched to the product: physical-camera demo videos showed the hands and stylus; podcasts conveyed the philosophy that screenshots could not; Apple features and video reviews made the product legible through motion. No single channel was durable—growth arrived as a series of temporary unlocks.
A devoted user base is not the same as a sustainable market
Muse had highly engaged customers and strong conversion among early users, but too few of them. The product became indispensable to a few thousand people, while prosumer economics required tens or hundreds of thousands. Product love is evidence of value, not proof of scale.
Business-model pivots do not erase product-market constraints
The B2B pivot was logical: collaborative ideation appeared valuable, and Muse already possessed sophisticated sync technology. But enterprise adoption introduced new requirements—cross-platform access, integrations, permissions, workspaces, and low-friction onboarding—that a seven-person team could not deliver.
Capital efficiency has an opportunity cost
The small-giants model protected autonomy, craft, and quality of life, but limited the ability to build the platform breadth required for B2B. Wiggins does not conclude that raising $5–10 million would have worked; he treats it as an unresolved counterfactual with its own risks.
Graceful endings are part of product stewardship
Rather than spend down to zero and abandon users, the team planned for continuity and transferred Muse to a former teammate. The ending preserved more value than a conventional shutdown and reflected the company’s interest in software longevity.
Practical takeaways
- Test learnability, not merely delight, when introducing a new interaction model or document type.
- Treat positioning as an empirical problem: generate many explanations and test them rather than searching for one perfect phrase by intuition.
- Choose a market wedge early enough to guide product development, even if the long-term product remains broad.
- Map each acquisition channel to the product’s explanatory needs. Products that are hard to explain may benefit disproportionately from video, live demonstration, or long-form conversation.
- Separate signals of enthusiasm—social engagement, praise, podcast listeners, launch spikes—from evidence of durable retention, willingness to pay, and scalable acquisition.
- Before a B2B pivot, identify the non-champion user’s adoption experience. A product that depends on one internal enthusiast to train and support everyone else has a serious deployment risk.
- Build a web-accessible or shareable surface early when virality, collaboration, or cross-platform adoption matters, even if native apps remain the core experience.
- Review whether principled choices are actually user-serving or merely disadvantage the business. Muse’s reluctance to request ratings depressed its App Store rating until a standard prompt rapidly improved it.
Caveats and counterpoints
- This is Wiggins’s retrospective and therefore an informed but single-person account, not an independent postmortem with full financial, cohort, or competitor data.
- The macroeconomic explanation for the 2022 decline is explicitly speculative; Wiggins says he still cannot fully explain the abrupt drop in active users.
- The article may understate alternative explanations such as delayed Muse 2.0 delivery, onboarding friction, platform limitations, or changing interest in the “tools for thought” category.
- The recommendation to focus narrowly conflicts with a genuine strength of Muse: combining many media types and knowledge tasks on one canvas. Focus may have improved business outcomes while reducing the product’s distinctive breadth.
- Claims about how much funding would have been required for B2B feature completeness are estimates, not a demonstrated causal threshold.
Questions worth revisiting
- When does a broad creative tool have enough evidence to justify choosing a vertical or narrow use case?
- Could Muse have preserved its general-purpose canvas while marketing separate workflows for distinct customer segments?
- What retention, expansion, or usage metrics would have distinguished temporary enthusiasm from durable product dependence earlier?
- Would a simple web viewer or share-to-web feature have materially changed acquisition and collaboration, or merely exposed the product to more low-intent users?
- Was the B2B opportunity genuinely weak, or was it primarily mismatched to Muse’s available resources and timing?
- How should a small software company balance capital efficiency against the platform breadth customers increasingly expect?
Return to this when…
Return to this note when evaluating a beautifully crafted product with enthusiastic users but uncertain scale; considering a broad “tool for thought” or creative-software idea; deciding between prosumer and B2B models; choosing a distribution strategy for a difficult-to-explain product; or planning a responsible shutdown or handoff.