Run your first real job

The most useful thing you can do after setup is take one real client through one real piece of work, end to end, including the part they see.

Not a test client. A real one, with real documents and a real deadline. Test data never surfaces the problems.

Why before templates

Templates, automations, and recurring schedules encode your process. Building them before you've run the process once means encoding a guess.

Firms that run one job first and then build templates get templates that match reality. Firms that build first spend the following month editing them.

The run

1. Pick the client and start the work. Create the job or task the way you would normally. Note anything you had to work around.

2. Request what you need from them. Send a real document request and watch what arrives. This is where wording problems show up — a request that's obvious to you is routinely ambiguous to the person reading it.

3. Move it through your statuses. Every stage, in order. If you find yourself wanting a stage that doesn't exist, or skipping one that does, your pipeline needs adjusting. Better to learn that now.

4. Look at it from their side. Use the portal preview. Check that the client-facing status labels say something a client would understand, and that nothing internal is showing.

5. Finish it. Signature, invoice, payment — whichever apply. All the way to done.

6. Then fix what annoyed you. Statuses, client labels, request wording, who gets notified.

What this usually surfaces

• A missing status, most often a review stage or a waiting-on-client stage.
• A status role set wrong, which is why the reminder action didn't appear where you expected.
• Client-facing labels that read as internal shorthand.
• A document request that assumed knowledge the client doesn't have.
• Nobody assigned, or everyone assigned.

None of these are hard to fix. All of them are much harder to fix after they've been copied into fifteen templates.

Then scale it

Once one job has gone through cleanly:

• Turn it into a template, so the next one starts complete.
• Put anything periodic on a recurring schedule.
• Add automations for the handoffs people currently remember by hand.

That order — run it, then template it, then automate it — is the one that works.