Process before product
We refuse to scope software before we understand how the work actually happens — including the workarounds people are slightly embarrassed to show us. Those workarounds are the requirements document.
About · Accelerating Change
Cyclotron Technologies is a software product company. We work with organisations whose processes have outgrown spreadsheets and messaging, but do not fit any product on the market — and we build the system that closes the gap.
Our history
Accelerating Change
Cyclotron began with software-product and customised-system ambitions — MIS and web-enabled applications for organisations whose work did not fit packaged software. That practice later expanded into IT services and, in time, into enterprise software implementation across finance, procurement, service and reporting.
Almost every growing company we met reached the same point. The ERP handled finance. The CRM handled pipeline. And between them sat the real operation — approvals chased over messaging, statuses tracked in a workbook one person maintained, decisions made from numbers that were accurate last Tuesday.
That gap is not a tooling problem to be solved with another subscription. It is an architecture problem, and it is why Cyclotron is returning to its product-engineering roots for the AI-native era: a real data model, enforced permissions, audit trails, and AI used precisely where judgement can be assisted rather than replaced.
Reserved — operational photography
Observational interior of a working professional operation — planning wall, shift board or control desk in use. Architectural framing, natural light, no posed portraits.
What we believe
These are not values on a wall. They decide what we scope, what we decline, and how a system is built once the work begins.
We refuse to scope software before we understand how the work actually happens — including the workarounds people are slightly embarrassed to show us. Those workarounds are the requirements document.
Off-the-shelf software is excellent at solved problems: accounting, payroll, email. It is poor at the specific coordination logic that differentiates your business. We build only the second kind.
Language models are extraordinary at reading, drafting, classifying and routing. They are unsuitable as the final authority on money, permissions or external commitments. We design that boundary explicitly.
The code, the data, the schema and the deployment path belong to you. No proprietary runtime, no hostage licensing, no clause that makes leaving expensive.
The people who run your Process Audit are the people who architect and build the system. Your engagement is not passed to a separate delivery team once the proposal is signed.
If configuring a product you already own is the right answer, we will say so — even when that means we do not get the build. Scope should follow the problem, not the invoice.
Working together
Bring a process that frustrates you. We will tell you what we would do, whether or not it involves us.