AI agents, built around one job

AI agents for billing checks, lead lists, meeting research, trade show prospecting and recruiting

We build an agent for that one job. It finds, checks and drafts the work your team does by hand. Nothing reaches a customer, a candidate or a record until a person approves it.

The billing check runs live at a five-center behavioral health network. Every other agent is labelled by status below.

01On your desk

What arrives on your desk.

Pick a job to see a sample of the work it hands over. Names and numbers are invented; the format is real.

What the records check agent hands your teamSample · invented data
ATTENDANCE LOGWhat the site recordedby day, by clientSYSTEM OF RECORDWhat the chart showsread-onlyTHE AGENT1Compares the twoday by day, by your rules2Drafts the recordin the format you useDRAFTThe reconciled recordready to check, not sentEXCEPTIONSEach one with its reasonmissing, mismatched, unsignedYOUR TEAMStaff review and approvenothing is billed until they doLOGThe site recordRECORDThe chartTHE AGENT1Compares the twoby your rules2Drafts the recordin your formatDRAFTReconciledready to checkEXCEPTIONSWith reasonsto reviewYOUR TEAMStaff review and approvenothing is billed until they do
ClientDayAttendance logSystem of recordResult
Client AMon3-hour groupSigned group note, same dayMatchedSame day, same session
Client BTue3-hour groupNo note that dayNeeds reviewPast the 24-hour note window
Client CWedNot on the logSigned group noteMissing from logConfirm attendance
Fig. 1 Green is the agent’s draft, amber is what needs a person, navy is your team.
02The agents

Three agents, each named for the job it takes.

Each one started from a job we saw done by hand. The label says how far it has gone.

Records check agent

Running

The job: someone compares two systems that should agree, line by line, before the numbers go out.

Reads
Attendance logs, the system of record (read-only), your template
Gives
A drafted record and the exceptions, each with its reason

Live at a five-center behavioral health network. Read the case study

Lead pipeline agent

In delivery

The job: a rep spends days building a call list, and it includes accounts already in your CRM.

Reads
Public lists and directories, your fit rules, your CRM (read-only)
Gives
New accounts that fit, why each fits, the right person to contact

In delivery for a B2B services company. Not yet live.

Research agent

We use it

The job: before a meeting or a decision, someone digs through websites and filings, and nobody knows which facts were checked.

Reads
Public sources you approve, your own notes
Gives
A one-page brief, every fact linked and dated, unknowns marked

In use in our own business before prospect calls. Not yet run for a client.

Other workflows we can design
  • Trade show prospecting. The lead pipeline pointed at exhibitor lists, to prepare prospects before a show.Designed
  • Recruiting research. People with the right experience for a role, as a shortlist with reasons. Outreach is drafted, a person sends it.Designed
  • Website check. Potential friction in the path from visitor to inquiry. An internal example we run on businesses we research.We use it
  • Inbound calls. The AI receptionist answers, books and routes calls by your rules.Designed

Running in behavioral health and in our own business. In delivery for a B2B services company.

03How it works

Our agents follow the same operating pattern.

You give it rules, sources and access to your systems. It finds, checks and drafts. A person on your team decides.

The operating patternIllustrative
THE RULESWho fits, what it may dowritten down before it runsTHE SOURCESWhere it may lookpublic sites, lists, directoriesYOUR SYSTEMSCRM, records, sheetsread-only by defaultTHE AGENT1Findsin the sources you agreed2Checksagainst rules and records3Draftsrows, briefs or exceptionsYOUR TEAM4A person decidesapproves, fixes or dropsnothing leaves without step 4LANDS INA review listkeep, correct or drop each rowLANDS INYour CRMapproved records onlyLANDS INA shared sheetfor the team that acts on itLANDS INA run recordwhat it read, spent and changedTHE RULESWho fits, what it may doTHE SOURCESWhere it may lookYOUR SYSTEMSRead-only by defaultTHE AGENT1Finds2Checks3Drafts4A person decidesapproves, fixes or dropsA review listkeep or drop each rowYour CRMapproved records onlyA shared sheetfor the teamA run recordwhat it read and spent
Fig. 2 Green is the agent’s work. Navy is a person on your team.
04When it cannot finish

When something is missing, it stops and says so.

This is how the records check agent behaves today. It never fills a gap with a guess.

When it cannot finishObserved · records check
The nightly runstarts on scheduleSourcesread?NoSTOPS, DOES NOT GUESSThat source marked “not read”and we are notifiedYesCheck and draftby your rulesLog andrecord agree?NoHELD, NOT PUBLISHEDThat center’s files waitwith the rows that disagreeYesYOUR TEAMReady to approvea person signs offThe nightly run startsSourcesread?NoMarked“not read”we are notifiedYesCheck and draftLog andrecord agree?NoFiles heldwith the rowsYesYOUR TEAMReady to approve

Run receipt Sample · invented numbers, real fields

Ran
Tue 3:02 AM ET, finished 3:41
Sources read
4 of 5 · one marked not read
Centers checked
4
Held for review
1 center, 3 rows
Weekly email
Draft ready, not sent
Fig. 3 Amber is a stop that a person resolves. Nothing held is published.
05Up close

Inside the lead pipeline: the agent prepares, your team decides.

It checks fit and your CRM before any paid contact lookup. A person approves every account, and your team decides the outreach. The agent sends nothing.

The lead pipeline agentIllustrative
YOUR FIT RULESAt least three locationsin the states you serveSOURCES YOU APPROVEDirectories and listspublic, dated, linkedYOUR CRMRead-onlyto skip anyone you knowTHE LEAD PIPELINE AGENT1Find candidatesfrom approved sources only2Check fitagainst your rules3Check your CRMalready known? set aside4Find the right personpaid lookup only if it passed5Draft the rowwhy it fits, the source, the dateYOUR TEAM6A person approvesthen decides the outreachapproved corrections become rulesSET ASIDE, WITH A REASONMisses and known accountsno paid lookup on themLANDS INApproved accountsin your CRM or a shared sheetLANDS INA weekly summarynew, set aside, and whyLANDS INA run recordwhat it read and what it spentFIT RULESAt least three locationsSOURCESDirectories and listsYOUR CRMRead-onlyTHE LEAD PIPELINE AGENT1Find candidatesapproved sources only2Check fityour rules3Check your CRMknown? set aside4Find the right personpaid lookup if it passed5Draft the rowwhy, source, date6A person approvesthen decides the outreachApproved accounts, a weekly summary,and a run record
Fig. 4 Based on a build in delivery. The example rule is illustrative, not a client’s.
06The rules

What it may do alone, what waits for you, what it never does.

Written down per agent before it runs, and changed only by you. These are the defaults for the records, list and research agents.

May do alone

Find, check, draft

  • Search the sources you approved
  • Read your systems, read-only
  • Spend within the agreed cap
  • Draft rows, briefs and exceptions
Waits for approval

Changes, and spend past the cap

  • Adding records to your CRM
  • Spending past the agreed cap
  • Anything a customer will see
  • Any change to its rules
Never

Go past its agreed permissions

  • Send an email or message on its own
  • Make clinical, billing or coding decisions
  • Touch patient data without a BAA
  • Run without a record of what it did
07Your tools

It reads from, and leaves work in, the tools you already use.

No new platform for your team to learn.

Where it reads, and where its work landsConnected for clients
READS FROM · YOUR SYSTEMSKipuread-onlyHubSpotread-onlyExcel workbooksreadSharePoint and OneDriveread, and files reportsSalesforcein buildTHE AGENTFinds · Checks · Draftsa person approvesLOOKS UPOutside sourcespublic sites, lists, capped dataLEAVES WORK INYour CRMapproved records onlyA shared sheetfor the team that actsA document librarybriefs and reportsAn email drafta person sends itREADS FROMKipu · read-onlyHubSpot · read-onlyExcel workbooksSharePoint, OneDriveSalesforce · in buildOutside sourcesFinds · Checks · Draftsa person approvesLEAVES WORK INYour CRMA shared sheetA document libraryAn email draft
Fig. 5 Systems we have connected for clients. Dashed means in build. Writing to a system is agreed separately.
08Is it helping

How we know it is helping.

Before anything runs on its own, we measure the job as it is done today, then run the agent beside the person doing it.

From baseline to a decisionHow we will measure your pilot
BEFOREManual baselinehow long the job takes todayWEEKS 1 TO 2Side by sideagent and person, same weekEVERY WEEKReview time, correctionsmeasured, not estimatedTHENDecide to continuewith the numbers in handBEFOREManual baselineWEEKS 1 TO 2Side by sideEVERY WEEKReview time, correctionsTHENDecide to continue
Fig. 6 No savings are promised up front. The numbers come from your own weeks.
09Status

Where each one stands.

  • RunningThe records check agent, live for a five-center behavioral health network.
  • In deliveryThe lead pipeline agent for a B2B services company. Not yet live.
  • We use itThe research agent and the website check, in our own business. Not client proof.
  • DesignedTrade show prospecting, recruiting research and the AI receptionist.

Not claimed: hours saved, meetings booked or revenue. When an agent produces a measured result for a client, it will appear here with the date.

10Questions

What owners ask first.

Is an agent a chatbot?

No. Nobody chats with it. It runs on a schedule or when you ask, does one job, and leaves its work in a place your team already uses: a review list, a sheet, your CRM or a document.

Will it email my customers or prospects?

Not on its own. It can draft a message. A person reads it and sends it. That rule is written down before the agent runs.

What does it need access to?

The least it needs for the job. Reading your CRM or system of record is read-only by default. Anything that writes, or spends past an agreed cap, waits for approval.

What happens when it is wrong?

Research and list agents show where every fact came from, and record checks give the reason for every exception, so a reviewer can check the work quickly. Corrections are reviewed, and once approved they become rules the agent follows next time.

Who owns it?

What it produces is yours. Where it runs, who maintains it and what happens if we part ways are agreed in writing before the build.

Can you build one for healthcare?

Yes, with a BAA in place before any patient data is touched, and a qualified service organization agreement where 42 CFR Part 2 applies. Your privacy lead approves what it reads. This is not legal advice.

Which job does your team do by hand every week?

Bring one to a free 20-minute call. We will tell you whether an agent fits it, or whether a simpler fix would do.