ColoureDev Studio — Product design and engineering

Product studio

Ideas that have not settled yet,shipped as products that hold.

The problem gets stated plainly before a single screen is drawn.

Tell us about your project

Key numbers

  • 48

    Projects delivered

    since 2019

  • 82%

    Clients who stay

    continue after the first project

  • 3

    Markets served

    Taipei · Tokyo · Singapore

  • 9 weeks

    Median time to launch

    from signature to production

Services

What we take on

Each one states what you get and how long it takes.

Services →

Product design

We turn a pile of unresolved ideas into something you can ship, measure and keep growing. The problem gets stated plainly before a single screen is drawn.

Lead time
4–6 weeks

Web and frontend engineering

Sites that search engines can read, that open on a slow connection, and that are still editable in three years. Performance and accessibility are acceptance criteria, not bonus points.

Lead time
3–8 weeks

Platform and backend engineering

Backends split into a few services with honest boundaries, running at the edge. Cold starts, connection limits and cross-region latency get solved in the architecture, not in production.

Lead time
6–12 weeks

Work

Things we have built

The numbers are the clients’ own measurements, not our estimates.

All work →

TSUKI

2025

Three markets, one commerce backend

Tax, payment and fulfilment rules for Taipei, Tokyo and Singapore collapsed into a single configurable rules engine.

3markets, one system

In the first meeting they told us the feature we came in asking for was the wrong thing to build. That sentence saved us more than the project cost.
Y. T. Chen Chief Operating Officer · Kaiho Freight

Insights

How we think about this work

Every piece comes out of a project we actually ran, including the decisions we nearly got wrong.

All insights →

Do not migrate in one go

Nine months to replace four systems, without stopping shipping for a single day. What made that possible was not careful planning — it was giving up on the idea of a cutover.

Put the performance budget before the merge

A monitoring dashboard after release looks impressive and prevents nothing. The number has to appear while someone is still willing to fix it.

Do not interpolate: draw the holes in your data

An interpolated line looks perfectly healthy, and that is exactly the problem. We made the dashboard uglier, and it caught a six-hour outage.

Tell us what you are trying to solve

You will hear back within two working days, from the person who would do the work.

Start a project