/ How we work /

A process with no surprises.

Five steps, each ending in something you can hold. You always know where the project stands and what you are paying for.

/ The five steps /

From first call to stable product

Typical timings for an MVP. Larger systems repeat the Build step over more sprints.

  1. Week 1

    Discover

    Workshops with your team to pin down users, goals, constraints and what success looks like. We challenge scope early, because the cheapest feature is the one you do not build.

    You get
    • Scope document
    • Fixed quote within 5 working days
    • Risk and assumptions list
  2. Weeks 2–3

    Design

    User flows, wireframes and a clickable prototype, reviewed with you every few days. Engineers join design reviews so nothing is drawn that cannot be built on budget.

    You get
    • Clickable prototype
    • Design system in Figma
    • Technical architecture plan
  3. Weeks 4–10

    Build

    Two-week sprints that each end in a live demo. You see working software on a staging link, not status slides, and you can change priorities between sprints.

    You get
    • Demo every sprint
    • Written report every week
    • Staging environment you can use
  4. Weeks 11–12

    Launch

    Load and security testing, app store submission and a planned go-live with a rollback path. We stay on call for launch week.

    You get
    • Production release
    • Full source code in your repositories
    • Technical and user documentation
  5. Ongoing

    Support

    Bug fixes, monitoring and improvements after launch, on a plan that fits your stage, or a clean handover to your own team.

    You get
    • 60-day bug warranty
    • Optional monthly support plan
    • Handover session for your team

/ Staying in touch /

You never have to chase us

Weekly written report

Every Friday: what shipped, what is next, open risks and hours used. One page, plain language.

Demo every sprint

A live walkthrough of working software every two weeks, recorded for anyone who could not join.

Shared channel

A Slack or Teams channel with the people doing the work, not only an account manager.

Open board

Read access to our Jira or Linear board, so you can see every task and its status at any time.

/ Security & handover /

Your IP stays yours

NDA from day one

We sign your NDA or ours before any detailed conversation, at no cost.

IP assigned to you

The contract assigns all code, designs and documents to you, under Hong Kong law.

Your repositories

Code lives in your GitHub, GitLab or Bitbucket account from the first commit.

Clean handover

Credentials, infrastructure notes and a walkthrough, so any team can pick up where we stop.

/ FAQ /

Working together

Book a free consultation
Which time zones do you work in?

Our working day overlaps fully with Hong Kong, Singapore and Australia, and we keep a daily overlap window with Europe. For clients in the Americas we schedule calls in your morning or evening.

How do payments work?

Fixed-price projects are paid per milestone, usually 30% to start and the rest as agreed milestones are delivered. Dedicated teams and time-and-materials work are invoiced monthly. We invoice in USD or HKD from our Hong Kong company.

Can we change priorities mid-project?

Yes. Between sprints you can reorder the backlog freely. On fixed-price work, a change that adds scope gets a written estimate before we start it, so the price never moves by surprise.

What happens after launch?

Every project includes a 60-day warranty: we fix bugs in delivered work at no charge. After that you can choose a support plan, keep a smaller team on, or take the code in-house with our handover documentation.

Hong Kong Island skyline across Victoria Harbour at dusk

Start with a free scoping call.

Thirty minutes, no obligation. If we are a fit, you get a scope and a fixed quote within five working days.

Book a call
Weekly written reportsA demo every sprintNDA before the first call100% source code ownership60-day bug warranty