Products
We build client work.
We also build our own,
to find out if we’re right.
A services studio has opinions about how software should be built. The only honest way to test them is to ship something under our own name and see whether the opinion survives contact with a real user. These four are that test. One has a public URL right now; the other three are further back, and we say so rather than dressing them up.
intentfirst
A way to build software that starts from intent rather than from screens. Eight context tokens carry what the user is actually trying to do, and three memory layers keep that intent true as the session goes on, instead of it draining out screen by screen the way it usually does. It is also the method behind most of the studio’s other work, described in full below.
Context tokens · memory layers
Open itMyBrainSpec
A short cognitive self-check. You answer it, the model scores it, and what comes back is a written profile of how your own attention and memory actually behave — prose, not a score out of ten. The point is a description you recognise yourself in, not a number to compare against anyone else’s.
React · Vite · Firebase · Gemini
No public URL yet
Moime
A link-in-bio page for promo codes and events. Point it at a flyer and it reads the dates, codes and venue straight off the image, rather than asking whoever is posting the event to retype what is already sitting there in the picture.
Image understanding · web
In production
Shopping on Fire TV
A concept for buying from the sofa: a ten-foot interface where the remote has five buttons and the basket still has to make sense with none of a mouse, a keyboard, or a touchscreen to fall back on.
Concept prototype
No public URL yet
The method
intentfirst isn’t just a product. It’s how the rest gets built.
Eight context tokens and three memory layers are not specific to intentfirst’s own interface — they are the same discipline the studio applies underneath its client work, so that what a project is actually trying to do stays legible from the first screen to the last, rather than getting quietly renegotiated by whichever screen came last. Building intentfirst as a real, openable product is what keeps that claim honest: the method has to work well enough to ship on its own before we trust it inside someone else’s project.