How we build
From briefto a systemthat keeps running.
Every build is made from the same tested parts. Here is how they fit together.
No magic. An agent is eight parts we choose, test and wire together. Scroll, drag or tap a level to see how parts become an agent, a workflow, a system and a delivered project.
Khlong Lantern Kitchens · Project Tidewater
An invented Bangkok group of three riverside restaurants, used to show how we would build a LINE booking and ordering agent. Not a real client; no real data.
Agent. Assembled: one agent with one job, in the chat app your customers use.
How we bring the stack together
One booking, five layers, in under a second
Logos are easy to put on a slide. The work is in how they connect. Press play and follow one Tidewater booking through every layer.
- · LINE message received · intent: booking
- · Identity verified · session issued
- · ฿ deposit authorised · receipt sent
- · Row written · constraints passed
- · Confirmation delivered in chat
Vendor names and logos belong to their owners and show integrations we can build with. They do not imply a partnership.
01 · Channel
The guest taps “Book a table” in the LINE chat they already use.
02 · Secure login
One tap identity. No new password; staff sign in with Microsoft or Google.
03 · Payments
Deposit by card, wallet or PromptPay QR. We pick what your guests use.
04 · Database
Booking, guest and table saved with rules that stop double bookings.
05 · Hosting & delivery
Fast pages and confirmations from the edge, with uptime monitoring.
Layered architecture
Every layer separate, changeable one at a time
The eight parts
- 01
Channel
Where it lives: LINE, WhatsApp, Telegram or your website.
- 02
Trigger
What wakes it: a message, a form, a schedule or an event.
- 03
Instructions
Its job, tone and limits, written down and versioned.
- 04
Knowledge
Your menus, policies and FAQs, kept current.
- 05
Tools
Connectors that let it book, look up or update records.
- 06
Memory
What it may remember about a conversation, and for how long.
- 07
Guardrails
Checks on what it may say or do, with logs you can read.
- 08
Human hand-off
When to pass to a person, and how fast they are alerted.
Design system in motion
One token changes every screen at once
Colour, type, spacing and motion are defined once, so every button, card and screen stays consistent as the product grows.
Data relationships
AI can write the code. Knowing where it will break is the job.
Here is Tidewater’s data in five tables. Pick a problem real projects hit, see it break, then apply the fix.
Without the fix
Two guests get table 4 at 19:00. Both arrive.
Engines we build with
Parts that come into a build when it needs them, each with its own page.
- Quote engineYour website scopes every enquiry before you answer it.
- Self-improving websiteA site that learns from what visitors do.
- Queue and bookingQueues and bookings over chat.
- Free invoicingQuotes, invoices and receipts with Invoice Maker.