FAQ

The questions people actually ask.

Straight answers about how we work. If something you need isn't here, ask — we reply within one business day, and a real person reads every message.

Who actually does the work?

Senior engineers, and the same ones throughout. There are no layers between you and the people writing the code, and nobody is learning on your budget. The person who scopes your project is the person who builds it.

Do you send work offshore or subcontract it?

No. The team is US-based and the people who design your product are the people who build it. There are no hand-offs to another shop, another timezone, or a queue of contractors you never meet.

We work remotely, and we work with clients wherever they are — but the build itself stays with us.

What platforms do you build for?

iOS, Android and web — normally from a single codebase, which is why one small team can ship to three places at once. Five of our six apps are built that way; ImageSlim is web-only, installable as a PWA.

If a project genuinely needs native, we'll say so rather than force it through a cross-platform stack.

How does a project actually run?

Four stages, and you see something working early rather than at the end:

  • Discover — one focused week to agree on the problem, the users, and the smallest version worth building.
  • Prototype — a working slice in front of real users within weeks, not a slide deck.
  • Build — production engineering with tests, CI and observability from the start.
  • Scale — measure, harden and grow.

You talk to the people doing the work every week, for as long as it runs.

What happens after launch?

We stay on as long as you need, and no longer. Deciding you're done is a conversation, not a process.

When we do hand off, the aim is that your team is faster than before, the codebase is cleaner, and the documentation is real rather than decorative.

Is there a minimum project size?

No. There is no floor you have to clear before we will talk to you, and small does not mean unwelcome — plenty of useful software is small.

What we will do is tell you honestly if we are not the right people for it, rather than take the work and stretch it.

What if we need to stop partway through?

You keep everything built up to that point. It is yours in exactly the same way the finished thing would have been — the code, the design work, all of it, with no clause that claws any of it back.

We would rather you stopped a project that stopped making sense than kept paying for one out of obligation.

Who owns the code?

You do. The code we write for you is yours — along with the design work and everything else produced for the project.

That is the point of the boring-tech bias: proven tools, documented decisions, no framework only we understand. If you want to take it in-house or hand it to another team, nothing about the way it is built stops you.

Do we need an NDA before talking to you?

No. You don't need one to tell us what you're building — we treat what you send us as yours and confidential by default, whether or not anything is signed.

Send as much or as little as you're comfortable with. We can give you a useful first read on a project from a couple of paragraphs.

What technology do you use?

Most recently: React Native, React, TypeScript, Firebase and Cloudflare. That's what we've reached for lately, not a limit — the stack should follow the problem.

The bias is toward boring, proven tools, so your software is still maintainable years from now by someone who isn't us.

Do you only build apps from scratch?

No. Alongside new products we do product engineering on existing codebases, platform and cloud work, modernisation of legacy software, and embedded engineers who work inside your team.

We also rebuild small-business websites end to end — structure, copy, imagery and speed — using what the business already has.

Have you actually shipped anything, or is this a portfolio of concepts?

Six products of our own, all started between May and July 2026 and all still under active development. Each app page lists when it started, when it last shipped, what it's built with, and the genuinely hard part of building it.

ImageSlim is live and free to use right now, in a browser, with no account. The others are in testing — the app pages say exactly which stage each one is at rather than implying they're all in stores.

How fast will you reply?

Within one business day, with honest first thoughts on how we'd approach your project — not a calendar link and a sales script.

If we're not the right people for it, we'll say that too.

Still have a question?

Ask it directly — we'd rather answer than have you guess.