Case study · Concept · Small-business tooling

A laundry ticket and status tracker

Selyo Laundry, a neighborhood shop, was running on paper stubs and a phone that rang all day with the same question. What it needed was a small piece of software: a ticket staff can create in seconds, and a status page customers can check themselves.

Practice project: Selyo Laundry is a fictional client. Both tools below are working software, not screenshots, and the staff and customer sides share the same data. Create a ticket on the left and look it up on the right.

ClientSelyo Laundry (fictional), a neighborhood laundry shop

The askPaper tickets get lost; "is it ready?" is a phone call, every time

BuildKiko Sagadraca, computer engineer

InvestmentFrom ₱6,000, the Workflows starting price. Bigger tools are quoted on scope.

The brief

A ticket system doesn't need to be complicated to be worth building. It needs two things: the staff side has to be fast enough to use during a busy drop-off, and the customer side has to work with just a ticket number. No app, no account, no password.

Try both sides

Create a ticket at the front desk on the left. Then look it up on the customer page on the right. No reload needed. The customer page also starts pre-loaded with three sample tickets (SL-0001 through SL-0003) so there's something to find right away.

Front desk

staff-facingOpen full size ↗

Check status

customer-facingOpen full size ↗

Built like software, tested like software

Before this got called done, a written checklist ran through the ordinary ways small-business tools break: typos, double submissions, and two people using it at once. A few of the ten:

✅Stray HTML typed into a name fieldShows up as plain text everywhere. Checked in the page source, not just on screen.

✅Two tickets created back-to-backIDs come from the highest existing number rather than a counter, so they can't collide even after a reset.

✅Ticket number mistyped at lookupA specific "we couldn't find it" message, not a blank page or a crash.

⚠Two staff phones open at onceA real limit of this demo's browser-only storage. The Google Sheet version doesn't have this problem.

"It works when I try it" isn't the same as "it works." The second needs a checklist like this, including the things that still fall short.

The real backend

The two tools above share a small browser-only data store standing in for what a live version would use: a Google Sheet, read and written through a documented Apps Script web app, the same setup used for the reminder emails in the Serve Day case. Nothing about the two pages above would need to change; only where they save data would.

Quoted per project · no flat package yet

I quote small custom tools after understanding the actual workflow. A two-person shop and a ten-person shop will rarely need the same build.

Is a repeated task still running on paper or a group chat?

Start a project

Or see everything I build