What we build, and what it takes to build it well.
Most software projects fall into a handful of patterns. Each page below explains one of them in plain language: the problem it solves, the decisions that shape it, the details that matter in Hong Kong and what a sensible first release looks like.
With an interactive concept you can try
These four have a working concept built with fictional data. Click through it, then read what a production version would still need.
Planning guides
These are common requests we can help scope. They are explained here as planning guides; there is no demo for them yet.
How these pages are written
We do not list client work here, because we do not present invented case studies as real ones. Each guide describes the pattern honestly: what usually goes well, what usually goes wrong and what to decide before any code is written.
Projects rarely fit one pattern exactly. A booking system often needs messaging; a client portal often needs documents; an internal tool often needs a customer record. We scope the pieces together so they fit.
Not sure which pattern fits?
Describe the situation in your own words. We will tell you which pattern it resembles and what a sensible first scope looks like.
Request a project quotePrefer to draft it first? Try the project brief builder.