Built for agencies

Present the product, not the mockup.

Master gives every client their own workspace, their own brand system and a repository they can keep. Fewer rounds, cleaner handoffs, better margins.

Engagement flow

From pitch to handoff without changing tools.

01

Pitch

Build the concept live in the pitch meeting instead of showing a static deck.

02

Build

One workspace per client, with the brand's design tokens applied from the start.

03

Review

Share a preview link. Clients comment on the running app, not on a PDF.

04

Hand off

Push the repository to the client's GitHub, or transfer the project outright.

Client portfolio

Every client in one place, cleanly separated.

Projects, access and usage stay per client, so an audit or an offboarding is a two-minute job.

  • Invite the client to review; revoke access at the end of the engagement.
  • See credit usage per project when you bill the work through.
  • Remix a delivered project as the template for the next one.
master-magic.dev/projects
Client projects
Project
Access
Status
northwind-portal
2 editors
Published
atlas-booking
1 editor · 3 viewers
In review
lumen-intranet
Agency only
Building
ferro-campaign
Client viewer
Published
Handoff

A repository their engineers recognise.

No proprietary format, no export tax. React, TypeScript, Tailwind and Postgres, laid out the way a senior engineer would expect.

  • Connect GitHub and push straight to the client's organisation.
  • The client can continue in Master, in their IDE, or in both.
  • Environment variables and secrets stay out of the codebase.
src/
pages/
· Dashboard.tsx
· Clients.tsx
components/
ui/
lib/
· api.ts
supabase/
migrations/
Capabilities

Built for the way studios actually work.

Workspaces per client

Separate projects, separate access, separate billing lines — no shared folder chaos.

Their brand, not ours

Set colours, type and radii as design tokens once; every screen follows them.

GitHub handoff

Standard React and Postgres in a normal repository. Their engineers can take it from there.

Role-based access

Invite the client as a viewer or editor, and remove them when the engagement ends.

Publish on their domain

Point the client's domain at the project and ship without a deployment ticket.

Reusable starting points

Remix a finished project as the base for the next client and keep your house style.

Need procurement-friendly terms?

SSO, audit logs, invoicing and security review for studios that deliver into regulated clients.
See Enterprise

Frequently asked.

Can the client keep the code?+

Yes. Connect GitHub and push the repository to their organisation, or transfer the whole project to their account.

Can we work with several people on one project?+

Yes. Invite teammates to a workspace and control who can edit and who can only view.

Does it match a brand we already have?+

Set the design tokens — colours, typography, radius, spacing — and everything the agent builds inherits them.

What about maintenance after delivery?+

Keep the project in your workspace for a retainer, or hand it over and let their team run it.

Deliver the next project twice.

Once as a prototype, once as the product — from the same prompt.