Automating the Salesforce + Tamarac + DocuSign stack at an RIA
For operations leaders at established RIAs with a trading desk on Tamarac and a CRM on Salesforce: seven workflows that hand work between service, trading and billing, what the native integration covers, and what is left.
On a Salesforce + Tamarac + DocuSign stack, the native Tamarac integration is strong on data: it syncs clients, households and financial accounts in both directions and gives single sign-on into Tamarac. What it does not carry is the request itself: the client's distribution, the new risk profile, the fee change or the termination letter that has to become paperwork, a trading task and a billing update, in that order.
This stack usually belongs to a firm with a real trading and rebalancing desk, so the costly handoffs run from service to trading and from service to billing. Below are seven workflows that cross the three tools, each with a trigger, the steps and what a person still reviews.
Who runs this stack
This is the stack of an established RIA, often multi-office, that manages portfolios in house. Envestnet | Tamarac covers rebalancing and trading, performance reporting and billing. Salesforce, often Financial Services Cloud, is the CRM of record. DocuSign carries the paperwork: custodian forms, advisory agreement amendments, investment policy statements.
The operations org has separate teams for service, trading and billing, and the friction lives between them. A client request starts with a service associate, needs a form signed, becomes a trade or a billing change, and has to be closed back in the CRM. Each handoff is a message, a spreadsheet or a task someone has to remember to create.
| Layer | Typical choice |
|---|---|
| CRM | Salesforce, often Financial Services Cloud |
| Rebalancing, reporting, billing | Envestnet | Tamarac |
| Signature | DocuSign, usually sent from Salesforce |
| Documents | SharePoint or Box |
| Ops shape | Separate service, trading and billing teams |
| Collaboration | Often Microsoft Teams between desks |
The pressure on this stack is handoffs between teams. The data sync is good, so the gaps are not about who a household is; they are about a request moving from service to trading to billing without being dropped or delayed. The workflows below are built around those handoffs, with the trade and the bill always left to the desk that owns them.
The workflows that cross Salesforce + Tamarac + DocuSign
Each workflow below lists what starts it, the steps across tools, and what a person still reviews. The steps are what Caddi runs when a firm automates it; the review is what stays with your team.
Distribution request to the trading desk
Trigger: A service case for a distribution is opened in Salesforce.
- Fill the custodian's distribution form for the account from Salesforce and send it through DocuSign.
- When it completes, file it to the case and open a task for the trading desk to raise cash, with the amount and date.
- Post the request in the trading desk's Teams channel if that is how your desks work.
- Watch for the transaction in Tamarac and close the case with a note when it appears.
What a person still does: The service associate verifies the request with the client under your procedures, and the trader decides and places any trade.
New accounts without a model
Trigger: A daily check of new accounts in Tamarac.
- List new accounts with no model or rebalancing assignment.
- Look up the intended model on the Salesforce record or signed investment policy statement.
- Open a task for the trading desk with the account, the intended model and the source document.
What a person still does: The trading desk assigns the model.
Risk profile or model change paperwork
Trigger: An advisor updates a client's risk profile or target model in Salesforce.
- Fill the updated investment policy statement or model selection form from the Salesforce record.
- Send it through DocuSign.
- When signed, file it and open a task for trading with the old and new model.
What a person still does: The advisor and compliance review the change under your firm's process before it goes to the client, and trading makes the change in Tamarac.
Fee schedule change
Trigger: A fee change is approved on the Salesforce household.
- Fill the fee amendment to the advisory agreement and send it through DocuSign.
- When signed, file it and prepare the Tamarac billing change for the billing team, with the effective date.
- On the next billing preview, check that the new schedule is applied and flag the household if not.
What a person still does: The billing team makes and approves the Tamarac change.
Account termination
Trigger: A termination letter or transfer-out notice arrives.
- Log it on the Salesforce household and open a case.
- Open the tasks your termination checklist requires: final bill under the agreement's terms, remove from rebalancing, close the Salesforce financial accounts after the custodian confirms.
- File the letter and every confirmation to the household.
What a person still does: Billing decides the final fee, trading removes the account, and compliance reviews the file under your procedures.
Address and household changes
Trigger: An address change or household reassignment in Salesforce.
- Fill the custodian account maintenance form for each account and send it for signature.
- File the signed form and let the native sync carry the Salesforce change to Tamarac.
- Open a task to confirm the change against the next custodian data in Tamarac.
What a person still does: A person verifies identity for any address change before paperwork is sent.
Client review packets
Trigger: Reviews scheduled in Salesforce for the next two weeks.
- Pull each household's Tamarac reports.
- Add open cases, pending trades noted on the record and the last meeting's notes.
- File the packet to SharePoint or Box and send the advisor the link.
What a person still does: The advisor reads it before the meeting.
Where to start
Start with distribution requests. They are frequent, time-sensitive, and cross all three teams, and every one already ends with a trader and a service associate checking the result. New accounts without a model are the second pick, because an unassigned account sits in cash until someone notices.
What the native integrations cover, and what they leave
Use the vendors' own integrations first. They are maintained by the vendors and they handle the data sync. The table is what each vendor says its integration does, read on the vendor's own pages on September 29, 2026, and the work it leaves for a person.
| Between | What the native integration covers | What it leaves |
|---|---|---|
| Tamarac and Salesforce | Envestnet | Tamarac's AppExchange listing describes a bidirectional connection with client, household and financial account data synchronization, on-command financial account values, and contextual single sign-on into Tamarac. Source: Envestnet | Tamarac (Salesforce AppExchange). | It keeps the records aligned. It does not turn a client request into signed paperwork, a trading task and a billing update, or check that each happened. |
| DocuSign and Salesforce | Docusign eSignature for Salesforce sends envelopes from a Salesforce record and saves the completed document back to it, with writeback to text and picklist fields. Source: Docusign eSignature for Salesforce overview (Docusign Support). | Choosing and filling the right custodian or agreement form, and opening the downstream tasks for trading and billing, are not covered. |
| Tamarac and DocuSign | We did not find a direct Tamarac and DocuSign connection on Envestnet's public pages. On this stack the signature step usually runs from Salesforce. | Signed paperwork reaches Tamarac only as a change someone makes by hand, such as a new model or fee schedule. |
Tools in this stack
Caddi connects to each of these:
- Salesforce: CRM of record: households, service cases, tasks
- Tamarac: Rebalancing, reporting and billing
- DocuSign: Signature on custodian forms, IPS and agreement amendments
- SharePoint: Document storage
- Microsoft Teams: Handoffs between service, trading and billing
Often around this stack, and not Caddi connections:
- Schwab, Fidelity, Pershing: Caddi does not connect to custodians. It fills the custodian's PDF forms from the CRM record, sends them for signature through DocuSign and logs the result back to the CRM. Submitting in the custodian portal stays with your team.
- Other Envestnet products: Caddi connects to Tamarac. Other Envestnet platforms are not Caddi connections today.
Where Caddi fits, and where it does not
Caddi is the layer that runs the work between these tools. Discover finds the repetitive work in the tools your team already uses. Caddi Automate builds each workflow: someone on your team screen-shares the process or describes it in chat, and changes it in plain English as the work changes. Govern gives the firm one view of the work done by AI and by people, with every run logged. AI builds it, verified code runs it, and any model step inside a run is scoped, logged, and reviewable.
Across customers, 99% of agent runs complete successfully, and it takes 45 minutes on average to build the first agent. What Caddi does not do on this stack:
- Place, approve or schedule trades. The trading desk owns every trade.
- Connect to custodians. It fills custodian paperwork; the portal stays with your team.
- Change fees in Tamarac on its own authority. It prepares the change for the billing team.
Related reading
- The RIA operations tech stack, by workflow
- Best automation tool for large RIAs
- The RIA director of operations
- Investment policy statements
- Model selection forms
- Automating the Salesforce + Orion + DocuSign stack
- Automating the Wealthbox + Black Diamond + DocuSign stack
- Automating the Practifi + Addepar + Box stack
More for RIA operations leaders
- The Wealth Advisory COO's Guide to AI
- What a Director of Operations at an RIA owns
- The RIA operations tech stack, by workflow
- RIA acquisition integration checklist
- Client repapering without the NIGO
- Onboarding a breakaway advisor team
Caddi connects to the systems an RIA back office runs on: Salesforce, Wealthbox, Practifi, Orion, Black Diamond, Tamarac, Addepar, DocuSign, Jump, Zocks. See how it runs client onboarding and the operational side of RIA compliance, or the RIA operations overview.
Caddi
See how Caddi AI Agents can hand client requests from service to trading and keep Salesforce and Tamarac work on the record
Frequently asked questions
Does Tamarac integrate with Salesforce?
Yes. Envestnet | Tamarac lists a Salesforce integration on the AppExchange that describes a bidirectional connection with client, household and financial account data synchronization, on-command account values and contextual single sign-on into Tamarac. It keeps the records aligned. Turning a client request into signed paperwork, a trading task and a billing update is still a process your teams run.
Can Caddi place trades in Tamarac?
No. Caddi does not place, approve or schedule trades. On a Tamarac stack it prepares the work around the trade: it fills and sends the client paperwork, opens the task for the trading desk with the amount, date and source document, and closes the Salesforce case when the transaction appears in Tamarac. The trader decides and places every trade.
How do you hand distribution requests from service to trading?
Make the handoff a record, not a message. When a distribution case opens in Salesforce, fill and send the custodian form, and when it is signed, create a trading task with the amount, date and signed form attached. Close the case when the transaction appears in Tamarac. Caddi runs those steps across Salesforce, DocuSign and Tamarac and logs each run.
What should an RIA on Salesforce and Tamarac automate first?
Start with distribution requests: frequent, time-sensitive, and crossing service, trading and the custodian's paperwork, with a trader and a service associate already checking every one. The second pick is new accounts with no model assigned, because an unassigned account can sit in cash until someone notices. Both have clear triggers and clear owners.
Is every automated step logged for compliance review?
In Caddi, yes. Every run is logged with what it read, what it wrote and where, and Govern gives the firm one view of the work done by agents and by people. AI builds the automation, verified code runs it, and any model step inside a run is scoped, logged and reviewable. Ask your CCO how those logs fit your books and records procedures.