Work
Things we have actually built
A short list, honestly described. No invented metrics — just what the job was and what was delivered.
Case study · Hospitality & retail
Elwood Bakery
The brief. A bakery selling in person only, losing orders every time the doors shut.
What was built. A WordPress and WooCommerce store on a custom Astra child theme, with Stripe checkout and a mobile-first ordering flow. Built and tested locally in Docker, deployed to managed hosting, with a documented handover so the team can run it themselves.
Product · Hospitality automation
Rest-O-Pi OS
The problem. Independent kitchens either pay enterprise prices for a POS or run on paper dockets re-typed at close.
What it does. A Raspberry Pi on the shop's own network receives Shopify order webhooks, prints the kitchen ticket automatically and drives a live kitchen display — and keeps working through an internet dropout.
Case study · AI, data & automation
Turning noisy logs into triaged tickets — and a draft fix
The brief. A support team was spending its day on the mechanical half of incident response: reading log output across several tools, working out which spike actually mattered, raising the ticket, writing up what happened, then hunting for where in the codebase to start. Client name withheld at their request.
What was built. A pipeline that watches the logs, correlates them against the host metrics, and hands the candidates to an AI model for root-cause analysis — then files the result everywhere it needs to go: the Jira ticket, a draft pull request on GitHub, Bitbucket or Mercurial, and a summary in the team's channels.
The team still decides what ships. The difference is that the triage, the write-up and a first attempt at the fix are waiting for them, instead of being the job.
How it runs
-
1
Watch
-
2
Correlate
-
3
Diagnose
-
4
Act
- Jira ticket via MCP
- Draft PR
- Slack & Teams
Tell us what's slowing you down.
A free, honest conversation. If the answer is "don't change anything", we'll tell you that too.