Work
Selected work.
Five projects plus the modules underneath them, with the engineering decisions written down rather than summarised. One of them you can open in a browser right now, and we can walk you through any of the others on a call.
- 5
- Systems built
- 3
- In production today
- 4
- Industries
- Every one
- written up in full
Everything else
Four more, each with the hard part written down.
Case studies, in detail
Restaurants · 2026
InvtoryX
Back-of-house for restaurant groups that have more than one house.
Ingredients tracked across every site, recipe-level food costing, suppliers and purchase orders, with stock deducted as orders land. Built for multi-location groups, where the hard part is that a person's authority changes depending on which restaurant they are standing in.
- Product Engineering
- Security & Access
- Data & Sync
Household · 2025
Larder
A kitchen that knows what is actually in it.
A stock ledger for a household: what is in the pantry, what this week's cooking needs, the difference between the two, and when to buy it. Eleven build phases, complete, and the environment where several of our offline-sync and AI-extraction patterns were proven before they went anywhere near client work.
- Product Engineering
- AI & Automation
- Data & Sync
Restaurants & retail · 2025
Eshop
A storefront that agrees with the till.
A POS-connected online store: delta sync against OneHubPOS, two payment gateways, magic-link SSO, multi-tenant access control, and a dual-table design so a merchant's own customisations survive the next sync from the point of sale.
- Systems Integration
- Payments & Commerce
- Devices & Edge
Delivery platform · 2025 — ongoing
Sill
The layer every engagement starts on.
Accounts, permissions, billing, notifications, admin, audit logging, multi-tenancy and background jobs, written once and hardened in production across every build. It is the reason a four-week delivery window is a commitment rather than an ambition.
- Platform Engineering
- Security & Access
- Payments & Commerce
Modules
Twelve components that already run.
Smaller than a product, bigger than a feature. Each one is live inside the systems above, which is why your project inherits it rather than commissioning it.
12 modules · all in production
Organisations & membership
Organisations with members, invitations, roles and permissions. The multi-tenant spine every B2B product needs before it can have a single customer.
Authentication & 2FA
Sessions, two-factor, phone sign-in and SSO, with the account recovery paths designed rather than left to a password reset email.
Billing & subscriptions
Plans, proration, trials, upgrades, dunning and failed-payment recovery. Charging real customers on live software every month.
Notifications & delivery
Email, SMS and in-app messaging with templates, preferences and delivery tracking, so a message that failed to send is visible rather than silent.
Staff backoffice
An internal admin area for the people running the business: accounts, impersonation with an audit trail, support tooling and operational overrides.
Content management
A CMS for the marketing surface and in-product copy, so changing a page does not require a deploy or an engineer. We work in WordPress where that is what a client already runs.
Running in
Audit trail
Append-only records of who did what and when, retained and queryable. Built in from the first commit because retrofitting history is impossible.
Delta sync engine
Changed-record sync with tombstoned deletes, idempotent writes and a written conflict policy. The component most integrations get wrong.
Location guard
Per-site role resolution for multi-location businesses: the effective role a user holds at the location being accessed, Redis-cached and integration-tested.
Running in
Document extraction
Receipts, invoices and delivery notes turned into structured records, with confidence scores and a human review step for anything uncertain.
Running in
Reconciliation jobs
Scheduled comparison across two systems that names the records which disagree rather than counting them. A day to build, and it saves an audit.
Device & peripheral layer
Receipt and label printers, barcode scanners, cash drawers and certified card readers, with offline queueing so a counter keeps trading through an outage.
Running in
Why we show it this way
Software you can open beats a logo you can’t check.
01
You can see all of it
Every architectural decision, every trade-off and every thing we would do differently is written up, and we will go deeper on any of it on a call.
02
Delivered, not prototyped
Three of these run in production today. Getting software live is one skill; keeping it working for a year afterwards teaches a different one.
03
The status labels are honest
Live means live, in development means in development. If a page said shipped and it was not, you would find out in ten minutes and rightly stop reading.
Tell us what you’re trying to build.
We’ll come back within one business day with a scope, a number and a date.
Phone
+1 (407) 796-2376Reply time
One business day, from an engineer
Based in
Orlando, Florida · serving the United States
What happens next
- A reply within one business day, from an engineer
- A thirty-minute call, with no qualifying call before it
- A written scope and a fixed number, if it fits