Where client intake starts
A full book of tax and bookkeeping clients is not an organized intake desk. Many firms already use practice software, shared drives, and email—then still chase a missing W-9 in one thread, bank statements in another, and a signed engagement letter with whoever answered the phone. The form is not the workflow. The workflow is the path from the first inquiry to a complete document set and scheduled follow-up.
This map is for accounting firms, tax preparers, and bookkeeping teams that share client intake across forms, email, portals, and phone. A new marketing site alone does not stop a missing statement from delaying a return. TwoQM develops custom software, portals, CRM workflows, automation, and connected systems when your current tools do not hand the work to the right person. Hosting and email can sit beside that work. They are not the whole job.
Here is an original example, not a TwoQM client and not a measured result. A four-person tax firm gets a Friday-afternoon website form from a new LLC owner who needs quarterly estimates and “whatever documents you usually need.” The partner sees it Monday. Over the weekend the same owner emailed last year’s return to a staff accountant’s personal inbox, texted a W-9 photo to the office line, and left a voicemail asking whether statements can wait until after payroll. Three channels, three partial packets, one flustered callback.
The same request may start on an intake form, in a Google Business Profile message, on the front-desk phone, in a partner’s personal email, or as a reply-all with unlabeled PDFs.
Ordinary practice tools cover a large share when they point at one place the team opens. Many firms use a client portal so clients upload files instead of emailing attachments. Public product pages describe portals where clients send documents into a shared workspace—for example, Karbon’s overview of client portals (https://karbonhq.com/resources/client-portal/). The IRS page about Form W-9 (https://www.irs.gov/forms-pubs/about-form-w-9) is the ordinary public reference for that early taxpayer-identification request. Those tools do not merge a texted photo with the website lead or tell a junior associate which missing items they may chase without a partner.
Write the staff path first
One intake shape. Every new client collects the same facts: entity type, services requested, tax year, preferred contact, and whether documents arrive through the portal. A form can require some of that. An email cannot, unless someone copies it into the shared record the same day.
One owner for unscheduled channels. Name who checks the form inbox, Google messages, after-hours voicemail, and partner forwards—and by what time. “Whoever is free” means Friday waits until Tuesday.
A document checklist both sides see. List what is still missing: W-9, bank statements for named months, prior-year return, payroll reports, engagement letter. If the list lives in one person’s head, the chase restarts every week.
Portal first, email as the exception. Prefer a portal or secure upload so files land on the shared record. Email attachments are fine when someone files them into that record and marks the checklist the same day.
Statuses the office will use. New inquiry, waiting on documents, documents incomplete, ready for work, questions for client, scheduled follow-up.
One follow-up owner. After a missing-item notice goes out, name who follows up—and when. Two people chasing the same W-9 is as bad as nobody chasing it.
Automation, then a draft a person sends
Use ordinary automation when the answer is already in the record: a confirmation that the intake arrived, a reminder that named documents are still missing, and an alert when a checklist sits untouched past your deadline. Those steps should not wait on a language model, and they should not invent a filing deadline.
AI fits when the message is messy and a person still decides. A note like “I have most of it, bank stuff is on my other email, can you start without the W-9” can become a short brief: services requested, what is present, what is missing, and whether the portal link was sent. A draft reply can restate your published document list and ask for one clean upload. It must not invent a due date, promise a refund estimate, or send itself. AI and automation (https://twoqmllc.com/ai-automation) at TwoQM starts with the task, the information it may use, and who reviews the result.
A CRM workflow (https://twoqmllc.com/crm) helps when stages—new intake, waiting on documents, ready for work—need a clear owner. If your practice or portal tool already holds the client record the team opens, connect that system (https://twoqmllc.com/connected-systems) instead of starting a second database.
When a custom piece is justified
Custom software fits when the same handoff breaks every week and no portal setting fixes it: bilingual intake, document sets that must stay with one client ID, staff who must not see one another’s open clients, or an intake that must land on one board with the original channel preserved. Agree on permissions—and on what happens if a vendor connection fails—before anyone builds it.
Software and websites for accounting and tax firms (https://twoqmllc.com/industries/accounting-tax) are planned around intake, document collection, client portals, and how an inquiry meets the work queue—alongside other professional services (https://twoqmllc.com/industries/professional-services) workflows. That is not a generic template, and it is not “you need a website” as the fix for missing statements. If the site hides the intake path, fix the path. If the office still loses documents and follow-ups, fix the workflow.
Describe a workflow
Write down the path you are losing: Friday forms without documents, W-9s in text threads, or checklists nobody updates. Describe that workflow (https://twoqmllc.com/business-automation) to TwoQM. We are based in Brownsville, Texas, and we deliver nationwide, in English and Spanish. We will say whether your current portal, a connection between tools, or a small custom piece fits—and what it will not do. An inquiry is not a quote, and it is not a claim that a system is already built.