// problem solvers who build

Your problem, thought through. Then built.

We start with your problem, not with the software. We work out how your club or association really runs, find the knot, and build a bespoke browser tool that undoes it.

thinking.log
  1. problem 140 competition entries, 3 volunteers, 1 spreadsheet
  2. ask why does Saturday take 4 hours to set up?
  3. finding 80% of the time goes on fixing bad entries
  4. insight make entries check themselves
  5. build self-validating entry form + live draw
  6. result set-up takes minutes, not hours
An illustrative example of how we work
  • Golf clubs
  • Garden clubs
  • Associations
  • Sports & social clubs
  • Charities
  • Small businesses

01 How we think

The code is the easy part. Understanding the problem is the job.

A

Understand before building

We sit with the people doing the work and map how things really happen, which is often different from how the handbook says they happen.

B

Find the real problem

The request is often "we need an app". The problem underneath is usually smaller and sharper. That's the one we solve.

C

Build the simplest thing that works

No bloat and no features nobody uses. You get one focused tool, secure by default, that your least technical member can use first time.

02 Problems solved

From the tangle to the fix.

These are the kinds of problems we untangle. Every organisation's version is different, which is why every tool we make is bespoke.

Golf club

Tangle

Competition results typed up by hand on Sunday night, with errors found on Tuesday.

Fix

Scores go in on the course and the leaderboard updates live, with the maths done for you.

Garden club

Tangle

Show entries on paper slips, judges' sheets rewritten, and prize lists pieced together at the end.

Fix

One schedule: entries, judging and results flow through a single simple tool.

Association

Tangle

Renewals chased by email, so nobody knows who's paid and the committee sees stale numbers.

Fix

A member portal with renewal tracking and a live dashboard for the committee.

03 Process

Four steps. No surprises.

  1. 01

    Listen

    A plain-English conversation about what's painful and what good looks like.

  2. 02

    Untangle

    We map the problem and agree the one thing worth solving first.

  3. 03

    Prototype & forge

    You can click something real within days. Then we build it properly: tested, secure and tried out before it goes live.

  4. 04

    Look after

    We handle hosting, backups and fixes, and we're ready for the next problem on your list.

  • Runs in any browser, with nothing to install
  • HTTPS and multi-factor sign-in for private areas
  • Hosted on AWS, and the data stays yours

// next step

Bring us a problem.

Tell us what's taking too long, going wrong or living in a spreadsheet nobody trusts. We'll come back with honest thinking and no jargon.

hello@vibesmith.net