Software shaped by the industry it runs in

No. These are the ones we have the deepest domain knowledge in, which is why they are the ones described in detail. The engineering underneath is the same whatever the sector. Tell us what you build and who buys it, and we will say honestly whether we have done work close enough to be useful to you.

We start with your people rather than with research. A short discovery with the team who does the work day to day, the systems it already runs on, and the rules it has to follow. What comes out of that is a written scope you sign off before anything is built, so you can see whether we understood the domain before you commit to it.

Where the requirement is something a build can be held to, yes: data handling, access control, audit trails, encryption in transit and at rest, and integration with whichever system already holds your record of truth. Send us the standard you answer to and we will tell you which parts affect the build and which sit outside it.

Usually alongside. Most of the industries on this page have one system nobody is going to switch off, an ERP, a practice management tool, a booking engine. We integrate with it and build the parts that are missing around it. Replacing it is a separate decision and a much larger one, and it should be made on its own merits rather than as a side effect of a project.

It depends almost entirely on how much of the domain has to be modelled before anything can be built, which is why we scope before we quote. The scope carries the timeline, the milestones and what each one delivers, and nothing starts until you have that in writing.

The build, its source and the documentation for it. The point of the handover is that another team could pick the project up without us, whether or not you ever need them to. Support after launch is a separate arrangement rather than something you are locked into.