1989-1994
RSAMS, charities and associations, and the first proof that business logic can be encoded faithfully in software.
Founded by Alistair Hancock in Cambridge in 1989, Rubicon has moved from early membership systems to enterprise web platforms, rules engines, AIM public-company life, long embedded partnerships, and now AI adoption and decision intelligence.
Origin
Rubicon began with RSAMS, a fundraising and membership system built while Alistair Hancock was studying Computer Science at St John's College, Cambridge. It was a modest first product, but it established the logic that still defines the company.
What computers are capable of has changed dramatically since 1989. The mission has not: getting computers to do what they are best at so people have more time for what they are best at.
History
Rubicon's history matters because the current AI proposition is not a clean-sheet reinvention. It is the latest expression of capabilities that have been built and tested in real operations for decades.
RSAMS, charities and associations, and the first proof that business logic can be encoded faithfully in software.
ACAS, BAE Systems, ICI Paints, DuSpec, DFinity, Borland Application of the Year 2000, CRM Innovation of the Year 2001.
Financial-services pivot, Accelerator rebuilt as a rules and workflow platform, Norton Finance signed, and AIM flotation in 2006.
Private again, deeper embedded relationships, including a 14-year development partnership with Segen.
Anchor, Sabre, and a focused AI adoption consultancy grounded in accountability and delivery discipline.
Principles
Rubicon has kept notable clients for eight, fourteen, and twenty years because the work is not organised as short-term theatre. Advice, engineering, and responsibility stay connected.
The answer may be AI, a rules engine, a workflow system, or something simpler. The discipline is in choosing correctly.
Rubicon has built products since 1989, so recommendations come from shipping and running systems, not just specifying them.
Institutional knowledge is retained because the work is not thrown over the wall after the project phase ends.