Portfolio, volume 01 Devon 2026

Digital products
and useful systems

Work made for
the real world.

Selected product, operations and design work.

Begin with PaperWatcher
CAT. 01

Public service · paperwatcher.co.uk

PaperWatcher

Know before the till does. A single source of truth for UK newspaper prices, barcodes and the changes coming next.

Role
Product, design, engineering
Platform
Web, email, JSON API
Status
Live and public
Year
2026
FIG. 01 Two changes due, dated and counting down
The PaperWatcher home page: two price changes due in the next fortnight, each dated and counting down, above the national title list with the changing titles flagged.
Captured from the running product. Free, no account, nothing sold.
01 / Purpose

A price change
is never one change.

“The newspaper price is changing on Monday” sounds simple. It has to reach the EPOS, the shelf labels, the ordering system and the staff before a customer is charged the wrong amount.

02 / Context

Newsagents and independent retailers historically tracked this by hand: trade emails, spreadsheets, and someone remembering. Miss an update and you get till discrepancies, corrections, and a customer who trusts you slightly less.

The data existed. What was missing was somewhere to look it up quickly, see what is coming, and act before Monday.

03 / System

An event log, not a spreadsheet

01Trade file inArchived before parsing
APPEND ONLY
02Title pagesPrice and barcode
03UpcomingWhat changes when
04Email digestsThree cadences
05Exports and APICSV, XLSX, JSON
05 / Contribution

From a data problem to a public service.

Product directionTurned a recurring trade annoyance into a service with a clear, narrow promise.

Data designModelled prices as dated events so history, barcode changes and audit trails all fall out of one store.

EngineeringBuilt the ingest pipeline, alerting, exports, JSON API and a toolbox of 87 retailer utilities.

OperationsRuns as one process on one small server, with streaming off-site backup and loud failure modes.

CAT. 02

Product system · Paperwatcher

Workspace (Working Title)

One operational home for campaign orders, product costing, provenance and compliance.

Role
Product, design, engineering
Platform
iPad, web, print
Status
Private pilot / building
Year
2026
FIG. 02 Campaign order taking, shared iPad
The Workspace order pad on a landscape iPad: campaign products as tap targets with quantity steppers, and an order rail holding the customer, collection date and confirmed lines.
Captured from the working product, not a mockup. Designed for quick, calm use at the counter.
01 / Purpose

Capture it once.
Use it everywhere.

Workspace replaces handwritten campaign books and repeated admin with one dependable source of truth for the shop floor and back office.

02 / Context

Independent food retailers hold a surprising amount of operational knowledge in paper notebooks, spreadsheets and memory. Christmas pre-orders make the problem visible: the same information is written, counted and checked several times.

The product had to feel quicker than paper, work on a shared iPad in a busy shop, and still produce useful prep, collection and compliance outputs.

03 / System

One record, many working views

01Order takenAt the counter
ONE RECORD
02Prep listsFor departments
03Collection viewFor handover
04Campaign totalsFor planning
05TraceabilityFor assurance
05 / Try it

Open the order pad and take an order.

A reduced copy of Workspace runs in your browser. Take an order at the counter pad, find it in Orders, print a preparation list, hand it over in Collections, and cost a recipe from scratch. The screens are the product’s own.

The shop, its catalogue and its customers are invented. What is missing, and why, is on the demo’s own About page: the counter till, catalogue import and provenance all need a server, and this has none. Nothing you type leaves your browser.

Open the demonstration copy
06 / Contribution

From shop-floor problem to working product.

Product directionDefined the information model and workflows around real campaign operations.

Experience designDesigned role-specific screens for iPad, desktop, phone and print.

EngineeringBuilt the web product, permissions, reporting and operational safeguards.

DeliveryPrepared the product for a private in-shop pilot and long-term low-maintenance use.

CAT. 03

Local-first product · propertill.app

Proper Till

A proper till, in the browser you already have. No account, no subscription, and no sales record leaving the counter it was taken on.

Role
Product, design, engineering
Platform
Browser, offline-capable
Status
Built, in pre-release review
Year
2026
FIG. 03 Ringing a sale, counter tablet
The Proper Till sell screen on a landscape tablet: product tiles grouped by department (drinks, counter, grocery, bakery) beside a running basket of three lines totalling £10.35, the VAT it includes shown beneath, and one Take payment action.
Captured from Proper Till using invented demo data. Being built: the screens may change before release.
01 / Purpose

A till you own,
not one you rent.

Small-business EPOS is usually rented: a monthly fee, a terminal you cannot replace, and a sales history held somewhere you have to ask for. Proper Till inverts all three. It runs in the browser already on the counter, and the shop's own record never leaves it.

02 / Context

For a market stall, a village shop or a Saturday pop-up, the realistic alternative to a subscription till is a cash tin and a notebook. The subscription is not just the cost: it is the card reader you must buy, the account you must keep, and the export you cannot get once you stop paying.

So the promise is deliberately narrow: this is a till, not an accounting system. Every boundary it will not cross is written into the product itself rather than left for a customer to discover.

03 / System

No server to trust

01Your catalogueImported, never uploaded
THIS BROWSER
02SellCash, card, transfer
03ReceiptsNumbered, then immutable
04Session closeCash up and variance
05Backup fileEverything, downloadable
05 / Contribution

A second product from a proven engine.

Product directionHeld the promise narrow: a till, not an accounting record. Every boundary it will not cross is written into the product's own wording.

ArchitectureMade the browser the whole system: no backend, no account, and money in integer pence from the tile to the receipt.

ReuseLifted the money, VAT and sale-lifecycle rules out of Workspace against a written reuse matrix, carrying their test cases rather than their code.

DeliveryBuilt, deployed and access-gated, deliberately held back from public release until the hardware checks and open VAT questions are settled.

CAT. 04

Private system

Primrose

A phone-first home for two. Automates the boring bits, remembers the important bits, and makes the free bits more fun.

Role
Product, design, engineering
Platform
Phone, installable
Status
In private use
Year
2026
FIG. 04 Deciding, planning, remembering
The Primrose home screen, asking “Right then. What are we doing?” above large choices: decide for us, what should we eat, get us out of the house, stay-in night.
The decide screen after choosing energy and indoor or outdoor: four suggestions drawn from the household’s own list, each with a single “We’ll do this” action.
The food plan: a week of meals on one shelf, each meal carrying its ingredients, with a control to push them onto the shared shopping list.
Captured from the running product, with invented household data. Built for the phone in your hand on a Tuesday evening.
01 / Purpose

Not another
chore list.

Most household apps open on everything you have failed to do. This one opens on a question worth answering: right then, what are we doing? The admin still exists, but it waits its turn.

02 / Context

Two people, one household, and the same small negotiations every week: what to eat, whether to go out, whose turn it is to ring the dentist. None of it is hard. All of it is friction, and most of it is decided while tired, on a phone, in the ten minutes before something else starts.

So the product is phone-first rather than phone-compatible, and it leads with a decision rather than a backlog.

03 / System

One shared record, four ways in

01What you likeThe household list
ONE HOUSEHOLD
02DecidePicked for right now
03Meal weekInto the shared list
04Life adminTasks and bills
05MemoriesWhat you actually did
05 / Contribution

A private product, built to the same standard.

Product directionChose a home screen that asks a question rather than listing obligations.

Experience designDesigned for one thumb, at night, with the decision always one tap away.

EngineeringBuilt the household model, the suggestion loop, the meal-to-list handoff and the reminder system.

DeliveryRuns behind Cloudflare Access with a proven install, guarded update and restore drill.

Selected work

The index will grow.

  1. 01PaperWatcherNewspaper pricing serviceLive
  2. 02WorkspaceOperational product system2026
  3. 03Proper TillLocal-first browser tillIn build
  4. 04PrimrosePrivate household systemIn use

Correspondence · Open to work

Work with me.

I design and build digital products end to end, and I am taking on new work.

The four case studies above are the evidence. PaperWatcher is a live public service, Workspace runs a shop counter, Proper Till puts a till in any browser, and Primrose runs a household. Each went from problem to working software with one person doing the product thinking, the design and the engineering.

I work best on small, real problems: operational tools, internal systems, products that have to survive daily use by people who did not choose them. Working software arrives early, and progress is reported plainly, including the problems.

What I buildWeb products, operational tools and quiet services, designed and engineered as one piece.

How I workRemotely from Devon, in short iterations, with something running by the end of the first one.

AvailabilityOpen to freelance projects and product roles now.

Or use the post box