White label development for studios of 1 to 10
Send a briefbefore lunch.Ship it tomorrow,under your name.
Three fixed prices, published below. Nothing starts until it is paid for. Every delivery arrives with proof it meets the acceptance criteria you wrote.
The brief form opens shortly. Until then aurorastudio@nanocorp.app is read and answered.
- Ticket
- $250
- next business day
- Build
- $900
- next business day
- Feature
- $2,500
- 2–3 business days
The brief
Cart drawer for a Shopify theme, from the attached Figma frame, tested.
Acceptance criteria
6 of 6 passed
- 1Drawer opens on add to cart with no page reloadpassed
- 2Quantity updates without refetching the cartpassed
- 3Empty state matches the supplied Figma framepassed
- 4Focus is trapped while the drawer is openpassed
- 5Unit tests cover add, update, remove and emptypassed
- 6Lighthouse performance stays above 90passed
Not included
- —Checkout page markup
- —Anything touching your live theme
Test report
$ npm test
cart-drawer 18 passed
quantity 6 passed
0 failed 1.84sA client says yes to more than you can build this month.
You are the person who sells, scopes and delivers. At 09:00 on a Tuesday the question is not strategic. It is whether one small, well-specified piece of work can be back in your hands today, for a number you can quote your client now.
Hire a senior developer
$70k–$120k
a year
Plus 25 to 35 per cent in benefits, against a pipeline that is lumpy by nature.
Post it on Upwork
20 proposals
to sift
Then you find out on delivery day whether the code is usable.
Brief an offshore partner
$3k–$25k
a build
After discovery calls, a Slack channel, a scoping document and timezone lag.
All three are priced by the hour. Your margin is whatever is left after someone else’s clock stops.
Three products. The price is on the page.
No quote, no discovery call, no hourly rate. You pick the size, you edit the criteria, you pay the listed number.
Ticket
01$250
next business day
A self-contained bug fix, a small component, a test suite or an audit.
“Cart drawer flickers on iOS Safari. Repo attached.”
Pay $250 for a TicketBuild
02$900
next business day
A page or a set of components, built from your spec or your design file.
“This Figma pricing page, as React, using our tokens.”
Pay $900 for a BuildFeature
03$2,500
2–3 business days
A full-stack feature on an existing codebase: routes, schema, integration, auth.
“Client portal with invites, roles and Stripe billing.”
Pay $2,500 for a FeatureHow buying works today
The brief form is not built yet, so the order is reversed for now: you pay, then you send the brief by email and we write the acceptance criteria from it.
Nothing is started until you confirm those criteria. If we cannot write criteria from your brief, we reply with the questions that would unblock it. If the work is outside what we take, the full price is refunded and we say why.
One time, paid before work. No subscription, no hourly billing, no stored credits. Revisions inside the agreed criteria are included.
$0
Your first Ticket is free.
A real bug or a real component, delivered tested, with the checklist and the test report. One per company domain. We call it a Proof Ticket, because the only argument that wins here is finished work.
No card, no call. Send the bug, get it back tested.
Twelve minutes from a paragraph to a funded brief.
- 01
Write the brief
Paste a paragraph. Attach a zip, a design link or screenshots. No account, no password, no call.
2 minutes - 02
Read the acceptance criteria
Numbered, in your own vocabulary, with a “not included” list beside them. Every line is editable.
4 minutes - 03
Confirm and pay
Hosted checkout at the price on this page. Nothing is started until the payment clears and you have confirmed the criteria.
one page - 04
Accept the delivery
Next business morning: the source, the setup guide, the test report and your checklist marked line by line.
next business day
The criteria step is the one that earns the fixed price. It is editable, not merely approvable, and it names the two things you were quietly worried we would assume.
A delivery, not a file dump.
Four things arrive together. The receipt is as much the product as the code, because it is what lets you hand the work to a client under your own logo without reading every line.
Source
The code, packaged so your own developer drops it in. We never touch your infrastructure and never ask for repository access.
Setup guide
How to run it, what changed, what it depends on, and what we assumed.
Test report
The full automated run, with passed and failed counted, not summarised.
Checklist
Every acceptance criterion you wrote, line by line, with the evidence against each one.
The guarantee, in full
If a delivery misses a written acceptance criterion, we rebuild once at no charge. If the rebuild misses too, the full price is refunded.
No haggling, no store credit. Credit does not exist here.
Send one real bug. Get it back tested tomorrow.
Free, one per company domain, no card. Write what is broken and what done looks like, and the queue does the rest.