What we generate
The documents that run your club. Generated for you.
Your exports go in. The numbers get reconciled, the narrative gets drafted, and everything waits at an approval gate. Here is the system assembling a real club document: it shows its work, and nothing leaves without your say-so.
Home / Workbench / Tournament quote
DraftingAction · /quote
Generate a tournament quote
From the tee sheet · corporate tournament · 24 players
Ace asking
I pulled the tournament. Before I draft, should this go out as a one-page sign-off, or the full packet?
A · choice
One-page sign-off
Line items, terms, e-sign block. Fast to approve.
B · choice
Full proposal packet
Scope, schedule, references, legal annex.
C · choice
Recommend one
I'll read the deal and the organizer, then pick.
Outbound actions require your approval
Sound familiar?
We built this from inside the golf club.
Not a feature list. The recurring documents that eat your team's month. Each one is a package the system generates for you.
“The board package is a week of stitching exports together by hand, every single month.”
“The QBR is a fire drill nobody has time for until it's already due.”
“Variance to budget gets explained from memory in the meeting, not from the numbers.”
“Membership numbers live in three systems and never quite agree.”
“Every committee wants the same data in its own format.”
“The GM's report gets written at 11pm the night before the meeting.”
How a document gets made
Every document, assembled the same way. On the record.
This is a system you implement, not a subscription you hope someone uses. It moves through every package the same way, and you hold the gate on anything that leaves the building.
Read the request
intent + context
Pull the data
tee sheet · CRM
- 3
Draft the work
in your club's voice
- 4
Your approval
gate on outbound
- 5
Send + log
on the record
Auditable by default
Every figure ties back to a source export, and every run is logged. You can see exactly what was used, when, and why.
Built around your stack
We read the exports your systems already produce. No rip-and-replace.
You only build what fits
The audit sets the order. Start with one document, add more when it earns its place.
■ Inspector · tournament-0418
Tournament quote: runtime trace
7 events · 2 sources · 3 tool calls
- 09:14:02
You Asked: "draft a quote for the corporate tournament"
- 09:14:04
Ace Asked one question: one-pager or full packet?
- 09:14:11
You Picked A · one-page sign-off
- 09:14:12
Ace northstar.teesheet.fetch
tournament-0418 · 1.2s · ok
- 09:14:14
Ace member.lookup
organizer · 0.8s · ok
- 09:14:18
Ace Drafted the quote
6 line items
- 09:14:21
Ace Awaiting your approval to send
outbound
Nothing goes out the door until you say so. Every action above is logged immutably.
What we generate
The documents that run your club.
Grouped by how often they come due. Each one is assembled from your exports and held for your approval before it ships.
The recurring monthly stack: the board package and the reports around it.
Monthly Board Package
Assembles the full board package: reconciled financials, the variance narrative, KPIs, and committee updates, ready for your approval before it goes out.
From your P&L, balance, membership, and tee-sheet exports.
GM / Executive Report
Drafts the GM's report for you: what happened, what it means, and what needs a decision this month.
From department updates and financials.
Financial Variance Narrative
Writes the plain-English explanation of actual vs budget, line by line, every figure tied back to source.
From your actual-vs-budget P&L exports.
Membership Report
Joins, resignations, waitlist, dues aging, and retention signals in one read.
From your membership system and dues exports.
Ops / Department Report
Golf, F&B, and grounds activity reconciled into one operating snapshot.
From tee-sheet, POS, and work-order exports.
The quarter, rolled up board-ready.
Quarterly Business Review
Rolls the quarter into a board-ready review: trends, variance to budget, and the story behind the numbers.
From your quarterly financials and operating data.
Always-on drafting in your club's voice, gated on your approval.
Member Communications
Drafts member updates and follow-up in your club's voice. Nothing sends without your approval.
From your CRM and member activity.
Committee and one-off packets, from the same reconciled data.
Committee & Finance Reports
Finance, golf, house, and greens committee packets, each in its own format, from the same reconciled data.
From committee data and financials.
Why not just use ChatGPT?
A fair question. Here's the honest answer.
| AceCall | ChatGPT | Claude | openclaw | |
|---|---|---|---|---|
| Knows your club's operations | if you build it | |||
| Connects to your club systems | DIY | |||
| Does the work (drafts, books, routes) | chats | chats | DIY | |
| Approval gate before anything sends | DIY | |||
| Auditable trail of every action | DIY | |||
| Golf-specific, out of the box | ||||
| Who builds and runs it | done for you | you do | you do | you self-host |
ChatGPT and Claude are excellent general assistants. We use them under the hood. The difference is that a club doesn't want to operate a chatbot: it wants the work done, wired into the systems it already runs, with a record of everything. openclaw is the powerful do-it-yourself path if you have an engineer and the time. AceCall is the done-for-you version, built for golf.
Built around your course. Not ours.
Not sure which document to start with? That is what the audit is for. Ten minutes, and you will know.