Work

Real problems. Observed results.

I am starting my independent practice. Here are two anonymised internal tools built in a professional role within a large company, alongside a personal project.

The professional tools are not public. Their gains relate to the tasks and volumes described; the personal project reports technical results, with no measured saving in business time. These results do not predict those of another project.

Personal tracking tool

Bring planning, tracking and adjustments together in one tool.

Personal project · installable web application

The need

The aim was to prepare a programme, track progress and make adjustments without switching between tools.

The challenge was continuity between planning and use: a programme needs to remain adjustable as it progresses, without rebuilding information already entered.

The solution

Bring the programme, timers and alerts together in an installable application. Structure the data so the programme can be adjusted, with local offline use. Features that call an external service require an internet connection.

Lighthouse performance score; mobile measurement on the live version reported for this project.: 100/100
npm dependencies or build steps in the version described.: 0

Installable web application with local storage and assisted adjustment features.

Discuss a similar need

Centralised data with version history

Bring data together, compare versions and reduce manual processing.

Built in a professional setting · private internal application

The need

A large volume of data was processed manually, with no archive making previous versions easy to retrieve.

The problem combined scattered data, the lack of a reliable history and exchanges with no shared format. Speeding up an isolated task would have left those difficulties unresolved: the data also needed to be brought together and its versions made comparable.

The solution

Build an internal application that brings the data together, preserves versions and automates the relevant processing. A common format makes comparison and exchanges between teams easier.

Time saved on the tasks handled by the tool.: Up to 95%
Data and its versions are now archived; previously, they were not.: History preserved

Internal web application, database and automated processing.

Discuss your scattered data

Batch document analysis

From around 4 hours to around 45 minutes of processing per document.

Built in a professional setting · private software

The need

Analysing large numbers of PDF documents relied on manual processing. Each document took several hours of work.

Repeating the same process across many documents multiplied the time spent. The aim was to process documents in batches and produce the analysis, instead of repeating the manual operation for each document.

The solution

Develop software that processes PDFs in batches and produces the analysis automatically. Within the scope covered, processing time fell from around 4 hours to around 45 minutes per document.

Time saved per document: around 4 hours previously, around 45 minutes with the tool.: Around 80%
Saved per year on the volume processed in this case.: Around 1,390 hours

Desktop software, batch processing and PDF analysis.

Discuss your document workflows

What takes up too much of your time?

Let’s discuss your needs. The initial call and up to one hour of scoping are free, with no obligation.

Book an introductory call

Replies by email on business days