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 be replaced with real transactional state, can tenancy and permissions be done properly, 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, beside the state machine 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
Split screen: a facsimile of the shared delivery sheet with four live defects marked, beside the same eight orders as a guarded state machine. Illegal actions stay on screen and name the rule that stopped them. Five scenarios, three of which reproduce a defect from the sheet.

Doubt
Can they replace a spreadsheet with real transactional state?

Model
Eight-state machine, guards shared by the UI and the store

Proof
Seven invariants, recomputed 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 patient database, five people signed in, five different shapes.

Row scope, column masking and expiring grants kept as three separate mechanisms, because conflating them is the usual way this gets built wrong.

Open the set →

01 Branch rolesPrototype Malasakit Clinics · Makati, Cebu, Davao · nine patient records
The live row predicate is printed beside the list. Group operations sees every patient in the country and the clinical notes of none of them. Out-of-scope records are shown struck through purely so you can try to open one; the refusal goes to the audit trail. A referral grant expires overnight on its own.

Doubt
Can they do tenancy and permissions?

Model
Row predicate, column policy and grants as three separate functions

Proof
Row counts, the live predicate, an audit trail of every refusal

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.

Double-entry throughout, integer centavos, nothing ever edited — and the receivables subledger proved against the ledger after every click.

Open the set →

01 CollectionsPrototype Casa Verde Property Management · three tenants · four months of books
A corporate tenant withholds 5% expanded withholding tax, so the invoice reads awaiting-2307 rather than overdue and closes into creditable tax, not cash. Payments allocate oldest-first with the remainder held as tenant credit. A disputed charge gets a credit note, because there is no edit path.

Doubt
Can they handle money?

Model
Append-only journal; every balance derived from postings

Proof
Six checks, including the subledger tying to the ledger

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