07 / Internal tools & software

Tools for the work your software doesn't handle.

A spreadsheet can become hard to manage. A team may need one place to see status, record a decision or handle a request. We start with the task and the people doing it, then check whether existing software can cover it before proposing a custom tool.

Show us what’s stuck
Choose the useful view

A tool needs
a clear job.

Start with one task people can try. Each screen should help someone act, not just add another place to check.

Internal tool

A place to review requests, update status or record a decision. Agree the users and what each one can change.

Dashboard

One view of information from known sources. Show missing or stale data and name the person responsible for acting on it.

Custom software

A focused system when existing tools cannot handle the task well. Start with the workflow and its upkeep, then decide what to build.

Give your team a clearer way to handle the task.

A focused tool with an agreed job, clear access and a way to check whether it makes the work easier.

What the work can cover

  • 01A walk-through of the current task and its users
  • 02A check of existing tools and available data
  • 03A small working version for the agreed use case
  • 04Permissions and input checks suited to the data
  • 05Testing with representative tasks and failure cases
  • 06Source, access and upkeep arrangements in writing

These projects are quoted after a review. The scope names the users, screens, data sources and tasks included. Hosting, licences, migrations and ongoing care are separate. A dashboard needs reliable source data; displaying a number does not make it accurate.

See the project scope and prices
Worth knowing

Your questions,
answered.

When is custom software worth it?

When an important repeated task remains awkward after checking what existing tools can do. We compare the cost of the problem with the build and its ongoing upkeep before recommending it.

Can we start with one part?

Yes. Agree one task, the people using it and a useful starting measure. Expand only after the first version has been tried in the real workflow.

Who looks after it afterwards?

Your quote sets out hosting, account control, documentation and any support arrangement. Ongoing support is a separate scope, not an unstated lifetime promise.

Start with the problem

Show us
what’s stuck.

A few sentences are enough to start. We’ll read them and reply at no charge.

Show us what’s stuck