About

Twenty years of events. Then the systems.

Pivot is the practice of Alex O'Neill. For over two decades he was director of a UK group-travel & events company — events across England, Holland and Dubai, groups arriving from Australia to Kenya. This site is what happened when the software he needed didn't exist.

He built the systems himself — bookings, quoting, payments, live operations. Turnover grew while overheads fell, and the same systems now handle multiple millions a year across several businesses. Every case study on this site was designed, built and shipped by the same hands.

Verify on LinkedIn ↗

Alex — founder and lead product engineer at PivotAlex O'NeillFounder & lead product engineer

The story

Operator first. Engineer second.

01

On the floor

Twenty-plus years directing events — England, Holland, Dubai — welcoming groups from every corner of the world. Budgets, suppliers, coaches at dawn, and every way an event day can go sideways.

02

Building the systems

Off-the-shelf tools never fit how a real events business runs. So the company built its own — bookings, quoting, payments, operations. Turnover up, overheads down, and software became the quiet advantage.

03

Pivot

Those systems now handle multiple millions a year across several businesses. Pivot exists to build the same class of systems for other event businesses — and the agencies that serve them.

How he works

Trust is the method.

01

Operator’s eye

Every feature is judged the way an event director judges it: does this survive contact with a real event morning? I’ve stood where you stand.

02

Ownership

One engineer owns your project from architecture to handover. Nothing is thrown over a wall, because there is no wall.

03

Communication

A demo every week and plain-English updates anyone in the business can sit in on. You always know exactly where the build stands.

04

Built to hand over

Documented, conventional, deployed — and walked through with whoever maintains it. Handover is a deliverable, not an afterthought.