We are a small team that builds and runs its own software. That shapes how we work more than any job description would, so this page describes the work honestly rather than selling you on it.
How we actually work
We ship in short cycles and look at the result before deciding what comes next. Nobody here writes a specification for someone else to implement — the person who designs a thing is usually the person who builds it and the person who gets the support message when it breaks at the weekend.
That last part is the honest catch. Running your own products means you own the consequences of your decisions, which is the fastest way to learn and occasionally an uncomfortable one.
Small on purpose
We are not trying to grow into a large agency. Fewer people, closer to the work, is a deliberate choice rather than a stage we are passing through.
Boring technology
Python, FastAPI, PostgreSQL, WordPress where it fits. We would rather spend our curiosity on the problem than on the stack.
Written, not just said
Decisions get written down with the reasoning attached. Six months later that is the difference between maintaining something and guessing at it.
What we look for
Evidence that you have finished something. Not a degree, not a list of frameworks — a project, a product, a contribution, anything real that went from idea to actually working and being used. Finishing is a much rarer skill than starting.
Beyond that: writing clearly, saying when you do not know something, and caring about the person on the other end of the software.
The work you would be joining
- Our own productsQRBranch, HandwashPro and NestSentry — three SaaS products we designed, built, launched and support.
- How we write about the workThe case studies are a fair sample of how we think and the level of detail we go into.
Open roles
None advertised right now. We hire when the work genuinely needs another pair of hands, not on a schedule, and we would rather say that plainly than keep a permanent listing up that goes nowhere.
Speculative applications are read, though — every one of them. If you have built something you are proud of, send it with a couple of lines about what was hard and what you would do differently. That tells us far more than a CV.