unbland Start a project
fixed scope
your
repo
STUDIO When the prototype needs to become the product

The pack is the look. Studio is the build.

Design, the product, and the agents around it. For founders who already have a prototype and need it to hold up in front of a customer.

Start a project Send the repo
Scope before any invoice You keep the repo Design and code on one brief
Look
The same eye as the packs, on the product itself
Product
Screens, payments, and a repo the next hire can read
Agents
The repeated work, still running after we leave
Yours
Files, Figma, and accounts in your name
Gilt weather Tiger print Paper ridge Pigment coast Ember petal Cobalt print Stillwater Poster red Night iris Ridge atlas Pearl blossom Blue ridge Rain city Dune sea Peach orchard Vesper violet Moon water Open meadow

A prototype gets the meeting. A product gets the customer.

The usual path is a designer, then a dev shop, then someone else for the AI. Three handoffs. One confused launch.

The usual path

Three briefs, three invoices, and a prototype that still isn't the thing people pay for.

The pitch looks finished. Signup, payment, and the empty states were never in anyone's scope.

separate invoices a long gap another round of fixes
Studio

One brief, from the brand to the deploy. It looks like the packs, and it actually runs.

You leave with the product, the files, and a way for a customer to pay.

one team fixed price

What we take on.

Steady the prototype, design and build the first version, or put agents on the work you repeat.

Steady

Hold it together

The agent got you a working demo. We go through sign-in, data, payments, and the parts that break when someone who isn't you tries it.

auth.ts
− session trusted the client
+ session checked on the server
review · cleanup · fixes · speed
Shape

First version

Brand, the screens, and the build. Something a customer can use, not a tour for a pitch.

North live
Pay · $48
Agents

The repeated work

Replies, follow-ups, invoices, the answers your team already knows. Models only where they change the product.

Support replies Follow-ups Inbox triage Invoices Team answers
Pipelines Search over your docs A chat that cites sources Hooks into the model A voice that sounds like you
Surface

The rest of it

A face, a site, or a phone app, scoped as its own job. Not a bundle you didn't ask for.

Brand Interface Web iOS and Android Product calls Connecting your tools

Start with a look. Pay for the ship.

The first pass is free. After that, a fixed price for the first version, or a month at a time once you're live. No hourly meter.

Start here

First pass

Free

Send the repo. You get a plain list of what's fragile, and a price for each fix. Stop there if you want.

Timing. Notes back within two days. Fixes, if you want them, start the week after.
Payment. The read is free. Each fix is priced on its own.
  • Bugs and risky spots, each with a price
  • Sign-in, data access, and payments, if those are the holes
  • Crashes, slow pages, and a checkout that finishes
  • Cleaner code, notes a new developer can follow, and a list of what to build next
Send the repo
fixed price
The product

First version

from $15,000

You have the prototype. We turn it into the thing with a brand, a working product, and a way to get paid.

Timing. About six to eight weeks, agreed before we start.
Payment. Three parts: kickoff, midpoint, ship.
  • Name, mark, and how it should sound
  • Screens in Figma you click through before we write the app
  • The web app, signup, admin, and payments
  • A simple dashboard, and AI only where it belongs in the product
  • Brand files ready for whoever writes the launch
Start a project
After it ships

Stay on

from $10,000 /month

You're live. You want a small team shipping a feature a week, without opening a hiring req.

Billing. Month to month. Pause when you want.
Leftover days. They roll into the next month.
  • One feature a week, shown when it's done
  • A shared thread. We answer on the same working day
  • A page and tracking when you run a campaign
  • Agents for the replies, the follow-ups, and the weekly numbers
  • A monthly look at what moved, then we pick the next month. The repo stays yours
Start a project

The ship date sits in the scope. If we miss it, the last payment waits until it ships.

Three steps. Then it's yours.

1

A short call

Tell us what the prototype does and where it stalls. We'll say if this is the wrong job.

2

A written scope

Price, list, and a date, before anyone starts. You can say no and keep the notes.

3

Build and hand it over

You see it each week. At the end: the repo, the files, and a short window of fixes on the same price.

One brief. The same people stay.

You don't meet a seller and then get handed off. Design, product, and the AI happen together.

Design
Brand and screens

Type, color, and layouts that don't look generated.

Agents
The repeated jobs

Built to keep running after the first demo.

Product
What people do

The flows, the empty states, the job the product is for.

Engineering
The app

Payments, and a repo the next person can read.

Interface
Where it lives

Web, iOS, and Android, when the product needs more than one.

Handoff
In your name

Docs, files, and accounts. Nothing locked behind us.

Questions?

Still stuck? Email dean@unblandai.com.

{{f.a}}

Got a prototype? Show us.

Send the repo or a link. We'll reply with whether we should take it, and what the first pass would cover.

Start a project

Just want the styles? See the packs.