Skip to content
한국어

Products

Built while applying the procedure to our own work.

Not products planned in order to be sold — things that had to be built while applying the same procedure to our own operation first. They also serve as a starting point after an assessment.

First Application

The first thing it was applied to

The order set out above — define the process, fix inputs and outputs, accumulate data, then AI — was first applied not to a client but to our own operation.

Starting a business brought all of it at once: expenses, invoices, receivables, turning what was said in a meeting into requirements, keeping track of what still had to be done. Memory did not scale. So the same procedure was applied to us first.

Our own workExpenses · invoices · receivablesRequirements from meetingsTo-do · state of playHeld together by memoryThe same four stepsdefine → in/out → data → AIidentical to what we proposeWhat had to be built along the wayVoice records — so nothing said is lostExpenses · approval — for what returns monthlyIntake · tracking — to give requests a numberThis is where the procedure is shown to workThe same procedure is applied to client work. The products are evidence of what it produces.

These were not built in order to be sold. They are what came out of the same procedure.

So the products do two things. One is to serve as evidence that the procedure actually produces working systems. The other is to be a finished starting point for the first thing adopted after an assessment. A company whose requests are scattered across chat and email does not need intake and tracking built from scratch.

The scope shows here too. Not only web screens — mobile applications and store release sit inside the same procedure. Where an app is what is needed, an app is what gets built.

Product or internal system, none of it began from a requirements document handed over. Each started by finding the problem and deriving the requirements first-hand.

EZClass

Members, attendance and billing in one place.

An operations system for multi-site academies and studios. Billing conditions that differ per member are held as rules, so nothing is recalculated by hand each month.

  • Billing becomes lookup
  • No payment method, no auto-run
  • Per site and consolidated

Get in touch about EZClass

EZHaru

Record. Everything else is done for you.

An AI voice recorder that files itself. Tap a category and record — the transcript, the summary and a tidy note file appear in your own cloud, already in the right folder.

  • Files itself
  • Transcribes and summarizes automatically
  • Learns your vocabulary

Explore EZHaru

EZWorks Expense

Receipts in. Bookkeeping done.

A receipt and expense workflow for companies that still move numbers by hand: capture, read, route for approval, and hand off to accounting.

  • Capture where the receipt happens
  • Reads the document for you
  • Approval that follows your rules

Get in touch about Expense

Not sure which one fits

Name the process that takes the most hands and we will say first whether a product fits or whether something has to be built.