Pick a stage to see what we do, what you do, what you get and when you pay.
A short call
Open
What we do
We ask what the task is, who does it today and which tools it touches. If a simpler tool does the job, we say so.
What you do
Describe the task and show us how it works today.
What you get
An honest answer on whether and how we can help. No charge.
Payment
Nothing yet.
We write it down
Scoped
What we do
A written scope of work: what is included, what isn't, what "done" means, and one fixed price.
What you do
Read it, ask questions and sign it.
What you get
The scope of work and the price, in writing, before anything is built.
Payment
40% to start.
We build on your real examples
Building
What we do
We build against your own files, forms and data, test it, and show you a working version.
What you do
Give us access to the tools involved, or exports and sample data if direct access isn't possible. Name one person who can answer questions.
What you get
A working demo you can try before it's finished.
Payment
Nothing more until delivery.
We deliver what the scope says
Delivered
What we do
We deliver exactly what the scope of work lists, connect it to your tools and walk you through it.
What you do
Try it, and sign off when it does what the scope says.
What you get
The finished work from the scope, short written notes on how it works, and a walkthrough call.
Payment
The remaining 60% on delivery.
Fixes are covered, then you choose
Supported
What we do
For 30 days after delivery, we fix anything that doesn't work as scoped, at no charge.
What you do
Tell us if something looks wrong.
What you get
30 days of fixes. After that, your choice: a monthly plan that covers monitoring and small changes, or pay only when you need a change.
Payment
Nothing for fixes in the first 30 days.
Automation examples: a job for your kind of business
Illustrations of jobs that run on their own. Not past clients.
Pick the kind of business closest to yours
Freight and logistics: late-load watch
Tracking emails and the system export arrive together and are matched by load number. Each load is checked against its delivery window. On-time loads are logged, at-risk loads go on the dispatcher's morning list with the reason, and loads with no update trigger a status request to the carrier.
Tracking emails
from carriers
+
Load export
from your system
→
Match by load
one record per load
→
Check the window
against each delivery time
→
On time
Logged, no action
At risk
Dispatcher's morning list, with the reason
No update
The carrier is asked for a status
Why not just software? Tracking platforms are priced for large carriers. This works from the emails you already get.
Trucking companies: driver settlements
Trip logs, fuel receipts and each driver's pay rules arrive from three places and are combined into a settlement per driver, checked against rate and deductions. Matching settlements go to payroll as drafts, missing receipts trigger a request to the driver, and settlements that don't add up are held with the difference shown.
Trip logs
from dispatch
+
Fuel receipts
photos and card data
+
Pay rules
per driver and lane
→
Build each statement
and check it against rate and deductions
→
Adds up
Draft settlement for payroll
Missing receipt
The driver is asked for it
Doesn't add up
Held, with the difference shown
Why not just software? Your dispatch software knows the miles. It doesn't read receipt photos and each driver's pay rules together.
Insurance agencies: renewal emails
A weekly policy list is read and policies expiring soon are found. A renewal email is drafted for each, then a person reviews and approves it, and their edits shape later drafts. Drafts with missing details go to the account manager instead.
Weekly policy list
from your system
→
Find renewals
in the next 60 days
→
Draft each email
using the client's details
→
A person
Agent reviews
edits and approves
↺ Edits shape the next drafts
→
Sent
Goes out under the agent's name
Missing details
Account manager fills in, then it's redrafted
Why not just software? Your management system tracks renewals. It doesn't write the email from the client's file.
Property managers: lease abstracts
Lease PDFs, scanned and in many layouts, are read and their key terms pulled out: rent, dates and notice periods. The dates are checked for renewals and rent increases. Nothing due is logged, dates coming up go on the manager's list with the clause, and unclear clauses are marked for a person to read.
Lease PDFs
scanned, many layouts
→
Pull out the terms
rent, dates, notice periods
→
Check the dates
renewals and rent increases
→
Nothing due
Logged in your spreadsheet
Coming up
Manager's list, with the clause
Unclear clause
Marked for a person to read
Why not just software? Property software holds the dates you type in. It doesn't read the lease to find them.
Distributors: supplier price lists
Price lists arrive from several suppliers in different formats and are each read and mapped to the company's own product codes. Prices are compared to current ones. Normal changes update the master sheet, big jumps go to the buyer with old and new prices, and unknown items are listed for someone to match.
Supplier A
PDF price list
+
Supplier B
Excel sheet
+
Supplier C
pasted into an email
→
Map to your codes
one reader per layout
→
Compare prices
to what's current
→
Within your limit
Master sheet updated
Big jump
Buyer approves, with old and new price
Unknown item
Listed for someone to match
Why not just software? Your system imports one clean format. Suppliers don't send one.
Contractors: change orders
Field notes and photos arrive together and are priced from the company's rate sheet. The change is checked against the contract. Covered changes are drafted for approval, changes outside the contract go to the project manager, and unclear scope sends the superintendent a question.
Field notes
text from the job
+
Photos
of the work
→
Price it
from your rate sheet
→
Check the contract
is it covered?
→
Covered
Change order drafted for approval
Not covered
Project manager decides
Scope unclear
The superintendent is asked
Why not just software? Construction software holds the change-order form. It doesn't price field notes from your rate sheet.
Accounting firms: client organizers
Clients return year-end questionnaires as PDFs, spreadsheets and photos in every layout. The answers are read into the firm's own workpaper layout and compared with last year. Unchanged answers fill the workpaper, changes are shown to the preparer, and blank answers send the client a question.
Client replies
PDF, Excel, photos
+
Last year's file
for comparison
→
Read into your layout
your own workpapers
→
Compare
what changed since last year
→
Same as last year
Workpaper filled in
Changed
Preparer sees what changed
Left blank
The client is asked to confirm
Why not just software? Client portals collect the files. They don't read free-form answers into your own workpapers.
Staffing agencies: incoming resumes
Resumes arrive from email and job boards and are read and sorted by role and skills, then matched to open jobs. A recruiter picks from the matches, and those choices improve the next round of matching. Picked candidates go to the hiring manager; the rest stay on file for future jobs.
Email
applications
+
Job boards
new applicants
→
Read and sort
by role and skills
→
Match to open jobs
against each job's needs
→
A person
Recruiter picks
from the matches
↺ Choices improve the next round
→
Shortlisted
Sent to the hiring manager
Kept on file
Matched to future jobs
Why not just software? Your system parses resumes. It doesn't apply how your recruiters judge a match.
Auto repair shops: parts invoices
Parts invoices from several suppliers arrive as PDFs and emails and are matched to the shop's repair orders. Prices are checked against what was quoted and returned parts are checked for credits. Matching invoices are ready to pay, price differences go to the advisor with quote and invoice side by side, and missing credits trigger a request to the supplier.
Supplier invoices
PDFs and emails
+
Repair orders
from your shop software
→
Match each part
to its repair order
→
Check price and credits
against the quote and returns
→
Matches
Ready to pay
Price differs
Advisor sees quote and invoice
Credit missing
The supplier is asked for it
Why not just software? Shop software tracks repair orders. It doesn't read each supplier's invoice and match it to the job.
Why it takes a build
Runs by itself, every time
Follows your own rules and formats
Keeps a record of every decision
Knowledge base and agent examples
Illustrations of assistants built on your documents and systems. Not past clients.
Pick an assistant
Insurance agencies: carrier guidelines
Staff ask a question in plain language. The assistant searches the carrier guides and the agency's own notes, sets aside outdated pages, and answers with the page it came from. If two sources disagree, both are shown and the owner is told. Questions nothing covers are logged for someone to answer.
Staff ask
in plain language
→
Search the guides
carrier rules and your notes
+
Use the newest version
outdated pages set aside
→
Answer with the source
the page it came from
→
Found
Answer shown with its source
Sources disagree
Both shown, the owner is told
Not covered
Logged for someone to answer
Why not just software? A shared drive finds file names. This finds the answer and knows which version is current.
Sales teams: answers for new reps
A new salesperson asks a question in plain language. The assistant searches the company's playbook, setting aside outdated versions, and answers with the page it came from. Questions the playbook doesn't cover go to the manager and are added afterward.
A rep asks
in plain language
→
Search the playbook
scripts, pricing, objections
+
Use the newest version
old documents set aside
→
Answer with the source
the page it came from
→
Found
Answer shown with its source
Not covered
Manager answers, then it's added
Why not just software? Chat tools don't know which of your documents is current. This follows your own versions and cites the page.
Freight and logistics: load status agent
A customer asks where their load is. The agent looks the load up in the system and the tracking emails and checks what it may share. It replies with the status. Late loads are handed to a dispatcher with the details already gathered, and anything it isn't sure about waits for a person.
Customer asks
"Where's my load?"
→
Look it up
your system and tracking emails
+
Check the rules
what you may share
→
Reply or hand off
decides which
→
On track
Status sent, logged
Late
Dispatcher takes over, details gathered
Not sure
Held for a person to answer
Why not just software? A chatbot only answers from text. An agent checks your systems and takes the next step.
Property managers: tenant questions agent
A tenant texts a question. The agent checks the lease and the open requests. It answers from the lease, or opens a work order and tells the tenant. Disputes and fee questions go to the manager.
Tenant asks
by text or email
→
Check the lease
rules and terms
+
Check open requests
what's already in
→
Answer or act
reply, or open a work order
→
Answered
From the lease, logged
Work order opened
Vendor booked, tenant told
Dispute or fees
Goes to the manager
Why not just software? A chatbot can quote a policy. An agent can also open the work order.
Fixed price, scope in writing first, 30 days of fixes.