- People copy, re-key, reconcile or chase the same things
- A spreadsheet or inbox now holds up part of the business
- Two useful systems don't share the right information
- You can see the delay, the errors or the one person it all depends on
- You want to fix one real job before talking about anything bigger
Practical software for UK SMEs
The work between your systems, fixed.
Your accounts, CRM and spreadsheets mostly work. The trouble is the copying, chasing and re-keying between them.
Show us one job like that. We'll tell you if it's worth fixing.
Not sure where to start? Take the Faff Score.
RZLVR means resolver. We took the unnecessary bits out. It seemed appropriate.
Say you invoice 40 jobs a week
Before
Job sheets typed into the accounts system40 jobs · about 8 mins each
5 hrs 20mins a weekA small RZLVR fixpull · draft · check
After
Invoices out the day the job's done40 drafts · about 1 min each
40mins a week4 hrs 40 mins backevery week, from one job
Who it's for
Is your problem a good fit?
The best first job is one clear job that comes round every week, with an owner who cares how it turns out.
- You need to replace a whole core system
- Nobody owns the process or agrees what good looks like
- The brief is just "put AI on it"
- Every case is different and needs someone's judgement
- An existing product or a changed process would do the job better
What we fix
The awkward work between systems.
We fix the re-keying, reconciling, document-making and chasing between the tools you already pay for.
Enquiry to quote
Take the details once, create the documents and put the next step in front of the right person.
Weekly reporting
The report is checked and ready on Monday morning, and nobody spent Friday building it.
Approvals without chasing
Send each request to the right person and show where it's stuck.
Document generation
Turn checked data into proposals, job sheets, certificates or client packs in a few clicks.
Single-job apps
One simple screen for one job, such as handovers, stock control or site updates.
System integrations
Connect the specialist tool you rely on to the accounts, CRM or spreadsheet it won't talk to.
Workflow automationBusiness process automationSystem integrationReporting automationDocument automationInternal tools & micro-apps
Sometimes the right answer is a changed form or a feature you already pay for. If so, we'll say.
How it works
Three steps, no requirements document.
1. Show us the job on a 30-minute screen-share.
2. If it's worth fixing, get one fixed price before any work starts.
3. We build it, test it on real work, and host and support it if you want us to.
Who you'll work with
Senior experience. Deliberately small delivery.
Every job is led by Mark Kaye, the founder. Before RZLVR, Mark spent more than two decades designing, improving and running business-critical technology. He co-founded Cognigent, which later became Flo Group, the logistics technology consultancy acquired by Accenture.
You deal with the people doing the work, from the first call to the finished fix. If something we support breaks, you contact us.
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.”
Pricing
Small jobs, priced up front.
The screen-share is free. After that we price the actual job, not a package. A first fix usually costs £1,500 to £3,500. You get one fixed figure before any work starts.
Start here
Problem screen-share
£0
30 minutes on a video call. You show us the real workflow, and we tell you whether a fix is worth doing.
Book a 30-minute screen-shareA first fix
Automation fix or small app
Fixed price, agreed first
One clear job, with the scope, the result and the finish line agreed before we build.
- Nothing you don't need
- A working release
- Plain-English handover
After launch
Managed care
Optional
Hosting, monitoring, backups and a human to contact, priced to fit what we build.
- Clear response window
- Sensible change allowance
- No long tie-in
Fair questions
Before you show us your spreadsheet...
Will we have to replace our current systems?
Usually not. We work with the tools your team already knows, and connect or simplify them where it helps.
Do you use AI?
Sometimes, where it does a job well, such as sorting messy text. We don't use it where a simple rule, form or integration does the job better.
Who owns the software and data?
Your data is yours. The proposal sets out who owns the code and how it can be reused. There are no exit fees and no data traps.
How long does a first fix take?
A first fix usually takes two to six weeks once the scope is agreed. Small ones can be quicker. Complex integrations may need a short look first.
Book a screen-share
Pick a time, or send us the problem.
30 minutes on a video call. We'll tell you whether it's worth fixing, and when a perfectly ordinary spreadsheet is still the right answer.
Book a 30-minute screen-share
Rather write it down? Send it here and we'll reply with a couple of times.