Your new client onboarding page should behave like an operations workflow, not a marketing page. In about 60 seconds, it should sort a new client into the right onboarding lane, set expectations, collect the minimum viable intake packet, and trigger an internal handoff so your team is not chasing basics by email.
This is for managing partners and operations minded managers at CPA firms serving owner managed businesses, especially when you have limited admin capacity and multiple service lines that start differently (tax, bookkeeping, advisory, payroll coordination, cleanup).
What the onboarding page must accomplish in one minute
When a new client lands on this page, you want three things to happen quickly and predictably.
- Route: The client chooses an onboarding lane (3 to 5 lanes) so your staff knows what “done” means for this start.
- Set expectations: The page states what happens next, who does what, and what you will not do until the minimum packet is complete.
- Collect the minimum viable packet: You gather only the fields and documents needed to schedule the kickoff and begin work, with role based requests that change by lane.
If your page tries to explain everything about your firm, it will fail at its real job: producing a complete, standardized start.
The seven sections that make the page run like a workflow
Keep the page scannable. Each section should answer one operational question.
1) Who this onboarding is for (and not for). Define “new client” for this page. For example, “You have signed an engagement or have been asked to begin onboarding.” If you also accept prospects here, separate that to a different page.
2) Choose your onboarding lane. Present 3 to 5 lanes with plain language labels. Each lane should map to a different readiness checklist and document matrix (below). If a client cannot tell, give one “Not sure” option that routes to a human review queue.
3) What happens next. In 4 to 6 bullets, state the sequence after submission. Include your acknowledgment timing, how you schedule kickoff, and what triggers “work starts.”
4) Readiness checklist (per lane). Publish what the client must have ready before they start the form. This reduces partial submissions and sets a standard your staff can enforce.
5) Intake form (minimum viable fields, with conditional logic). The form should ask for stable facts first, then show conditional questions only if they change the work (for example, multi entity, multiple states, cash versus accrual, prior year cleanup).
6) Document handoff instructions. Give one primary method for document transfer, plus one fallback. State file naming rules and what to do with “too large” files. If you use a portal, link to it here, but keep the onboarding page as the hub that explains what goes where.
7) Timelines, responsibilities, and escalation. List what your team will do, what the client must do, and who to contact if something is stuck. This is where you prevent repeated “checking in” emails.
New Client Onboarding Page Blueprint for CPA Firms
Use this blueprint as your build spec. It includes a lane map, page sections, minimum viable intake fields, a document request matrix, and a 24 hour internal routing SOP.
Lane map (choose 3 to 5)
- Business tax and bookkeeping: Ongoing books plus business return support.
- Individual tax: Personal return only, with possible K 1s and investment reporting.
- Advisory and CFO: Ongoing advisory cadence, forecasting, KPI reviews, decision support.
- Payroll coordination: Oversight and coordination with a payroll provider, or payroll cleanup and setup.
- Cleanup project: Historical catch up, reconciliations, prior period fixes, or books to tax ready.
Page section checklist (what to publish)
- Eligibility statement: “Use this page after engagement is approved” plus one sentence on what to do if they are not yet approved.
- Lane chooser: 3 to 5 lanes, each with a one sentence definition and a “what you will need” link that jumps to the readiness checklist.
- What happens next: Acknowledgment, internal review, kickoff scheduling, access setup, start date trigger.
- Readiness checklist: Per lane, list the items the client should gather before completing the form.
- Intake form: Minimum viable fields plus conditional fields.
- Document handoff: Primary transfer method, fallback method, file naming convention, and what not to send in free text.
- Responsibilities and escalation: Client tasks, firm tasks, and a single escalation contact path for onboarding issues.
Minimum viable intake fields (with conditional fields)
These fields are designed to be enough to route, schedule, and request the right documents, without turning onboarding into a long interview.
| Field group | Minimum viable fields | Show only if |
|---|---|---|
| Client identity and contacts | Legal name, preferred name, primary contact name, role, email, phone, billing contact (if different) | Add additional stakeholders if they need to attend kickoff or approve deliverables |
| Entity and scope | Entity type, tax year end, services requested (choose from your lanes), prior preparer or bookkeeper name (optional), states involved (free text allowed but prompt with “list them”) | Ask for additional entities only if “multiple entities” is selected |
| Work timing | Reason for onboarding now, next filing or reporting deadlines the client is aware of, preferred kickoff window | Escalation flag if “urgent” is selected, route to a specific owner |
| Systems and access | Accounting system used, banks and credit cards count (placeholder only, no numbers required), payroll provider (if any), bill pay tool (if any) | Request system admin contact only if access must be granted by someone else |
| Communication preferences | Preferred channel (email or phone), meeting availability notes, who should be copied on onboarding updates | Ask for cadence preferences only for advisory and CFO lane |
| Engagement logistics | Engagement signed (yes or no), invoicing preference (email invoice, portal, other), purchase order requirements (yes or no) | If “PO required,” ask for the client’s internal process owner |
Document request matrix (role based by lane)
Publish this as a “you will be asked for” list, then mirror it behind the form with conditional document prompts. Keep it focused on onboarding, not the entire year.
- Business tax and bookkeeping: Prior year business return and supporting workpapers the client has, current year YTD financials (if available), chart of accounts export (if available), bank and credit card statements access method, list of owners and ownership percentages, prior year depreciation or fixed asset detail (if applicable), sales tax filing states and frequency (if applicable).
- Individual tax: Prior year personal return, identity and filing information needed for organizers, list of entities that issue K 1s, brokerage and retirement statement access method, list of major life changes relevant to filing (client provided summary).
- Advisory and CFO: Current YTD financials, prior year financials, existing budget or forecast (if any), list of decision makers and meeting attendees, current reporting package (if any), top three questions they want answered in the first 60 days (client provided summary).
- Payroll coordination: Payroll provider name and primary contact, payroll access method, current quarter payroll reports available, list of states where employees work, benefits and deductions list (if applicable), any notices that require response (client provided files).
- Cleanup project: Time period to clean up, what “done” means (tax ready, lender ready, monthly close), list of known issues (client summary), bank and credit card access method, prior bookkeeper files or exports (if available), any deadlines driving the cleanup.
24 hour internal routing SOP (so staff stops re asking)
This is the internal spec that makes the page effective. Keep it short enough that someone can follow it during a busy week.
- Submission capture: Every onboarding submission creates one record in your system of record (CRM, ticketing, or practice system). The record must include lane, entity type, primary contact, and urgency flag.
- Ownership assignment: Assign an onboarding owner (a person, not a team) within the same business day. If the owner is out, route to a named backup.
- Tagging: Apply standardized tags: Lane, Service start month, Urgency, Missing packet, Ready for kickoff, Access pending.
- Packet check: The owner checks the submission against the readiness checklist for that lane. If incomplete, send one consolidated request that lists missing items, not multiple emails.
- Acknowledgment: Send a short acknowledgment that confirms lane, repeats the next step, and states what you need before kickoff can be scheduled.
- Kickoff scheduling rule: Schedule kickoff only after the minimum packet is complete, except for a defined exception path (for example, urgent notice response).
- First meeting agenda: Confirm scope and deadlines, confirm systems and access owners, confirm document sources, agree on communication and turnaround expectations, confirm “definition of done” for the first deliverable.
New client onboarding page failure modes to plan around
Sensitive data in open text fields. Do not invite clients to paste account numbers, IDs, or other sensitive data into free text boxes. Use controlled upload prompts and clear instructions on what is acceptable through your chosen transfer method.
Overpromising timelines. Avoid publishing turnaround times you cannot control. Instead, publish what triggers each step (for example, “kickoff is scheduled after the minimum packet is complete”).
One form that tries to cover every edge case. If you keep adding fields for unusual situations, completion rates drop and staff still has to clarify. Keep the base form minimal, then use lane based conditional prompts and a “notes for our team” field with guardrails (for example, “do not include sensitive information”).
Too many lanes. More than five lanes usually creates confusion and routing errors. If you have a niche service, consider making it a conditional option within an existing lane rather than a new lane.
A 45 minute teardown you can do with your last 10 starts
Pull the last 10 new client starts and do a quick review against the blueprint.
- List missing basics: For each start, write the first three things your staff had to chase (documents, access, decision maker, deadlines).
- Map each chase item: Decide whether it belongs in a readiness checklist, a minimum intake field, or a lane specific document prompt.
- Pick your top five fixes: Choose the five changes that would have prevented the most follow up emails, then rewrite your onboarding page to enforce them.
If you want help implementing this as a fast hub page with conditional intake logic and clean internal routing, Greenwich Web can build it as a small upgrade within Web Design & Development.
