The hours
The times you already publish
Build & Integrate
Software shaped around
the workflow
A focused app, integration, or migration for the job. Screens, rules, and a review boundary — not another generic category.
The ledger
Facts you already stand behind
A person
Outside the published rules
The inbox
Checked against published hours
A slot
A free time, then it is held
Phone
The published hours you already keep
The pack
Cited, ready for review
Facts
The approved set — not the open web
The queue
Handoff with the record attached
Messages
Same rules when you add a channel
The record
What the rest of the job can use
Write-back
With an audit trail, or it does not write
Screens for the job
The interface is the work, not a dashboard of everything.
Channels
1 of 5
Caller, Tuesday 08:14
Hi —
Booked a follow-up in the hours you already publish. Name, need, and callback window captured.
Same day, as a handoff
Queued for a person, with the record attached.
Phone
Rules the job uses
Hours, services, and handoff stay in the facts you already maintain.
The approved set
Facts
- Hoursopening_hours
- Serviceswhat_you_take
- Open websearch
Check published hours. Hold a free slot. Queue anything outside the rules with the record attached.
Reply from the set
opening_hours what_you_take — Nothing from outside it.
Question in
Are you open Saturday?
2 / 3Review boundary
Consequential actions wait for a person. The rest can run.
1Known hours questionMatches published factsTry
2Complaint caseQueued — outside the rulesWait
3New tool callBlocked until reviewWait
Then a person
Anything outside those rules waits with the record attached.
Outside the rules
API integrations
Connected, not copy-pasted
Move data and actions between the systems you already pay for, with permissions and an audit trail.
CRM
The record the rest of the job can use.
System of recordLedger
Reminders and exceptions, not a chase list.
PaymentsQueue
Handoff lands where the team already looks.
HandoffPhone
The published hours and services you already offer.
ChannelInbox
Files and notes stay with the job that opened them.
InboxWrite-back
With an audit trail, or it does not write.
APIBrowser automation
The job still runs
Drive a site that has no useful API the way a person would — clicks, forms, downloads — under review. Consequential submits wait. The run does not invent a confirmation.
Discuss thisMigration tools
A cutover you can stop
Move records from one system to another with mapping, checks, and a halt if something looks wrong.
1Map the fieldsShape you already useTry
2Run the checksFlag what does not mapWait
3Write liveStopped until reviewWait
Map the fields you already use
Source to destination in the shape the job expects.
Inbox
- HoursOpen
- A slotHeld
- The queueQueued
- A personGap
Ledger
- HoursOpen
- A slot—
- The queueQueued
- A person—
Hours
Same record, both sides.
Run the checks
What does not map is flagged — not silently dropped.
Halt
Stop if it looks wrong
Live write waits until the exceptions are judged. Cutover is a controlled step, not a one-way dump.
Agent-ready websites
Safe tools on the site you already have
Expose the pages and actions an agent needs, with the same limits a person would have. Hours, services, booking — what a person would already use. No extra write, no extra read.
Discuss this
Temporary project software
Not another permanent product
A short-lived tool for a defined job, then shut down — not another product to maintain. Screens, rules, and a review boundary for the duration. When the job ends, the tool comes down.
Discuss thisThe job
Built around the stack you already run
Build
- Screens
- Rules
- API
Review
- Boundary
- Handoff
- Sign-off
An app for the work, then shut down if it should
Across the business
Work that runs in your tools
Screens, rules, and a review boundary — around the CRM, calendar, phone, and the rest of the stack you already run.
Ask about thisThe prompt
HoursNext step
Hours, slot, queue
Hours
A slot
Queue
Same rules, written once.