
Halyard
Every booking started with a call, because the web form was long enough that the sales team apologised for it.
Most customers now quote and book on their own. The sales team spends its calls on the shipments that need a human.
View project →I'm Joel Mercer, a product engineer in Manchester. I replace hand-cranked bookings, payroll, quoting and ordering with software people trust.
ten years of shipping
previously Halyard + Pilcrow
now independent, one project at a time

Every booking started with a call, because the web form was long enough that the sales team apologised for it.
Most customers now quote and book on their own. The sales team spends its calls on the shipments that need a human.
View project →
Payroll month, without the spreadsheets: a checklist with a database behind it, for an eleven-person accountancy practice.
The run that used to fill a day now fits in a morning, and a new starter can be trusted with it in their first week.
View project →
A live trade price list and ordering, replacing a PDF that was out of date the week it was sent.
Regular trade customers now order without calling, and the counter queue is for people who want timber advice, not prices.
01
Postgres, server-rendered pages, a thin layer of JavaScript. The exciting part should be your product, not your stack. When something newer genuinely earns its place, I'll make that case in writing.
02
You see working software from the second week, in your hands, not in a slide deck. Course corrections cost days instead of months.
03
Before the payroll tool for Sable & Rowe, I sat through two full payroll runs. The software mirrors the checklist they already trusted.
04
Empty states, error messages, what happens on a slow connection. That's the part users actually touch.
“Joel sat with our payroll team for two days before he wrote a line of code. The tool works the way we actually work.”
currently booking : autumn 2026
I take a single engagement so it gets my full attention. If autumn works for you, get in early.
hello@joelmercer.dev