Stoudio

Great design with an operating system to match.

Product and design help for teams that need to ship — without waiting on a hire.

A Practice by Matt Pearce

Start a project

Thirty minutes, what's your company, product and what's stuck.

Next availability January 4

Three distinct Products

Swipe sideways to see the other products.

Current-state report

3-6 weeks

A written picture of how product and design actually run — then whether to retain, hire, or wait.

  • Product and design workflow

  • Design-to-dev workflow

  • Design systems

  • Design AI practice

  • Product AI practice

  • Team alignment

  • Team vision

Continual design retainer

60 hours / month · three-month minimum

  • Experience design & development

  • Service design

  • Product strategy & vision

  • AI product strategy & development

  • Design systems

  • Operating system

Design system

4-8 weeks

A system the product can ship with — tokens, components, and the path from Figma into code.

  • Foundation tokens

  • Core components

  • Figma library

  • Figma-to-code path

  • Multi-brand theming

  • How the system is used

Selected projects

Why Stoudio

  • Part of the team

    I join the rituals and tools you already have. Not a parallel agency track.

  • The person you talk to does the work

    Solo practice. No account manager, no junior bench.

  • Onboard in days

    A hire takes months. Work here starts in days, not a quarter of recruiting.

  • Remote, in your stack

    Figma, code, Slack, Linear. I'll sit in a room when the work needs one.

  • Leave it written

    Briefs, critique, and handoff stay documented. The operating system doesn't live in my head.

Who is behind Stoudio design?

I'm Matt Pearce. I ran product design atNesto for a Canadian mortgage product, built a design practice from nothing inside regulated pharma-tech atMontrium, designed and built atAppDirect, and shipped front-end as a founder atRekwai

That's the work this practice sells: how a product company designs, decides, and ships when there isn't a department to do it. Sometimes a current-state report first. Then a design system, reserved monthly capacity, or both.

Matt Pearce
  • 4

    Design systems created

  • 25

    Partner brands tokenized

  • 14

    Years of experience

  • 200+

    Prototypes created

  • 150+

    User testing sessions

  • 12

    Design sprints completed

Frequently asked questions

  • Teams without a design function, or with one designer stuck in tickets. Seed to Series B is typical — later-stage works when design is still a side job. Messy product focus, no system, weak AI practice, or unclear product target are common reasons to start.

  • Not extra hands for a sprint, a logo, or a team that already has a design lead. Not product and design HR services. Not a report you want so you can downsize.

  • Only when the picture is messy. If the work is already clear, we can start a retainer or a design system without a report.

  • Named tracks against reserved monthly hours — experience design, service design, product strategy, AI product work, systems, and the operating system those tracks run on. Unused hours do not roll.

  • After a short fit call and a proposal. Next availability is shown in the header. Work starts in days once we agree — not a quarter of recruiting.

  • No. Solo practice. The person you talk to does the work — no account manager, no junior bench. I join your rituals and tools, not a parallel agency track.

  • Products are priced as a monthly retainer or a fixed engagement, not an open timesheet. Numbers come in a private proposal after we talk — nothing is published here.