A Fort Worth wealth and tax practice runs its whole book on Salesforce. Intake to invoice, one system.

Two businesses, one client base

The firm is really two businesses sharing one book: a wealth advisory arm with compliance obligations and money in motion, and a tax practice with brutal seasonal peaks. Every piece of work became a typed Salesforce case - cashiering, onboarding, tax return, payroll setup, missing documents - routed automatically to the right queue, with the fields, visibility, and automation each side needs.

Cashiering without the back-and-forth

Money movement is where advisory work gets risky, so it got the strictest treatment. Contribution and distribution requests are typed cases where state and federal tax-withholding fields are required before the case can proceed, Financial Account flows keep the account number synced onto every case automatically, and statement-family requests route straight to operations. Sensitive fields are visible only to executive and financial-management roles, enforced by the platform rather than by trust.

Planning engagements, signed and billed from the record

Financial planning got the same end-to-end treatment: the firm's planning services disclosure documents, in single and joint versions, route for signature through Titan, and the billing formulas live on the engagement itself - flat planning fees for new plans, planning fee by hours for updates, hourly rates for wealth research and consulting. An advisor opens the case, the right disclosure goes out, and the right amount gets billed, with nothing recomputed by hand.

Tax season, absorbed by the same system

The tax side runs on the identical pattern. The 1040 and S-Corp organizers are custom LWC forms on public links, joined by the AICPA form and 1041 engagement letters: answers write straight onto Salesforce records, a generated PDF files itself into the client's Box folder, and signatures route through Titan. Routing respects IRS Section 7216 consent, so clients who have signed route to one staff group and everyone else to a restricted operations team, enforced on every single case. An Experience Cloud portal adds secure uploads, a self-service FAQ, and a video library whose premium tier is unlocked through the same Stripe rails as billing.

Billing where the work happens

A Send Invoice button on the case reads the engagement's own rate fields - planning fees, hourly rates by role, flat annual fees - computes the amount, offers invoice or immediate charge, finalizes it in Stripe, and emails the client, logged back on the case. Recurring engagements run on Stripe subscription schedules, and a webhook listener keeps customers and payment methods in sync both ways. The Apex behind it ships at 85-100% test coverage; the full pattern is in Stripe + Salesforce: The Integration Done Properly and our Stripe playbook.

The unglamorous half: clean migration

None of it matters if the system starts empty. The long haul of the engagement went into migrating and cleaning the book: accounts, contacts, task history, opportunity contact roles, deduplication, owner reassignment, and rate fields backfilled across every client. It is the unglamorous half of a platform build, and the half that decides whether a team trusts the system on day one. The engagement is ongoing: the core routing flow is past its eightieth version, which is what keeping pace with a real practice looks like.