Stop reacting to AI.
Start architecting it.

Most teams don't have an AI problem. They have a governance, consistency and tool-sprawl problem. AI just exposed it.

Designers use tools nobody approved

Some pay for them on their own card. Output varies by person, and nobody can say what the team actually spends.

Vibe-coded screens reach production

They look close enough to pass review, then drift from your tokens and components one merge at a time.

No way to propose change to the system

So people work around it, and the design system team finds out after it ships.

How it works & pricing

One week to diagnose. Then we build.

Start with a 1-week audit, pick the build that fits, and see your total before we ever talk. Fixed prices, published, with the audit fee credited if you continue.

  1. Step 1

    Design Stack Audit

    1 weekAlways included

    I interview a few of your designers and engineers to see how design work actually moves.

    You get a written recommendation covering:

    • Where design time goes
    • How AI enters the product
    • How changes reach your design system
    • Whether a proof of concept is worth building

    S$ 1,500 fixed

    Yours to keep, even if we stop there

    Credited toward Guided or Embedded if you continue within 30 days

  2. Step 2

    Choose how we build

  3. Optional

    Team Workshop

    Half or full day

    Runs once the system exists, so your team trains on its own components: the AI-assisted workflow, blind-brainstorm-then-compare, and how to propose changes to the system.

    S$ 600 half day S$ 900 full day

Your plan

Pick Embedded or Guided to build your plan

Audit
S$ 1,500
Choose a build
—
Workshop Optional
—
TotalS$ 1,500Add a build to see your full total

What people ask before they book.

I'm a designer, not the budget holder. How do I get this approved?

Lead with how small the first step is: a one-week audit at a fixed price, ending in a written recommendation, with nothing after it committed. Once we've confirmed it's a fit, I'll send you an overview and an approval-request template you can forward. Until then, here's the one-line version for whoever approves spend:

"One week, S$ 1,500 fixed, and credited toward the build if we continue within 30 days. We get a written recommendation on where design time goes, how AI enters our product, and whether a build is worth doing. It's ours to keep, and nothing further is committed."
Why pay S$ 1,500 before we know it will work?

Because the audit is how you find out, at a size that's easy to approve. In one week I talk to a few of your designers and engineers, then write up where design time goes, how AI enters the product, how changes reach your design system, and whether a proof of concept is worth building. The price is fixed, the recommendation is yours to keep even if we stop there, and if you go on to Embedded or Guided within 30 days, the fee is credited toward it.

What if the audit says we don't need this?

Then I'll tell you, and you'll have spent S$ 1,500 instead of a much larger build on the wrong thing. You still keep the written recommendation, and nothing after the audit is committed.

What will all of it cost? Any surprises?

The plan above shows your total before we ever talk. The audit is S$ 1,500, credited toward Embedded or Guided if you continue within 30 days. That makes audit and Embedded S$ 5,000 in total, fixed with a 50% deposit. Guided is S$ 1,250 a month for 3–6 months, with the audit fee credited against it. A team workshop is optional, from S$ 600 for a half day. The only thing quoted separately is travel for on-site days.

Has this worked for other teams?

The tutorials and Builder Series on this site are a public preview of how I work. I don't name client engagements without their written permission, so on the fit call I'll walk you through the client work I can share.

Who owns what we build?

You do. Everything built during the engagement belongs to your company: the design variables, components, context files for AI tools, and the documentation. I only describe the engagement publicly with your written permission.

Do we need a design system team?

For Embedded, yes: the proof of concept is built with them. For Guided, a design lead with a few hours a week is enough.

We're a small team or an early-stage startup. Is this for us?

Probably not yet. Below five designers and without a design system, the audit would cost more than it saves. The free Pattern Library and the tutorials are a better place to start.

Can you give a talk instead?

Yes, separately. A 45-minute talk gets everyone on the same page about how AI is changing design work, and leaves your team with a short list of what to fix first. The workshop is for putting it to work: half or full day, hands-on with your own design system, so your team can work the new way on its own.

Not sure if it's a fit?

Book 30 minutes and bring whoever else should be in the room.