- People repeatedly copy, re-key, reconcile or chase
- A spreadsheet, inbox or workaround has become operational infrastructure
- Two useful systems refuse to share the right information
- Delay, effort, error or key-person dependency can be observed
- You want to improve one real workflow before discussing anything larger
Practical software for UK SMEs
Practical technology for awkward business problems.
You already have the main systems you need. The problem is what people have to copy, chase, check and rebuild between them.
RZLVR means resolver. We removed the unnecessary bits. It seemed appropriate.
- Smallest sensible solution
- Clear proposal before work
- Hosted and supported
One weekly reportIllustrative workflow · agree the real measure first
Before
Three exports, copy-paste and chasingFriday afternoon · built by hand
47minsA focused RZLVR interventionconnect · check · prepare
After
Checked weekly report, ready to useOpen it · review it · send it
4mins43 minutes backevery week, from this one task
Problem firstStart with the work, not a product.
Engineered to fitKeep the systems that work.
Built without bloatOnly what the outcome needs.
Run responsiblyHosted, monitored and supported.
A useful working fit
The systems are in place. The manual work between them is the problem.
RZLVR works with UK SMEs that have a real operational problem worth fixing. The best first problem is bounded, recurring and owned by somebody who cares about the result.
- You need to replace an entire core platform
- The process has no owner or agreed outcome
- The brief is simply to “put AI on it”
- Every case is genuinely different and judgement-heavy
- An existing product or changed process would solve it more sensibly
Usually brought to us byOwner or managing directorOperations leaderFinance or operations managerCommercial leader
Founder experience
Senior experience. Deliberately small delivery.
RZLVR is led by Mark Kaye. Before RZLVR, Mark spent more than two decades designing, improving and operating business-critical technology environments, and co-founded Cognigent, which later became Flo Group—the logistics technology consultancy acquired by Accenture.
RZLVR applies that judgement differently: not to create another transformation programme, but to solve one awkward operational problem properly.
Why Mark built RZLVRSelected previous experience of RZLVR founder Mark Kaye
“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.”
Problems we solve
The awkward work between systems.
Most operational friction lives between the tools you already pay for. We fix the re-keying, reconciling, document-making and chasing that falls through the cracks.
Enquiry to quote
Capture the useful details once, create the right documents and put the next action in front of the right person.
Operational reporting
Bring figures together, check the repeated bits and deliver a concise weekly view without the Friday-afternoon ritual.
Approvals without chasing
Route requests, surface hold-ups and keep a useful audit trail without adding another sprawling platform.
Document generation
Turn checked data into consistent proposals, job sheets, certificates or client packs in a few clicks.
Focused micro-apps
Give a team one clear interface for the job, whether that is handover, stock control or site updates.
System integrations
Connect the specialist tool you rely on to the accounts, CRM or spreadsheet it refuses to talk to.
SMALL
ON
PURPOSE
ON
PURPOSE
Enough engineering to solve the problem.
Nothing extra to feed.
Our engineering principle
Build only what the job needs.
We are not here to sell a transformation programme or force a new platform around every workaround. We find the smallest dependable intervention that improves the outcome.
- ✓Use what you have
We integrate before we replace.
- ✓Keep people in the right loop
Automate repetition, not responsibility.
- ✓Collect less data
Only what the job and support genuinely need.
- ✓Design the exit
Clear documentation, sensible exports and no hostage-taking.
The Smallest Sensible Solution method
A direct route from awkward work to a proved outcome.
This is the RZLVR delivery principle: understand enough to intervene safely, build only what earns its place, and prove the result before expanding the scope.
- 01
Show us the problem
A 30-minute screen-share beats a 30-page brief. Walk us through the real process, including its workarounds and awkward edges.
- 02
Observe the workflow
We trace where information starts, who touches it, which decisions matter, what fails and what a good finish looks like.
- 03
Quantify the friction
Together we agree the useful measure: handling time, turnaround, error, chasing, reporting delay, continuity risk or days-to-cash.
- 04
Choose the smallest intervention
A form, changed hand-off or existing feature may be enough. Where software earns its place, we define one bounded release.
- 05
Prove the outcome
We test with representative work and compare the result with the agreed measure before widening the scope.
- 06
Host and support it
We can run, monitor and maintain what we build, with documented dependencies, exportable data and a human to contact.
Proof before expansion
Agree what better means before building.
A Faff Score can point to an exposure; it cannot prove a business case. For paid work, the workflow and its baseline are examined directly and the relevant measure is agreed in the proposal.
Sometimes the right answer is not to build. A changed form, clearer owner, better template or feature you already pay for can be the smallest sensible solution.
Why RZLVR?
Choose the lightest responsible way to solve it.
These alternatives all have a place. The distinction is knowing when a focused, operationally supported intervention fits better.
Another SaaS platform
Choose this when
A mature product fits most of the process and the team can adopt its way of working.
Choose RZLVR when
The existing systems are useful and the awkward joins between them are the real problem.
A no-code specialist
Choose this when
The automation is clearly understood, low risk and contained within a familiar platform.
Choose RZLVR when
The job needs workflow diagnosis, engineering where necessary, operational support and a documented exit route.
A software agency
Choose this when
The brief is a larger product, complex interface or substantial programme needing a broader delivery team.
Choose RZLVR when
The intervention is too small for conventional bespoke delivery but too important to remain a workaround.
Build it internally
Choose this when
Somebody has the time, mandate and operational responsibility to own it properly.
Choose RZLVR when
The team needs senior attention and accountability without creating another unsupported side project.
How pricing works
Small scope. Serious value.
The screen-share is £0. After that, we price the actual job—not a package. You see the outcome, scope and one clear figure before you commit. Because we strip away unnecessary software, you may be surprised how much operational value a focused intervention can unlock.
Start here
Problem screen-share
£0
30 minutes to see the real workflow, understand the snag and decide whether a bounded intervention is plausible.
Show us the problemA defined first move
Automation fix
One clear figure
One well-bounded process with the scope, outcome and finish line agreed before we build.
- No packaged bloat
- Working release
- Plain-English handover
The useful middle
Bespoke micro-app
Built for value
A focused tool stripped to the essentials, so the operational benefit can feel disproportionately large beside the amount of software involved.
- Smallest sensible build
- Short feedback loops
- Launch and team walkthrough
After launch
Managed care
Optional, not assumed
Hosting, monitoring, backups, dependency care and a human to contact, quoted to fit what we build.
- Clear response window
- Sensible change allowance
- No long tie-in
What changes the figureNumber of systemsAPI availabilityData qualityException volumeSecurity requirementsInterface complexity
Built like it matters
Small software still deserves grown-up care.
Security in the scope
Access, data handling, backups and recovery are considered from the start — not added as a launch-day footnote.
No mystery machinery
You get a clear account of what the tool does, where it runs and what it depends on.
Continuity without lock-in
Choose managed support for convenience, not because your data or operations have been trapped.
Who you work with
Senior attention. A short chain of accountability.
Your first conversation, workflow assessment and build decisions stay close to founder Mark Kaye—the person accountable for the result.
RZLVR is deliberately focused: fewer hand-offs, direct communication and no junior delivery layer between the operational problem and the engineering response. Where specialist help is appropriate, responsibility for the finished system still remains clear.
If something supported by RZLVR breaks, you contact RZLVR—not a marketplace of anonymous contractors.
Fair questions
Before you show us your spreadsheet…
If yours is not here, send it over. A direct answer is free.
Is this only for large automation projects?
No. The best first job is often an annoyingly small process that established software ignores. We start there, prove the value and only widen the scope if it earns it.
Will we have to replace our current systems?
Usually not. We prefer to work around the tools your team already understands, connecting or simplifying them where sensible.
Do you use AI?
Sometimes, when judgement-like tasks such as sorting messy text genuinely benefit from it. We do not force AI into work that a dependable rule, form or integration handles better.
Who owns the software and data?
Your data is yours. Ownership and reuse of bespoke code are set out plainly in the proposal; there are no surprise exit fees or proprietary data traps.
How quickly can we start?
A focused first release commonly takes two to six weeks after scope is agreed. Tightly scoped interventions can be quicker; complex integrations may need a short discovery first.
What will it cost?
The 30-minute problem screen-share is £0. If there is a fit, we recommend the smallest sensible intervention and give you one clear proposal before any paid work begins. No packaged bloat and no bigger programme than the outcome needs.
What happens after launch?
Managed care can cover hosting, monitoring, small updates and human support. If you prefer to run it, we provide a sensible handover.
A useful first conversation
Show us the problem. We’ll trace the workflow.
We will tell you whether it is worth fixing, what the smallest sensible solution looks like and when a perfectly ordinary spreadsheet is still the right answer.
Taking on focused UK SME projects
Initial calls are 30 minutes, by video.