Canva lays off over 1,200 people amid slowing growth
- ID
- 42883
- Status
- summarized
- Published
- 04 Nov 2026, 7:59 PM
- Fetched
- 04 Nov 2026, 8:30 PM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/11/04/canva-lays-off-over-1200-people-amid-slowing-growth/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 6.5
- Created
- 04 Nov 2026, 8:30 PM
- Tags
- Audience
- foundersdevelopersvibe_coders
What happened
Canva is cutting 22% of its staff — 1,271 people — with co-founder and CEO Melanie Perkins telling employees growth has slowed for the first time in a decade. The company is merging its product, growth and platform teams, reducing "subspecialisation" so staff take on broader responsibilities, and moving to hybrid work with a few office days per week. It cut its revenue growth forecast to 20% from 30% to absorb ballooning AI costs, has been shipping its own models to reduce reliance on third-party ones, and early investors marked its valuation down to about $35 billion, while ChatGPT and Gemini image generation make posters and presentations trivially easy.
Why it matters
Two concrete numbers to plan against: a 30%→20% growth-forecast cut attributed to AI costs, and a $35B down-round valuation, at a company that already runs its own models to cut third-party spend. If you are building a design, deck or content tool on top of someone else's model API, that combination says the margin squeeze arrives before the growth does — model your inference cost per paying user before you assume a wrapper business works, and price for the chatbot's free image generation as your real competitor, not the incumbent SaaS. The reorg detail also matters if you sell into or benchmark against orgs like this: merged product/growth/platform teams and less specialisation is the shape buyers will expect from smaller vendors too.
Discussion angle
Canva cut its growth forecast from 30% to 20% because of AI compute costs while ChatGPT and Gemini give away poster and deck generation — is the defensible move to self-host open-weight models like Canva is doing, or to stay on third-party APIs and compete purely on workflow and distribution?