TecHub

Proof carries a name and a date, or it isn't proof.

This sheet holds call recordings, case studies and the status board. Nothing goes up without a product, a date and consent on file. Where consent hasn't arrived, the slot stays empty and says when it fills.

Publishing rules

Call recordings
Caller and client consent
Client names
Written consent from the client
Numbers
Measurement period and source
Footage
Vessel or site, date, camera
Demo scripts
Labelled synthetic on screen

Recordings go up only with consent, each with its date and transcript.

Every recording carries its product, language, date, duration, transcript and trace. We publish the full unedited call and mark the 20-second cut separately.

Recordings ledgerAs of
ProductThe product and agent that took the callLanguageLanguage spoken on the callDateThe full date of the callDurationFull unedited call; the 20 s cut listed apartTranscriptFull text by speaker, as spokenTracePer-turn latency in ms and tool callsConsentCaller and client, both required

No recordings are published yet.

Each call gets one row here once both the caller's and the client's consent are on file.

The recording already public on our earlier demo page comes here too, after the same consent check, with its date and transcript.

The call demo on the home sheet plays a synthetic script. This ledger holds real calls only. Open the synthetic demo

Each case study runs situation, deployment, numbers, quote.

We write one only after the client agrees in writing to be named, numbers included. One case is one page, written separately in Korean and English.

How one case study is built

One case · one page

  1. Situation

    The operation before: stores, rooms or vehicles, daily call volume, and what was being missed.

    Only figures the client supplied

  2. Deployment

    Which product, where, and since when. How it is installed and what it connects to (POS, PMS, CRM).

    The start date, written as a date

  3. Numbers

    Measured values such as calls handled, orders taken and requests routed. Each carries its period and source.

    No date and source, no number

  4. Quote

    One or two sentences from the person who runs the operation, with their name and title.

    Only with written consent

No case studies are published yet.

The first one goes up in this outline as soon as a client's written consent is on file. Until then, the status board records where each product runs, without client names.

What is live today is on the status board, with dates.

Each of the 12 products carries its stage as one word and a date, with a dated changelog per product. Updated weekly, and published as RSS.

Products by stageAs of

Live
Orda · Overture AI
Production-ready
gohotel.io
Available
Dallang · Retailytics · ReVision SDK
Early access
Sori AI · Caffelytics
Market-ready
Helm
Proof of concept
Property OS
In procurement
AegisView AI
Architecture delivered
SeeAnything Pro

We work out which product fits your operation in a working session.