Lando is one system with two faces. The engine room runs the business around the clock without being asked: catching leads, chasing estimates, watching reviews. The conversation layer is how the owner talks to it: ask a question, give a command, approve a decision, all in plain language. Both sides run on the same shared memory, so the agent the owner texts at lunch already knows everything the engines did overnight.
Side one · The conversation
The owner talks to Lando
Questions, commands, and approvals in natural language. The owner's interface to everything below.
Side two · The engine room
Lando runs the business
Signals in, engines act, decisions route. Works every hour whether anyone is talking to it or not.
This diagram is live. Pick a scenario in either section and follow it through the system. Hover any engine for what it does.
Side one · The conversation
Conversational Agent Architecture
How a plain-language message becomes an answer or an action. Try one:
A1 · Owner channels — wherever the owner already is
Voice
SMS
App Chat
▼
A2 · Understanding & reasoningIntent, context, and judgment
What's being asked · What matters Claude API
▼
A3 · Shared operational memory — the hinge between both sidesOne memory, both sides
Jobs · Leads · Threads · Schedule Engine activity log · Briefing history
▼
A4 · Two ways out
AnswerComposed reply, state + next move
Command DispatchHands the action to the engine room
Dispatch flows into the engine room below ▼
LandoIllustrative conversation · product in build
The conversation shows up here. Pick a scenario.
Side two · The engine room
Multi-Agent Operations Architecture
What runs whether or not anyone is talking to it. Follow a signal:
B1 · Signal layer — where the business talks
Inbound Calls
Web Forms
SMS Threads
Reviews
CRM / FSM Events
Data APIsWeather · Property · Geo
▼
B2 · Orchestrationn8n Orchestration Backbone
Signal routing · Engine dispatch State management · Full activity log
▼
B3 · Engine layer — 6 of 25 modules shown
Lead ResponseEngine module
Follow-UpEngine module
Review & ReputationEngine module
Morning BriefingPlatform exclusive
Daily Close-Out AuditPlatform exclusive
Proactive ObservationsPlatform exclusive
▼
B4 · Decision routing — what AI decides, drafts, or hands off
Autonomous
System acts. Every action logged.
Lead acknowledged in under 60 seconds
Follow-up steps sent on cadence
Approved-template review responses
Draft for Approval
System prepares. Owner approves from phone.
Negative review responses
Reactivation and campaign copy
Customer reschedule proposals
Escalate
Owner decides. Full context attached.
Pricing exceptions and disputes
Upset customer threads
Anything ambiguous or first-of-its-kind
▼
B5 · The owner
Sees only the decisions that need a human. Everything else is handled, logged, and auditable. And whenever they want more, they just ask. That's side one.
Design standard: nothing falls through the cracksLando · Design excerpt