Selected work

What we've shipped, and how long it took.

Each of these is a real system in real use. We include the timeline, the divisions involved and what we would do differently, because a case study that admits nothing is not worth reading.

Retail · Billing & inventory · Shipped in 3 days

A jewellery retail billing panel that replaced three registers and a spreadsheet.

Billing, GST invoicing, stock movement and customer ledgers in one screen, built and handed over in three days.

Sector
Retail / jewellery
Delivered in
3 days
Divisions
TEC · CLD · SUP
Status
In daily use

The situation

Sales were written into a register, then re-entered into a spreadsheet at closing. Stock was counted by memory and reconciled weekly, and invoices were handwritten with GST calculated on a calculator.

The problem

Two staff spent the last hour of every day on data entry, invoice errors surfaced at filing time, and nobody could say what was actually in stock without opening the safe.

What we built

A single billing screen: item lookup by weight and rate, automatic GST on the invoice, stock decremented at the point of sale, and a per-customer ledger with outstanding balances. Printable invoice, day-end summary, no training manual needed.

What changed

Closing-time data entry is gone, invoices are consistent, and stock is accurate at the moment of sale instead of at the end of the week.

What we'd do differently

We built the reporting screen before asking which two reports they actually open. They use two; we built six.

Finance · Employee management · Shipped in 2 days with ryha.dev

An employee management system for a finance department that ran on paper.

Employee records, leave and payroll inputs in one system — delivered in two days using our own platform, reviewed by a named engineer.

Sector
Finance / accounting
Delivered in
2 days
Built with
ryha.dev + human review
Status
In daily use

The situation

Employee records, attendance and leave lived in physical files and one shared spreadsheet that only one person edited safely.

The problem

Payroll inputs were assembled by hand every month, leave balances were disputed, and no one could answer a simple question about headcount without opening a cabinet.

What we built

Employee master records, attendance and leave with balances calculated automatically, payroll input export, and role-based access so a manager sees their team and nothing else.

How we built it

Planning, implementation and test generation ran through ryha.dev in parallel; a Ryha engineer reviewed every change and owned the release. Two days from brief to live.

What changed

Monthly payroll preparation went from a multi-day assembly job to an export, and leave balances stopped being an argument.

This system was built using our own product, ryha.dev, with a named engineer reviewing everything before handover.

Want something like this for your business?

Describe what the business does today and what isn't working. We'll come back with scope, cost and a timeline.