A five-day build is not the impressive part. The handover is.

Every small studio eventually gets the same request: a client wants a working product in two weeks, and the studio has designers, a project manager, and no one who wants to spend three months on backend work.

There are two common answers. Hire for the project and let the hire go afterwards. Or say yes, subcontract to the first freelancer who replies, and spend the next six weeks managing something nobody can see. Both answers cost more than the invoice suggests.

A third answer is duller: buy the build from a partner who only does builds, agree the scope and the price in writing, and take delivery in a form you can maintain.

What "five days" actually means

Five days is enough when the scope is small and honest: one form that really submits, sign-in with two roles, one integration with a system the client already pays for, an admin screen for ten cases rather than a hundred.

It is not enough when "the app" turns out to be three products. Saying that before the quote is worth more to a studio than a delivery date that slips in week six.

What makes it fast is unglamorous. Sign-in, data models, payments, deploys and store submissions are not rebuilt from scratch every time; the handwork goes into the parts a client will actually notice. That is the whole trick, and it is why a small studio can quote a fixed price instead of an estimate with a range.

What you receive at the end of a slice

  • The repository, with access in your account
  • A running environment on a domain you control
  • A short document: data model, environment variables, how to deploy, what happens when you restore a backup
  • A handover in writing, in your language

The last item decides repeat work. Clients who call again after three months usually are not asking for features. They are asking who knows how the thing runs.

The arithmetic, for a studio in Australia or the UK

Day rates for agencies in Sydney, Melbourne and London sit well above what a build-only partner charges, because the rate carries sales, account management and several layers of coordination. Working with a partner who only builds means paying for the build.

Our rate is EUR 45 per hour, or EUR 320 per day, with payment after you have seen the result of the first slice. For a studio, that usually means the margin stays in the studio's own contract, where it belongs.

Where we are the wrong partner

So nobody wastes a week:

  • We work in writing, in English or German. We do not run meetings or calls in English.
  • We are a studio in Seoul, not a local company. Invoices come from a Korean corporation and are paid by bank transfer.
  • Work that requires on-site presence, local residency, or handling regulated personal data under a local processor agreement is not for us.
  • We do not do discovery, branding or design. You design; we build, and we say early when something will not hold technically.

How it starts

Send the scope you want to sell — three sentences and a link to the design is enough. You get a written assessment within 24 hours: what ships in 3–5 days, what takes longer, what we would cut. Nothing is charged before a contract, and the balance is paid after you have seen the first slice.

By way of reference: we build and ship our own products — a turn-based tactics game with 48 units and 53 stages live on Google Play, the App Store and as a mini-app, plus a market-data app running on live feeds. Interfaces, data models, review processes and releases are what we do every day.

CPC AI Studio (CPC AI Inc., Seoul) https://cpcai-studio.netlify.app/en/ · yyhak12345@gmail.com

Comments

Popular posts from this blog

From 80% to shipped: what a 3-5 day finish of an AI-built app actually looks like

An Australian app build in AUD: GST, ABN and the three decisions to settle on day one

The app was finished on Thursday. Apple let it in the following Wednesday.