Studio

Working inventory for investor and partner discussions. Software for businesses that still run on spreadsheets: what has shipped, what exists as a prototype, and what state each of them is honestly in.

Start with the commercial briefing — it explains how the studio is structured and how the work is sold. Everything below it is the evidence: two sites in production, then the prototypes, which come in two shapes on purpose.

The Operations sets are one deep prototype each, answering a doubt rather than offering a choice — can a spreadsheet actually be replaced, can branches be kept genuinely apart, can money be handled. Each exposes its own rules and lets you try to break them. The Commercial sets take one design question and answer it several incompatible ways, so the choice between them is a real decision rather than a preference.

Commercial briefing

/brief start here

● Operating model & go-to-marketv1.3 The two practices, infrastructure, target market, unit economics
How the studio is structured and how the work is sold. Pricing, the validation sprint and its waivers, the two infrastructure models, target verticals with a qualification gate, payback quoted net of retainer, and a plain statement of what the track record does not yet prove.

In production

shipped 2 sites

Logistics

/logistics 1 set · 1 prototype

Dispatch

logistics/dispatch

The briefing’s core claim is replacing manual spreadsheets. This is that claim, made checkable: the sheet a last-mile operator runs on today, side by side with the system that replaces it.

One prototype built deep, not four directions — the question is whether the hard part works, and the only honest way to show that is to let you try to break it.

Open the set →

01 Orders consolePrototype Hatid Logistics · Metro Manila last-mile · 40–60 drops a day
A working console — orders board, driver load, activity log — where the refusals are the argument: every blocked action names the rule that blocked it. The spreadsheet it replaces, with four live defects marked, sits in the demo drawer alongside five guided scenarios and a live list of what the system guarantees.

Doubt
Can they replace a spreadsheet with real transactional state?

Model
Eight named stages, with the rules enforced in one place

Proof
Seven promises, re-checked after every action

Healthcare

/healthcare 1 set · 1 prototype

Multi-branch

healthcare/multi-branch

The briefing promises multi-branch operation with role isolation. Nothing else on this site shows it. This does — one set of patient records, five people signed in, five different answers.

Who you can see, what you may read, and the one way across a branch line, kept as three separate locks — because running them together is the usual way this gets built badly.

Open the set →

01 Branch rolesPrototype Malasakit Clinics · Makati, Cebu, Davao · nine patient records
A clinic record system with a patient list, a chart panel and an access log. Group operations can see every patient in the country and read the clinical notes of none of them. Records beyond your reach are greyed rather than hidden, purely so you can try one — the refusal goes on the log with your name on it. A referral opens exactly one patient and expires overnight on its own.

Doubt
Can they keep branches genuinely apart?

Model
Three separate locks: who you see, what you may read, the one way across

Proof
Live record counts, and a log of everyone turned away

Property

/property 1 set · 1 prototype

Billing

property/billing

Anyone can render an invoice. This one is about the awkward money: the payment that is deliberately 5% short, the round number that matches no invoice, the charge disputed after it was issued.

Every change written down twice and nothing ever edited — with the unpaid bills proved against the books after every single click.

Open the set →

01 CollectionsPrototype Casa Verde Property Management · three tenants · four months of books
A receivables system — tenants, statements, aged debt, ledger. A company tenant holds back 5% of the rent and pays it to the BIR itself, so the money that lands is short on purpose and the bill reads awaiting-certificate rather than overdue. Payments go against the oldest bill first, anything left over is held as the tenant’s credit, and a disputed charge gets a credit note because there is no way to edit a bill that already went out.

Doubt
Can they handle money?

Model
Nothing ever edited; every figure worked out from what happened

Proof
Six checks, including that the bills and the books always agree

Wedding

/wedding 1 set · 4 prototypes

RSVP

wedding/rsvp

What shape should a wedding website be? Four answers that disagree structurally, not cosmetically — the primary surface, the information architecture and the record a backend would have to store are different in each.

Philippine settings throughout: church then a separate reception, principal sponsors, Filipiniana dress codes, GCash instead of a gift table.

Open the set →

School

/school 2 sets · 5 prototypes

Public site

school/public-site

One K–12 school website, four editorial strategies. The section inventory and the fixture content are identical in all four — same principal, same science-fair medals, same exam week.

What differs is what a parent hits second, after the hero. That is the only real decision a school website makes, and each version answers it differently.

Open the set →

CMS

school/cms

The other half of a school website, and the half that decides whether it stays current: who updates it, and how much they have to understand to do it safely.

Filed as its own set rather than a fifth public-site direction — different audience, different artifact.

Open the set →

01 SiteDesk AdminEvergreen Academy · seven panels
Sidebar shell with an activity-led overview, then a panel per content type. News carries draft and published states; uploaded files show which page links them, so deleting one is not a guess.

Surface
Sidebar shell, panel switching

Audience
School staff, not developers

Access
Admin, plus editors scoped per section