Skip to content
Start a project

Process

Start small,and see real screens often.

What you get at each step, the ways to contract, the terms and the common questions, in one place. Scope, cost and schedule always go in the written estimate and the contract.

Steps
5
Ways to contract
4
Terms
6

Steps

  1. 01

    30-min free intro call

    Tell us what you want to build, and we look at the right way to run it together.

  2. 02

    Discovery & written estimate

    We work out the requirements and screen flow with you, and the written estimate sets out scope, cost and schedule.

    You get
    Requirements document, screen flow or prototype, written estimate
  3. 03

    Build in short cycles, with demos

    We build in small steps and show you the real screens at the end of each cycle.

    You get
    Screen design document, API specification
  4. 04

    Release & acceptance

    You check the work against the acceptance criteria in the contract, then it goes live.

    You get
    Source code, test report, handover document
  5. 05

    Care plan

    You get
    Operations manual

Start small

You can start small. We work through the requirements with you, then send a screen flow or prototype and a written estimate. You decide whether to continue. Scope, cost and schedule are all in that estimate.

Ways to contract

Discovery

When the scope isn't settled yet

We work out the requirements and screen flow with you first. You see the results and a written estimate, then decide on the next step.

Fixed-scope build

When what to build and how to accept it are clear

The scope and acceptance criteria go in the contract, and you review the work at each milestone. When and how you pay is agreed with you to suit your situation.

Time and materials

When the work changes as you go and you want an engineer for a set period

Our engineer works on your project for an agreed period. We set the time commitment together and put it in the contract.

Care plan

After launch, to keep the product running and improving

We keep running and improving the product after launch. Support scope and response times are agreed with you in the maintenance contract.

Terms

NDA

If you'd like, we sign an NDA before you share any details. If you have your own template, we'll review it.

#nda

Code and copyright

Who owns the source code and the copyright, and from when, is agreed in writing before you sign the contract. We ask first how you would like it, and write exactly that into the contract.

#ip

Payment

Payment terms are set with you to fit how your company pays, and written into the contract.

#payment

Defects after release

How defects found after release are fixed (for a fixed-scope build, the scope and length of the defect warranty) is in the contract, and we walk you through it before you sign.

#warranty

Ending early

If the engagement ends early, the contract already says how the work done so far is handed over.

#termination

Accounts

Repos, cloud and store accounts can be in your name from day one.¹

¹ Store releases need a developer account in your company's name

#accounts

How long we keep copies of the code we deliver and of the files you share with us is agreed with you before signing and written into the contract. Unless the contract says otherwise, we delete our copies whenever you ask and confirm it in writing.

How we build

On the invoicing system for a Canadian business that supplies stores, the code as delivered carried 234 automated tests that check screen behaviour, calculations and printing.

Working together

  • We work in English, Japanese or Korean.
  • Calls are scheduled in advance.

Time zones

Seoul is UTC+9 all year, with no daylight saving. Our 8–10 am is 4–6 pm Pacific and 7–9 pm Eastern on the previous day in summer, and an hour earlier in winter (3–5 pm PT, 6–8 pm ET).

From day one, your code can live in a repository under your organization's own account.

Frequently asked questions

  • Who actually writes the code?

    The programmer you first speak with. There is no sales layer and no outsourcing: the same person designs, builds, runs and maintains it, and a designer works alongside on the screens. Each case study names the team that worked on it.

    #faq-1
  • How do you price an MVP, and how long does it take?

    We scope it with you first, then send a written estimate. You can also start with a small first step. How long it takes depends on the size and complexity of what you're building, so we set the schedule per project and put it in the written estimate.

    Payment⁠#faq-4
  • How do you use AI tools on our code?

    We use AI coding tools, and a person reviews and tests everything they produce. Your data and secrets never go into a prompt. Ask us and we will send the details of the tools, plans and settings in writing.

    #faq-5
  • Can we start small?

    Yes. We work through the requirements with you, then you get a screen flow or prototype and a written estimate, and decide whether to continue.

    #faq-6
  • We found you on Upwork or Fiverr. How does the contract work?

    Hired us on Upwork or Fiverr? The contract and payments stay there.

    #faq-7

Tell us what you're building.

Here is what happens next.

Start a project
  1. We read it and reply with questions or call times.
  2. A free 30-minute video call, NDA first if you'd like.
  3. A written proposal and estimate, with scope, cost and schedule spelled out.