AI-native operating software for growing businesses
Your business already has a system.
We turn it into software.
If approvals live on WhatsApp, reports live in spreadsheets and critical processes depend on people remembering what happens next, we map the way your business actually works and turn it into software your team can run.
- Approvals
- Trapped in messages
- Reporting
- Assembled manually
- Knowledge
- Held by people
- Workflow
- Dependent on follow-up
Recognise this
Growth exposes the systems your business is missing.
These are not people problems. They are system problems.Cyclotron builds the system.
- 01A quotation waiting in someone's inbox.
- 02A purchase approved on WhatsApp.
- 03A report assembled manually every Monday.
- 04A process that stops when one person is away.
- 05A project whose true margin is known too late.
- 06Data duplicated across tools that do not talk to one another.
The transformation
Same process.
Finally a system.
We do not ask you to change how the business works in order to fit software. We record how it already works, then remove the parts that only exist because there was no system.
01 — Today
The process exists. It is just distributed across tools and people.
02 — Cyclotron system
- Modelled entities & states
- Roles, permissions, audit
- Approvals & escalation
- Integrations to existing tools
- Bounded agents
03 — Operating state
Observable, measurable and improvable — because it is now a system.
Three ways to get there
Deploy. Adapt. Build.
Not every company needs software written from scratch. We work out which of the three is right for the problem in front of you, and say so plainly.
01 — Deploy
Use a ready Cyclotron product
When an existing Cyclotron product already covers the operating problem, you run it. No rebuild, no bespoke project.
02 — Adapt
Configure a proven system around your workflow
We shape a proven Cyclotron system and its reusable modules — approvals, permissions, audit, documents, reporting — around how your company actually works.
03 — Build
Create the missing operating software
When nothing existing fits the process well enough, we build the system, and you own the code and the data.
Products
We’ve already systemised some of the hardest workflows.
Procurement, project money, social publishing and development feasibility — recurring problems we are turning into durable Cyclotron products.
- 01
Evidence-first procurement
RAQOZ
Launch preparation
RequisitionApprovalQuotationOrderEvidence
One accountable record from a request raised on the floor to approval, competitive sourcing, purchase order, receipt and reconciliation.
- 02
Project financial control
CostGrid
In development
BudgetCommitmentBillPaymentMargin
Project money in one place: what was budgeted, committed, billed and paid, so commercial drift is visible while work is still running.
- 03
Social publishing orchestration
Synquestra
Early access
CreateApproveSchedulePublishLearn
A low-cost publishing layer for teams and AI-built brands that need one governed queue across their social channels.
- 04
Development feasibility
DevPartner
Concept
LandAssumptionsScenariosFeasibilityDecision
Structured feasibility for land and development decisions, preserving assumptions, scenarios and the basis of the investment decision.
And when the system you need does not exist, Cyclotron builds it.
The gap
Software where SaaS stops fitting
Off-the-shelf software can cover the standard parts. The operational gap is what teams rebuild in spreadsheets, messages and manual follow-up.
Keep the systems that genuinely work — your accounting package, your ERP, your email. Cyclotron builds the operating layer between those systems and what actually happens day to day: the approvals, the quotations, the handoffs and the follow-up.
- What SaaS does well
- Standardised, regulated, commoditised functions: ledgers, payroll, mailboxes, storage.
- Where it stops
- The coordination between those functions — approvals, exceptions, evidence, handoffs, judgement.
- What usually fills the gap
- A spreadsheet, a messaging group and one person who understands both.
- What we build
- That gap, as software you own — integrated with what you already run.
Where it starts
Cyclotron Systems Audit
We map how the work really moves — people, process, data, decisions — and then say what the software should be.
PeopleProcessDataDecisionsSoftware
The output: a System Blueprint identifying
- Where work stalls
- Where manual coordination exists
- What depends on individuals
- What can be automated
- What existing software should stay
- Whether the answer is Deploy, Adapt or Build
Outcomes, stated plainly
What a well-designed operating system is meant to improve.
- Fewer manual handoffs
- Work moves because the system moves it, not because someone remembered to forward a message.
- One source of truth
- A single record per order, job, site or customer — with everything else pointing at it.
- Faster approvals
- Authority encoded once, decisions taken in seconds, every one of them auditable.
- Searchable institutional knowledge
- Contracts, SOPs and correspondence become answerable, with the source attached.
- Measurable workflows
- Cycle times, ageing and exceptions are observed continuously rather than reconstructed monthly.
- Controlled AI actions
- Agents act inside defined boundaries, with permissions, audit trails and human approval gates.
Solutions
What else we build
Beyond the products, these are the system types we build repeatedly — each starting from patterns we have already solved, then shaped to how your business runs.
- 01
Operate
Operations OS
The core operating layer: entities, statuses, ownership, handoffs and records for the work your business actually performs — orders, jobs, sites, batches, cases or shipments.
Explore - 02
Operate
Procurement & Vendor Management
A procurement workflow that enforces authority limits without slowing the buyer: requisition, comparison, approval, purchase order, receipt and reconciliation.
Explore - 03
Commercial
Sales & CRM
CRM shaped around your sales motion rather than a generic funnel: enquiry capture, qualification, estimation, negotiation and clean handover into delivery.
Explore - 04
Intelligence
Finance & Collections Intelligence
Collections and finance operations run as workflow: who owns each account, what was promised, what is disputed, and what will actually land this month.
Explore
Also built regularly:
Applied AI
Agents that are supervised, not trusted blindly.
AI is not the product. It is a capability inside the workflow — and it earns autonomy the same way a new employee does.
01 — Read
Inboxes, documents, tickets, records and operational messages.
02 — Analyse
Classify, compare against history, detect variance and gaps.
03 — Prepare
Draft the reply, the comparison, the summary, the brief.
04 — Route
Send it to the right person, queue or stage with context attached.
05 — Follow up
Chase commitments, re-check conditions, escalate on ageing.
06 — Execute
Take a narrow, enumerated set of permitted actions — nothing else.
The boundaries, stated up front
- Permissions: an agent can never read a record its requesting user could not open.
- Audit: every run records input, action, outcome and approver.
- Determinism: calculations, eligibility and policy stay in code, not in a prompt.
- Human approval: money, contracts, external commitments and deletions require a person.
- Escalation: low confidence hands work to a human, already prepared.
How we work
Five phases, each with an output you own
The same phases apply whether we deploy, adapt or build — the depth of each one changes.
- 01
Process Audit
1–2 weeks
We sit with the people who run the process and record how it actually works — including the parts that live in messages, memory and workarounds.
- 02
System Blueprint
1–2 weeks
The design: data model, users and permissions, workflow states, integrations, automation opportunities and explicit AI boundaries.
- 03
Working Prototype
2–4 weeks
One critical workflow, running with your data and your users. Not a slide deck, not a clickable mock — a system you can operate.
- 04
Build & Integrate
6–14 weeks
Production build: the full workflow set, integrations with existing systems, migration of live data, access control, testing and staged rollout.
- 05
Operate & Improve
Ongoing
Monitoring, support and a standing improvement cadence — plus the intelligence layer, which usually only becomes valuable once real data has accumulated.
Global delivery
Built for distributed businesses, wherever they operate
Multi-entity, multi-currency, multi-language and multi-timezone are design assumptions, not paid extras.
Our systems are designed for companies whose teams, sites, vendors and customers are not in one place. That shapes everything: access models scoped by entity and region, asynchronous approval flows, audit trails that hold across jurisdictions, and interfaces that work on a phone with poor connectivity as well as on a desk.
We build for operational reality rather than an idealised head-office scenario: intermittent connectivity, people working across shifts and time zones, approvals that must survive an audit months later, and reporting that has to reconcile across entities. Systems designed against those constraints hold up wherever a business operates.
Entities
Multi-company, multi-site
Access
Region and role scoped
Delivery
Async-first, distributed
Industries
Where we are starting
Six sectors where the gap between real operations and available software is widest. Starting points, not limitations.
Start here
Show us the process you run today.
Send us the workflow that is costing you the most time. We will tell you plainly whether it is worth building, buying or leaving alone.