If the job depends on spreadsheet workarounds, scattered updates or one person's memory, the next step may be a focused tool. We define the useful task first and check existing options before proposing a custom build.
A generic interface example, not a delivered client app.
Work list
JOB-1042
Site inspection
Needs attention
JOB-1043
Prepare estimate
Ready
JOB-1044
Schedule visit
Waiting
Selected job
JOB-1042
Next action
Confirm access requirements
Due
Thursday
Notes
Photos and scope kept with this job
01
See what needs attention
02
Keep the details together
03
Give the team a clear next action
Let's start with what matters
Another system is only useful if people can actually use it.
You may be wary of a complicated build that creates more upkeep. We keep the first version centred on a real task: what someone needs to see, the action they take and who needs the result. That gives you a practical way to judge the work before considering extra features.
What the work is designed to change
01
Put the useful information together
A tracker or dashboard can show the agreed details in one place. People can see the current state and the next action without piecing together several sources.
02
Build around a real routine
Define the users, essential data and access needs before building. The first version has a clear job, so you can review it against how the work is actually done.
03
Keep ownership and upkeep clear
Hosting, access, data handling, handover and support belong in the agreement. The ongoing responsibility is part of the decision to build.
A brief can start here
Does this sound familiar?
Illustrative briefs to help you picture the work. Your deliverables and scope are agreed around your business.
01
Your spreadsheet has become a job in itself.
Several people use the same file, status is hard to follow and the useful information is scattered across tabs.
What we would work on
We turn the essential workflow into a focused tool, agreeing the users, information and key actions first. A usable first version is reviewed before more features are added.
A small, prioritised specification
Clear screens and user permissions
An agreed hosting and support plan
02
A useful online experience, shaped around your idea.
You want a guided selector, simple calculator or booking enquiry flow that your current website cannot comfortably provide.
What we would work on
We work out the inputs, decisions and useful result, prototype the interaction and check it on desktop and mobile. Integrations and ongoing costs are agreed before the build.
A practical interaction prototype
A tested responsive experience
Source and operating instructions as agreed
Business uses
A focused tool for one useful job.
Job trackers that show what needs attention and who acts next
Booking or request tools that keep the essential details together
Simple dashboards that make current work easier to review
Admin helpers and calculators built around a defined repeatable task
Studio work
An interactive project from the studio
Our own project
Apricorn Club is a self-initiated, independent and non-commercial fan project. It shows our approach to a custom interface and responsive interaction; it is not a client tool or evidence of paid-client outcomes.
We check off-the-shelf options first and define the smallest useful scope before proposing bespoke work.
01
Users
Who will use the tool and what each person needs to see.
02
Main task
The one job the first version must make clearer or easier.
03
Essential data
Only the information needed to complete that task well.
04
Access needs
Who can view, add or change information.
05
Handover and support
Whether your team takes over or asks us for optional ongoing support.
“Experience building systems that have to work in the real world, every day.”
If you're still weighing it up
The hesitation is worth talking about.
What if an off-the-shelf tool already does this?
Then it may be the better choice. We check the main task against existing options first. Bespoke work makes sense when there is a clear requirement that a simpler available approach does not meet.
How do we stop the project becoming too big?
Agree the users and essential task for the first version, with a written scope and review points. Additional ideas can be considered separately, so they do not silently become part of the original build.
Need the website and marketing to work together?
Growth brings website care, Google and Meta ads, a monthly page improvement and regular social content together. Materials and automation can be added.
Custom tools are quoted as a fixed-price project, with the agreed scope written down before work starts.
Optional support is agreed separately. Additions outside the agreed scope receive a separate quote, and any paid platform subscriptions remain separate from our fee.