Narrow the scope
Understand the consequential bit and resist allowing a bounded workflow problem to become a platform programme.
Mark Kaye · founder of RZLVR
Experienced enough to know what not to build.
RZLVR applies senior technology judgement to narrow, consequential operational problems—without turning them into large technology programmes.
Why RZLVR exists
Senior experience, used with restraint.
Mark has spent more than two decades designing, improving and operating business-critical technology across logistics, retail and government. He co-founded Cognigent, which later became Flo Group—the logistics technology consultancy acquired by Accenture—serving as a senior consultant and country manager.
That experience taught him that the most valuable technology decision is often a smaller one: preserve the systems that work, isolate the real source of friction and build only what the outcome needs.
RZLVR exists to make that level of judgement available to UK SMEs without the machinery, hand-offs or appetite for scope that often comes with a conventional programme.
Selected previous experience of RZLVR founder Mark Kaye
Previous professional feedback
What people said about Mark’s earlier work.
“Mark, you are a serial optimiser!”
“Mark's architectural vision and technical depth were pivotal to the success of a €1 million information management programme. He brings rare clarity, professionalism, and leadership that inspire confidence at every level.”
“Mark is an excellent Solutions Architect with deep expertise across Documentum, application servers, and infrastructure. His design leadership and technical insight were key to the success of our Network Rail deployment.”
“Mark is a highly motivated technology consultant with deep technical knowledge and an infectiously enthusiastic attitude. He brings energy, expertise, and genuine passion to every project — a pleasure to work with.”
How that experience shows up
Small scope. Serious value. Grown-up care.
Enterprise experience is useful here because it improves judgement—not because a bounded SME workflow needs enterprise ceremony.
Use engineering judgement
Choose a changed process, an existing feature, an integration or bespoke software according to the job—not the sales model.
Build for working life
Treat access, monitoring, documentation, maintainability and exit as part of the solution rather than aftercare.
Keep accountability close
The person assessing the workflow remains close to the technical and operational decisions that follow.
A direct first conversation
Show Mark the real workflow.
No slides and no transformation preamble. Thirty minutes is enough to decide whether a focused intervention is plausible—and whether doing nothing is the better answer.
Book the workflow screen-share