01
Few projects, fully owned.
We take on a small number of engagements at a time, so each one gets the attention it deserves.
Index № 01
Studio overview
43.6532° N
79.3832° W
A Toronto software studio
Patient software, built for the long arc.
NH Cube is a small studio in Toronto that designs and engineers software for founders and product teams — from the first sketch through every release after launch.
fig. i — the cube
Scroll
MMXXVI · A studio of two disciplines
Product strategyInterface designArchitectureEngineeringLaunchPartnershipToronto, CanadaEst. 2024Product strategyInterface designArchitectureEngineeringLaunchPartnershipToronto, CanadaEst. 2024
№ 02The studio
Every product we touch is treated like a building, not a campaign. We care about the foundations as much as the façade — because the work has to hold up for years, not weeks.
A small team
Senior designers and engineers who do the work themselves. No handoffs to a back row.
A long horizon
We measure success in what your product is still doing two years after we wrote the first line.
Two disciplines
Product design and software engineering, treated as one craft. Each side sharpens the other.
№ 03The practice
Six things we do, deeply.
We work end-to-end on every engagement. The list below isn't a menu — it's a description of how a product moves through the studio when you ask us to build it with you.
- 01Product strategyWe sit between the business and the build, turning ambition into a product worth shipping.
- 02UX & interface designQuiet, considered interfaces. Designed by people who can also stand behind the code.
- 03Software architectureThe shape of the system, decided early. Composable, observable, and built to be lived in.
- 04Full-stack engineeringTypeScript, modern frameworks, real infrastructure. Production code, not prototypes dressed up.
- 05Launch & iterationWe stay in the room through release week and the quieter weeks that follow it.
- 06Long-term partnershipWhen the engagement ends, the product still has to grow. We make ourselves easy to keep around.
№ 04The method
How a product moves through the studio.
The same four phases run through every engagement, whether we're shipping a first release or growing a product in its fifth year. The boundaries between them are deliberately soft.
- IPhase
Frame
We start by understanding the people, the problem, and the constraints — not the brief.
- IIPhase
Shape
Strategy turns into design and architecture decisions. Trade-offs are made on paper, in daylight.
- IIIPhase
Build
Tight engineering loops with the team in the room. Releases that are small, frequent, and quietly correct.
- IVPhase
Tend
Software is gardened, not finished. We stay on as the product grows into the shape it needed.
№ 05House beliefs
Four convictions we don't trade away.
They shape who we work with, how we estimate, and which corners we refuse to cut. Reading them is a fair way to know whether we'll work well together.
02
Boring tech, sharply applied.
We pick well-understood tools so the surprises stay where they belong: in the product itself.
03
One craft, two disciplines.
We don't draw what we can't build, or build what we haven't thought through. Design and engineering are one practice.
04
The first release is the start.
We design for what comes after launch, not just what gets you there. Shipping is when the work begins.
№ 06An invitation
Have a product in mind?
We'd love to hear about it.
We open a small number of new engagements each season. Tell us what you're building, where you are with it, and what good would look like a year from now. We read every note ourselves.
Studio
Toronto, Canada
Working remotely with teams worldwide.
Engagements
Six to eighteen months, typically.
Full product partnerships preferred.
Response
Within two business days.
Always from a person, never a queue.