Before you ask

A two-week sprint is the floor. Below that you usually need a conversation rather than a project — we will say so, and the 90-minute focus session is free either way.

Fixed scope, fixed price. If the scope changes, you get a new price and schedule before any work starts. We do not build first and discuss money later.

You do. At the end, source, Cloudflare account, domain and third-party services all transfer to your ownership. We leave no technical lock-in behind.

Yes, and we prefer it. We use your review process and branching strategy rather than introducing a parallel one.

The studio is in Taipei. Full overlap with Tokyo, near-full with Singapore and Sydney. For European and North American clients we hold a fixed morning window for synchronous calls.

A Taiwanese company invoicing in USD, JPY or TWD, under a standard commercial agreement. Quarterly billing available on retainers.

Because two things both called "a website" can differ by a factor of ten in actual scope. Publishing a number persuades half the readers it is too expensive and the other half that it is cheap, and both conversations then have to start over. The proposal carries an exact figure, and that figure does not move.

Most projects run on Cloudflare Workers and D1, with React or plain server-rendered HTML depending on the page. Every technology choice is written into the proposal with its reasoning, and if you already have an internal standard we work to yours.

Yes. There is a working version every two weeks, so every two-week boundary is a clean exit: you keep everything built to that point, including source, and owe nothing for the remainder. It is written into the contract rather than offered as goodwill.

Project delivery includes a three-month warranty: defects in code we wrote are fixed at no charge. After that you can move to a retainer or not — the system is built to run without us, which is the point.

Yes, with one condition: a weekly working session during implementation. Design-only handovers start drifting from the intended result around week three, and by the time anyone looks back it is expensive to correct.

Better. One of our most common arrangements is supplying the engineering and systematisation alongside an in-house design team, so your designers stop spending afternoons arguing about which blue the button is.

Yes — it is an acceptance criterion. Copy, case studies and service descriptions all live in a back office, needing neither an engineer nor a deployment. At handover we sit with your team while they make a real change and publish it.

Two at most. That is the only way we can keep showing you something every week, and it is why the calendar usually has a queue.

Yes, and we are happy to use your paper. Separately: nothing about your project goes on our work page without your written agreement, quotes included — we send you the exact wording to approve before anything is published.

No. Our proposals avoid technical vocabulary and describe decisions as what they will cost or save you later. What we ask you to judge is always a trade-off, never a technology.