Skip to main content
Nameless (Thailand)

The work people still do by hand.We hand it to AI.

So far, AI has paid off mainly for companies large enough to keep specialists on staff. The technology is ready. It has simply not been built to fit anyone else. Our engineers work inside the operation, and we do not stop at a prototype — we keep going until it is used every day.

You decide from something that runs

We do not lock the specification first. We put something you can use in front of you.

We build where the work happens

Not a round of interviews and a document. Our engineers sit with your team.

Your data stays with you

If it cannot go to an outside service, the system runs on your own servers.

01

Problems we see twice become products

Build from scratch for every client and the price never comes within reach of a mid-sized company. Where the same shape turns up at several, we carry it as a product, and the next company starts from there. What only large companies could afford should be within reach of everyone else.

01 · In build

Regulatory tracking

You find out after the fact

What happens today

Thai statutes and ministerial notices change constantly. The source text is legal language, and nobody tells you which parts apply to you. Either someone reads everything, or you hear about it when somebody points it out.

What we are building

A machine reads the gazette daily, checks it against the scope each company defines, and delivers only what applies. Summaries in language the team actually uses, always linked back to the source.

Read more — Regulatory tracking

02 · Planned

Working across two languages

The translation is correct. The meaning does not land.

What happens today

Thai and Japanese teams work together every day, but the dictionary-correct translation is rarely the phrase used in the room. The gap accumulates in email threads and meeting notes.

What we are building

Learning built around real situations at work, not vocabulary lists. Talk it through with an AI in the situation as it actually happens, and see the cultural differences that stall projects written out plainly.

Read more — Working across two languages

03 · Planned

SME paperwork

The information is in the documents, not in a system

What happens today

Quotes, invoices and contracts are spread across email and spreadsheets. What happens next lives in one person's memory, and stops when they are away.

What we are building

Read the document, pull out the fields, and connect them to whatever has to happen next. Designed so you can start without an IT department.

Read more — SME paperwork
The three we are on now
Regulatory trackingWorking across two languagesSME paperworkBangkokTokyoMove quickly and Fix thingsRegulatory trackingWorking across two languagesSME paperworkBangkokTokyoMove quickly and Fix things

02

Solved where the work happens

Nobody knows what needs building better than the person doing the job every day. We put engineers next to them and decide together, from something that already runs.

  1. 01Modeling

    Draw the real work before writing code: who does what, where the data goes, and where it currently breaks.

  2. 02Requirement Analysis

    Separate what is needed from what is wanted, and write it so both sides read the same thing.

  3. 03Design

    Screens, data structures and interfaces. The decisions that are expensive to change later get settled here.

  4. 04Implementation

    Build it, in short cycles, so you see something working long before the whole thing is finished.

  5. 05Program and System Testing

    Tested at the unit and the system level, including against real data before it goes live.

  6. 06Deployment

    Released with monitoring and a way back. Nothing ships that cannot be rolled back.

  7. 07Configuration & Change Management

    Every change has a source and a history. A system in production has to be changeable without holding your breath.

See how we work

03 · Where we help

Are you stuck on one of these?

We do not sell a fixed product. We build around whatever has stalled. And the decisions stay with your people.

01

The prototype exists. Nobody uses it.

A demo that runs and a tool people open every morning are two different things. Who can see what, what happens when a case does not fit, how it reaches the systems you already run, and who fixes it at eight in the morning. Closing that gap is the work we take on.

02

What head office asks for does not match how the local team works

For Japanese companies, we know the quality bar and the level of reporting head office expects. We settle the specification in Japanese and deliver the screens and manuals your team uses in Thai.

03

The data cannot sit on an overseas service

It can run on your own servers, or inside Thailand. Building and running AI inside a company is the Tokyo team's day job.

See Nameless Tokyo

04

Where we are

We operate from Tokyo. Bangkok is being set up. Where we go after that is still open.

  • TokyoJapanOperating · 2023
  • BangkokThailandSetting up
  • Silicon ValleyUnited StatesExploring
  • SingaporeSingaporeExploring
  • TallinnEstoniaExploring

05 · Careers

We are looking for people who build, not people who write proposals

This is not implementing a specification somebody handed you. You watch a client's work and decide what to build. We pay for training and certification.

See open roles

Was this page useful?

Tell us where it is stuck

You do not need a finished specification. We reply within two business days.

Talk to us