Home / Demos / Client onboarding portal

Watch onboarding chase itself.

The week after someone says yes is where small businesses lose the most goodwill. Forms bounce back and forth over email, one document never arrives, and the kickoff call quietly slips two weeks. Play the new client, walk the four steps, and watch the owner's side of the screen keep score as you go. Skip a document on purpose and see exactly what the owner gets.

Demo

Live demo. Fictional firm, fictional client, simulated data. Nothing is uploaded, sent, or stored. There is no file picker, no storage bucket, no calendar, and no mail server. The attach buttons create fake file chips. Every name, address, and time slot below is invented, and all of it runs in your own browser and disappears when you close the tab.

Quarry Lane Bookkeeping Fictional firm · demo only
You are the new client Step 1 of 4

Welcome to Quarry Lane.

Five questions, then a short list of documents. You are playing Avery Nunez of Cedarpost Landscaping, a fictional client. The answers are prefilled so you can move fast, and you can change any of them.

Nothing leaves your browser. The owner's console on the right updates the moment you save.

What the owner sees Live
Cedarpost Landscaping Not started 0%

    Nadia Prewitt, the fictional owner of Quarry Lane, sees this board for every client at once. In this demo it holds one.

    Drafted for the owner Never auto sent
    Draft Waiting on the client
    ToAvery Nunez
    SubjectWelcome to Quarry Lane
    TriggerPortal opened, no steps completed yet

    Progress notifications are drafted for the owner to send. Nothing sends on its own. Every nudge, reminder, and confirmation waits in a review queue with the client's status attached. A person decides whether today is the day to chase a document.

    The wording of each draft is written into this page ahead of time. In a real build the copy comes from your own templates and your own voice, and it lands in the same review queue.

    Activity log Simulated clock

    Nothing has happened yet. Every action on the left writes a line here.

    Timestamps are simulated and start at 9:02am. A real build stamps wall clock time, which is what makes a disagreement about who was waiting on whom a five second lookup.

    What this would do in production

    The demo is the honest half of it.

    Everything above is the status layer, running where you can see it. A real build keeps the same one shared board and wires it to storage, e-signature, your calendar, and the tools you already pay for.

    Real document intake

    Actual uploads into storage you control, with file type and size checks, virus scanning, and a link that expires. The client never emails a bank statement to a shared inbox again.

    Nudges on a schedule

    Day three, day seven, day ten, escalating in tone. Each one is drafted and queued, and the owner approves the batch in one pass rather than remembering who owes what.

    Signature where it belongs

    The engagement letter goes out through the e-sign tool you already use, and the signed copy files itself against the client record with the date on it.

    Your actual calendar

    Kickoff slots come from live availability, hold the time when the client picks one, and send the invite. No double bookings and no back and forth about Thursday.

    One status both sides trust

    The client sees the same percentage and the same outstanding list the owner sees. Most onboarding friction is two people holding different versions of the truth.

    A handoff that actually happens

    When the last item lands, the file moves from onboarding to the work itself, with the intake answers already on the record instead of in somebody's memory.

    Losing the first week with new clients?

    Onboarding is one example. The same approach works on intake, document chasing, scheduling, and every handoff where both sides are waiting on each other and nobody says so.