People decide what gets built. Agents do the hard implementation work. Nothing ships until it has been driven the way a real user would drive it.
Design.
We work out what the product has to do before a line of it exists. That judgement stays with people.
Build.
Agents write the implementation under our direction. We hold the architecture and own what ships.
Test.
Every build gets driven the way a person would drive it. Real screens, real journeys.
Working with us
A long collaboration, not a one-off. Diligence and care on the product, and a bit of craic along the way. The aim is to be your software department, so you do not have to hire one.
01
Diligence, dignity, and attention. A person is answerable for the work, and you will know their name.
02
We would rather stay and build with you than deliver a folder and disappear.
03
We can be the software team. You do not have to hire one to get the product made.
How we work
No black box, and no handover to a team you never met. Three stages, and a person answerable for each one.
01
We work out what the product has to do, who it is for, and what finished means, before a line of it exists. That judgement stays with people.
02
Agents write the implementation under our direction. We hold the architecture, review what comes back, and own what ships.
03
Every build gets driven the way a user would drive it: real screens, real journeys, at phone, tablet and desktop widths. Not just unit tests passing in isolation.
Case study
We built Pitched, the AI-assisted marketplace live at pitched.ie. We designed it, agents implemented it, and before release we put it through an AI-run QA harness.
~180
user paths driven end to end
3
layout widths: phone, tablet, desktop
Every path
checked for visual regressions and accessibility
Pitched was tested as a web app at those three layout widths by an AI-run QA harness. It was not tested on physical handsets.
pitched.ieFind a way through
The bold letters are the walls. Split one and you go back to the start.
Find the opening.
This is not a drawing of a maze. It is the type itself, set in a way the rest of the page is not. The letters run in reading order, one after another, across a grid. Where the type is bold, that letter is a wall. Where the type is light, that letter is the way through. There is no tile and no picture behind the words. The maze is only a change in the weight of the letters. Drag the square, or use the arrow keys. It travels through the light letters. Letters it has already crossed turn blue, so the way you came stays on the page. The way out is the blue opening in the bottom wall. If the square splits a bold letter, the wall is broken and you go back to the start. The blue letters stay, so a wrong turn does not wipe the ground you have already covered. This is the same arrangement as the rest of Loinnir. A person decides what the thing is, who it is for, and what finished means. Agents do the building under that direction. Then the thing is driven the way a person would drive it, before anyone is asked to trust it. A team of agents played this maze before it went on the page. They moved the square on their own. They found the opening. They split a bold wall and were sent back to the start. They did it on a wide screen and on a narrow one. The case study above is that same arrangement at the size of a product. We built Pitched, the AI-assisted marketplace live at pitched.ie. We designed it, agents implemented it, and before release an AI-run harness drove it at phone, tablet and desktop widths. Pitched was tested as a web app at those three layout widths. It was not tested on physical handsets. The judgement stays with people. A person is answerable for what ships. We would rather stay and build with you than deliver a folder and disappear. Tell us what you are trying to build.
Through.