There is already a product for it.
Use something already built.
Simply Works products solve specific recurring jobs and are maintained as products rather than one-off builds.
Less friction. More progress.
I build and run focused products, make Small Tools for specific manual jobs, and use Friction Audits to find the places where people get stuck.
Use an existing product if it fits. Know the job that needs fixing? A Small Tool may be enough. Know something's wrong but can't see why? Start with a Friction Audit.
You do not need to diagnose the whole business before choosing a next step.
Use something already built.
Simply Works products solve specific recurring jobs and are maintained as products rather than one-off builds.
Remove the annoying job.
A Small Tool handles one specific repetitive, manual or awkward job without turning it into another giant platform.
Find the friction first.
A Friction Audit shows where people hesitate, guess, backtrack or do unnecessary work before you decide what to change.
Products
Software already built for recurring problems.
Built and run by Simply Works
Simply Link
Simply Link is for UK solo professionals and small service businesses who finish the work and then still have to remember who owes what, what is due and when something needs chasing.
Create the request, send it, track what happens and keep the follow-up in one place.
Create
Preview
Make live
Share
Track
Paid
Friction Audits
A small wording, hierarchy or handoff problem can create much larger downstream work. A Friction Audit follows those moments back to the cause instead of treating the symptom.
See Friction AuditsTwo options look equally important.
They have to decide what your interface means.
Progress becomes hesitation or abandonment.
The tiny interface problem becomes real work elsewhere.
Recommended changeMake one action primary. Explain when the alternative is appropriate.
Small Tools
Sometimes the right answer is not another platform. It is one focused tool that removes one repetitive job.
Explore Small ToolsExport CSV → delete columns → calculate totals → reformat → paste into report
Drop in CSV → ready report
Illustrative example, not a client case study.
Understand the actual difficulty before making the solution bigger.
What is the person having to figure out?
What happens because of that problem?
What is the smallest useful change?
I'm Jonjo. I have a Computer Science background, around a decade of field-service engineering experience and years of building software.
That work trained me to notice ambiguity, hidden assumptions, awkward handoffs and the knock-on effect of a small bit of bad logic.
You deal with me. I do the work.
More about me