Forty minutes, no slides.
We open the back office and work in it. If you would rather see a deck, we are probably not the right fit — and you will find out in the first ten minutes either way, which is the point.
The demo is the software.
We import a chart of accounts
Yours if you send it ahead, ours if you would rather watch first. Stage, validate, commit — including what the validation report says when something is wrong.
We run a dues preview
Four hundred charges before they are four hundred immutable entries, with every membership listed — including the ones not being billed, and why.
We post a charge and settle a payment
Watch the receivable move, the merchant fee land as an expense, and the allocation run FIFO against open items.
We try to break it
Edit a posted entry. Delete one. Post an unbalanced journal. The database refuses, and you see the refusal rather than a claim about it.
We show you the trial balance
Still in balance, with the subledger tied to its control account, after everything above.
Request a walkthrough
Prefer email? [email protected]
Two, ideally.
Your controller
They are the person who will find the problem, and we would rather they found it on the call. Ask them to bring a real statement and the four questions their current system cannot answer.
Your general manager
Because half of what matters here is what the membership experiences, and that is not a judgement a controller should have to make alone.
Before you book, read the roadmap. The financial backbone ships today and most of the suite does not. If your club needs a tee sheet or a working terminal this season, a walkthrough will be an enjoyable forty minutes that ends in a no — and we would both rather have that time back. Where we actually are