Customer-facing site
A fast marketing-to-product surface that still feels human on a phone.
Web craftsmanship for real people
Colomo is two people — Tona and Mau — who care about structure, interaction, and code you can live with. We work in the open, keep scope honest, and stay close after launch.
You talk to us
No account manager in the middle. Design and engineering sit in the same conversation.
Small, clear scope
We would rather ship a sharp slice than a bloated roadmap you will never finish.
We write the code
Readable, maintainable work you can hand to your own team — or keep us on.
Not Colomo clients — companies where Tona and Mau built production software.
Frontend in a large monorepo, shipping with the rest of the platform.
Full-stack work on an Azure-hosted product, in a larger engineering team.
Frontend on consumer-facing experiences that had to hold up at scale.
A short loop we can explain in one sitting. You always know what happens next.
01
We learn the goal, the users, and what “done” actually means.
02
We prototype the experience until it feels clear and kind.
03
We ship stable, testable software you can read and change.
04
We deploy with care so go-live is calm, not a fire drill.
05
We iterate on real use — or hand off cleanly if you prefer.
Two people covering the work that usually gets split across a whole agency.
Layouts, flows, and UI that feel quiet and obvious — not decorated for the deck.
Modern frontends (and the backend they need) with tests, structure, and room to grow.
Fixes, small features, and a partner who still knows the codebase next quarter.
Products we've shipped. MesaTodos is live; more case studies will land here as we publish them.
Split a restaurant bill from a photo of the ticket. Share a link with the table — no signup, everyone picks what they ordered.
A fast marketing-to-product surface that still feels human on a phone.
Shared tokens and components so a small team can ship consistent UI without a design ops department.
Two people. That's the whole company.
Lead engineer
Owns the hard structural decisions — architecture, quality, and making sure the product still makes sense a year later.
Frontend engineer
Lives in the interface: interaction, accessibility, and the details that make a site feel considered rather than assembled.
We're two people, so we read every note ourselves. A few sentences about the problem is enough — we'll reply with next steps.