Overview. Figma is a browser-native, multiplayer design editor targeting product designers at seed-to-Series-A SaaS companies, built on the thesis that screen design is a collaborative activity and the dominant tool — Sketch — has locked the entire workflow to a single OS, single user, and async-by-default coordination model. The solution is a custom WebGL rendering engine that lets two designers edit simultaneously while developers and stakeholders open the same file in any browser, license-free. The GTM question this report addresses is whether that rendering performance bet pays off convincingly enough in a 12–18 month window to establish paid team adoption before Adobe ships a collaboration feature into its ~12-million-seat Creative Cloud install base.

Key findings.

• Market sizing (§3): TAM estimated at $200–300M globally (bottom-up — no primary 2015 industry report sizes this segment; treat as calibration, not measurement); SAM $4–12M among design-forward US/UK tech companies, 10–500 employees; SOM reaches $12M ARR by Year 3 in the base case, contingent on browser-performance skepticism clearing in the community before that window closes. The SAM is small — the thesis is market expansion through new seat types, not share capture from an existing market.
• Competitive white space (§5): The top-right quadrant — browser-native delivery combined with full vector design creation — contains no shipped product in December 2015. Sketch dominates design creation but is Mac-only and single-player; InVision and Marvel operate browser-natively but cannot create designs. Adobe's Project Comet (XD), announced October 2015, is targeting the native-app quadrant and has no public build. The white space is real; the question is whether it is unoccupied or technically infeasible — and Figma's WebGL renderer is the only answer.
• Channel (§6): The right primary motion is hand-to-hand Dribbble and Twitter seeding — 30 personalized cold emails, not a public launch. Multiplayer is not yet in the product, making 1:1 demos the only context where a vision pitch survives a skeptical technical audience. The same tight SF design community that enables near-zero CAC acquisition is also the highest-risk reputational surface: one negative post from a high-follower designer after a poor performance demo can anchor the "Google Docs of design" perception for 12–18 months.
• Pricing and unit economics (§7): Free → $15/editor/month Professional → Enterprise custom. Positioned as cost-neutral against the combined Sketch ($99/yr) + InVision Pro ($25/mo) stack, at approximately $33/month per designer today. Free view-only access for developers and stakeholders is both the viral mechanism and the core differentiator over InVision. Base-case unit economics: LTV:CAC ~2.0×, 17-month payback — viable for a PLG motion, fragile against two specific failure modes: monthly churn doubling to 6% (performance doesn't retain professionals) or free-to-paid conversion falling below 2.5% (free tier becomes permanent parking). WTP is triangulated from adjacent tool pricing, not a primary survey.
• Existential risks (§8): Three are High×High or structurally equivalent: the WebGL renderer failing the professional performance bar; collaboration pain not being acute enough to drive active switching rather than passive interest; and Adobe shipping co-editing into XD before Figma has 500 paying teams. All three are live and unresolved. They are entangled — a renderer that "mostly works" won't displace Sketch at 60–70% mindshare, and a fast renderer without an acute switching trigger produces waitlists that never convert.

Overall verdict. Conditional Go — proceed if (1) the WebGL renderer clears the 55fps Mac / 45fps Windows benchmark by Day 14, and (2) ≥20 of 30 structured pain-acuity interviews rate Sketch workflow friction as a daily blocker (4+/5 on ≥2 of three dimensions) by Day 28. Both conditions must hold simultaneously; one without the other does not clear the thesis. If either fails, the unit economics and the bottoms-up acquisition model need rebuilding before any public launch spend.

Expert confidence rating. Medium — TAM/SAM/SOM are entirely bottom-up constructions with no primary 2015 industry data; WTP is inferred from competitor pricing, not surveyed; conversion rate and CAC assumptions are extrapolated from adjacent PLG tools (Slack, InVision) with zero Figma-specific evidence. The competitive and channel analyses draw on primary sources but are applied to a product without public users. The directional logic is sound; every number is a hypothesis pending the 90-day validation program.

Top 3 recommended actions.

1. Build a standardized 500-layer benchmark test file and document a pass/fail result against defined frame-time thresholds (≥55fps Mac, ≥45fps Windows in Chrome) by Day 14 — no community demos until this clears. It is the kill-criterion gate for every downstream GTM action; discovering the performance gap via a negative influencer post is the one failure mode with no recovery path.
2. Map Dribbble and Design Twitter to identify 50 product designers with documented Sketch workflow pain, send 30 personalized cold emails by Day 14, and schedule ≥10 structured 30-minute pain interviews before Day 30 — these calls simultaneously advance the collaboration-pain validation quota required before public launch and seed the private beta cohort from which the influencer tracking pool is drawn.
3. Lock .sketch file import to P0 in the current sprint with a defined fidelity acceptance test (≥90% fidelity on a multi-artboard file with shared symbols) — every designer from the outreach cohort will ask about migration in the first two minutes of a call, and "we're working on it" ends the evaluation before the product has a chance to demonstrate anything.

---

Market definition: Professional software tools used by digital product and UI/UX designers to create, prototype, and hand off screen-based interfaces — covering wireframing, high-fidelity visual design, and design-to-developer handoff. Explicitly excluded: photo editing for photography, print/publication layout (InDesign), video production, 3D rendering, and physical industrial design CAD. The boundary matters because most existing research lumps these into a single "creative software" bucket; Figma targets only the screen-design workflow.

No primary industry report for this specific segment exists as of December 2015. The "UI/UX design tool" category had not yet been formally bounded and sized by Gartner, IDC, or Grand View Research in a report available at this date. All figures below are bottom-up constructions using observable market data, clearly labelled as such.

Bottom-up TAM construction (global, December 2015):

Step 1 — Addressable professional seats:

• No primary 2015 US BLS or LinkedIn report on dedicated screen-design headcount is identified in this analysis. The closest available signals are Adobe's Creative Cloud subscriber base (6.17M end-2015) and Sketch's installed-base estimates (200K–400K active licenses); combined with frontend-developer headcount that increasingly handles design-tool work, the dedicated + adjacent global seat count is estimated at 150,000–280,000 in 2015. Treat as an analyst-constructed range — the formal category headcount has not been measured by BLS or any contemporaneous industry report.

Step 2 — Revenue per seat:

• Adobe reported record annual revenue of $4.8 billion in FY2015, with approximately 6.17 million Creative Cloud subscribers. At Adobe's single-app pricing of $20/month (~$240/year) and full-suite pricing of $50/month, the subset of CC subscribers primarily using it for screen design (estimated at 10–15% of the base, or 600K–900K designers) generates $140M–$215M in attributable revenue. Sketch priced at $99/license (perpetual, pre-subscription) with an estimated 200,000–400,000 active licenses = $20M–$40M. InVision had surpassed one million users by mid-2015 with over 500 enterprise customers; InVision does not publicly disclose ARR, so its 2015 contribution is left as an analyst estimate of $10–20M based on the freemium-to-paid conversion patterns visible in comparable PLG tools at this stage. Other tools (Axure, Marvel, Framer, Pixate): combined $10–20M.

Bottom-up TAM range:

Bottom line on TAM: The honest answer is $200M–$300M for the base scope in December 2015 — and the category barely existed as a separately recognized market. Adobe's $4.8B total does not meaningfully proxy this; the relevant slice is small. What makes this interesting is that Figma's thesis would expand the market by making non-designer roles paying seats — a bet on market creation, not just share capture.

Geographic split: No primary 2015 geographic breakdown of UI/UX design software adoption was identified. Based on broader SaaS adoption patterns (North America ~40%, Europe ~25–30%, APAC/RoW ~30–35%), the implied split on the base $250M estimate is approximately US ~$100M, Europe ~$70M, APAC/RoW ~$80M — directional only.

---

Filters applied:

1. Geography filter — English-speaking tech ecosystems: Figma's browser-native distribution eliminates geographic friction, but initial community traction will concentrate in SF, NYC, London, and Toronto, where design-heavy SaaS startups cluster. Applying North America + UK/Ireland ≈ 45% of global seats.

2. Segment filter — Product-led, design-forward tech companies (10–500 employees): Figma's bottoms-up motion targets individual designers at SaaS startups, not enterprise IT procurement. By 2015, Sketch had evolved to become an affordable alternative to Adobe's Illustrator, providing a fully functional tool with an attractive price point — the same buyer profile Figma is targeting. Filter to companies actively using Sketch or InVision (the indicator of design maturity): estimated at 30–40% of total seats in the geographic filter.

3. Pain-point filter — Distributed/remote-friendly teams where async fragmentation is most acute: Not all Sketch users suffer the collaboration problem acutely; teams co-located on Mac hardware and using file-sharing effectively tolerate the current workflow. Figma's acute pain is felt most by teams with mixed OS, distributed members, or heavy stakeholder-review cycles. Estimated at 50–60% of the segment-filtered pool.

SAM arithmetic:

• Global base: 250,000 addressable seats × 45% (geographic) = 112,500 seats
• × 35% (product-led, design-forward segment) = ~39,000 seats
• × 55% (distributed/acute-pain filter) = ~21,500 seats
• At $180/seat/year (midpoint of $12–$25/month hypothesis): ~$3.9M/year

This is tight. The number expands materially if the freemium model converts non-designer collaborators (PMs, devs, stakeholders) into paid seats, which is part of the thesis but unproven. Applying a 3× seat multiplier for collaborative roles (still at $120/seat blended, acknowledging many will stay free-tier):

• 21,500 design seats × 3 collaborative seats = 64,500 total seats × $120/year = $7.7M/year

SAM range: $4M–$12M in December 2015, rising to $20M–$40M by 2018 as remote work normalizes and the collaboration thesis is validated. These numbers are small. That is the honest read.

---

Motion context: Figma is in private beta in December 2015. Public launch is expected late 2016. The product is free at launch; paid tiers come later. The growth model is bottoms-up: individual designers adopt for side projects → migrate main work → pull in teams → teams upgrade to paid.

Year 1 (2016) — Public launch, free:

Figma publicly released its flagship design editor in 2016. To attract users, Figma initially focused on individual designers, trying to get them on board for side projects even before they incorporated the software into their daily work. The product was initially free, only adding a paid tier two years after its launch.

Comparable: InVision launched in 2011 with a relatively bare-bones prototyping tool; since launch, the company had grown to see over 500 enterprise customers and more than 3,000 new user signups each day. The company had just surpassed the one million user mark by mid-2015 — roughly four years in. Figma faces steeper skepticism (browser performance) but solves a broader problem. Realistic Y1 expectation: 3,000–8,000 registered users, $0 revenue (entirely free, building word-of-mouth in SF design community).

Units: ~5,000 designers registered; $0 ARR.

Year 2 (2017) — Paid tiers introduced:

At the 18-month mark, Figma begins converting users to paid. At a 5–8% free-to-paid conversion rate (consistent with PLG tools at this stage) on a base of 30,000–60,000 registered users by end 2017: 1,500–4,800 paying accounts. At $15/editor/month average with 2 editors/account: $540K–$1.7M ARR.

Comparable: InVision at ~4 years from founding is at an estimated $10–20M ARR (analyst inference; not publicly disclosed) — but InVision was purely a collaboration add-on (no design creation), simpler onboarding, and no performance skepticism to overcome. Figma's conversion should lag InVision's early trajectory by 12–18 months due to adoption inertia.

Units: ~40,000 users; ~$1M–$2M ARR.

Year 3 (2018) — Early scaling:

If Figma's performance on WebGL proves itself (the key open question), word of mouth compounds. Teams adopting fully can contribute 5–10 paying editors each. At 200,000 registered users, 10% paid conversion, 2.5 editors/account at $18/month average: $10M–$18M ARR.

Comparable: InVision received $45M in funding in 2015 (Series C). If InVision converts that runway into Series-D-scale ARR over the next 24 months, that would put it on a credible unicorn trajectory by 2017–2018. Figma should expect to trail that by 2–3 years, given higher technical risk and migration friction from Sketch.

Units: ~200,000 users; ~$12M ARR.

GTM capacity note: All three years assume a founder-led, product-led motion with no outbound sales team. This is appropriate given the intake's bottoms-up hypothesis and the pre-revenue stage. Adding a sales function in Year 2–3 would accelerate enterprise conversion but compresses runway — not modelled here.

---

Growth rate and trajectory — expanding, but the evidence is indirect:

No 2015 industry report directly sizes this market's CAGR. The best proxies available: Adobe reported record annual revenue of $4.8 billion in FY2015; recurring subscription revenue represented 74% of the business. Adobe's CC subscriber count grew from 1.4 million at end-2013 to 6.17 million by 2015 — a 110%+ cumulative gain in 2 years — driven substantially by screen-design workflows. In 2015, there were 25 billion iOS app downloads and 50 billion Android app downloads — the underlying demand creating new design jobs. The screen-design tool market was likely growing 20–30% annually in 2015, but this is an analyst inference from surrounding data, not a primary measurement.

Key drivers:

1. Mobile app explosion: The App Store had 1.25 million apps by 2015 and was accelerating, each requiring purpose-built mobile UI — a workflow Photoshop handled poorly and Sketch handled better, but neither collaboratively. Every new app team needs a design tool.

2. Sketch's disruption of Adobe's monopoly proving the market: In 2012, Apple awarded Sketch with their Design Awards. On May 6, 2013, Adobe announced discontinuing the development of and support for Fireworks, its bitmap and vector graphics editor. The result was the most loyal Fireworks users migrated to Sketch as it could do exactly that in far less time with more features. By 2015, Sketch had evolved to become an affordable alternative to Adobe's Illustrator. This transition demonstrated that designers were willing to switch tools when the workflow fit was meaningfully better — a key signal that Figma's own disruption pitch is plausible.

3. Cross-platform OS fragmentation as a forcing function: Windows had been the dominant player with ~80% market share, which was entirely ignored by Sketch by having a Mac-only app. As enterprise IT estates (Windows-first) increasingly hired product designers, the Mac-only constraint was becoming a genuine procurement blocker. Figma's browser-native delivery directly addresses this; the TAM expansion from unlocking enterprise Windows shops is real.

4. Adobe's competitive response signalling market importance: Adobe announced "Project Comet" (later XD) in October 2015 but had not shipped a public version as of this writing. Adobe's decision to build a dedicated screen-design tool, despite the creative portfolio overlap risk, confirmed that a standalone category existed and was worth fighting for. It also confirmed Adobe's CC suite was not solving the workflow.

Regulatory / macro: None that directly constrain this market in December 2015. Standard enterprise data-residency concerns around cloud SaaS apply generically; not design-tool specific.

Timing assessment:

An honest analyst in December 2015 would say: probably early, not right time. The ingredients are assembling — mobile app growth, Sketch demonstrating designer willingness to switch, InVision demonstrating that designers will pay for collaboration — but the core thesis carries two unresolved questions that are not minor:

First, browser performance. The Figma backend infrastructure is such that having complex shapes and big images is not a problem; data is sent easily across the network; interaction performance is described as smoother than desktop applications — but this is marketing copy from a post-launch perspective. In December 2015, "browsers are too slow for vector design" was the dominant prior, and it was based on real experience with browsers circa 2014–2015. WebGL was maturing, but the performance gap between a native Cocoa app and a browser-based renderer had not been closed in the public's view. This is the thesis's single biggest technical risk and cannot be assumed away.

Second, collaborative design as a primary wedge. Sketch's lack of robust real-time collaboration features makes teamwork challenging, especially for remote or cross-platform teams; Mac-only availability restricts collaboration with Windows users. These are real frictions, documented in user reviews. But in December 2015, distributed design teams were not yet the norm at the scale needed to make collaboration the decisive purchase criterion. "Real designers use native apps" was a genuine cultural priors, not just inertia — and until Figma ships publicly and proves the performance bar, the collaboration argument cannot be evaluated on its merits. The window for "right time" likely opens in 2017–2019 as remote work normalizes and Figma's performance record becomes observable. Launching in 2015–2016 is early enough to build the community ahead of that wave; it is not early enough to assume the wave is already here.

---

All figures in USD. Bottom-up construction throughout; no primary 2015 industry report exists for this segment. Base column matches §3.1–3.3 figures above.

TAM note: Conservative assumes only currently-paying seats in dedicated screen design tools; base includes prototyping/handoff spend + Adobe's attributable UI/UX slice; optimistic assumes Figma's thesis expands seat count 2–3× by making collaborative roles paying users. All three are bottom-up estimates — label them as such in any investor or board presentation. The segment's formal market size was not reported by Gartner, IDC, or Grand View Research at this date.

SOM note: Y1 revenue is $0 by design (freemium, no paid tier at launch). Y2/Y3 figures anchor against InVision's reported trajectory — InVision received $45 million in funding in 2015 after crossing 1M users — adjusted downward for Figma's higher technical risk and migration friction. Optimistic Y3 of $28M would require the browser performance bet to pay off visibly by 2017 and remote design workflows to accelerate; conservative Y3 of $4M reflects the scenario where Sketch migration stays slow and adoption concentrates in early-adopter design communities rather than crossing into mainstream tech teams.

---

The ideal first customer: A product designer (mid-level to lead) at a seed-to-Series-A SaaS startup in San Francisco or New York, 5–50 people, Mac-first culture, who owns design end-to-end and is already annoyed enough by the Sketch + InVision + Zeplin coordination tax that they will try almost anything on a free plan.

Demographics / firmographics

• Role: Product Designer, UI/UX Designer, or "the designer" (often singular) at a startup; 2–6 years of experience
• Company stage: Seed through Series A; 5–50 employees total; 1–3 designers on the team
• Geography: SF Bay Area first; NYC secondarily; English-language global as secondary reach
• Industry: Design-heavy SaaS — consumer apps, developer tools, B2B productivity
• OS/setup: MacBook on a Mac-dominant team; the Windows-exclusion pain is not this segment's problem directly, but cross-OS access for stakeholders and PMs (many of whom are on Windows) is
• Funding stage: Has raised at least a seed round, so there is a real product and a real dev team that needs the designs

Pain intensity

This is a Top-3 daily problem for this segment, not a "would be nice." The canonical Sketch workflow in December 2015 means:

• File ownership is manual. Before tools like Figma, design handoff was a file-sharing nightmare — when UI designs were ready, nothing could begin until designers manually added redlines to their latest local design file, saved it as a locked Sketch or Photoshop file or PDF, and made sure developers were working on the correct file after every update.
• Real-time collaboration doesn't exist. Sketch is only available on macOS, which limits access for Windows users, and it lacks real-time collaboration features. A two-designer team is coordinating file access over Slack messages.
• Developer handoff requires a separate tool. The predominant 2015 workflow — Sketch for design, InVision for prototyping and stakeholder review, Zeplin (launched early 2015) for specs — means three licensed products, three context switches, and manual re-export on every iteration. In many companies, collaboration only happens when the designer hands off the design specs to the developer — and this is wrong for so many reasons.

Observable coping behaviors: uploading Sketch files to Dropbox for "version control," using Craft by InVision to push artboards to InVision after every change, scheduling a Zoom call with a developer to walk through an InVision prototype because the developer can't measure spacing directly.

Willingness and ability to pay

The typical designer in this segment is already spending on adjacent tooling. Sketch's price of $99 was considered a significant barrier for people only mildly interested in trying it out. Adding InVision Pro ($8/month per designer) plus Zeplin ($17/month, their 2015 launch pricing) means a total combined stack spend of roughly $25–35/month per designer before the team has paid anything for stakeholder access.

Figma's hypothesized $12–25/editor/month is roughly cost-neutral against the combined Sketch + InVision pair — which is the right pricing comparison to make at pitch time. The real WTP unlock is framing it as replacement, not addition. The risk: in December 2015, a designer who already bought a Sketch license this year and is mid-project is not going to self-authorize a $15/month recurring charge for an unproven browser tool. Free-tier entry is not optional — it's the only credible wedge.

Note: These WTP estimates are triangulated from adjacent tool pricing pages and contemporary reviews, not a primary 2015 survey.

Reachability

In December 2015, this segment is concentrated and reachable through a small number of channels with genuine signal:

• Designer Hangout — invite-only Slack community, already over 10,000 UX designers and researchers as of late 2015 era; a network for UX designers and researchers connecting over 23,000 professionals globally, fostering meaningful discussions and providing expert advice. Tool discussions, Sketch gripes, and new-tool discovery are among the most active thread types. This is the most direct channel to reach the exact segment.
• Dribbble — where SF/NYC product designers post work, follow each other, and discover new tools; a Figma beta invite dropped in a Dribbble comment thread in late 2015 would reach the right people.
• Twitter (#uxdesign, #productdesign, #sketch) — the SF design community is unusually concentrated on Twitter; Sketch-related complaints are frequent and public.
• Product Hunt — the default discovery channel for new design tools in this geography and stage; an early Figma listing (even in beta) would reach the exact ICP.
• r/userexperience and r/UI_Design — active communities with frequent tool discussions and pain-sharing.
• InVision Blog and Smashing Magazine — the two editorial channels this segment reads for workflow content; sponsored or contributed posts here would have high signal-to-noise.

---

Segment B: Design leads at growth-stage tech companies (Series B–C, 50–300 employees) with distributed or remote-partial teams

One-sentence definition: A design lead (IC or manager) at a 50–300 person tech company who manages 3–8 designers across 2+ cities and has already experienced the Sketch file-coordination failure mode at scale.

This segment has sharper pain than the primary ICP — coordinating six Sketch files across a distributed team is meaningfully more broken than coordinating two. But it is secondary because:

1. Longer evaluation cycle. A design lead at a 200-person company doesn't unilaterally adopt a new design tool; it requires sign-off from engineering (who need to inspect files), product management, and IT. The bottoms-up motion that works at a 20-person startup stalls into a committee at 200.
2. Higher migration cost. An existing team with 12 months of Sketch files, custom symbol libraries, and developer handoff workflows built around Zeplin has real switching cost that a pre-product-market-fit startup does not.
3. Risk aversion. "Browser-based design tool" maps to "what happens when Chrome crashes mid-sprint" in the mind of a design lead who owns delivery timelines.

What would make this primary: Figma proving stable performance on complex files in the browser (the core "can it really be as fast as native?" question), and a handful of credible reference customers at companies this segment respects. In late 2015, those references don't yet exist.

---

Segment C: Freelance product designers working with multiple clients

One-sentence definition: An independent product designer with 2–5 simultaneous clients who bills hourly or by project and needs to share work without requiring clients to purchase software or install anything.

This segment's pain is distinctive: every InVision prototype link requires explaining what InVision is; every Sketch file shared for client feedback requires the client to have either Sketch ($99) or a way to view it. Figma's view-only URL elegantly solves a real problem here.

Secondary because:

• No team adoption flywheel. A freelancer who loves Figma doesn't pull 10 colleagues into a paid workspace. The virality mechanism that makes bottoms-up SaaS work (one designer converts the team) is absent.
• Historically lower WTP. Freelancers often run tight margins on tooling spend and are more likely to stay on free tier indefinitely.
• Smaller aggregate volume in the SF wedge. The density of design-heavy startup teams in SF/NYC is higher than the density of high-value freelancers; the team motion is where the revenue accrues.

What would make this a primary segment later: If Figma builds client-specific features (branded share links, client approval flows, project-level permissions by client), the freelance segment has strong LTV and would refer other freelancers rapidly.

---

Profile

Day in the life

It's 11am. She's been on Sketch since 8:30 finishing the redesigned onboarding flow — twelve artboards, two states each. She pastes the Dropbox link into Slack and tells the other designer "done with auth screens, don't touch for now." The PM wants to see it in 30 minutes for a stakeholder sync. She opens the InVision Craft plugin, waits for the sync to complete, sends the prototype link, then gets a reply: "the link shows the old version." She re-syncs, checks InVision, re-sends. The developer has meanwhile measured a spacing value directly off a screenshot she shared last week and gotten it wrong by 4px; she only finds out when she sees the implementation in staging. The stakeholder feedback comes back as annotated screenshots in a Keynote file shared via email. She manually transcribes the comments into Jira. It's now 2pm and she has done four hours of workflow management and forty-five minutes of design.

Buying triggers

1. New designer joins the team. The second designer makes the single-file coordination problem immediate and daily — file-locking, "who has the latest version," and "can I work on this screen while you work on that one" are now unsolvable with Sketch.
2. Dev handoff blows up. A developer implements the wrong version of a design, or spends a sprint asking for measurements that aren't annotated, or the designer wastes a day producing a Zeplin spec file only to realize the designs changed again. The trigger is a specific incident, not ambient dissatisfaction.
3. Remote collaboration breaks down. A team member starts working from another city (or even from home regularly). The manual Dropbox + Slack coordination that worked with two people in the same room becomes untenable at geographic distance.
4. Stakeholder review cycle bogs down a sprint. Getting sign-off from a CEO or PM on high-fidelity designs takes three rounds of screenshot-in-email feedback; the designer sees Figma's in-context comments as a direct fix.

Decision criteria (ranked)

1. Performance parity with native apps. In December 2015, this is the kill criterion. The dominant prior — "Figma, at first seemed like an impossibility — a web tool has never been fast enough to compete with a native app" — is what every skeptical designer will say. If the beta doesn't feel fast, the evaluation ends here.
2. File fidelity and migration path from Sketch. Can she open a .sketch file, or does she lose two weeks of work? What happens to her symbol library? This is almost certainly the second question out of her mouth.
3. Developer access without a license. The view-only browser URL is genuinely differentiated; it solves the "dev needs to inspect but we don't want to pay a $99 Sketch seat" problem in a single demo moment.
4. Free tier that's real. Freemium only works as a wedge if the free tier is generous enough to prove value before asking for money. Figma initially focused on individual designers, trying to get them on board for side projects before they incorporated the software into their daily work — the product was initially free, only adding a paid tier two years after its launch. This approach is correct for this segment; charging at beta stage would kill the adoption loop.
5. Collaboration quality. The multiplayer editing is the headline, but it's actually fifth in the evaluation sequence — designers don't fully believe it until they see it live in a demo or side-by-side with a colleague. The collaborator-pulls-in-team flywheel addresses the fragmented workflow where "designers would need to use multiple tools from ideation to creation to handoff," creating "inefficient feedback loops because designers were often siloed from a constantly iterative process" — but that framing resonates more with a design lead than with an IC who just wants to stop re-exporting screens.

Honest ex-ante uncertainty (December 2015)

The segment thesis is directionally sound — the pain is real, the community is concentrated, and the freemium entry point is the right unlock. The two open questions that could invalidate this ICP entirely:

• Browser performance. The concept was radical — real-time editing, version control, and no downloads required — and not everyone was ready. Many traditional designers, used to local files and solo workflows, were skeptical of Figma's multiplayer model. If Figma's WebGL renderer can't handle a 50-artboard Sketch-equivalent file without lag, the primary ICP never converts because they won't tolerate performance regression even for collaboration gains.
• Collaboration as the wedge vs. performance as the wedge. The founder's thesis is that collaboration is the primary pain — but for the individual designer who is often solo on a small startup, the collaboration pain is theoretical until the second designer joins. It's possible the actual wedge for first adoption is something simpler: free, browser-based, shareable without sending a file. The collaboration story may be the retention story, not the acquisition story.

In 2017, only 11% of designers reported using Figma, compared to 71% who went for Sketch — which means the segment conversion in 2015–2016 was very slow even after public launch, consistent with the migration-cost and performance-skepticism headwinds this analysis flags.

---

---

1. Sketch

URL: sketch.com | Founded: 2010 | Funding: Bootstrapped — Bohemian Coding (Dutch) raised no external venture capital through end-2015 | Pricing: $99 one-time license (perpetual, with paid major-version upgrades); Sketch continued to sell for $99 with a free trial available after Bohemian Coding pulled it from the Mac App Store in December 2015, concluding that directly licensing the software outside of Apple's storefront would provide customers with a better experience

Positioning: The purpose-built vector design tool for digital product designers; explicitly not a print tool, not a photo editor.

Strengths:

• A vector graphics editor for macOS, it won an Apple Design Award in 2012 and has become the dominant mindshare leader among SF-area product designers by late 2015
• Built to measure in pixels first, with a much simpler interface than Illustrator — designed for screens, not print
• Rapidly growing plugin ecosystem that extends functionality without Bohemian Coding needing to ship every feature themselves

Weaknesses:

• Being only available for macOS, third-party software and handoff tools are required to view Sketch designs on other platforms — this is the single biggest structural constraint Figma is exploiting
• Lack of real-time collaboration makes teamwork challenging, especially for remote or cross-platform teams; sharing files and keeping versions in sync can be inconvenient
• Zero native developer handoff — CSS inspection and asset export require third-party tools (Zeplin, launched 2015, is the emerging workaround) that fragment the workflow further

---

2. Adobe Photoshop

URL: adobe.com/photoshop | Founded: 1987 (Adobe; Photoshop 1.0 shipped 1990) | Funding: Public (ADBE on NASDAQ) | Pricing: ~$19.99/month for single-app Creative Cloud subscription, or ~$49.99/month for full CC suite (pricing current as of 2015; Adobe moved fully to subscription in 2013)

Positioning: The world's professional image editor, adapted over years for UI design work despite not being built for it.

Strengths:

• Absolute ubiquity — every designer on every team has Photoshop experience; enterprise IT departments have pre-existing Adobe licensing
• Windows and Mac, removing the platform lock-in that Sketch creates
• Photoshop CS6 used to cost around $700 as a perpetual license — the muscle memory and institutional knowledge across global design teams is enormous

Weaknesses:

• Photoshop was built for print first; Sketch is built to measure in pixels first, with a much simpler interface — Photoshop's UI is visibly bloated for screen design
• Raster-based by default: working in vectors requires deliberate workarounds; exporting for Retina/multiple screen densities is painful
• No collaboration, no developer handoff, no stakeholder review — everything that happens after the Photoshop file is exported requires separate tooling

---

3. Adobe Illustrator

URL: adobe.com/illustrator | Founded: 1986 (first shipped) | Funding: Public (Adobe) | Pricing: ~$19.99/month single app via Creative Cloud

Positioning: Industry-standard vector graphics editor; used by product designers who need scalable assets and icon systems.

Strengths:

• Unmatched vector editing capabilities for complex illustrations and icon work at any scale
• Windows + Mac; exports to every format any downstream consumer could need
• Deep integration with the rest of the Adobe suite — assets flow from Illustrator into Photoshop, After Effects, and (soon) Project Comet

Weaknesses:

• Like Photoshop, not purpose-built for multi-artboard UI design; lacks the artboard workflow, symbols system, and screen-density tooling that Sketch introduced
• No prototyping, no handoff, no collaboration — purely a creation tool requiring the same downstream fragmentation
• Steep learning curve that filters out casual use; overkill for most product design workflows

---

4. Adobe XD ("Project Comet")

URL: adobe.com/products/experience-design | Founded: N/A (internal Adobe project; Adobe founded 1982) | Funding: Adobe corporate R&D — public company | Pricing: As of December 2015, not yet public; planned as part of Creative Cloud (no standalone pricing announced)

Positioning: Adobe announced they were developing a new interface design and prototyping tool under the name "Project Comet" at the Adobe MAX conference in October 2015, which was a response to the rising popularity of Sketch

Status note: As of December 2015 this product does not exist in the market. In December 2015, Adobe aimed towards a public beta in early 2016 and was running a private pre-release program to share alpha builds and get feedback on specific features. Every claim below is based on announced intent, not a shipped product.

Strengths:

• Adobe built the engine from scratch with a determined focus on fundamentals — reportedly capable of handling hundreds of artboards and thousands of objects without slowdown
• Distribution advantage: any designer already paying for Creative Cloud gets it at no marginal cost, eliminating purchase friction
• Windows support announced for late 2016, which addresses the Mac-only gap left by Sketch

Weaknesses:

• Vapor for now: not publicly available; designers cannot evaluate it, adopt it, or leave Sketch for it as of December 2015
• The engine was built from scratch to be native to OS X — despite the Windows roadmap, this is still a native-app-first approach with no browser access
• Adobe's creative tools history creates skepticism: every major UI design-adjacent tool they've shipped (Fireworks, Muse) eventually stalled or was cancelled

---

5. InVision

URL: invisionapp.com | Founded: 2011 (New York) | Funding: Through end-2015, InVision raised $45M in Series C funding (July 2015, led by Accel) following $21M Series B (2014) and $11.6M Series A (2013) — approximately $79M total, at a ~$232M valuation | Pricing: Free (1 active prototype); paid tiers ~$15/month and up; enterprise custom — exact 2015 pricing not publicly archived, treat as directionally accurate

Positioning: The design review and prototype-sharing layer for teams using Sketch or Photoshop — not a design creation tool, but the collaboration wrapper around design files.

Strengths:

• Designers can share links for quick feedback and give instant comments instead of sharing JPGs or PDFs and waiting for a response — meaningfully improving the stakeholder review problem Figma also targets
• Strong traction: well-funded, widely adopted at SF startups and growing into enterprise; used by Netflix, Uber, and other design-forward companies by 2015
• Integrates with popular design tools like Sketch and Photoshop, making it additive to existing workflows rather than requiring displacement

Weaknesses:

• Takes significant time to put everything together — uploading work doesn't allow fast prototyping, and linking mocks together is laborious
• Not a design tool at all: designers still need Sketch or Photoshop to create; InVision only adds the review layer, leaving the core fragmentation problem unsolved
• Prototype fidelity is limited by what designers can upload — interactive hotspots on static images, not live design

---

6. Marvel

URL: marvelapp.com | Founded: 2013 (London) | Funding: Founded by Brendan Moore, Murat Mutlu, and Jonathan Siao; backed by Index Ventures, Connect Ventures, and Ustwo in an August 2015 round — total raised through end-2015 estimated at ~$2–3M | Pricing: Free (1 project); Pro ~$14/month — exact 2015 tiers not precisely archived, treat as directionally accurate

Positioning: Simpler, faster prototyping for everyone — emphasises accessibility over power.

Strengths:

• Cloud-based, mobile-supported platform; browser-based environment providing a "Design Mode" for creating mockups from imported Sketch or Photoshop compositions, or from scratch
• Substantially lower barrier to entry than InVision — getting a clickable prototype in front of stakeholders in minutes rather than hours
• Free tier creates broad top-of-funnel adoption in exactly the bottoms-up market Figma is targeting

Weaknesses:

• Underperforms for those needing advanced animation or deep integrations; positioned as an easy entry point, not a power tool
• Like InVision, not a design creation tool — designers still produce their screens elsewhere, limiting Marvel to the review and handoff layer
• Small team (London, ~10 people in 2015) with limited engineering bandwidth to close the gap between what it does and what a full design platform needs to do

---

7. Axure RP

URL: axure.com | Founded: ~2002 (San Diego) | Funding: Bootstrapped / self-funded — no disclosed venture investment | Pricing: In the 2015 era, Axure RP 8 was the current version; perpetual license approximately $289/user (Pro), $589/user (Team) — these are directional figures based on the era; Axure had both subscription and perpetual license models; Axure RP Pro perpetual licenses started at $495 for a later version, so 2015 pricing was in the same range but likely lower

Positioning: The enterprise UX prototyping tool for teams that need conditional logic, dynamic panels, and full interaction documentation — beyond what any "designer tool" can produce.

Strengths:

• On-premise and cloud-based; includes wireframing, prototyping, flowcharts, notes, co-authoring, revision history, team project hosting, and SAML-based SSO — effectively a documentation platform, not just a design tool
• Windows + Mac; favored in enterprise IT shops where Sketch is literally unavailable to the engineering side due to Mac-only requirement
• High switching costs and institutional knowledge: Axure files become documentation artifacts that UX teams reference for years

Weaknesses:

• Significant learning curve — complex feature set that requires substantial training; frequently characterised as the tool of enterprise UX departments rather than product designers
• Pricing and complexity make it inaccessible for bottoms-up adoption — purchased top-down by IT procurement, not by individual designers
• Described even by users as "the best professional prototyping tool... from the past" — functional but showing its age in a market where design aesthetics have evolved rapidly since 2010

---

8. Webflow

URL: webflow.com | Founded: 2013 (San Francisco; graduated from Y Combinator's startup accelerator in 2013) | Funding: ~$2.9M seed through end-2015 from Khosla Ventures, Y Combinator, Tim Draper (secured a $1.5M seed round led by Khosla Ventures and Draper Associates after joining Y Combinator's Spring 2013 cohort; total seed-era funding approximately $2.9M) | Pricing: Free (up to 2 pages, hosted); paid from ~$16/month — directional, 2015 rates

Positioning: A SaaS application that allows designers to build responsive websites with browser-based visual editing software, automatically generating HTML, CSS, and JavaScript — bridging design and production for web.

Strengths:

• The 2015 introduction of an integrated CMS was pivotal, enabling dynamic, data-driven sites without backend developers — meaningfully reducing handoff friction between design and engineering for web projects
• Browser-native editor demonstrates proof-of-concept that complex visual design is possible in the browser, which is relevant context for Figma's own thesis
• Design-to-production without a separate engineering handoff step for web — the closest thing to eliminating the design-engineering gap in its category

Weaknesses:

• Wrong category for Figma's immediate use case: Webflow outputs production websites, not design specs for app UI; no overlap with mobile app design, screen flow documentation, or component library management
• Learning curve steeper than alternatives — despite "no-code" positioning, some understanding of CSS and HTML is essential; not a tool for non-technical designers
• Very small company in 2015 with limited traction; primarily serving freelance web designers, not the product design teams Figma is targeting

---

Feature Comparison Matrix (as of December 2015)

* XD/Comet: announced but not yet publicly available in December 2015; features marked as planned for public beta (March 2016) ** Sketch developer handoff requires third-party tools (Zeplin, etc.) not included in the license

---

Keynote / PowerPoint — The dominant stakeholder review substitute. Designers export artboards from Sketch as PNGs, assemble them into a Keynote deck, and present or share for async feedback. Widely practiced in 2015. Missing: any design-fidelity, live interactivity, or in-context commenting. Feedback arrives via email or verbal notes. The overhead is significant — a new presentation must be rebuilt for every design revision.

Google Slides / Docs — Used by smaller or more collaborative teams who can't get stakeholders to open Keynote files. Same structural weakness: static screenshots, no interaction, feedback threading in the document body rather than in context of specific design elements. The Google Docs collaboration model is Figma's closest analogy for the workflow it is proposing, but Docs cannot render vector graphics.

Zeplin (launched 2015) — A developer handoff tool that accepts Sketch exports and provides a structured inspection view. Solves one slice of the fragmentation problem (CSS/spec extraction) without addressing design creation, collaboration, or stakeholder review. Fills a gap that Figma will replace in its target workflow once it ships dev handoff natively. Worth watching as an indicator of where the market is feeling pain.

Framer (founded 2013, Amsterdam; launched its official platform in 2015, offering a Figma-like interface for building interactive web prototypes) — Code-based prototyping for technically-oriented designers and developers. Supports complex, data-driven interactions that InVision/Marvel cannot achieve. Missing: accessible to non-coders, visual design creation, team collaboration beyond sharing links. Niche audience; not a mass-market threat in 2015 but the most technically sophisticated alternative to native design tools.

Spreadsheets + FTP / Dropbox — For small or non-design-heavy teams: design mocks live in Dropbox folders, feedback lives in email threads, versioning is by filename (homepage-v3-FINAL-v2.psd). Not a real "product" but the aggregate behavior that Figma is displacing. Stickiness comes entirely from inertia and absence of migration cost to something better.

Consultants / Design agencies — Enterprise companies without in-house design teams use agency relationships to produce design deliverables; the agency owns the toolchain. Switching away from this model requires both tool adoption and in-house design hiring, making it a longer-term substitution path than the startup wedge Figma is targeting.

---

Axes chosen:

• Horizontal: Native app only ←→ Browser-native (no install required)
• Vertical: Prototyping/review layer only ←→ Full design creation

These axes were chosen because they expose the precise gap Figma is claiming. Every competitor occupies either the native-app quadrant (full design power, no browser access) or the browser-native quadrant (collaboration-friendly, no serious design creation). No shipped product in December 2015 occupies the top-right quadrant.

Where Figma sits: Top-right — the only product (if the performance thesis holds) that combines serious vector design creation with full browser-native delivery.

Where the white space is: The top-right quadrant is entirely empty of shipped products in December 2015. The hypothesis is that the white space exists because it is genuinely hard to achieve (browser performance has historically made it unviable), not because nobody has thought of it. XD/Comet represents Adobe's acknowledgment that the design-tool market has shifted away from print-heritage tools, but Adobe is targeting the top-left with a native approach. Nobody is seriously competing on the browser-native + full-design-creation combination. Whether that is an opportunity or a warning sign about technical feasibility is the central open question of this brief.

---

What Figma could defensibly own, in rough order of build time:

1. Custom rendering engine (exists today, in private beta). Figma built a bespoke WebGL rendering pipeline because standard browser graphics APIs were inadequate for real-time vector editing at scale. This is genuine technical differentiation that took years to build and cannot be replicated in a sprint. It is the precondition for everything else — without it, the browser-performance objection wins. If it works at production quality (undemonstrated publicly as of December 2015), it is a real head start.

2. Switching costs (near-term, once adoption begins). Once a team's design files, shared component libraries, and developer inspection links live in Figma, the cost of migrating back to Sketch is substantial — not because exporting is hard but because all the institutional workflow (links in Slack, dev bookmarks, stakeholder comment threads) is embedded in Figma's URL structure. Google Docs built the same switching cost. The caveat: this moat does not exist yet and requires meaningful team-level adoption to materialise.

3. Network effects (medium-term, speculative). A design tool that allows developers and stakeholders to access files via browser link — without a license — creates passive network pull: every developer who opens a Figma link and inspects CSS without installing anything is a word-of-mouth vector. This is the same mechanic that made Google Docs spread virally through organizations. It is, however, unproven in the design tool category and requires that the product experience for those passive viewers is genuinely good.

4. Data advantages (long-term, highly speculative). At scale, Figma could observe design patterns, component reuse behavior, and handoff friction across thousands of teams — potentially valuable for product intelligence. This is third-order thinking for a company still in private beta and not worth weighting heavily.

What Figma does not have:

• Brand or distribution (zero public customers, zero word of mouth)
• Regulatory or IP moat (no patents filed publicly; WebGL rendering techniques are not patented)
• Institutional relationships or enterprise contracts

The honest difficulty: The "no moat yet" verdict understates the fragility. Sketch has 60–70% mindshare among the exact audience Figma is targeting, has a passionate community, and is actively improving. Adobe — with ~$4B in annual revenue — just announced a direct response (Project Comet) with a free Creative Cloud distribution advantage. InVision has $79M in funding and is embedding deeply in the same teams' workflows. Figma would need to convince designers to adopt a tool whose core premise ("browser performance matches native for vector work") the design community largely disbelieves in December 2015 — and to do so before Adobe ships XD, and before Sketch adds collaboration features of its own.

No moat yet. The custom WebGL engine is real technical differentiation and the closest thing to a defensible foundation, but it is only a moat if the browser-performance hypothesis holds under production conditions — something undemonstrated publicly. Switching costs and network effects are the logical destination if adoption happens, but they do not exist in December 2015. An honest assessment is that Figma is one fragile, technically credible bet in a market where the incumbent (Sketch), the gorilla (Adobe), and a well-funded workflow tool (InVision) are all moving in adjacent directions. The path to a durable moat runs through proving the rendering engine at scale and locking in enough team-level workflows before Adobe ships. That window is probably 12–18 months.

---

Temporal framing note: All analysis reflects what is knowable in December 2015. Figma has just entered private closed beta, multiplayer is not yet in the product, and the public launch is roughly a year away. The thesis — browser-native collaborative design — is contrarian. Channels are evaluated for their ability to recruit 100–500 true-believer designers into a closed beta, not to achieve scale.

---

Channel 1 (best fit): Hand-selected designer outreach — Dribbble cold email + Twitter design community social graph seeding

Fit rationale. The ICP (product designers at 10–500-person tech companies, SF/NYC bias) overwhelmingly congregates on Dribbble and Twitter's design community ("Design Twitter") in late 2015. By late 2015, Figma had launched its private beta introducing a new way of working to a small group of designers — a concept many traditional designers, used to local files and solo workflows, remained skeptical of. That skepticism makes mass-market channels wasteful; the right move is to target the small cohort of designers who are already frustrated with Sketch's file-handoff bottleneck and are curious about new paradigms. Critically, before Figma even had a public product, the team built individual relationships with designers through one-on-one demos and personal emails — not "sign up for our beta list" spray-and-pray, but targeted outreach to people who would become true believers. The team mapped Twitter's design community like a social graph, identifying the nodes with influence that designers actually listened to.

Dylan cold-emailed 50 designers on Dribbble during early development. This is the right channel template for the beta recruiting phase. The first few years on Designer News from 2013 through late 2015 have been filled with quality discussions with incredibly knowledgeable people — DN's invite-only policy kept discussion and post quality high, but Dribbble and Twitter are where designers with public audiences live. Sketch has no marketing arm in 2015 (it's a 4-person Dutch shop), and InVision's content strategy targets the reader rather than seeding individuals directly, leaving the social graph approach as a genuine gap.

Estimated CAC. Near-zero in cash outlay — entirely founder-time cost. No comparable 2015-era benchmark exists for this specific approach. Reasoning from adjacent data: referral programs deliver about 30% lower CAC than most paid acquisition channels, and modern PLG benchmarks place referral CAC at roughly $150 for B2B SaaS tools. Hand-to-hand influencer seeding — where the "referrer" is a trusted designer with 5,000–50,000 followers and the conversion intent of their audience is extremely high — should produce effective paid-seat CAC below $50 at this price point ($12–25/month), assuming even a 10–15% free-to-paid conversion rate from this audience. No primary benchmark; estimate derived from conversion-rate reasoning, not direct data. Confidence: low precision, directionally credible.

Time to traction. First signal (1–5 high-quality beta users engaging deeply): weeks 1–3. Reliable flow of qualified beta users from influencer word-of-mouth: months 2–4, contingent on at least one high-following designer genuinely endorsing the product publicly. First paying customers via this channel would not come until post-public-launch (likely 12+ months away), so this channel is presently about beta quality, not revenue.

Scalability. This channel is inherently capped — Dribbble is invite-only and the influential designer pool is small (hundreds of genuinely high-reach individuals). It cannot scale beyond ~500–1,000 beta recruits without transitioning to a more public mechanism. That is fine for December 2015; the goal is not volume but signal quality. What breaks first: founder bandwidth. A solo founder cannot sustain personalized outreach beyond 20–30 contacts per week while also building the product.

Risk. Sketch's community is ferociously loyal in 2015. By 2015, Sketch had evolved to become an affordable alternative to Adobe's Illustrator and designers who championed the Sketch migration from Photoshop see that as their credibility. Any outreach that reads as "Sketch is bad" rather than "here is a genuinely new capability" risks backlash in a tight community. The second risk: multiplayer — the headline differentiator — is not yet in the product as of December 2015. Multiplayer still did not have the right feel by December 2015; cutting multiplayer out of the initial release was tough, but the thinking was that starting with something that felt bad — even with all the right features — would have created a credibility problem. This means every demo must sell the vision of what the product will be, not what it currently is — a materially harder pitch.

---

Channel 2: Designer News + Hacker News simultaneous community launch

Fit rationale. The ICP is not just designers; it is designers at tech companies who read the same feeds as engineers and PMs. Designer News in late 2015 is in its prime: the first few years from 2013 through late 2015 have been filled with quality discussions with incredibly knowledgeable people. Designer News is a global community of people working in design and technology, launched in 2012; it started as an invitation-only community and let the community decide the most "designer-friendly content" by voting on stories. A well-timed "Show Figma" post on HN, cross-posted with a DN submission, reaches the designer-developer crossover audience that is the first internal champion of a new design tool at a SaaS startup. No design tool has credibly launched on HN in this way in 2015; Sketch doesn't have a company to do it, and InVision's product is prototyping/handoff, not the design tool itself.

Estimated CAC. Zero cash cost. Expected click-through from a front-page HN post: 3,000–15,000 unique visitors in 48 hours (no 2015 HN-specific data found; extrapolated from typical HN "Show HN" traffic patterns for design/dev tools, which are not reliably benchmarked pre-2016). Beta signup conversion from this audience at 5–10% = 150–1,500 beta signups from a single strong post. Paid conversion from beta is speculative at this stage. CAC is effectively founder time; no comparable primary benchmark found.

Time to traction. First signal within 48 hours of a strong post. But Designer News has platform risk: LayerVault — which built Designer News — ceased operations in 2015 and Metalab (or Tiny) acquired Designer News that year. The acquisition introduces uncertainty about community engagement trajectory, and if the new owners change the tone or gates, this channel's quality could degrade through 2016.

Scalability. One-time burst channel, not a reliable ongoing acquisition source. A second post 6 months later (public launch) can work, but repeated seeding of the same community reads as spam. Pairs well with Channel 1 as an amplification event: the outreach network amplifies the DN/HN post, and vice versa.

Risk. The "browser is too slow for real design work" prior is strong in both the DN and HN communities as of 2015. When Figma first launched, the idea of designing in a browser sounded almost absurd — design software had always lived on heavy desktop programs. A DN/HN post that meets dismissive comments ("WebGL can't match Sketch's rendering performance") will compound the skepticism rather than dissipate it. The post requires a live demo or video that concretely overcomes the performance objection. If the product doesn't survive that scrutiny in December 2015, this channel backfires.

---

Channel 3: Product Hunt closed-beta listing (invite-only framing)

Fit rationale. Product Hunt in late 2015 is a curated, smaller community than it later became — closer to 100,000–500,000 monthly visitors than the millions of today. It skews toward founders, PMs, and early-adopter designers: the exact people who would be Figma's internal champions at design-heavy SaaS companies. Product Hunt is the best site of its kind, followed by Betalist; both sites represent a unique opportunity for early-stage startups to gather product feedback and land their first users. Critically, in 2015 the "hunter" mechanic still works: if you were able to recruit an influencer with a large following to hunt your product on launch day, it would automatically notify all of their followers via email that they had hunted your product, driving a ton of traffic and upvotes. Getting a prominent designer or founder to hunt Figma — not a generic tech person — would route the launch notification specifically to designer-adjacent audiences.

Estimated CAC. Zero cash cost. Typical Product Hunt launches in this era generated 500–3,000 beta signups for a #1 or #2 product-of-the-day finish. Oleg Campbell of Reply.io stated their Product Hunt launch resulted in 10,000 visitors in two days, 600 signups, and about 60 new paying customers. That is a well-funded company with an established email list; a raw private-beta launch at Figma's stage would realistically produce 200–600 beta signups. At $12–25/editor/month and an estimated 3–8% free-to-paid conversion from PH traffic (tech-forward audience, above-average intent), this implies 6–50 eventual paid conversions with $0 spend. CAC: effectively $0 cash; founder time to execute. No direct 2015-era comparable found.

Time to traction. First signal day-of-launch. But Product Hunt traffic is a 48-hour spike, not a compounding asset. It is a moment, not a motion.

Scalability. Not scalable — one meaningful launch per product per cycle. This is a launch day play, not an ongoing channel.

Risk. Product Hunt's community in 2015 is heavily builder/investor biased, not pure designer. A design tool risks generating high upvote counts from people who won't use the product, inflating vanity metrics while actual designer adoption stays flat. The bigger risk: launching a private beta on Product Hunt too early — before the product can demonstrably overcome the "browser is slow" objection — could create an anchoring impression that is hard to dislodge. If the December 2015 beta invites a PH launch too soon, it may burn the launch moment on an under-polished product.

---

Channel 4 (tied #3): Invite-only beta referral loop ("each beta user gets 3 invites")

Fit rationale. The invite mechanic creates scarcity, drives aspirational demand, and — most importantly — means every beta signup comes pre-qualified: a real designer trusts this person enough to give them one of three invites. Dropbox and Gmail perfected this mechanic; in 2015 it is still underused in the design tool space. The viral loop here is not just growth but signal quality: Figma followed a bottom-up SaaS go-to-market approach. By offering a free version first, designers could use it for a side project in a lower-stakes environment and eventually become repeat customers and advocate for its use in their day jobs, leading to business adoption.

Estimated CAC. Near-zero. Referral mechanics in PLG contexts structurally reduce CAC; modern data shows referral programs deliver about 30% lower CAC than most paid acquisition channels. In a closed-beta context with zero spend, the effective cash CAC is $0 — but the invite mechanism only works if the initial seed cohort (Channel 1) generates genuine enthusiasm. This channel is downstream of Channel 1, not independent.

Time to traction. Weeks 3–8 after initial seeding, assuming the seed cohort finds the product compelling enough to share invites voluntarily. The risk is that in December 2015, without multiplayer in the product yet, the "magic moment" that motivates sharing is harder to engineer.

Scalability. Naturally self-limiting: it scales proportionally to the quality of the seed cohort's enthusiasm. With a K-factor below 1.0 (likely in a niche designer community), it cannot compound to thousands on its own. It reaches a ceiling of ~1,000–3,000 beta users without a public burst event (Channel 2 or 3).

Risk. Invite scarcity can create a gated community perception that is at odds with Figma's "design is for everyone" thesis. If early invitees are primarily elite Dribbble designers, the product gets the "it's just for fancy SF designers" brand positioning — wrong for the eventual enterprise motion.

---

Channel 5 (weakest): Content + SEO ("Sketch alternatives," "collaborative design workflow")

Fit rationale. In 2015, the query "Sketch alternatives" has thin but growing search volume. InVision has already built a content moat here — their blog "Inside Design" started in October 2014 and had about 500,000 subscribers when Kristen Hillery joined, built over 3 years with primarily in-house content. Figma has no domain authority, no editorial team, and no existing audience. SEO/content is a 12–24 month investment before meaningful organic traffic accrues.

Estimated CAC. The average customer acquisition cost for organic channels like SEO and content marketing is $205, while paid channels cost roughly $341 per customer acquired — but those benchmarks apply to companies with existing domain authority and publishing cadence. For a brand-new domain in December 2015, organic content produces near-zero return in the 90-day window relevant to this plan. CAC is indeterminate in the near term; meaningful only at 12+ month horizon.

Scalability. Theoretically high ceiling; practically, this is the channel that compounds over years, not quarters. InVision proved the model works in design, but that requires editorial investment Figma cannot yet sustain.

Risk. Opportunity cost. Every hour spent on content in the first 90 days is an hour not spent on the direct seeding (Channel 1) that has clear signal-to-effort ratios at this stage. Building SEO with no social proof also produces low-quality content; content only earns traffic when it is the definitive resource, not an aspirant.

---

Channel Comparison Summary

All CAC estimates are cash-cost only. No primary 2015 benchmark for any of these channels in the design tool vertical was found. Figures derived from PLG referral benchmarks (modern) + conversion-rate reasoning. Treat as directional, not measured.

---

Direct, self-serve, bottoms-up. Figma's distribution model should be entirely direct at this stage — zero intermediaries between the product and the designer. To attract users, Figma initially focused on individual designers, trying to get them on board for side projects even before they incorporated the software into their daily work. The customer relationship must be owned by Figma because the bottoms-up motion depends on the individual designer having a complete, unmediated product experience before they evangelize upward to their team and org. Any reseller or agency layer would break this feedback loop.

Self-serve only — sales-assisted economics do not work at this price point. At $12–25/editor/month, the math for any sales-assisted motion is straightforwardly hostile. A sales rep closing a 5-seat team at $25/editor/month yields $1,500 ARR — a deal that would require fewer than 60 days of payback on a $7,500/month SDR cost. The CAC for B2B tends to be much higher than B2C; selling software to businesses, especially midmarket or enterprise, usually means longer sales cycles, more stakeholders, and hands-on sales involvement — that drives up costs. Sales-assisted only makes sense when and if average deal sizes move to $5,000+ ARR, which requires either enterprise pricing or multi-seat expansion — neither is accessible until Figma has more product credibility than a closed beta can establish. The correct model in December 2015 is frictionless free access: sign up with email, see the product, share with one teammate, never talk to a salesperson.

Marketplace/platform distribution. Product Hunt is the only meaningful discovery marketplace for a tool like this in December 2015 — and it should be reserved for the public launch moment in late 2016, not burned on the private beta. Betalist is a secondary option for early waitlist building (free, low friction). Zapier did not have a meaningful app marketplace for design tools in 2015; Slack's app directory launched in 2014 but there is no obvious Figma integration surface until the product has sharing and notification functionality. The Claude MCP directory, OpenAI GPT Store, and App Sumo are all post-2015 constructs that do not exist in this temporal frame. No credible marketplace listing serves Figma's distribution in the December 2015 beta phase — the product is too early, and the markets that matter (design teams inside SaaS companies) are reached person-to-person, not through listing platforms.

---

Primary channel: Hand-selected direct seeding into the Dribbble + Twitter design community.

One sentence: Start by identifying 30 product designers on Dribbble whose work signals Sketch-fluency and team collaboration friction (look for comments on handoff pain, multi-file coordination, cross-OS team problems), cold-email them with a live demo link, and ask for 30 minutes — not a signup, not feedback, a conversation.

This channel wins over Designer News/HN (#2) and Product Hunt (#3) for a specific reason: in December 2015, the private beta product cannot yet demonstrate multiplayer — the headline feature — because multiplayer still did not have the right feel by December 2015; cutting it from the initial release was a deliberate choice to avoid starting with a credibility problem. That means the demo sells a vision and a thesis, not a complete product. That pitch works in a 1:1 conversation with a designer who is already frustrated with Sketch's single-player file model. It does not survive a DN comment thread where "but Sketch already does X and it's native" gets 50 upvotes before the founder can respond. Hand-to-hand is the only channel where the nuance of "this is what we are building toward" is tolerated and even compelling.

Over Designer News + HN (#2): Those channels require the product to defend itself publicly. Product quality in a closed beta with no multiplayer is not yet there for public scrutiny.

Over Product Hunt (#3): Product Hunt should be saved for the public launch — the team made the difficult decision to launch without multiplayer, opting for a closed beta that would allow them to gather user feedback while finishing development of their signature feature. Burning Product Hunt on a beta is a one-time launch moment that should be staged for when multiplayer is ready.

---

90-Day Channel Experiment Plan

Weeks 1–2: Build the target list and first 10 conversations.

Map the Dribbble + Twitter design community. Identify 50 designers whose public work signals: (a) they work on product teams (not just graphic/print), (b) they are on teams (not pure freelancers), (c) they have expressed frustration with Sketch's limitations or cross-OS friction in tweets or Dribbble comments. No mass emailing. Write 50 distinct one-paragraph cold emails referencing something specific about their work or their Sketch usage. Ask for a 30-minute Zoom/call — not a beta invite, a conversation. Target: 10 scheduled calls by end of week 2. Each call has two goals: (1) understand their current Sketch workflow bottlenecks in depth, (2) demo the browser-based editor and gauge their visceral reaction to performance. Close each call by inviting them into the closed beta with 3 invites to share if they want.

Weeks 3–6: Convert 3–5 true believers into active beta users and seeded amplifiers.

From the first 10 conversations, identify the 3–5 designers who showed the strongest reaction — not the most polite, the most emotionally agitated about their current workflow. These are the seed nodes. Work with them hand-in-hand: respond to every bug report within hours, get on 1:1 calls weekly, build around their actual workflow. Ask them to share their beta invites only with designers they trust would give honest feedback, not boosters. Run a second outreach wave of 30 more contacts using what you learned from the first 10. Target: 20–40 total active beta users by end of week 6.

Watch for the Designer News acquisition transition (Metalab bought DN in 2015) — if the community is stable, a "what are you working on" post from a respected member of the beta cohort could organically surface Figma to that audience without a formal launch.

Weeks 7–12: Stress-test the core thesis and set up the public launch funnel.

By week 7, you should have 20–40 designers using the product on real projects. Run a structured qualitative survey: what does the product have to do before they would switch their daily workflow from Sketch? Document the specific objections — performance, plugin ecosystem, Sketch file import, vector precision. This is the product roadmap input, but it also tells you whether the channel-to-conversion funnel is real. Simultaneously, begin building a waitlist landing page for the public launch. The beta cohort becomes the testimonial backbone: one or two will be willing to be named ("I've been using Figma for X weeks and here's what surprised me about browser-based design"). Target: 200+ waitlist signups by week 12, sourced from beta user shares and any organic DN/Twitter mention the seed cohort generates.

---

Decision criteria: what tells you to double down vs. kill this channel.

If the Day 30 or Day 60 signal is red, the problem is likely product-side (browser performance has not cleared the bar), not channel-side. Switching to a louder channel (Product Hunt, press) before solving the demo problem would accelerate a negative impression, not a positive one. The honest assessment as of December 2015: this is not a marketing problem yet. It is a product credibility problem. The channel's job is to surface that verdict as cheaply and quickly as possible — and hand-to-hand seeding with 20 designers in 60 days does that for essentially zero dollars and maximum signal density.

---

December 2015 framing. Figma is in private beta. The product has not shipped publicly and has zero paying customers. The economics below are projections from synthesis-grade inputs — every material assumption is labelled.

---

Model A — Freemium per-editor SaaS subscription, free viewer access

Structure: Free tier for solo / small projects (e.g., 3 active files, 2 editors); paid Professional tier at $12–15/editor/month billed annually; Enterprise tier custom-quoted for IT-managed environments. Critically: view-only access for developers and stakeholders is free and unlimited, charged only on editors.

Why it could work here. The entire wedge thesis is bottoms-up: one designer at a SaaS startup adopts Figma, shares a file with a developer, the developer opens it in the browser without buying anything, the PM comments directly on the live design, and suddenly the team asks "why aren't we all using this?" Per-editor billing with free viewers is the only revenue model that supports this motion — it lets the viral loop run while still monetizing the people doing creative work. InVision had already proven by 2015 that design-adjacent teams will pay ~$15-25/month for collaboration on design assets. Slack had proven by late 2015 that bottoms-up freemium with free tiers can reach $38M ARR inside 18 months in the enterprise collaboration category — the buying pattern Figma's ICP (design-heavy SaaS startups, 10–500 person teams) already recognizes.

Why it might not. The free tier creates a real cost liability before revenue. Browser-native, real-time multiplayer design requires persistent WebSocket connections, server-side rendering infrastructure, and cloud file storage — all of which run whether users pay or not. If the free-to-paid conversion rate is below ~5%, the economics break at scale (see §7.3). The harder risk in December 2015 is that the product has to overcome massive incumbent inertia — Sketch has 60–70% mindshare among SF designers — and the standard PLG playbook (get professionals on a free tier, convert to paid as teams grow) will be slow if browser performance skepticism prevents serious professional adoption in the first place.

Comparable companies (adjacent models): InVision (Free → $15/mo Starter → $25/mo Professional); Slack (Free → $6.67–8/user/month Standard); GitHub (Free for public → $7/user/month Teams). No direct comparables exist for a browser-native multiplayer design editor — this category does not exist at scale in December 2015.

---

Model B — Per-project / per-prototype subscription (project-gated, not user-gated)

Structure: Gate access by number of active design projects or prototype connections rather than by editor count. Comparable to InVision's model: Free (1 project), Starter ($15/mo, 5 projects), Professional ($25/mo, unlimited projects). Unlimited users on any plan.

Why it could work. Removes per-seat friction for team adoption — the entire design team can pile in without each person needing to buy a seat. For a tool trying to displace Sketch, this lowers the "why should I pay when I can just use Sketch for free" objection at the individual level. InVision validated this model works in the design adjacency.

Why it might not. Figma's value proposition is explicitly about simultaneous editing and team scale — the number of editors on a file is the value driver, not the number of files. A project-gated model captures almost none of the expansion revenue that comes from growing design teams. A startup that starts with 3 designers and grows to 15 pays exactly the same amount. That makes the model actively hostile to the land-and-expand motion Figma needs to eventually move upmarket. Additionally, project limits are gameable: teams will work around them by reusing a single file as a sprawling canvas.

Comparable companies: InVision (2015 era), Marvel. Both in prototyping, not full-workflow design — not a clean analog.

---

Model C — One-time perpetual license per seat ($69–99)

Structure: Pay once per designer, receive perpetual local access. Optional annual update subscription (~$29/year) for new features. Mirrors Sketch's 2015 model.

Why it could work. Designers in 2015 understand and prefer this model. Sketch was selling for its regular price of $99, with a free trial available — the price point has clear market acceptance. No subscription anxiety for individual buyers.

Why it might not. Figma's delivery model makes this structurally incompatible. Real-time multiplayer sync, server-side rendering, WebSocket infrastructure, and cloud file storage all require ongoing operational costs that a one-time license cannot fund. The moment a user opens a Figma file in the browser, the server is running compute — you cannot sell that as a perpetual license. A lifetime-deal pricing model for a cloud-native tool has a structural cost mismatch that compounds as the user base grows. Rejected.

---

Recommended model: Freemium per-editor SaaS subscription with free viewer access (Model A).

The buyer (product designers at SF-based SaaS companies, §4) already pays $15–25/month for InVision on top of $99/year for Sketch — a combined run rate of ~$25-35/month per designer in tooling. Figma can credibly position as a Sketch-and-InVision replacement at the same or lower all-in cost per designer, while eliminating the "developer needs a separate license" problem that inflates InVision's total team cost. The free-viewer model directly addresses the §4 buyer's biggest complaint: stakeholder review and developer handoff require zero additional licenses. The market size (§3) is small enough in 2015 that the freemium funnel may need to be intentionally generous — Figma cannot afford to gate too aggressively while trying to dislodge an entrenched native app. This argues for delaying paid tiers until the tool achieves genuine professional credibility, and pricing the paid tier to maximize conversion velocity rather than extracting maximum margin at launch.

---

Competitor Pricing Benchmarks

Note: Figma's category (browser-native multiplayer design editor) does not exist as of December 2015. All benchmarks are drawn from immediately adjacent tools designers use in the same workflow. Pricing reflects early-2015/late-2015 era. Sketch 2015 pricing confirmed from a December 2015 primary source; InVision and Marvel pricing from historical support documentation and contemporary reviews; Adobe CC pricing stable since 2013 launch. Where pricing has changed since 2015, the note column flags it.

Adobe XD announced October 2015 as "Project Comet" — no pricing announced, no public availability. Not included.

---

Willingness-to-Pay Estimation

Range: $10–25/editor/month.

Two anchors:

1. What the buyer already pays. A designer at a 30-person SF SaaS startup in December 2015 typically runs Sketch ($99/year ≈ $8.25/month) plus InVision Professional ($25/month) — a combined tooling spend of $33/month per designer. InVision's Starter plan is $25/month for unlimited prototypes for one user, and Sketch sells for $99 with a free trial available. Figma, if it genuinely replaces both tools, can charge up to the combined equivalent ($25-33/month) without asking the buyer to spend more in absolute terms — and would likely win on price even at $20/editor/month given the developer-handoff use case comes free.

2. The value ceiling. A designer at an SF startup earns roughly $120-150k/year fully loaded (~$80-100/hour). Eliminating one 3-hour weekly cycle of "export-from-Sketch → upload-to-InVision → compile-stakeholder-feedback → re-import" returns $240-300/month in time value per designer. At $15-20/editor/month, Figma prices at 5-8% of the value it claims to unlock — well inside the 10-20% rule of thumb for SaaS pricing relative to ROI. The real constraint is not WTP but belief that the tool reliably delivers the claimed value. In December 2015, that belief has not been established. Introductory pricing should be positioned to minimize regret risk, not to extract maximum value.

WTP caveat: No primary WTP research exists for this category in December 2015 — it is a category that does not exist yet. This range is triangulated from competitor pricing × adjacent-tool spend and should be treated as a hypothesis, not a measurement.

---

Recommended Price Point

Free tier → Professional at $15/editor/month (monthly billing) / $12/editor/month (billed annually) → Enterprise custom.

• Free: 3 active design files, 2 editors, unlimited viewers and commenters. Designed to be genuinely usable for solo designers and small projects — not crippled, but naturally pressure-tested once files exceed 3 or a third editor joins.
• Professional at $15/mo monthly / $12/mo annual: Unlimited files, full version history, unlimited editors, free viewers. This sits above Marvel ($12/month) and below InVision Professional ($25/month), which is appropriate positioning: Figma is more capable than Marvel but does not yet have InVision's proven track record with enterprise buyers.
• Enterprise: Custom, targeted at companies needing SSO, access controls, and IT-managed provisioning. Do not set a public price in 2015 — the positioning story is not yet proven at enterprise scale.

The annual/monthly split (20% discount for annual) creates a meaningful commitment signal and smooths cash flow. At $12/year, 10 editors on a design team cost $1,440/year — well within a line-item that a startup's head of design can approve without finance sign-off.

Price $15/month rather than $12/month on the monthly tier. The 25% markup over annual encourages annual commits and makes the monthly rate feel like a trade-off, not the default.

---

Pricing Psychology Considerations

1. Anchoring via the Enterprise tier. Without a public Enterprise price, the Professional tier at $15/month has no upper anchor and risks feeling expensive by default. Consider publishing even a vague range ("Organization plans from $25/editor/month — contact us") to anchor the $15 tier as the approachable option. The decoy effect works best when the middle tier — the one you want to sell — has visible alternatives above and below it.

2. Free viewer access as the real conversion mechanism. The standard SaaS freemium lever (free → paid conversion based on feature gating) is not the primary mechanism here. The driver is: a developer or PM uses Figma's view-only access for free, tells the design team it's useful, and the team converts. This means the free tier's value to non-editors determines conversion velocity more than the free tier's editor limits. Do not gate viewer access — it is both a growth mechanic and the core value proposition over InVision, where developer inspect access costs a paid seat.

3. Free trial vs. freemium. A time-limited free trial (14 or 30 days) is structurally wrong for this product. The conversion to paid requires a team to migrate their workflow — that takes months, not days, of gradual adoption. The free tier needs to last long enough for a designer to genuinely integrate Figma into their work before hitting a conversion prompt. Freemium with a project limit (not a time limit) gives the product time to prove itself.

4. Annual discount design. The 20% annual discount ($12 vs $15/month) is the standard market signal. Consider making annual billing the default for the checkout flow — most B2B SaaS buyers will accept annual if it is presented as the primary option rather than the opt-in. This accelerates cash collection at a stage when the company needs runway more than it needs pricing flexibility.

---

Projections from synthesis-grade inputs as of December 2015. No primary financial research was conducted for this section. Every number is either directly cited from competitive data or explicitly labelled as an assumption. Substitute your own numbers where you have better data.

---

1. Per-Unit P&L

Reference unit: one editor-month on the recommended Professional plan at $15/month (monthly billing). Browser-based design tool with real-time multiplayer infrastructure; no human fulfillment component.

Note: As the user base scales from 1k to 100k editors, cloud COGS per unit should fall toward $1.50–2.00, pushing gross margin to 70–75%. The 60% figure is appropriate for early-stage sizing, not at-scale projection.

---

2. Customer Acquisition Cost (CAC)

Base-case CAC: $150/paying editor.

This is keyed to a product-led growth motion dominant in the first 12 months: no paid acquisition, community presence at SF design events and design blog seeding, organic WOM through the developer-viewer viral loop. The $150 figure is built from a simple model:

• Assumed free-to-paid conversion: 5% of active free editors convert to paid within 12 months (assumed — no primary data)
• Cost to serve a free editor for the average 3-month trial period before conversion: $2/month × 3 months = $6/user
• For every 100 free editors, 5 convert: free-tier serving cost = 100 × $6 = $600 for 5 paid users → $120 CAC from free-tier costs alone
• Add ~$30/paid-editor blended for content marketing, conference presence, product seeding (assumed — substitute your own)
• Total blended PLG CAC: ~$150/editor (assumed: substitute your own if you have data)

This CAC is in the same neighborhood as early Slack (2014–2015 era PLG tools typically ran $80–200 CAC for SMB bottoms-up). It will worsen significantly if the product requires paid acquisition to overcome browser skepticism, and improve if the viral loop through free viewer access fires cleanly.

---

3. LTV Calculation

Subscription model: LTV = ARPU × Gross Margin % × (1 / Monthly Churn Rate)

• ARPU: $15/month
• Gross Margin %: 60%
• Monthly churn assumption: 3% (assumed — no primary data; 3% is a reasonable industry benchmark for early-stage B2B SaaS with moderate switching costs; Figma's switching costs from Sketch are high once adopted, but Figma has zero switching costs of its own in Dec 2015 — churn may be higher in year 1 as users revert to Sketch if browser performance disappoints)

LTV = $15 × 0.60 × (1 / 0.03) = $300 per editor

If churn is actually 2% (reflecting genuine workflow lock-in once the team has migrated files to Figma): LTV = $15 × 0.60 × 50 = $450 per editor

The wide range ($300–$450) reflects the fundamental uncertainty: does Figma achieve switching-cost lock-in fast enough to suppress churn? This is the biggest single economic variable in the model, and it cannot be resolved without live user data.

---

4. LTV : CAC Ratio + Payback Period

LTV / CAC = $300 / $150 = 2.0× (base case)

The conventional VC benchmark is ≥3×. For this product at this stage, that bar is wrong: Figma is targeting bootstrapped-to-seed-stage self-funded growth, not institutional venture growth. The relevant bar is ≥1.5× for bootstrapped unit economics to be worth pursuing. 2.0× passes that bar.

Two important upward adjustments the static LTV model misses:

1. Natural seat expansion. A team that starts with 2 editors and grows to 8 as the startup scales generates 4× the monthly revenue without any incremental CAC. Per-seat SaaS on a growing team produces NRR > 100% even at flat churn, which improves the realized LTV:CAC ratio materially.

2. Org-tier upsell. If 20% of teams eventually upgrade from Professional ($15/editor) to Organization/Enterprise, blended ARPU increases. Not modelled here.

Payback period: $150 CAC ÷ $9.07 contribution/editor/month ≈ 17 months. This is long, but acceptable for a product-led growth motion where the first paying customers are also your most reliable advocates. The viral loop (free viewers → team conversion → editors pay) means the effective payback on the acquisition spend is shorter than on the full COGS-loaded contribution.

---

5. Sensitivity Scenarios

---

6. Path to Break-Even

Break-even at approximately 572 paying editors per month, assuming $5,200/month in fixed costs (founder draw $4,000 + cloud infra baseline $800 + domain, tools, misc $400 — assumed: typical solo/two-person SF startup operational cost; substitute your own number).

Calculation: $5,200 / $9.07 contribution per editor = 573 editors.

At 5% free-to-paid conversion, that implies a free user base of ~11,400 active accounts — ambitious but not implausible for a design tool building bottoms-up in the SF SaaS community within 12–18 months of public launch. The bigger question is whether 11,400 active free users is achievable in year one against Sketch's dominant mindshare.

The honest read on these economics in December 2015: the unit economics are viable but fragile. Every assumption in this model — 5% conversion, 3% churn, $150 CAC, 60% gross margin — is directionally defensible but empirically unvalidated. The model lives or dies on whether browser performance is good enough to retain professional designers after their initial curiosity pass. If it is, the per-editor seat model with free viewer access is structurally one of the best designs in SaaS: low CAC through viral expansion, natural NRR uplift from team growth, and a value proposition that displaces multiple budget lines simultaneously. If it isn't, no pricing model rescues the unit economics.

---

The three risks that could actually kill this venture are Risks 1, 2, and 6 — and they are structurally entangled. Risk 1 (rendering performance) and Risk 2 (collaboration pain acuity) must both be true simultaneously for the thesis to hold: a browser tool that "mostly works" will not displace Sketch at 60–70% mindshare, and a browser tool with excellent performance but no acute switching trigger will be admired and not purchased. Risk 6 is the forcing function: approximately 60% of startups that secure pre-seed funding fail to progress to Series A, and Figma's specific version of that failure mode is spending its pre-seed runway on a rendering engine that either underperforms or arrives after Adobe has shipped a "good enough" collaboration feature to its existing Creative Cloud user base. Any honest December 2015 analysis has to acknowledge that all three of these risks are live and unresolved.

---

Load-bearing assumptions, ranked by severity of the "if wrong" consequence.

---

Assumption 1: A custom WebGL vector renderer can achieve native-quality performance within the available pre-Series A runway

Assumption: Figma's engineering team can build a WebGL rendering engine that achieves professional performance parity with Sketch's native Cocoa renderer — specifically, smooth pan/zoom on complex files, reliable text rendering, and sub-100ms responsiveness — before cash forces a Series A at terms that reflect an unproven product rather than a working one.

If wrong: The entire product thesis fails, not just the technical roadmap. §4's ICP (professional designers at tech companies) requires a performance bar that justifies switching from a tool they already know. §3's SOM projection assumes a credible share of the Sketch-dominated professional market; a tool with visible browser lag is not competing for that share — it is competing for the beginner or side-project segment, which has different pricing ceilings and much weaker word-of-mouth dynamics. The §7 revenue model at $12–25/editor/mo is unsupportable if the tool is perceived as a productivity downgrade.

Validation experiment: Build a performance regression benchmark — a specific test file (500+ layers, nested components, a representative Sketch import) that runs automatically against each major development build. Define a hard launch gate: if the benchmark does not pass 55fps median on Chrome Mac and 45fps on Chrome Windows by Month 8 post-incorporation, the public launch is delayed regardless of business pressure. Measure this, do not estimate it.

---

Assumption 2: The collaboration pain point is acute enough to drive active switching, not passive interest

Assumption: Designers at distributed SF/NYC product teams experience Sketch's async-by-default workflow — lock files, screenshot-to-Keynote stakeholder review, "ping me when you're done" coordination — as a genuine daily blocker, not merely a known inconvenience. Acute pain produces active switching; tolerable annoyance produces a waitlist that never converts.

If wrong: §4's ICP definition and §6's entire bottoms-up channel strategy collapse. If collaboration is a "nice to have," individual designers adopt Figma for greenfield or side projects but never push for team adoption, and the PLG engine stalls at the individual free tier. Without team pull, there is no conversion event, no paid workspace subscription, and no path to the ARR targets in §3's SOM. This also invalidates the central framing in the intake — "design is collaborative, the tools haven't caught up" — as a market insight rather than a product insight.

Validation experiment: Before writing any marketing copy or running any paid channel, conduct 30 structured interviews with designers at 10-person+ distributed teams. For each of three specific friction categories (simultaneous editing, developer handoff, stakeholder review), ask respondents to rate whether the friction is a "blocker" (4–5) or "annoyance" (1–3). Success threshold: ≥20 of 30 respondents score 4+ on at least two categories. If fewer than 15 do, the collaboration wedge is not the right entry point — consider leading with developer handoff (a less contested framing) instead.

---

Assumption 3: Bottoms-up individual adoption converts to paid team subscriptions at a rate that supports the business model

Assumption: Free individual adopters will pull teammates into shared workspaces and trigger paid team subscriptions at a 3–5% free-to-paid conversion rate within 90 days — consistent with B2B SaaS collaboration tools with strong network-effect loops in the 2013–2015 period. The freemium tier is an acquisition channel, not a permanent parking lot.

If wrong: §7's revenue model and all downstream §3 SOM projections require rebuilding. Freemium conversion rates average 2–5% for SaaS products, with top performers reaching 8–12% — but those top performers typically have either a very clear paywall trigger (Dropbox: storage limit) or a mandatory collaboration moment (Slack: team messaging that fails without a shared workspace). Figma's paywall trigger in 2015 is not yet defined with this precision. If conversion sits at 1–2%, the unit economics break at any customer acquisition cost above approximately $5/free user, which is lower than the CAC for virtually any channel beyond pure organic word-of-mouth.

Validation experiment: In the first 500 free signups, tag each user by acquisition source and whether they were invited by an existing user vs. discovered Figma independently. Track 90-day paid conversion separately by cohort. Gate any paid marketing spend on seeing ≥4% conversion in the invited-by-teammate cohort — that cohort is the signal for whether the collaboration loop is generating genuine pull. If it is not, revisit the free-tier friction and paywall structure before scaling acquisition.

---

Assumption 4: Adobe will not ship credible real-time multiplayer collaboration in XD within 18 months of Figma's public launch

Assumption: Adobe's Project Comet, announced October 2015, ships without meaningful simultaneous co-editing for at least 18 months after Figma's public launch — giving Figma time to establish paid team adoption and community reputation before the collaboration feature becomes table stakes across the category.

If wrong: Adobe's distribution advantages — Creative Cloud's install base, adobe.com domain authority, and existing enterprise procurement relationships — mean that a "good enough" collaboration feature in XD would neutralize Figma's primary wedge in exactly the segment (10–500 person design teams at tech companies) that §4 targets. §5's competitive analysis implicitly treats Adobe as slow; if that assumption is wrong, the durable differentiators become developer-handoff and the free view-only model rather than multiplayer editing. That is a defensible position but a materially narrower market entry than the intake's thesis.

Validation experiment: Assign one team member to track XD public beta releases and feature announcements on a monthly cadence starting from January 2016. Define a trigger condition: "if XD ships any form of simultaneous co-editing in public beta before Figma reaches 500 paying teams, immediately re-prioritize the developer-handoff and design-systems roadmap." Do not model Adobe's historical pace — Project Comet was announced after a relatively tight internal development cycle by Adobe standards, and XD's scoped-down initial feature set suggests it was designed to ship fast.

---

Assumption 5: Free view-only developer access creates genuine stickiness and internal network effects, not just goodwill

Assumption: Developers and PMs who receive a Figma view link — with no license required — become internal advocates who pressure design teams to stay on Figma, creating a cross-functional stickiness that makes churning off the platform costly even after Sketch adds a web-preview feature.

If wrong: Free view-only access increases adoption metrics but not retention. Developers are grateful but passive; the switching cost lives only on the designer side, which makes Figma's retention profile identical to any other design tool — dependent entirely on designer preference, with no cross-functional lock-in. This narrows the network-effects moat claimed in §6's channel analysis and means the business is more dependent on the designer community sentiment (and thus more fragile to the community-dismissal risk in the matrix above) than the intake implies.

Validation experiment: In the first private beta, explicitly survey developers and PMs who received view-only links: "If your design team were considering switching tools, would you advocate for keeping Figma?" Success: ≥60% respond "yes" or "strongly yes." Additionally, at 6 months, compare churn rates between teams where at least one developer/PM actively used view-only access vs. designer-only teams — if cross-functional teams churn at meaningfully lower rates, the network effect is real.

---

Assumption 6: The SF design community's tight network accelerates adoption rather than uniformly amplifying a negative first impression

Assumption: The same concentrated, Twitter- and Dribbble-active SF design community that gives Figma a low-CAC early-majority channel also means that performance or UX quality is observable and public from day one. The assumption is that the private beta produces enough credible social proof — from designers with community credibility — to establish "this is a serious tool" before the skeptical majority forms a fixed opinion.

If wrong: §6's bottoms-up word-of-mouth channel becomes a liability rather than an asset. A high-follower SF designer publicly posting "tried Figma, impressive idea but too slow for real work" in 2016 creates a reputational anchor that could take 12–18 months to displace in a community where that designer's opinion carries outsized weight. The "real designers use native apps" prior is already the default in December 2015; one credible public confirmation of it from inside the beta converts that prior from a hypothesis to received wisdom. This would not kill the business but it would materially extend the time to early-majority adoption and compress the window before Adobe ships.

Validation experiment: Curate the initial private beta list to include ≥15 SF designers with ≥5K Twitter followers and a history of sharing tool opinions publicly. Track unsolicited public mentions — not prompted posts, not sponsored reviews — over the first 90 days of beta access. Success: ≥5 unsolicited positive public posts from credible community voices. Failure: zero unsolicited public mentions, or any public dismissal from an account with ≥10K followers. If failure, run another performance sprint before the public launch, regardless of timeline pressure.

---

---

#1 — Define the performance benchmark and establish a hard demo gate before any external exposure

Action: Build a standardized 500-layer test file — nested frames, components, text, an imported .sketch artboard — and run it against defined thresholds (≥55fps median on pan/zoom in Chrome on a 2014–2015 MacBook Pro; ≥45fps on Chrome/Windows with equivalent mid-range GPU) before any designer from the Action 2 outreach receives a live product demo. Document the result in writing. If the thresholds are not met, the outreach in Action 2 continues as interviews only — no demos until the renderer sprint closes the gap.

Why it matters: §4 ICP Decision Criteria #1 is unambiguous: "performance parity with native apps" is the kill criterion — if the beta doesn't feel fast, every subsequent evaluation step ends there. §8 Risk 1 rates this high-likelihood, high-impact and §8 Assumption 1 calls for exactly this benchmark with exactly these thresholds. The risk of skipping this step is §8 Risk 10: "influential SF design-community voices publicly dismiss Figma as 'the Google Docs of design' — connoting toy, not tool — after a bad performance experience," creating a reputational anchor in the tight SF design community (§6.3) that takes 12–18 months to dislodge. Community capital spent on a bad demo cannot be unspent.

Expected outcome: A documented benchmark result by Day 14. Either (a) the renderer passes and Action 2's demo phase proceeds on solid ground, or (b) it fails and you have a specific technical milestone to chase rather than discovering the gap via a negative influencer post.

Estimated effort: 8–12 hours to build the test harness and document the benchmark protocol; 4–6 hours to run across platforms and record frame-time data. Engineering execution, but the founding team must personally review and sign off on the result before demos proceed.

---

#2 — Build the 50-designer target list and send the first 30 personalized cold emails by Day 14

Action: Map Dribbble and Design Twitter to identify 50 product designers who signal: they work on product teams (not print/graphic), coordinate with at least one other designer, and have expressed Sketch workflow frustration in tweets or Dribbble comments. Within that list, flag the ≥15 with ≥5K Twitter followers for priority tracking. Write 50 distinct one-paragraph cold emails referencing something specific about each designer's work or Sketch usage — not a template blast. Send the first 30 by Day 14. Target 10 scheduled 30-minute calls by end of week 2, structured as a pain interview first and a product demo second, with demos conditional on Action 1's benchmark result.

Why it matters: §6.3 names hand-selected Dribbble + Twitter seeding as the primary launch channel, with this exact approach prescribed: "Start by identifying 30 product designers on Dribbble whose work signals Sketch-fluency and team collaboration friction — cold-email them with a live demo link, and ask for 30 minutes — not a signup, a conversation." The calls simultaneously advance the §8 Assumption 2 validation quota (30 structured pain-acuity interviews required before public launch), recruit the initial beta cohort (§6 weeks 1–2 plan), and seed the §8 Assumption 6 influencer monitoring pool. This is the single action doing the most simultaneous work in the 30-day window.

Expected outcome: By Day 30, ≥15 calls completed, each scored on three pain dimensions (simultaneous editing, developer handoff, stakeholder review) using the §8 Assumption 2 rubric. At least 5 designers with beta access who have completed a full session on a real project. The high-follower subset is identified and tagged for unsolicited mention monitoring.

Estimated effort: 6–8 hours to build and research the 50-designer list; 10–15 hours to write personalized emails across the month; 8–10 hours in calls. Approximately 25–35 founding team hours, concentrated in weeks 1 and 2.

---

#3 — Lock .sketch file import to P0 in the current sprint and define a fidelity acceptance test

Action: In the next sprint planning session, move .sketch file import to P0 and protect it from scope creep. Define a specific acceptance criterion: a multi-artboard Sketch file with shared symbols and text styles should import with ≥90% fidelity without manual reconstruction. Track 30-day retention separately for beta users who import a .sketch file versus those who start from scratch — §8 Risk 3 identifies this split as the primary signal for whether the migration story is working.

Why it matters: §4 ICP Decision Criteria #2 is "file fidelity and migration path from Sketch — this is almost certainly the second question out of her mouth" after performance. §8 Risk 3 rates Sketch migration friction as high-likelihood, high-impact: "even designers who want to switch are blocked by team inertia and asset lock-in." The §7.2 pricing thesis — Figma replacing Sketch + InVision at a cost-neutral $15/editor/month — falls apart if a designer has to abandon 12 months of Sketch files to evaluate it. Every designer recruited in Action 2 will ask; "we're working on it" is not a credible answer in a 1:1 demo with an influential community designer.

Expected outcome: By Day 30, at least 3 designers from the Action 2 cohort have imported a real Sketch project and reported on fidelity. Either the import story is strong enough to use in demos, or specific fidelity gaps are identified and on the roadmap with explicit priority.

Estimated effort: 2–4 hours of founding team time for the sprint planning conversation, acceptance criteria definition, and retention tracking setup. The engineering work is the team's — but the product decision to protect this scope from being deprioritized requires explicit founder intervention.

---

#4 — Instrument the beta signup flow with acquisition-source tagging before the cohort exceeds 50 users

Action: Add acquisition-source capture to the signup flow: at minimum, distinguish (a) invited by a designer or teammate, (b) Dribbble/Twitter discovery, (c) Designer News/HN, (d) other. Pair with date-stamped records that support 30-, 60-, and 90-day retention and conversion tracking by cohort. Use UTM-tagged invite links per outreach wave so referral sources are machine-readable. A spreadsheet is sufficient at this scale; this does not require a full analytics stack.

Why it matters: §8 Assumption 3 and §7.3 unit economics both require the invited-by-teammate cohort to be separated from self-discovered users before any conclusions can be drawn about the bottoms-up flywheel. §7.3 states explicitly: "Tag the first 500 free signups by acquisition path; track 90-day paid conversion separately by cohort; if invited-cohort conversion is below 3%, redesign the team-invite paywall before any paid marketing spend." The §10.3 Month 3 go/no-go depends on this data. Retrofitting cohort tracking at 500 users is expensive; building it at 20 users costs an afternoon.

Expected outcome: Every beta signup from Day 1 forward is acquisition-tagged and date-stamped. By Day 90, the founding team can pull a clean retention and conversion report by acquisition source — the data needed to make the go/no-go decision before any public launch spend.

Estimated effort: 4–6 hours to instrument the signup flow, generate tagged invite links, and document the cohort schema. One-time setup.

---

---

Experiment 1: Is the collaboration pain genuinely blocking, or just annoying?

Hypothesis: Product designers at distributed 10–50-person SF/NYC product teams rate Sketch's async workflow — simultaneous file-locking, screenshot-to-Keynote stakeholder review, cross-OS developer handoff — as a daily blocker (4–5 on a 5-point severity scale) on at least two of three specific pain dimensions. Fewer than 20 of 30 respondents reaching this threshold means the collaboration pitch is the wrong primary wedge; the product should reframe its acquisition story around developer handoff, with multiplayer as a retention differentiator. (§8 Assumption 2; §8 Risk 2.)

Method: The calls from Action 2 serve as the instrument — no additional recruiting or spend required. Before showing the product, ask each designer to describe their current workflow for (1) working simultaneously with a second designer on the same file, (2) getting measurements and assets to a developer, and (3) collecting stakeholder feedback on a live design. After their own description, ask them to rate each pain: 5 = "this is a daily blocker that slows our team down," 1 = "annoying but we work around it easily." Record ratings verbatim. Do not frame the questions around Figma before the rating.

Success criteria: ≥20 of 30 respondents score 4 or 5 on at least two of the three pain dimensions, across at least 20 distinct companies.

Timeline and decision trigger: 28 days, anchored to the Action 2 call schedule. If the threshold is met → proceed with collaboration-first messaging in the public launch and the §6 community seeding plan. If it is not → shift the primary acquisition message to developer handoff; treat multiplayer as the retention story, consistent with §4's honest uncertainty note that "the collaboration story may be the retention story, not the acquisition story."

---

Experiment 2: Does the WebGL renderer pass the professional bar on the ICP's actual hardware?

Hypothesis: Figma's custom WebGL rendering engine sustains ≥55fps median on pan/zoom in Chrome on a 2014–2015 MacBook Pro, and ≥45fps on Chrome/Windows with equivalent mid-range GPU, on a representative 500-layer design file — AND at least half of the beta cohort with recent Sketch experience describe the performance as "comparable to Sketch" when asked directly. If either threshold fails, the §4 ICP's kill criterion is not cleared, and community seeding should not proceed regardless of schedule pressure. (§8 Risk 1; §8 Assumption 1.)

Method: Build the standardized benchmark from Action 1. Run it on target hardware with Chrome DevTools frame-time recording — quantitative half. Then seat 5 Action 2 beta users in front of the same file on their own machines (not a controlled test environment — their actual MacBooks, their actual Chrome builds) and ask: "Tell me honestly — how does this feel compared to working in Sketch?" Record verbatim responses without steering toward a positive answer.

Success criteria: Both must hold: (a) ≥55fps on Mac hardware, ≥45fps on Windows; AND (b) ≥3 of 5 beta designers describe performance as "comparable to Sketch" or better in open-ended response.

Timeline and decision trigger: 14 days for the hardware benchmark; 7–14 additional days for the subjective phase — 21–28 days total. If both pass → proceed with demos at scale. If fps passes but subjective response does not → there is a perception gap to address in the demo framing or onboarding before wider seeding. If the fps metric itself fails → run a focused rendering sprint; no community seeding until the quantitative bar is cleared, regardless of other GTM pressure.

---

Experiment 3: Will credible community designers speak positively about Figma without being asked?

Hypothesis: The ≥15 SF designers with ≥5K Twitter followers seeded into the private beta will produce ≥5 unsolicited positive public posts — tweets, Dribbble comments, Designer News mentions — within 90 days of receiving beta access, without any prompted or sponsored framing. If this does not happen, the tight SF design community's network effects (§6's primary channel advantage) are not firing: the product is generating goodwill but not the earned media that turns word-of-mouth into a compounding acquisition channel. (§8 Risk 10; §8 Assumption 6.)

Method: From the Action 2 target list, prioritize the ≥15 with ≥5K followers for first-wave beta access. Track unsolicited public mentions via Twitter search and Dribbble notifications — not prompted posts, not "please share your experience" nudges. Log each mention by account follower count, sentiment, and which aspect of the product they reference (performance, multiplayer, developer handoff, or other). Update the tracking sheet weekly.

Success criteria: ≥5 positive unsolicited public posts from beta designers; zero negative posts from accounts with ≥10K followers, within 90 days of beta access being granted.

Timeline and decision trigger: 90-day window; early warning at Day 30 — if zero unsolicited mentions have appeared from any beta user, the product has not yet produced a "magic moment" worth sharing, likely because the flagship differentiator (multiplayer) is not yet in the product (§6.3). If a negative post appears from a high-follower account before Day 30, pause external seeding and diagnose the specific issue — rendering, missing features, or demo framing — before any additional community exposure. Do not counter-message publicly.

Combined hard expense across all three experiments: <$200 in cloud compute and tracking tools. Combined founding team time: approximately 55–65 hours across 90 days, with the majority overlapping with Action 2 outreach activity.

---

Month 1 (Days 1–30): Prove the product can meet the professional bar

Target outcome: Performance benchmark passes (≥55fps on Mac, ≥45fps on Windows); ≥10 designers from the first outreach wave have completed a full design session in the beta on a real-work project — not a demo file; .sketch import running for at least 3 of those users; every beta signup acquisition-tagged from Day 7 forward.

Workstreams:

• Performance gate — Build the test harness and document the result by Day 14. If the benchmark fails, the remaining workstreams shift: outreach calls continue as pain interviews but no product demos until the renderer sprint closes the gap. This is a non-negotiable gate.
• Designer outreach, wave 1 — 50-designer list built; 30 personalized emails sent by Day 14; ≥10 calls completed by Day 30. Each call: pain interview first (collecting §8 Assumption 2 data), demo second (conditional on benchmark). Close by offering beta access with 3 invites to share at their discretion.
• .sketch import sprint — P0 designation confirmed in sprint planning; fidelity acceptance test defined; first real-world Sketch file imported and reviewed with a beta user by Day 30.
• Tracking setup — Acquisition-source tagging live on signup flow by Day 7.

Go/no-go at Day 30: If the performance benchmark fails with no credible path to clearing it in the following sprint, this is the company-level signal §8 Assumption 1 describes explicitly — not an engineering ticket, a scope or technology re-evaluation. Month 2's plan assumes the benchmark passes. If it does not, Month 2 becomes a focused renderer sprint with external outreach held at the interview stage only. Running community seeding on a product that fails its own performance benchmark is the specific failure mode §8 Risks 1 and 10 jointly warn against.

Green light for Month 2: benchmark passes AND ≥8 designers actively using the beta on real work.

---

Month 2 (Days 31–60): Prove the acquisition thesis

Target outcome: ≥30 active beta users on real projects (not onboarding walkthroughs); ≥25 of 30 pain-acuity interviews completed; preliminary pain scoring trending toward ≥18 of 25 scoring 4+/5 on ≥2 categories; first .sketch import retention split available; zero unsolicited negative posts from high-follower accounts.

Workstreams:

• Outreach wave 2 + interview completion — 20 additional personalized contacts; ≥25 interviews completed by Day 55. Use what the first 15 calls surface: which pain category is scoring highest in live conversation? Adjust the framing to lead with whatever resonates most — simultaneous editing, developer handoff, or stakeholder review — rather than leading with the product's self-description.
• Beta user depth program — Weekly 1:1 check-ins with the 8–10 most engaged beta users. Respond to every performance complaint within hours. The explicit question to ask each one: "What would this product have to do before you'd switch your daily Sketch workflow to it?" Their answers are the public launch roadmap input and the testimonial pool for Month 3.
• Adobe XD monitoring — One person tracks XD public beta releases monthly starting January 2016 (§8 Assumption 4). First checkpoint this month: what is XD's current public state? Does any form of co-editing appear in the feature list? If yes at any point in Month 2, immediately shift product roadmap emphasis to developer-handoff and design-systems features that are structurally harder to replicate inside Adobe's legacy codebase — per §8 Risk 5's explicit mitigation and the §5.4 "12–18 month window" framing.
• Experiment 3 tracking — Log unsolicited mentions weekly. If zero mentions have appeared from any beta user by Day 50, investigate whether the "magic moment" depends on multiplayer — the feature §6.3 identifies as deliberately cut from the initial release.

Go/no-go at Day 60: Two independent signals must both be green to proceed to Month 3's launch preparation:

• Pain interviews: ≥18 of the ≥25 completed interviews scoring 4+/5 on ≥2 categories (tracking toward the full 20/30 threshold)
• Active users: ≥20 using the product on real projects with no major renderer regression in the past 14 days

If either is red, Month 3 becomes continued product development and interview expansion rather than launch preparation. A public launch with weak pain validation against Sketch's 60–70% mindshare and an inbound Adobe XD (§5.4) generates expensive noise, not traction.

---

Month 3 (Days 61–90): Set up the public launch flywheel

Target outcome: ≥50 active beta users; ≥200 waitlist signups accumulated without paid spend; ≥5 unsolicited positive public posts from credible community voices (Experiment 3's threshold); a live waitlist landing page with at least one named designer testimonial; a documented go/no-go decision on public launch timing with explicit multiplayer staging.

Workstreams:

• Waitlist landing page — Build and publish a launch waitlist page at a public URL. One or two named testimonials from beta users willing to go on record — honest, not polished PR copy. The page must communicate what the free tier includes, and specifically that developer view-only access requires no license, because this is both the core competitive differentiation over InVision (§7.2) and the viral mechanism that drives the bottoms-up loop (§6.2). Do not speculate on pricing before tiers are finalized.
• Organic amplification — By Day 75, ask the 8–10 most engaged beta users whether they are willing to share their experience on Twitter or Designer News. Do not ghost-write. Any unsolicited post from a ≥5K-follower designer before the public launch contributes more signal than any paid channel at this stage and feeds Experiment 3's count.
• Launch timing decision — Assess multiplayer's development status by Day 75 and make an explicit staged decision. §6.3 is unambiguous: "Save Product Hunt for when multiplayer is ready — burning it on a beta is a one-time launch moment that should be staged." If multiplayer is ≤4 weeks from shipping, hold the full public launch to lead with it. If it is further out, plan a public beta announcement on Designer News + HN (the burst channels from §6 that can be reused for the true public launch) staged around current capabilities.
• 90-day cohort report — Pull the first retention data from the Action 4 tracking setup. The paid tier is not yet live (§3.3 SOM notes Figma remains free through Year 1), so the relevant metric is retention: what share of the invited-by-teammate cohort is still active — logged in and working on a file — at Day 60? If this is below 40%, the bottoms-up flywheel is stalling at the team-share step, and the team-invite paywall structure needs redesign before any paid acquisition spend is considered.

Go/no-go at Day 90: Three thresholds:

• Waitlist ≥200 without paid spend
• ≥40% of the invited-by-teammate cohort still active at Day 60 (retention proxy for eventual team-upgrade intent, since no paid tier exists yet)
• ≥5 unsolicited positive public posts from community-credible beta designers

All three passing → the public beta announcement and Designer News/HN launch are ready; Product Hunt staged for when multiplayer ships. Any one failing → push the launch date and address the specific signal. The §3 SAM is $4–12M in December 2015, with Sketch commanding 60–70% mindshare and Adobe shipping XD into an existing 12M-seat Creative Cloud install base (§5.4). Spending launch momentum on a product that hasn't cleared these thresholds moves the clock forward without moving the odds.