Worked example · new-client setup and document collection
One form opens the file. The chasing happens by itself.
Lakeside Bookkeeping is a made-up accounting practice. When a client signs up, the software builds the document checklist from the service chosen, gives the client a page to send things in, reminds them on day 3, 7 and 14, and stops the moment the file is complete.
This is an example, not client work. The firm and its clients are made up. You have your own private copy, so click anything. Emails are shown in the activity log, not sent. The example's clock reads Monday, October 5; jump it ahead to watch reminders go out.
What the client sees · Ridge Road Landscaping
Documents Lakeside Bookkeeping needs from you
0 of 6 received. Send each one when you have it; this list updates on its own.
- Prior year tax return
- Year-end profit and loss
- Year-end balance sheet
- 1099s issued and received
- Fixed asset purchases list
- Owner's estimated tax payments
In a real build this page accepts the files themselves. The example takes a file name so nothing is stored.
How this would work in your business
- The checklist is a rule, not a memory. Each service has its own list. Change the list once and every new client gets the new version.
- The client has one place to look. No hunting through email for what they still owe. In a real build the page takes the files and keeps them in your own storage.
- Reminders stop on their own. Nobody has to remember to stop chasing, and nobody gets chased for something they already sent.
- A person takes over at the right moment. After the last reminder, or when the file is complete, the software hands it to a person and says why.
Built from the same parts as the client intake system I run for a financial planning firm, where the questionnaire is filled in from a meeting transcript and the client confirms it.