Picture the last weekly meeting of next quarter. The Rock review reaches your controller, who says one word: done. Every overdue invoice now gets its follow-up prepared before Tuesday noon, to the standard of the best collector the company ever had. The test record is on file, the clerk who runs it would not go back, and the leadership team has already picked the next seat to power up. That is the first step toward 10X what your team can do, and it took one quarterly priority.
You already have the rhythm.
Most AI pilots stall for want of three things: one owner, a date and a moment when somebody has to decide. A team that runs on EOS has all three built into its quarter. A Rock has one owner and a due date. The weekly meeting asks whether it is on track. The quarterly session closes it and sets the next.
So an AI pilot needs no steering committee and no separate program. It needs to be written as a Rock. The first 90 days of an AI adoption plan is the general plan, from naming an owner to mapping the work. This piece takes one pilot and fits it into the quarter you already run.
Write it so it can be done.
“Explore AI in finance” can never be called done. Three choices turn a pilot into a Rock.
- Name the outcome as work the seat does every week. One recurring piece of work, one finish line a person can check. Choose your first AI wins ranks the candidates.
- Give it to the seat that owns the result. The capability sits beside the person your chart already holds accountable, as in Add AI capabilities to your Accountability Chart. It is never the IT lead’s Rock for someone else’s work.
- Make the decision the finish line. The Rock is done when the capability has been tested on your own work and the team has decided to expand, adjust or stop. All three count as done, so the owner reports what the evidence shows.
The Rock, written out.
An invented 70-person commercial HVAC service company runs on EOS. At its December session the leadership team gives the finance seat one Rock for the first quarter of 2027. The pilot is overdue-invoice follow-up preparation: every Monday the aging report comes out, and by Thursday some follow-ups have gone and some have not.
Illustrative example with invented data. The company, its people and every date are invented. The layout is ours.
Rock, Q1 2027: overdue-invoice follow-up, prepared every week
- The Rock
- By Friday 26 March 2027, overdue-invoice follow-up preparation has passed its acceptance test on our own invoices, is in weekly use in finance, and the leadership team has recorded its decision to expand, adjust or stop.
- Outcome
- Every Tuesday by noon, each invoice more than 30 days overdue has a follow-up ready for approval, in our tone for its age, or a recorded reason it is held.
- Owner
- The controller, who holds the finance seat. One owner; the Rock is not shared.
- Who runs it
- The accounts receivable clerk, each Monday, from that morning’s aging report.
- AI prepares
- A draft follow-up for each overdue invoice and a list of the invoices it held, with the reason for each.
- People decide
- The controller approves which follow-ups go and which are held. The clerk sends them. Nothing is sent, credited or written off by the workflow.
- Not in this Rock
- Posting payments, payment plans, credit holds and anything sent to a collections agency.
- Reported
- On track or off track at every weekly leadership meeting, against the milestones below.
Agreed at the quarterly session, December 2026. The quarter runs 4 January to 26 March.
Six milestones the weekly meeting can call.
Each milestone ends in something a person can open and read. That is what lets the controller answer “on track” in five seconds and mean it.
Illustrative example with invented data. The milestones for the quarter, complete.
| Due | Milestone | Done means | Who |
|---|---|---|---|
| 15 January | Baseline recorded | Four weeks of past aging reports measured: time from report to follow-ups sent, hands-on effort, review time, follow-ups corrected or missed | Clerk records; controller accepts |
| 29 January | Method captured, test set approved | The clerk’s steps, the tone for each age band and the hold rules in writing; a test set of real past invoices, awkward ones included | Clerk and controller |
| 12 February | Acceptance test passed | Every test case run and recorded; the controller signs the pass rule | Controller |
| 26 February | Ready for weekly use | A one-page job aid written and walked through; from Monday 1 March the clerk runs it on the live report and the controller reviews every draft | Clerk |
| 19 March | Measures retaken | The January measures taken again, the same way, on three live weeks; the hold list and the clerk’s notes read | Clerk records; controller accepts |
| 26 March | Decision recorded | Expand, adjust or stop, with the evidence, in the quarterly session’s record | Controller proposes; leadership team decides |
Three pieces show each milestone in full: the baseline worksheet, the test set and the rollout checklist.
The week it goes off track.
On 12 February the controller reports off track. Two test cases failed the same way: the workflow drafted a firm reminder for an invoice the customer was disputing, because a technician had been called back to the site and the repair was still open. The clerk would never have sent it. The rule lived in her head.
The meeting treats it as an issue and solves it in ten minutes. Operations will send finance the open-callback list each Monday. Any invoice on it is held for the controller with the reason shown, and the test set gains three callback cases. The retest passes on 19 February, the job aid is ready on the 26th as planned, and the Rock is back on track.
This is the pilot doing its job. A rule one person carried is now written down, tested and owned, before a single customer saw the miss.
The review decision.
The quarter ends with a decision the whole leadership team hears. The owner brings the record; the team decides.
Illustrative example with invented data. The decision recorded at the quarterly session.
Review decision: overdue-invoice follow-up preparation
- Evidence read
- The signed acceptance-test record, including the callback retest. Four live weeks of drafts and held invoices. The January measures retaken on 19 March.
- Decision
- Expand, with one case kept manual.
- Reason
- Run every Monday since 1 March. Each week’s follow-ups were ready for approval by Tuesday noon. Disputed invoices reached the controller with their reason. The controller judges the change in elapsed time and corrections worth keeping.
- Kept manual
- Customers on a payment plan stay with the controller until a rule for them passes its own test.
- After the Rock
- The controller owns the capability and reviews it each quarter. The clerk logs every draft she rewrites.
- Next quarter’s Rock
- Weekly receivables summary, same seat, so the weekly meeting opens with cash on one page.
The Rock is done. Had the evidence said adjust or stop, it would be done as well, with the gap or the reason in writing.
The capability now belongs on the company’s capability overlay under the finance seat. Who owns an AI capability after the pilot? sets out the standing job that keeps it good.
Write yours for next quarter.
Pick one seat, one piece of weekly work and one owner, and write the Rock before your next quarterly session. We bring the method and the capability template, tested on your own cases. It runs in the ChatGPT, Claude, Copilot or Gemini your team already uses. Your platforms, your pace, your people, and your organization keeps control of how the work gets done.
EOS, Rocks and the Accountability Chart are EOS Worldwide’s terms. This write-up is Fully Powered AI’s own working layout for teams that run on EOS, and it is independent of EOS Worldwide.
Bring the seat whose result matters most next quarter and the weekly work you would pilot first.