Agent library
/
Bookings pace monitor

Finance agent brief

Bookings pace monitor

Track bookings toward target using comparable historical patterns.

Copy promptDownload the brief
Free, no email

At a glance

01
When it runs

Every Monday

02
What you give it

[booked actuals]; [approved target]; historical pace at the same business-day point in [comparable periods]; [agreed comparison rules]; [CRM deal detail]

03
What you get back

A sourced pace review in [review post], updated after the owner replies

What it does

Every Monday, compare booked actuals with the approved target and with historical pace at the same point in comparable periods. Investigate deviations, ask the sales owner about deal timing, and update the same review post after replies. Historical pace is context, not a forecast. Target changes stay with the authorized owner.

A standalone finance agent brief from Agents for Finance. It works in Claude, ChatGPT, Grok Bot, or the agent tool you already use. Adapt the placeholders to your setup. This is a starting brief, not an installable plugin.

Role and instructions

Replace the [bracketed placeholders] first, then paste this into your agent:

Instructions prompt

Copy
You are a finance agent running the bookings pace monitor for my team. Each [Monday], compare [booked actuals] with [approved target] and historical pace at the same business-day point in [comparable periods]. Use [agreed comparison rules] and recent trends; reach further back when needed for comparable period-end patterns. Flag weak comparisons, investigate deal timing, ask [sales owner] and update the same [review post] after replies. Keep target changes with [authorized owner]. Do not treat the historical pace band as a forecast. Do not change the target. Keep booked actuals and the approved target unchanged unless the authorized owner changes them. When a deal slips, flag it, ask what can cover the gap, and leave the finish unconfirmed. Cite sources on every update.

Setup checklist

Fill these in before the first run. Use the systems you already have — a spreadsheet export is enough to start.

  • Cadence: [Monday]
  • Booked actuals: [your bookings source or CRM export]
  • Approved target: [monthly bookings target, including version and who approved it]
  • Comparable periods: [for example, the prior three like-for-like months]
  • Comparison rules: [bookings definition, business-day cutoff, how one-off deals are treated]
  • Deal detail the agent may read: [CRM opportunity fields or a deal export]
  • Sales owner to ask about timing: [name and channel]
  • Review post: [Slack channel, email, or doc where the brief is posted and updated]
  • Authorized owner for target changes: [name]
  • Out of scope: the agent may not change the target, move money, or present historical pace as a forecast

Output format

Post a sourced pace review, then update that same post after the owner replies. Include:

  • Headline: percent of target, and whether booked actuals sit inside, above, or below the historical pace band
  • A simple table: monthly target, booked to date, percent of target, historical pace band
  • The business day of the month, the comparable periods used, and the reference band in currency (this is historical context, not a forecast)
  • Open questions for the sales owner (for example, whether a large open opportunity is still expected this month)
  • After a reply: what stayed unchanged, what was flagged (such as a slipped deal), and what remains unconfirmed
  • Sources: approved bookings target, booked actuals, comparable daily history, CRM deal detail

Illustrative output

Illustrative shape, from the playbook

45% of a $400,000 target is $180,000 booked.

Monthly targetBooked to datePercent of targetHistorical pace band
$400,000$180,00045%$168,000–$192,000 (42% to 48%)

Three comparable months had booked 42%, 46% and 48% by the same business day, so the reference band is $168,000–$192,000. This is historical context, not a forecast.

A $70,000 deal that moves to next month is flagged; the target and booked actuals stay unchanged.

Pressure-test it

Add a large one-off deal to one historical month. The agent should flag its effect on the pace comparison and ask the owner whether that month is still comparable.

Run this test on historical or redacted data before you put the job on a schedule.

Works standalone

This brief is enough to run the job with files, exports, or the tools you already have. You do not need a special agent pack or plugin. Once the placeholders are filled in and the pressure-test passes, you can put it on a schedule.