- Result
- 3 bookings booked this week. The week before had 0.
- Method
- Each guest matched to someone who engaged, by email: 3 of 3.
- Witness
- Each one has the comment, reply or booking link behind it on file: 3 of 3.
Bookings per week, where each one came from, and the proof behind every meeting. It runs on your computer, and it sends nothing unless you do.
SIMULATED A demo workspace with fictional people. Every number here comes from it.
Eight weeks of the demo workspace. A quiet week stays a zero; it is never filled in.
SIMULATED Counted by the week the meeting was made, not the week it is held.
| Week of | Bookings | Marks |
|---|---|---|
| Sep 7 | 0 | |
| Sep 14 | 0 | |
| Sep 21 | 0 | |
| Sep 28 | 0 | |
| Oct 5 | 1 | |
| Oct 12 | 3 | |
| Oct 19 | 0 | |
| Oct 26 | 3 | this week |
| Channel | Engaged | Booked |
|---|---|---|
| 4 | 3 | |
| an event | 5 | 1 |
| 7 | 2 | |
| Substack | 2 | 0 |
| X | 3 | 0 |
| YouTube | 3 | 1 |
All eight weeks of the demo. Engaged means a comment, reply or sign-up; spam and skipped comments are left out. Not every booking follows a send: two came from a link in an email signature or a video.
The words they wrote, the day, and how the guest was matched. A meeting counts only when the evidence supports it.
SIMULATED 7 counted bookings, newest first. Fictional people.
“The section on sampling was useful. Could you share how you pick which agent runs to review?”Oct 12, on Audit Notes #12: who reads the trail? (email)
“Rollback is the part nobody rehearses. We drill it quarterly and it still surprises us.”Oct 21, on rollback plans (LinkedIn)
“Can the trail be exported to our SIEM, or is it a separate store?”Oct 14, on Audit trails for AI agents: a live teardown 2026-10-14 (an event)
“Sam, we have the trail but nobody reads it until something breaks. How do other teams schedule review?”Oct 11, on Audit Notes #12: who reads the trail? (email)
“How would this work at our scale? We run a few thousand agent calls an hour.”Oct 1, on agent identity (LinkedIn)
A plain calendar count says six this week. Groundtrace says three, and shows you why the other three are held back.
SIMULATED Fictional people.
people_you_know
clients
awaiting_check
The number has to survive a hard question.
Ten meetings reached the booking ledger in this demo. 7 are counted, 3 are held back, and each held-back one says why in plain words. Nothing is rounded up to make a week look better.
Groundtrace reads, matches, counts and drafts. You decide, you send, and you press Mark as sent.
| Step | Who | Note |
|---|---|---|
| Connect your calendar and mail, or paste what you have | You | Nothing is read until you connect it |
| Read new comments, replies and meetings | Groundtrace | On your computer, each morning and on demand |
| Match each guest to the person who engaged | Groundtrace | By email; a name alone waits |
| Count the booking and file its proof | Groundtrace | Dated, and quoted from your own records |
| Write a draft for each person waiting | Groundtrace | Labelled by what wrote it, never sent |
| Confirm a name-only match | You | One tap per person |
| Decide who is worth answering | You | Held-back meetings stay held until you say |
| Send the message, on LinkedIn or by email | You | Every reply, note and email |
| Press Mark as sent | You | That is what records it as sent |
Each says what wrote it. A connection note is counted in code against LinkedIn’s 300-character limit before you see it.