Practical examples · A little less awkward

Same business.
A much more useful way to work.

The spreadsheet that’s doing three jobs. The paper form that gets typed up twice. The database only one person understands.

They all started somewhere sensible. Here’s what the next version could look like — built around the people doing the work.

Bryn proudly holding a laptop with a completed system.
Bryn’s note: “Same work. Fewer workarounds.”

These are illustrative examples, not client case studies. The sample screens show possibilities; the right solution depends on your process, people and budget.

From spreadsheet to shared workspace

When the spreadsheet becomes
the whole system.

A growing job list lives in Excel. Dates arrive by email, updates happen over the phone, and a colour in column H means something very important. If you know what it means.

  • One place to update the work.A shared job board could give each job an owner, a status and a next step.
  • Useful detail behind each row.Notes, documents and previous activity could stay with the job instead of being scattered across inboxes.
  • A clearer start to the day.See what needs attention and who is handling it, without asking which spreadsheet is current.

Bryn’s note: “Nobody should be frightened of column H.”

Job tracking · choose a view
Jobs_FINAL_v8(2).xlsx
The weekly job listSample data
Three jobs. A few unanswered questions.
JobOwnerStatus
104 · Site visitAlex?Date in email
105 · RepairSamParts ordered?
106 · Follow-upJoCall customer?

Latest copy on someone’s desktop. The colour key is in another tab.

Illustrative starting point · sample records, not a client system.
Team workspace / Jobs
A shared picture of the workConcept
Ready to start
JOB 104Site visitAlex
Next: confirm date
In progress
JOB 105RepairSam
Next: fit parts
Follow-up
JOB 106Customer callJo
Next: check result

A named owner, a clear status and the next step — in the same place.

Illustrative concept · one possible approach, not a finished product.

Sound familiar?
Bookings, repairs, orders, enquiries, projects — anything that moves through a set of stages.

A possible starting point
A small web application for the team, keeping the calculations and exports that still earn their place.

From paper trail to useful update

The work is done.
The paperwork isn’t.

Someone fills in a job sheet, takes a photo on their phone and brings the paperwork back later. Someone else deciphers it and types the same details into another system.

  • Record it where it happens.A mobile form could collect the notes, parts used and supporting photos while the details are still fresh.
  • Give the office a useful update.Once shared, the record could be ready for checking, follow-up or invoicing.
  • Make the next step easier.Agree what information is needed, then give people a short, clear way to capture it.

Bryn’s note: “A clipboard is a place to start. Not a place to get stuck.”

Job sheets · choose a view
Job sheet / Back at the office eventually

Job sheet · 104

Work completed
Replaced the seal
Parts used
1 × seal kit
Follow-up
Photo on my phone
Please type this up.
When it comes back.
Illustrative starting point · sample records, not a client system.
Job update / From the point of work
Job 104✓ Saved
Work recorded
CompletedReplaced the seal
Parts used1 × seal kit
Photo reference1 image attached
Office viewReady for reviewNotes, parts and the photo are together.

Next: check the work and prepare the invoice.
Illustrative concept · one possible approach, not a finished product.

Sound familiar?
Site visits, inspections, deliveries, maintenance and any work that happens away from a desk.

A possible starting point
An iOS or Android app, or a mobile-friendly web form. Where connection is patchy, we can discuss saving work offline and syncing later.

From old database to clearer workspace

It knows your business.
It just needs a way forward.

An Access database, a FileMaker system or an older application has served you well. Now the awkward parts are getting harder to ignore: access, reporting, maintenance or simply finding the right record.

  • Keep the knowledge that matters.We’d start by understanding the records, calculations and business rules the current system holds.
  • Make everyday tasks clearer.A new workspace could bring records, history and next actions together for the people who need them.
  • Plan the move properly.Data checks, a trial import and a sensible transition would be part of the conversation, not an afterthought.

Bryn’s note: “Keep the useful bits. Retire the rituals.”

Customer records · choose a view
Office PC / Customer records
It’s all here. Somewhere.Sample files
  • Customers.accdbMain database · use the office PC
  • Customer-export-latest.csvFor everyone who cannot open the database
  • Renewals-check.xlsxUpdated separately after each call

The useful rules are there. So are years of workarounds.

Illustrative starting point · sample records, not a client system.
Team workspace / Customer record
The record, in contextConcept
Example customer A
Example customer B
Example customer C
Last activity
Support call logged
Renewal
Due next month
Next step
Alex to confirm details

Details, history and next steps together, with access suited to each person’s role.

Illustrative concept · one possible approach, not a finished product.

Sound familiar?
Customer records, memberships, stock, renewals, scheduling or a specialist process with years of history.

A possible starting point
A Windows or macOS desktop application, or a shared web workspace. Sometimes improving or connecting the existing system is the better answer.

A practical approach

Keep what works.
Improve what doesn’t.

You don’t need to replace everything at once. A useful first step might be one better screen, one less handover or a connection between tools you already use.

  1. 01 · Understand

    Start with the actual work.

    Show us how things happen today — including the exceptions, sticky notes and unofficial shortcuts. They often explain what the system really needs to do.

  2. 02 · Shape

    Make the idea concrete.

    Work out what a better process could look like, what it needs to connect to and which details matter most. The format follows the job.

  3. 03 · Make useful

    Choose a sensible first step.

    Define a manageable scope, plan the data and agree how people will start using it. Build around the awkward bit that is worth fixing first.

Your business. Your awkward bit.

Not quite your industry?
Still your kind of problem?

That’s a good place to start. Tell us what’s frustrating, what you’re working around and what you wish were easier. Rough notes are plenty.

A question about existing software, or just touching base? Contact the team.

Windows · macOS · iOS · Android · Web · Connections between existing tools

Bryn enjoying a cuppa after getting the paperwork sorted.
Bryn’s note: “Tell us the awkward bit.
We’ll put the kettle on.”