# How a project runs, from intro call to launch

A prototype takes one week. A full build takes four to six weeks. Monthly engagements run open-ended and can be ended any month. You get the written scope and a fixed date within two days of the intro call, and during a build you get a live link to use every Friday, not a mockup to review.

## The three steps

One call. A written scope. A live link every Friday.

1. **Scope.** One call about your goals, your users, and what is in the way. A written scope and a fixed price follow within two days.
2. **Build.** Design and code move together, in the same hands. Every Friday you get a live link to use, not a mockup to review.
3. **Ship.** We launch, watch real people use it, and fix whatever gets in their way. Then we decide together what comes next.

## The prototype week, day by day

Prove it turns an idea into a coded product experience in five business days. It covers one critical workflow, up to eight key screens or states. User recruitment and formal testing are not included.

- **Day 1.** Pick the one critical workflow and name the screens and states it needs, up to eight. Decide what is out.
- **Days 2 to 4.** Design and code the workflow together as a coded prototype with real product behavior, not a Figma mockup.
- **Day 5.** Walk through the working prototype, agree the one revision round, and receive a concise recommendation on what to build next.

## A full build, week by week

Ship it takes four to six weeks depending on the agreed scope. The shape is the same every time:

- **Before day one.** A 30-minute intro call, then a written scope with deliverables, dates, price, and payment split within two days. Work starts when you accept it in writing and the first payment is in.
- **Weeks 1 to 2 - Decide.** Flows, hierarchy, and the calls behind them: what to build first and what to cut. The first live link goes out on the first Friday.
- **Weeks 2 to 5 - Build.** Design and code move together in the same hands. Every Friday there is a new live link to use. Design sign-off is the second payment milestone.
- **Final week - Ship.** Launch on the web, iOS, or Android. Then we watch real people use it and fix whatever gets in their way.
- **The 30 days after.** Defects in our own work are fixed at no charge. Past that, a month-to-month engagement covers ongoing changes.

## Ongoing work, month to month

Grow it reserves product capacity for the month, works on one clear priority at a time, and ships something meaningful every week. You talk directly to the people doing the work. Major new products and complex integrations are scoped separately. Stay while it is useful; leave any month.

## What you do

A founder or executive who can make weekly decisions. Material, access, and answers in good time. Delays on your side move the timeline; late payment pauses work until it is received. That is the whole list.

## The right fit keeps scope, timing and price clear.

Focused product work, weekly decisions and one accountable owner.

### Best fit

- A defined web or mobile project, at a startup or a larger company
- One primary user and critical workflow
- One owner who can make decisions every week
- A clear goal and a realistic first release

### Better elsewhere

- A program that needs dozens of people at once
- Every platform and integration in one first release
- Open-ended staff augmentation
- No clear owner, user or first release

## Questions about timing

### How long does a project take?

A prototype takes one week. A full build takes four to six weeks. Monthly engagements run open-ended and can be ended any month. You get the written scope and a fixed date within two days of the intro call.

### What happens if something breaks after launch?

We fix defects in our own work at no charge for 30 days after launch. Past that, a month-to-month engagement covers ongoing changes and fixes.

### How do we start?

One 30-minute intro call about your goals, your users, and what is in the way. No preparation needed. A written scope and a fixed price follow within two days.

### What if we are not sure what to build yet?

Start with the one-week prototype. You get one critical workflow as a coded product experience with real behavior, not a Figma mockup, plus a concise recommendation on what to build next. If you begin a build within 60 days, the fee is credited in full.

HTML: https://www.choie.co/process