Skip to content

About the studio

Every one of these is a real system, running for real people today — not a portfolio of mockups.

After this page you’ll know: whether we build things people actually use, not just look at.

Proof — 03 exhibits

What’s live

Real systems, in daily use by real people right now.

Live · built for a clientExhibit 01

Meridian1st

Internal operations dashboard — in daily use

A picture, in markup, of the Meridian1st dashboard as it appears in the product’s own public demo: a sidebar, five summary tiles, a list of recent sales and panels for delist failures and stock warnings. The figures shown are the demo’s sample data rather than a customer’s. Alongside them is an illustration of what the system does when something sells: one example item is listed on Etsy, eBay, Shopify and WooCommerce, sells on one of them, and is then delisted from the other three automatically. That illustration repeats on a timer. Nothing here is interactive.

Meridian1st’s own demo screen, reproduced in markup — sample data throughout, and the sync panel is an illustration of the delisting rule rather than part of the product

Meridian1st was born out of a client’s frustration. Managing multiple online shops meant that every time an item sold on one platform, it had to be manually removed from all the others — a slow, error-prone process that ate into the working day.

The answer was a single dashboard that speaks to every shop: Etsy, eBay, Shopify, WooCommerce and more. Now, when an item sells on one platform it is automatically delisted from the rest, removing the risk of the same item selling twice.

One
Dashboard for every shop
Automatic
Cross-platform delisting
Real-time
Stock sync across shops
No more
Overselling the same item

What the client asked for, in one line:

One dashboard I can use to speak to all of my online shops — Meridian1st

Pre-publish: swap the descriptive figures for real numbers once you have them — sign-ins, listings managed, time saved.

Live · one of oursExhibit 02

The sales agent

Prospecting tool — built for our own use, not sold to clients

A looping demonstration of our prospecting agent taking one made-up company through four stages: prospect, signal check, draft, logged. The companies and findings below are invented.

Sales agent — prospecting runRunning

Stage 01 — Prospect

Northgate Joinery Ltd

Joinery & shopfitting — Sunderland

Matched from the public company register.

Finding the right companies to talk to used to mean an afternoon of searching, reading and copying things into a spreadsheet, for a handful of names that might not have been worth a message anyway. It was the slowest part of running the studio and the easiest part to put off.

So we built something to do the reading. It runs on a schedule, checks each company for real signs of the sort of problem we fix, then checks the company information, against Companies House, drafts a first message, and logs everything so nothing needs typing out by hand — every email still gets a human check before it is sent.

4
Stages, start to finish
Scheduled
Runs automatically
Human-checked
Before anything sends
Ours
Built for our own prospecting

It does the reading. We still write the part that matters, and nothing leaves here without one of us seeing it first.

The sales agent — internal
Live · one of oursExhibit 03

Omarchy on a Raspberry Pi 5

Unofficial desktop port — verified on real hardware

Hyprland running on Pi 5 hardware

Omarchy — DHH’s Arch/Hyprland desktop — only officially runs on x86-64. There’s no Pi image, no ISO, nothing to download for ARM. An unofficial port existed on paper, but nobody had proven it actually boots on a real Raspberry Pi 5 rather than just a VM.

So we built the image ourselves and put it on real hardware. Six separate faults stood in the way — a wrong partition table, a twelve-hour filesystem hang, a renamed WiFi interface among them — each traced back to its actual cause in kernel and systemd source rather than guessed at. The desktop now boots clean: GPU, WiFi, Bluetooth and display all working.

First
Confirmed boot of this port on real Pi 5 hardware
6
Root-cause faults found and fixed
5
Upstream bugs identified for the project maintainers
428
Boot files verified byte-for-byte against the image

Every hard moment in this project came from guessing instead of reading the source. Once we stopped doing that, every problem turned out to be understandable.

Build notes — Omarchy Pi Version
Read the full write-up

Pre-publish: swap in a photo of the running desktop (via ShotPlaceholder or similar) once available.

The short version

3
Live systems in daily use
0
Of your details we keep