Keep the know-how.
Lose the workarounds.
Excel, Access, FileMaker, paper forms—or a bit of everything. We turn the systems you’ve outgrown into useful software built around your team.
You know how your business works. Our job is to understand it, untangle the awkward bits and build something that makes the working day easier.
Windows & macOS desktop · iOS & Android · Web applications
What are you working with today?
These tools probably earned their place. The question is whether the workarounds around them are now costing more effort than the job itself.
A spreadsheet that has quietly become the whole system.
The formulas are clever. The daily routine is less so: copying rows, fixing broken links and checking which version everyone is using.
Those sheets often contain years of useful business rules. We work out what needs to stay, then design an application that makes those rules easier to use.
A database only one person dares to change.
It still does an important job. But a new report, another user or a different way of working has become a bigger task than it should be.
We look at the tables, relationships, queries, forms and reports—not just the screens. That gives us a sensible starting point for the next system and its data migration.
A useful FileMaker solution you’re starting to outgrow.
What once fitted neatly now needs more workarounds. Perhaps the team has changed, customers need access, or the system needs to do a different job.
We explore the layouts, scripts, data and connections you already depend on. Then we work out what to retain, what to rethink and whether a replacement is the right move.
The form is filled in. Then someone types it all again.
Clipboards, job sheets, folders and handwritten notes get the job started. Finding the latest information—or passing it to the next person—is where things slow down.
We follow the paperwork through the business and design a digital process around it: capture information once, make the next step clear and help people find what they need.
A collection of tools held together by good people.
A spreadsheet here, an old database there, details in an inbox and a process that mostly lives in somebody’s head. Everyone is doing their best to join it up.
We map what happens between the tools, then start with the part that creates the most friction. Sometimes that means a connection; sometimes it means a new application.
At a desk. On the move.
In a browser.
You do not need to choose a technology before we talk. We help you work out where the application should live, who needs to use it and what it needs to connect to.
Windows & macOS desktop apps
For the work that happens at a desk, on Windows or Mac: managing records, planning jobs, producing documents and getting a clear view of the business. We can plan for local files, printing and offline working where the job needs them.
Office systems · Operations · Reporting
iOS & Android apps
For the people doing the work away from a desk. Apps for iPhone, iPad and Android devices can put forms, job details, photos and updates where they are needed. Connectivity and any offline requirements are part of the design.
Site visits · Inspections · Field teams
Web applications
For a team, customer or partner who needs access through a browser. From shared internal tools to customer portals, we design the screens, roles and workflow around the people using them.
Shared systems · Portals · Browser access
And they can work together.
A mobile app for the field team. A web view for the office. The same job moving between them. We plan the connections, permissions and data flow as part of the system.
First, we understand.
Then we build.
The most useful software starts with the right questions. We keep the conversation practical, show our thinking and work through the decisions together.
“Measure twice.
Set fire to nothing.”
— Bryn, keeping things sensible
Show us the real working day.
Walk us through the files, forms and little rituals that keep things moving. We listen to the people using the system and identify the part that would make the biggest difference.
Make the plan clear.
We turn that conversation into a practical outline: what the application will do, what the first version includes and how it might look. Scope, costs, timings and ongoing needs are discussed before development begins.
Build it with your feedback.
You see working progress and try the important tasks as the application takes shape. We check the everyday jobs, the awkward exceptions and the details that make it feel right for your team.
Move over with a plan.
Existing data, backups, checks, training and the changeover all need thought. We agree a sensible route into use, plus what support and future changes will look like.
Before we talk.
You do not need all the answers yet. These are the things we can work through together.
Explore our ready-made software →Do we need a technical brief?
No. A few lines about what you use, who uses it and what keeps getting in the way are enough to start. You bring the business knowledge; we help work out what the software needs to do.
Can you bring our existing data across?
Often, yes. We first need to understand how it is stored, what can be exported and whether it needs cleaning up. We plan and test the move, including checks against the original records, rather than assuming an export tells the whole story.
Do we have to replace everything at once?
Not necessarily. We can explore a smaller first phase or a staged changeover where the systems allow it. The aim is a workable transition for the team, with clear decisions about what stays and what changes.
What will it cost, and how long will it take?
That depends on the workflow, number of users, integrations and data involved. We discuss the scope, an estimate and a realistic timetable before development starts. Hosting, licences and ongoing support are considered alongside the initial build.
What happens after launch?
We agree the handover and support arrangements as part of the project. That includes what your team needs to run the system, how issues are reported, and how maintenance or future improvements will be handled.
What if an existing product would do the job?
Then it is worth looking at. Bespoke software makes sense when the way you work needs something more specific. We can talk through the options—and our ready-made tools are another useful place to start.
Show us the awkward bit.
Let’s get it sorted.
Tell us what you use now, who uses it and the one thing you wish it did better. No polished presentation needed.
Bryn’s ready. The kettle’s on.