A WILDERNESS INTERACTIVE PRODUCT
Atrium.
Your booking business as a Toyota plant. Operating at Taiichi Ohno depth.
Full conversion infrastructure for any business that takes bookings. Every call, every click, every appointment, every pound of revenue, all writing to one shared data surface. The closed loop that makes ad spend genuinely smart.
How a TPS andon signboard would render a booking line. Atrium runs this discipline under the hood — your team and customers see a clean, modern interface.
LINE 01
BOOKING FLOW
SHIFT 2026-04-24 · DAY
--:--
TAKT15mPACE 14m
01
INBOUND
TAKT20mPACE 18m
02
BOOKED
TAKT30mPACE 28m
03
SEEN
TAKT45mPACE 60m
04
PLAN
TAKT60mPACE 56m
05
PAID
CONVERSION · LIVE BOOKING RATE BY SOURCE
47CALLS
22CALLBACKS
14BOOKINGS
9MISSED RTN
ANDON
LEAD 412 · CALLBACK OVERDUE 2h
BOOKING 88 · NO GTM EVENT
PLAN COL · PACE 60m vs TAKT 45m
Green is on takt. Yellow approaches the SLA. Red has crossed it. Empty cells are open capacity. Andon below lists live exceptions. Heijunka, jidoka, takt — Ohno’s discipline, made visible. Atrium runs the same logic in code, behind tooling your team will actually want to use.
Not just a booking system. The whole loop.
Most software in this space is a single station. A CRM. A booking widget. A phone system. An attribution tool. They glue together with integrations, and integrations break.
Atrium is one factory floor instead, end to end, with every station designed by us. The phone system writes to the same surface as the lead pipeline. The booking confirmation fires the offline conversion event. The attribution stamp travels through every handoff because there are no handoffs to travel across — it’s all one system, on one shared data surface.
The value is in the loop holding. A call without attribution is muda. A booking without a GTM event is muda. A lead that pays but never fires back to Google Ads is a broken telemetry line that the algorithm can never learn from. Every broken link makes ad spend dumber.
Atrium is how every link holds.
Built for healthcare. Works for anything that books.
Atrium grew out of dental practice operations. The lineage shows in the floor view, the call routing, the attribution chain. But TPS works for any business where customers flow through stations toward an outcome.
PRIMARY DOMAIN
Healthcare practices
Where Atrium was forged. The flagship deployment is a dental practice running daily on real patients.
- Dental practices — NHS, private, mixed
- General Practice and GP surgeries
- Physiotherapy and rehabilitation
- Chiropractic and osteopathy
- Optometry and opticians
- Mental health and counselling
- Veterinary clinics
- Dermatology and aesthetics
- Fertility and IVF clinics
- Audiology and hearing centres
- Podiatry and chiropody
- Speech and language therapy
- Specialist consultation rooms
- Diagnostic imaging centres
SECONDARY DOMAIN
Anything that books
Same architecture, different unit on the line. A salon chair, a tutoring slot, a service van — the production discipline applies.
- Salons and barbers
- Spas, massage, beauty clinics
- Personal trainers and fitness studios
- Yoga, pilates, climbing gyms
- Legal consultation booking
- Accountants and financial advisors
- Tutoring, music and language schools
- Photographers and videographers
- Wedding and event services
- Vehicle service, MOT, valeting
- Locksmiths, plumbers, electricians
- Travel agents and tour operators
- Restaurants and private dining rooms
- Co-working space booking
Wherever a customer flows through stations toward a result, Atrium runs the line.
Your floor, as a Toyota line.
The business floor is the line. The customer is the unit flowing through. Each pipeline stage is a workstation.
When Taiichi Ohno built the Toyota Production System, the line wasn’t a metaphor. It was the actual physical plant he was perfecting. He spent thirty years carving discipline into Toyota’s reality, and the cars came out so consistently good that the rest of the world had to retool around what he’d discovered.
That’s the inheritance Atrium carries forward into software. A customer enters via ad click, call, or walk-in. They flow through stations. Atrium tracks each unit through the line internally — takt, pacing, andon signals, kanban handoffs — all running in code. The principles do the work; the interface stays clean.
Most software in this space does it the other way around. It demands attention. It asks the operator to work for it. Atrium is built so the operator never has to think about the system — the system thinks about itself, and surfaces only what needs the human eye. Booking customers get a fast, modern booking flow. The team gets tooling that doesn’t fight them. The TPS discipline lives quietly underneath.
Ohno, not Lean.
When Western consultants brought TPS back to the West in the 1990s, they translated it into a system called “Lean.” It works. But the translation lost things. Things that mattered.
LEAN
WESTERN INTERPRETATION
- First principleEliminate waste.
- How it arrivesConsultants. PowerPoints. Toolkits.
- Wastes7. Plus an 8th retrofitted (human talent).
- Three MsOften reduced to muda alone.
- JidokaAutonomation. Machines that stop.
- 5S5S, with “Sustain” added for enforcement.
- Six SigmaRebranded as “Lean Six Sigma”.
TPS
トヨタ生産方式 · OHNO LINEAGE
- First principleHighlight problems so we can solve them.
- How it arrivesIngrained worldview, every employee.
- Wastes7. Respect for people built in from the start.
- Three MsMuda, mura, muri. All three. Always.
- JidokaWorkers’ authority to halt the line.
- 5S4S. Discipline already covered the fifth.
- Six SigmaOriginated outside Toyota. Barely used inside.
We build Atrium from the source material. Ohno’s writing. The original Japanese discipline. Everything that mattered, kept in. Every link in the loop, intact.
The numbers are stark.
These aren’t projections. They’re documented results from organisations that took TPS seriously and applied it. The same discipline, brought to a booking floor, produces the same kind of effect.
This is what happens when a business operates on Ohno’s discipline. Atrium puts that same discipline at the centre of your booking infrastructure.
Ads that learn from real revenue.
Most platforms see the click and stop there. Atrium follows the customer all the way to the till, then sends the truth back to Google so the algorithm can spend smarter tomorrow.
WORK SEQUENCE · REV-LOOP-01
9 STEPS · END-TO-END
- ADGoogle Ads spend drives traffic to a landing page.
- TAGA dynamic phone number is assigned per visitor and the lead is stamped with its UTM source.
- CALLThe visitor calls or books online. Either way, the lead carries its attribution.
- WRITEAtrium creates the lead, the booking, the appointment record, the payment record, all on one shared data surface.
- EVENTEvery booking fires a GTM dataLayer event the moment it confirms.
- PUSHGTM pushes an offline conversion event back to Google Ads, carrying the source metadata.
- LEARNGoogle Ads learns: that keyword, that campaign, that creative produced a paying customer at this revenue level.
- SHIFTThe algorithm shifts budget toward what actually converts to revenue, not just to clicks.
- LOOPMore qualified calls and bookings arrive. The loop continues, getting smarter as it runs.
Most marketing platforms stop at step three or four. Atrium tracks through step nine. Google Ads stops guessing and starts seeing what genuinely paid.
That’s the emergence. Nobody programs the improvement. The system simply writes truthful numbers to shared surfaces. Google reads them. The ads get smarter. And they keep getting smarter the longer the business runs — month twelve will outperform month one without anyone working harder.
Notice what isn’t in the chain. No names. No addresses. No personal data. The attribution runs on click IDs, booking slots, treatment costs, revenue numbers, and the business’s own costs. The intelligence is in the emergence, not in identities. Like an ant colony — we don’t need to look at any individual ant to understand the colony’s behaviour. We only need to look at what happens. That’s the secret.
Ohno’s substance. Not Western lean’s vocabulary.
The difference matters. Lean often reduces Ohno’s three enemies (muda, mura, muri) to just muda. Lean takes jidoka as “autonomation” and drops the human-judgment-and-authority piece that was the heart of it. Lean cargo-cults the tools without the culture.
We build from Ohno’s writing directly. Seven principles, all alive in Atrium, all doing real work in the floor view above.
自僸化
JIDOKA
P·01
Automation with a human touch.
The system stops itself when abnormalities occur. Any agent can pull the andon. An incoming call is a real andon. A lead overdue for callback glows on the board. Problems surface immediately. They do not hide.
ジャストインタイム
JUST-IN-TIME
P·02
Pull, only when needed.
Alongside jidoka, the second pillar of TPS. Nothing is produced or held until the next station signals demand. Calls flow when capacity exists, callbacks queue without piling, reminders fire on signal not schedule. The line breathes.
ポカヨケ
POKA-YOKE
P·03
Mistake-proofing.
The hold system makes double-booking impossible. Every common error is either made impossible at the design level, or caught at the instant it happens. The system protects the operator from the work, not the other way around.
現地現物
GENCHI GENBUTSU
P·04
Go and see.
Decisions on the floor, not through reports. The owner walking through Atrium sees the actual work right now — live state, not yesterday’s summary. Reports are how decisions go bad slowly.
改善
KAIZEN
P·05
Continuous improvement.
Many small changes, from the operators themselves. Every script, every callback-timing pattern, every lead-scoring heuristic gets baked in once proved. The system learns from use, every shift.
平準化
HEIJUNKA
P·06
Level the flow.
Smooth callback cadence. Space reminder volume. Keep throughput even. No Monday with fifty callbacks piled up and Wednesday with three. Even flow beats heroic flow, every time.
五回
5 WHYS
P·07
Root cause on every deviation.
When a call drops, when a booking fails, when a customer walks away, the chain of cause is recoverable. The system logs enough for any failure mode to be traced to its origin and fixed at root, not papered over.
三M
MUDA · MURA · MURI
P·08
Waste. Unevenness. Overburden.
Every duplicate note, every re-entered field, every minute a lead sits silent, every agent swamped while another is idle — all of it must be visible, then killed. All three enemies, never just one.
When the floor is on another continent.
Modern booking businesses run distributed. Call teams across timezones, supervisors watching from another country, owners stepping onto the floor in the evening to see how the day went.
The owner can’t physically walk the floor when the team is three flights away. The digital floor view is their gemba. So it has to support real genchi genbutsu, not a watered-down dashboard version.
Walk-in reading: one glance reveals the entire shift state, no orientation delay. Zoom without losing the floor: clicking any lead or agent opens a side panel while the whole board stays visible — Ohno walked up to a worker without losing sight of the line, and we replicate that exact movement. Live listen: supervisor monitoring and whisper, so an owner can hear a call in progress for kaizen without disturbing the work. Rewind: scrub the floor back to any timestamp and see the state as it was, because every event was logged. Annotate: a lightweight way to mark what was observed, and annotations become kaizen candidates the next morning.
A remote owner observing from another timezone gets the same instrument Ohno had walking the plant in Toyota City.
Behaviour nobody programmed.
Every engine in Atrium is sovereign. None of them know each other exist.
The notifications engine sweeps every five minutes and sends what needs sending. The booking-system bridge pushes appointment writes upstream. The attribution engine stamps leads with their source. The availability engine computes blocks minus appointments minus active holds. The email transport does its one thing. They never call each other. They all read and write one shared surface — the 20 database tables that are the ground of the system.
From that, emergence. A caller who misses three times gets routed differently than a first-timer, because routing rules read the call history and the history is just there. Ad sources producing high-callback-rate leads drift toward priority without anyone deciding. New engines added later make old engines start doing things we didn’t anticipate.
The ads algorithm improves because real conversion data flows back. Nobody programs that improvement. The system simply writes truthful data. Google reads it. The ads get smarter. That’s the emergence engine.
54
ROUTE ENDPOINTS
20
DATABASE TABLES
Rust
END TO END
Live
REAL BOOKINGS WEEKLY
Atrium runs when we run your growth stack.
Not licensed separately. Part of the work we do when you bring us in to run the full conversion infrastructure of your business.