Software development and artificial intelligence

We build software because we needed it ourselves. Our entire company runs on a system we built — quotes, purchasing, receiving, invoicing, time. And for the past year, that system also answers in plain language, because we wired agents into it.

That’s what we now offer others: custom software that fits your real operations, and AI where it replaces work someone is doing by hand.

What we actually do

• Custom management software: the logic of your operations, not a vendor’s
• AI agents wired to your data: plain-language questions, answers pulled from your systems
• Integration between your existing systems, to stop retyping the same data
• Hosting, evolution and support

What AI actually does once the system is in place (finding, summarizing, sorting, drafting, extracting) is described on the AI integration for business page.

The limit we state up front

AI can propose, analyse and prepare. The final decision stays human. For anything that commits your operations, whether it is sending something to a client, invoicing or deleting, human approval is required. A system that acts on its own inside your operations is a system that will eventually hurt you.

That is a design choice, grounded in our own experience of the tools we build and use every day.

How a development mandate unfolds

The general shape of a mandate is described on the custom business systems page. What follows is specific to software development.

Proof on your real data. Before building the system, we validate the idea on a sample of your actual data. A model that impresses in a demo can fall apart on your own documents. Better to find out at this stage.

Choosing the technologies. We pick what your team will be able to maintain, not what is fashionable. The code is yours, documented, and your IT team can take it over without us.

Integration with what exists. The software connects to your current systems rather than replacing them. We only replace what genuinely limits your operations.

Handover. Documentation, access, deployment procedures. A system only its supplier can run is a dependency, not a solution.

Questions we get asked

“Does our data train a model?” No. We work with providers whose terms exclude it, and we can isolate what’s sensitive so it never leaves your walls. That’s a question we settle at the quote stage, not after.

“Why would a broadcast integrator build our software?” Because we write code for environments where a failure shows up on air. That shapes the design: we document, we plan for recovery, and we hand over something your team can take on without us. The full reasoning is on the custom business systems page.

“What happens if we stop the subscription?” The system is yours and keeps running. The subscription pays for evolution and support, not for the right to use your own tool.

“We already have software — do you want to replace it all?” No. Often the biggest gain is making what you already have talk to each other. We replace only what costs more to keep than to rebuild.