About Brilliant Systems
Built by the people who answer at 2am.
We have been shipping production software since 2017, for hospital groups, infrastructure contractors, aviation suppliers and more than fifty technology start-ups. Every line of it written by our own engineers.
What we are
An engineering firm that also runs its own products.
Most software firms sell hours. We do that too, but we also build and operate two live platforms of our own, Open Lance and BotUp, which carry real users and real transactions every day. That changes how we work. When you run the thing you built, you stop shipping decisions you would not want to be woken up about.
It also means the AI capability we sell is the AI capability we depend on. Model evaluation, guardrails, cost caps and audit trails are not a service line we assembled for a pitch; they are the machinery keeping our own products honest.
The team is deliberately senior. There is no junior bench being funded by your budget and no delivery partner in another timezone quietly doing the work. The engineers who scope your build are the ones who write it and the ones who maintain it afterwards.
How we work
Five commitments, each with a number attached.
Principles are cheap. These are the ones we are willing to be measured against, and the evidence we hold ourselves to.
-
01
Engineering, not engineering theatre
No résumé-padding technology choices. We pick the smallest architecture that meets the requirement, then defend it in review.
- Around 40% fewer moving parts than comparable builds
- Replaced one client’s twelve-service estate with three modules
-
02
Security is a practice, not a phase
Threat modelling starts in week one. Every project runs a dedicated red-team week before launch rather than a pen test after it.
- Zero critical vulnerabilities in production since 2017
- Dependency and secret scanning on every push
-
03
The 2am rule
If we would not be willing to answer the phone about it at 2am, we should not have built it that way. Support is designed in, not bolted on.
- 10-minute median response on critical issues
- Every client gets direct access to their engineers
-
04
Built to outlive the engagement
Systems ship with the seams needed to extend them. You should not need us in three years, and most clients keep us anyway.
- 80% of our five-year-old systems still scale without a rewrite
- Documentation and handover written for engineers who have never met us
-
05
Transparency by default
You see the same board we do. Scope, spend and risk are visible continuously rather than summarised in a monthly status call.
- Live project dashboards from day one
- Cost-against-outcome tracking, not just hours burned
How an engagement runs
You will always know what happens next.
Most of the risk in hiring a software firm is not technical, it is procedural. Not knowing who is doing what, or when you will next see something real. Here is the whole shape of it.
-
Week 0
A conversation with an engineer
Not a discovery call with a salesperson. Someone who will actually work on the build reads what you sent and comes back with questions, constraints and an honest read on feasibility.
-
Week 1
Written scope and fixed price
Architecture, milestones, assumptions and price, in writing, before anyone commits. If our estimate turns out wrong, that is our problem to absorb, not a change request.
-
Weeks 2+
Build in the open
You get repository access, CI results and a live board from day one. Demos every sprint against working software, never slides.
-
Pre-launch
Red-team week
Before anything ships we attack it: threat model review, dependency and secret scanning, load and failure testing, and a written report of what we found and fixed.
-
Launch +
Handover and support
Documentation written for engineers who have never met us, then 24/7 cover from the same people who built it. No transition to a support tier that has never seen the code.
What you walk away with
You own it. All of it.
The uncomfortable question nobody asks on a sales call is what happens if this goes wrong, or if you simply want to bring the work in-house. Our answer is the same either way.
-
You own the code outright
Full IP and repository transfer on final payment. No licence, no seat fees, no permission needed to change it later.
-
No proprietary lock-in
We build on mainstream, well-supported technology. Nothing we write depends on a framework only we understand.
-
Documented for a stranger
Handover is written for an engineer who has never spoken to us, because one day that is who will be reading it.
-
Leave whenever you want
No minimum term on support. If you take the work in-house we help you transition rather than making it difficult.
What we invest in
We spend our own capacity staying good at this.
The team behind it
A hundred senior engineers, none learning on your budget.
We do not staff projects from a junior bench. The people who scope your build are the people who write it, and the people who maintain it afterwards.
Who we build for
The organisations that trust us with production.
A track record spanning enterprise groups and more than fifty technology start-ups, some of them for the better part of a decade.
Next step
Talk to the engineer who would run your build.
No discovery call with a salesperson, no deck. A senior engineer reads what you send and replies with a real assessment, including when we think you shouldn’t build it.
