long-form-interview· Melanie Perkins

The woman behind Canva shares how she built a $42B company from nothing

Durable companies are built by planning from a dream state (Column B) rather than from the bricks in front of you (Column A), then collapsing the gap between imagination and reality through a disciplined chaos-to-clarity process: crazy-big goals broken into mission pillars, taking microscopic first rungs, iterating on rejection, celebrating each rung, and refusing to import other companies' playbooks wholesale.

planningvision-led strategycrazy big goalsproduct craftfundraisingpitchingcompany culturephilanthropyAI integrationauthenticity88% confidence

Why this is in the corpus

Melanie names and grounds an entire operating system in specific Canva decisions — the 2012 pitch deck she still uses, the 100+ investor rejection loop, the 2-year front-end rewrite rubber-ducky board, the mission pillars (empower everyone, to design anything, with every ingredient, in every language, on every device), the Two-Step Plan, the 2050 wall, the Canva Foundation's $150M commitment to GiveDirectly. It is a founder externalising a coherent planning discipline, not an observer summarising principles.

Summary for skimmers

Read this for five linked mental models: Column B thinking (plan from the dream, not the bricks), chaos to clarity (add clarity in microscopic increments via visual artifacts), crazy big goals (feel inadequate before them, celebrate each rung), authentic scaling (do not borrow bricks from other companies' houses), and the Two-Step Plan (build a valuable company AND do the most good you can — each fuels the other).

Decision layer

Start here: the tensions that actually matter

If this episode is worth anything, it should sharpen judgment — not just hand you clean principles. These are the contradictions a thoughtful founder actually has to navigate.

within episode

Column B dream vs. microscopic first step

Claim A

Start from a crazy-big 10- or 25-year vision — the world you want to live in — and work backwards. Reasonable goals get abandoned at the first roadblock; only crazy-big goals generate the willingness to will things into existence.

Claim B

The first step toward that vision has to be embarrassingly small and made before you have any answers. "A ladder to the moon" means the first rung is writing the idea down.

Why it matters

Most founders do one or the other: either they dream without shipping, or they ship without a vision big enough to earn the years of embarrassing early work. Perkins's whole method is holding both at once.

How to hold it

These are not opposed — they are sequence. The vision is required precisely because the first step is too humiliating to take without one. Skip the vision and the tiny step feels pointless; skip the tiny step and the vision stays on a wall.

within episode

Reject a hundred investors vs. let rejection rewrite your pitch

Claim A

The investors were wrong. It was clear in my mind it was the future, and I had to persist past 100 Nos.

Claim B

The feedback embedded in rejection — "market's not big enough," "you're the same as X" — made the pitch deck stronger. Each No became a new slide pre-answering the next investor's objection.

Why it matters

Founders who treat rejection as noise never update and die slowly. Founders who treat rejection as signal change product-market fit. Perkins did neither — she kept the vision fixed and let the 100 Nos rewrite her pitch.

How to hold it

Conviction about the *destination* is non-negotiable; conviction about the *articulation* is wrong by default. Persist on the vision; iterate aggressively on how you explain it.

within episode

Authentic bricks vs. borrowed playbooks at each new scale

Claim A

Every time the company doubles, all systems break; you have to reinvent them for the new scale.

Claim B

But the reinvention must be authentic to Canva, not taken off the shelf from a bigger company. "Many times we went to try what worked at some other company, and it didn't work out so well."

Why it matters

This is why mid-stage companies often decay — they hire from scaled companies and paste in the scaled playbook at 1/10 the size. Perkins's signal: reinvention is fine, *borrowing* is the trap.

How to hold it

Scale-driven rebuilds are mandatory; scale-driven imports are not. Use the forcing function of breakage to build the *next* Canva-native system, not to install someone else's.

within episode

Two years of no shipping vs. product-company motivation

Claim A

The front-end rewrite that was supposed to take 6 months took 2 years, during which a product company shipped no product — the engineering rewrite was genuinely essential (unlocked cross-platform, RTL languages, 2.5k engineers, real-time collaboration).

Claim B

But shipping and customer feedback are the core motivation for a product team — two years of silence is a recipe for no fun and investor pressure.

Why it matters

Founders routinely under-estimate platform work (6 months → 2 years) and then either kill it halfway or let the team implode. Perkins shows the third path: commit, but invent visible internal shipping even when external shipping stops.

How to hold it

They coped by gamifying the tunnel (rubber-duck game board, weekly stand-ups, emergency lane). The real resolution: when a platform rewrite is genuinely load-bearing for the next decade, you commit; but you must manufacture artificial milestones to keep morale compounding.

Briefing

What survives the editorial filter

This page should feel like a smart colleague already listened for you and left only the operating logic worth keeping. Not everything said in the episode makes it through.

Trust signal

direct_practitioner_account

Guest type: practitioner.

Best used for

Best used when a founder is deciding how to plan at a 10-year horizon, how to iterate a pitch deck through rejection, how to avoid importing other companies' playbooks at scale, how to set and celebrate company-wide goals, how to choose a wedge problem, or how to integrate philanthropy into the core business rather than bolting it on.

Hold lightly

Some ideas (vision-led planning, work-life balance, community feedback) are common advice; the value is in Canva-specific integration and scale proof, not raw novelty.

Trust layer

Why this confidence score is what it is

Confidence here means confidence in durable, transferable insight — not just whether the episode is interesting.

Evidence quality

High — nearly every principle is grounded in a named Canva decision or anecdote (rubber-ducky board, 2012 deck, 100+ rejections, GiveDirectly $50M).

Generalisability

High — the models transfer cleanly to any founder-led company and several apply to creative practice broadly.

Clarity

High — Melanie names concepts explicitly (Column B, chaos-to-clarity, Two-Step Plan, mission pillars) and gives worked examples for each.

Consistency

High — the planning discipline is internally consistent across fundraising, product, hiring, scaling, philanthropy.

Why not higher

Some ideas (vision-led planning, work-life balance, community feedback) are common advice; the value is in Canva-specific integration and scale proof, not raw novelty.

The Plays

Try these this week

Verb-first executable actions — each one tied to a stated outcome in the episode.

Iterate your fundraising pitch through rejection feedback (100+ pitches)

Outcome: Transform investor rejections into pitch refinements by systematically adding slides that address each rejection reason until the deck resonates.

“Melanie Perkins — The woman behind Canva shares how she built a $42B company from nothing”
— Melanie Perkins
100 per fundraising period
  1. 1

    Pitch to investors broadly

    Speak to literally everyone; cast a wide net rather than being selective

  2. 2

    Catalog rejection reasons

    Track the specific objections: market size, competitive positioning, problem clarity, etc.

  3. 3

    Add a slide per objection

    When told 'market's not big enough,' add a market size slide; when told 'you're the same as X,' add competitive landscape slide

  4. 4

    Pre-answer objections upfront

    Move refined answers to early slides so future investors see them before raising the concern

  5. 5

    Continue pitching with updated deck

    Each iteration makes the pitch clearer and stronger for the next round of investors

Before you start

  • · A core vision you believe in strongly enough to persist through 100+ rejections
fundraisingearly-stage0-1

Close feature request loops systematically (1M+ annual requests)

Outcome: Tally community feature requests at scale, deliver them to product teams, and close 200+ loops per year to build what users actually want.

“Melanie Perkins — The woman behind Canva shares how she built a $42B company from nothing”
— Melanie Perkins
ongoing1000000 per 1 year
  1. 1

    Collect feature requests from community

    Gather more than 1 million requests per year through structured feedback channels

  2. 2

    Tally and categorize requests

    Dedicated team breaks down requests by theme, frequency, and impact

  3. 3

    Deliver tallies to product teams

    Route categorized requests to relevant product groups for roadmap consideration

  4. 4

    Build and ship requested features

    Prioritize features knowing each represents many more users who didn't submit formal requests

  5. 5

    Close the loop with requesters

    Inform requesters when their feature ships; aim for 200+ closed loops per year

Stop or pivot when

  • →200+ loops closed per year as success metric

Before you start

  • · Infrastructure to collect, categorize, and route feature requests
  • · Product team capacity to act on community input
productcommunity1-1010-100

Run hundreds of online user tests to validate product decisions

Outcome: Conduct hundreds (to thousands) of remote user tests to catch friction points and validate that 10 random users' feedback generalizes to large populations.

“Melanie Perkins — The woman behind Canva shares how she built a $42B company from nothing”
— Melanie Perkins
100 per ongoing
  1. 1

    Recruit random users online

    Use platforms like UserTesting.com to find participants who aren't familiar with you

  2. 2

    Observe them use the product remotely

    Watch for hesitation, confusion, or failure to understand features via screen share

  3. 3

    Collect frank feedback

    Users are more honest when it's just them and their camera, not in-person with the founder

  4. 4

    Identify patterns across ~10 users

    Validate that feedback from a small sample (10 people) represents broader user behavior

  5. 5

    Iterate product based on findings

    Fix friction points, clarify UI, improve onboarding based on observed pain points

Stop or pivot when

  • →~10 users to validate a pattern

Before you start

  • · Access to remote user testing platform
  • · Time to run and analyze tests
productuser-research0-11-10

Tensions surfaced

Contradictions and trade-offs the episode raises — judgment calls a thoughtful operator has to navigate.

Tension

Tension: Column-B thinking (find new framing) vs Column-A optimization

Column-B suits category creation; Column-A suits category maturation.

“Column-A optimizes. Column-B reframes. Different jobs.”Melanie Perkins

Durability: Durable.

Productive tension.

Corpus connection

Where this episode fits for retrieval

What kinds of decisions this briefing is best pulled into.

Primary decisions

  • • how-to-plan-long-term
  • • how-to-fundraise
  • • how-to-design-product
  • • how-to-set-goals

Temporal flag

timeless

Limitations

Where to hold this lightly

A trustworthy research product should tell you where the extraction is strongest and where it is still inferred, constrained, or partially uncertain.

Strongest grounded parts

  • • Column B vs Column A with the castle-on-the-hill metaphor
  • • Chaos to clarity with the pitch-deck and visual-artifact examples
  • • Crazy big goals coupled with celebrations (plate-smashing, doves, La Tomatina)
  • • 2-year front-end rewrite with the rubber-ducky game board
  • • 100+ investor rejection loop producing the problem-first pitch deck
  • • Mission pillars (design anything, every language, every device)
  • • Two-Step Plan with GiveDirectly $50M + $100M commitments

Weakest inferred parts

  • • The Mission-Pillar-Goal-Celebration framework is editorially assembled from Melanie's descriptions — she discusses the parts but does not name the framework as such
  • • The do-not-borrow-bricks principle is implied from multiple examples rather than stated as a rule

Needs verification

  • • Exact count of 100+ investor rejections vs yes
  • • $42B valuation and $3.3B ARR figures quoted by host