# Gemba

> A discovery agent for AI consulting and deployment agencies. You say what you
> want to know. Gemba calls the client's people, watches their screen while they
> work, and asks until it understands. You get one markdown report over everyone,
> plus one per person.

Understand how it really works, at scale. Deploy more clients faster, with the
same team.

Site: https://withgemba.com/ · Contact: info@withgemba.com · Book a call: https://withgemba.com/call

## The film

A 63-second silent film plays at the top of https://withgemba.com/ and shows the
whole product. Eight sections:

1. brief -> calls -> report -> deploy.
2. The brief. The agency types what it wants to know: the process from offer to
   invoice, and the goal.
3. Upload. The client's employees land in a table, then 100 invitations go out
   from the agency's own address, white label.
4. The employee opens the invitation and clicks one button to start the session.
5. The call. Mid-conversation, the agent sees a number after a customer name on
   the screen, asks what it is, learns it is a supplier number typed into the
   name field, then asks which other customers are handled the same way and how
   the clerk remembers them. Beside the transcript: what the agent saw on screen.
6. The board. Reports land row by row as the calls finish, up to 100 of 100.
7. The report. One long markdown file, scrolling.
8. Close: Gemba. Understand how it really works, at scale.

## The problem

Before you can automate anything, someone has to find out how the work is really
done. That means sitting next to people for days. Watching the screen. Asking
why. It caps how many clients you can take.

## What Gemba does

| step | what happens |
| --- | --- |
| brief | You write what you need to know. |
| calls | Gemba calls each employee and watches their screen. |
| report | One markdown file, agent ready. |
| deploy | Your team builds. |

## What comes out

Markdown. Not a PDF, not a slide deck. Your agent reads it directly — Claude
Code, Codex, whatever you use.

Every finding says where it came from:

- `employee_head` — the person told us. Written down nowhere else.
- `system` — we saw it on the screen.

That line is the difference between an automation that works and one that
quietly produces garbage.

Example finding:

```markdown
## Identifiers hidden inside name fields (31 people)

- What happens: the supplier number is typed into the customer name field.
- Why: the customer matches on it. Without it the invoice is not paid.
- Source: employee_head · not documented anywhere
- If automated: a clean write drops the suffix and payment stops.
```

## What your client's IT will ask

- Runs as the employee. No admin rights.
- One small program the employee starts, and closes when the call ends.

## White label

The invitations come from your address. Your name, your branding. The client's
staff never see Gemba.

## The name

現場 — gemba. Japanese for the real place where the work happens. You do not
learn how a job works from a process diagram. You learn it by standing next to
the person doing it.

## Who is behind this

Peter Haupt.

- 25 years deploying new technology inside businesses.
- Microsoft Partner of the Year, globally.
- Psychologist, data scientist and book author.

## Book a call

30 minutes. Tell us how you run discovery today, we show you the agent.
https://withgemba.com/call

## Legal

- Imprint: https://withgemba.com/imprint
- Privacy: https://withgemba.com/privacy
- Operator: Curavani GmbH, Jülicher Str. 72a, 52070 Aachen, Germany