Skip to content

How we work

We build things to operate, not to demo

Here’s what we hold ourselves to, and what working with us is like, from the first email to launch day and after.

  1. Numbers, not adjectives. We’d rather tell you what something does, and how well, than call it powerful. If it’s still in development, we’ll say so. IWE takes this furthest: the numbers on its own pages are checked against the code, so a stale count stops the build.
  2. Measured AI. AI features are easy to demo and hard to trust. So before one ships, it has to pass a set of test cases with known good answers, and we keep scoring it once it’s live. Pocket Philosophy’s referee, for one, is tested with 5 faults planted on purpose in a real debate. It has to catch all 5, and leave a trap alone.
  3. Built to run. Software has to keep working long after launch day, whoever runs it. So it comes with tests, monitoring and a written plan for the failures we can see coming. A Fetchpawz deploy backs up the database before every migration, and stops at the first sign of trouble.
  4. Show the workings. You’ll see the reasoning, the trade-offs and the test results behind your project, not just the finished thing. We build software the same way: IWE marks each finding in your text with its reason, and the 3D configurator shows the slat count, housing and weight behind every spec.

What working with us is like

  • It starts with a conversation, then a written brief with the trade-offs and the risks out in the open.
  • Early on, you get a prototype you can click. From there it’s built to production standard, so accounts, payments and admin don’t need redoing later.
  • Every week, an update in plain words on what changed and what’s next, like “Week 3: the configurator now covers garage doors.”
  • At launch, you choose who runs it. Host it yourself and we hand over everything, with the procedures to go with it. Or we run it for you, and when something breaks you reach the person who built it.
  • Either way, it’s yours: the code, the design and the data. Taking it in-house later is a handover, not a negotiation.
  • If we don’t know something yet, we’ll say so. If we get something wrong, we’ll tell you and fix it.