8
Studio options
on the menu
on the menu
Now booking · 3 slots remaining this quarter
Sites. Brands. Systems. Words.
Made well. Shipped this month.
A boutique studio for operators who’d rather see it built than discussed. Fixed scope. Flat price. You sign off when it matches the version in your head — not when a calendar hits.
From $5k
Where most
projects start
projects start
7–28d
Typical window
scope to ship
scope to ship
Your nod
Closes every
project
project
§01 The work
Eight options. One studio.
Pick one. Stack two. Hand us a strange one in the Bespoke slot. Every engagement gets a fixed scope, a flat price, and a target ship window. The number on the card is where it starts — your scope sets the rest.
§02 How we work
Scope it. Build it. Until you nod.
The brief is never the hours. It’s making the thing match the version you saw in your head — and not closing the project until that’s true.
Day 01
01/
Scope the outcome
20-minute call. By end-of-day you have a one-page scope: the deliverable, the price, the ship window, the terms. Sign it and we start the next morning. Not a proposal — a contract.
Deliverable · signed scope
Through the build
02/
Options, not a finished thing
Updates as the work moves. When a creative call comes up — typography, layout, color, voice — you see options, not a finished thing you have to react to. Nothing is locked until you say so, and every choice can be walked back.
Deliverable · the work in progress
Sign-off day
03/
Done is when you say so
Files, access, documentation, and a handoff video — the moment you nod. We don’t invoice the final or close the project until the version on screen matches the one in your head. The calendar is a target, not the deciding vote.
Deliverable · handoff pack
§03 The kit
What we ship with. No fluff.
Proof by craft, not by quotes. Here’s the actual stack under the work — the tools we reach for first, the artifacts we hand back, the things you’ll never see on our deliverables list.
Build
- Next.js 15 · React 19 · TypeScript
- Tailwind · shadcn · custom design tokens
- Vercel · Cloudflare · CMS of your choice
- Postgres · Supabase · edge runtimes
Design
- Figma — but we don’t live there
- Code-first design systems, not handoff PDFs
- Editorial typography · OKLCH color · motion
- Accessibility baked in, not bolted on
Words
- Voice capture before a single line is written
- Sales pages · launch emails · sequences
- Document typography that reads like a magazine
- No AI sludge. No committee prose.
AI & Skills
- Custom Claude Code skills, installed in your repo
- Prompt libraries · style guardrails · evals
- Generative content engines for retainer clients
- Tooling that compounds — not one-off automations
§04 The terms
Same rules. Every job.
Eight services, one rulebook. No hourly. No open-ended retainers hiding behind “scope creep.” No invoice-day surprises.
01 · Scope
Fixed, in writing, before we start.
You leave the call with a one-page scope: deliverable, flat price, ship window, sign-off terms. Signed before we touch the work.
02 · Price
Flat. Quoted to the outcome.
No hourly. No surprise add-ons. Bundle services and we quote them together. The number on the scope is the number on the invoice.
03 · Sign-off
Yours, and only yours.
The work isn’t done until you say it is. We don’t close the project, and you don’t pay the final, until the version on screen matches the version in your head.
04 · After
You own it outright.
Files, codebase, design tokens, accounts — all yours. Stewardship retainers are optional, never assumed. We’re not your shadow team.
§05 Answers
The questions founders actually ask.
Founders, operators, and small teams who care what their work looks like. The kind of people who know a generic template when they see one and refuse to ship it. We're built for premium boutique work — if you need fifty deliverables a month at the lowest possible price, we're not your studio.
Because the work is hand-built. There's no offshore production line, no junior-only team, no template farm. Every project gets the senior eye from scope to ship. The price reflects the craft, not the hours.
Every engagement runs until you sign off — not until a calendar date hits. We don't close the project, and you don't pay the final, until the version on screen matches the version in your head. Hours aren't the brief; getting it right is. The calendar is a target we work toward, not the deciding vote.
Yes — most engagements do. Brand + site + copy is the most common stack. Bundles are quoted together and ship in one window. Tell us the outcome on the call; we'll scope the bundle.
A Claude Code skill is a packaged, installable workflow your team invokes by name inside Claude. We take your repeated, hard-to-delegate work — briefs, onboarding flows, audits, content ops — and encode it into a skill. One install. Your team uses it forever. Most studios aren't selling this yet.
If you'd rather have a monthly engine quietly producing high-craft content while you run the business — yes. If you have an in-house content team already shipping work you're proud of — no. It's a premium tier on purpose; we cap the roster so we can keep the quality up.
Yes. If your problem is strange, specific, or doesn't fit the menu — tooling, microsites, custom apps, internal portals, generative content engines — bring it. The Bespoke card exists for exactly this. We'll quote with the scope.
§06 Next step
Tell us what you want made.
We’ll scope it the same day.
20-minute call. If it’s a fit, a one-page scope lands in your inbox before you go to bed — flat price, ship window, sign-off terms. If it isn’t, we’ll tell you who to call instead.
Response timeWithin 1 working day
Fit or no fitStraight answer, always
Slots this quarter3 remaining