Selected work

Selected projects and independent builds.

These are products we own and operate. Client engagements are confidential, so they are published only when the client approves the details.

Read the case studies Start a conversation

In development · Restaurant operations platform

Mesob

A single system for restaurant operations.

Context

Restaurant teams often work across paper tickets, spreadsheets, messaging threads, and separate menu tools. Orders, tables, payments, and menu changes sit in different places, which slows handoffs and makes errors harder to trace.

What we built

Mesob is built around the restaurant's daily flow. Menu items connect to orders, orders to tables, payments to revenue, and staff accounts to permissions. The platform includes a guest menu, staff dashboard, kitchen view, payment status, and reporting.

Current state

Mesob is in active development. The operations dashboard, menu management, order flow, roles, and reporting are built. We will present it as a live product once it is ready for daily restaurant use.

Product page

Live and open source · Developer tools

TypeDock

52 browser-based developer utilities.

Context

Developers often need a small tool to format a query, convert JSON to types, test a regular expression, or generate a UUID. Many existing tools require an account or send input to a server.

What we built

TypeDock puts 52 tools behind one keyboard-friendly interface. Most processing happens in the browser, so input stays on the device. There is no account, and the source code is public.

Current state

TypeDock is live and open source. It covers JSON, encoding, conversion, security, design, and general development tasks.

Product page Visit TypeDock

Independent builds

Other systems we have built.

These are independent builds and open-source projects, not client case studies. They show the range of systems we work on.

Scroll or drag to browse. Click a card to enlarge it.

What we publish.

Product work is labelled by status. Client work appears only after the client has approved the details.

Start with the workflow

We look at how work moves between people before deciding what the interface should do.

Publish what we can verify

Products in development are labelled as such. Client work is published when the client approves the details.

Build for operation

A working screen is only part of the job. Permissions, failure states, documentation, and maintenance matter too.

Client confidentiality

Most client work involves internal systems and operational data. If you need to understand our experience with a similar problem, contact us and we can discuss what is relevant without disclosing client details.

Start a conversation

Your project could be the next one here.

If the work is a fit, we will scope it carefully, build it in the open, and describe the result without exaggeration.

Discuss a project See our work