Automating the Practifi + Addepar + Box stack for complex households
For operations leaders at UHNW advisors and multi-family offices on Practifi, Addepar and Box: seven workflows built around entities, alternatives and documents, what the native integrations cover, and what is left.
On a Practifi + Addepar + Box stack, the native integrations cover the view: Addepar sends accounts and holdings into Practifi on a daily sync, and Box files open from a tab on the Practifi household. The work that remains is documents about entities: capital call notices, K-1s, trust documents and subscription agreements that arrive by email and have to be filed, logged and acted on for the right entity.
Complex households generate far more paper per dollar than a typical advisory relationship, and most of it arrives outside any system. Below are seven workflows that cross this stack, each with a trigger, the steps and what a person still reviews.
Who runs this stack
This is the stack of a firm serving complex households: ultra-high-net-worth families, multi-family offices, and advisors with many trusts, LLCs and partnerships per client. Practifi, which runs on Salesforce, holds relationships, entities and service work. Addepar aggregates and reports across public holdings, private funds, real estate and direct investments. Box is the document vault, usually a folder tree per family and per entity.
The team is organized around relationships: relationship managers, client service associates, reporting analysts and an operations group that handles money movement and documents. Much of the work is driven by third parties, such as fund administrators, trust companies, CPAs and attorneys, whose notices and requests arrive by email on their schedule, not yours.
| Layer | Typical choice |
|---|---|
| CRM | Practifi, on Salesforce |
| Aggregation and reporting | Addepar, including alternatives and entity structures |
| Documents | Box, a folder per family and per entity |
| Signature | DocuSign for subscription documents and agreements |
| Outside parties | Fund administrators, trust companies, CPAs, attorneys |
| Ops shape | Relationship teams plus reporting analysts and a documents group |
The pressure on this stack is documents tied to entities. A single family can hold dozens of private fund positions across several entities, and every capital call, distribution notice and K-1 has to land in the right entity's folder and the right CRM record. Custodian account paperwork matters less here than it does at a mass-affluent RIA, so the workflows below lean on documents and data exceptions.
The workflows that cross Practifi + Addepar + Box
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.
Capital call and distribution notices
Trigger: A notice from a fund administrator arrives in the shared inbox.
- Identify the fund and the investing entity from the notice.
- File the PDF to that entity's Box folder with your naming convention.
- Log it on the Practifi entity with the amount, due date and notice type, and open a task for operations.
- When the transaction shows in Addepar, match it to the notice and close the task.
What a person still does: Operations confirms the entity and amount and handles any funding instruction. Money movement stays with a person.
K-1 collection season
Trigger: The start of your K-1 tracking window each year.
- Build the list of expected K-1s per entity from the private holdings in Addepar and the entities in Practifi.
- As K-1s arrive by email, or are saved to Box from a fund portal, file each one and tick it off.
- Send the relationship team and the family's CPA liaison a weekly list of what is still outstanding.
- Share the entity's K-1 folder with the CPA under the sharing rules your firm sets.
What a person still does: Operations decides which documents are final and which are estimates, and approves each external share.
New trust or entity onboarding
Trigger: A trust agreement or operating agreement is saved to a family's Box folder.
- Read the key fields: entity name, type, trustees or managers, dates.
- Draft the Practifi entity record from them, linked to the family, for review.
- Create the entity's Box folder structure from your template.
- Prepare the entity and ownership details for the reporting team to set up in Addepar.
What a person still does: A person confirms every field read from the document before the Practifi record is saved, and the reporting team sets up Addepar.
Subscription documents for a new commitment
Trigger: A new commitment is approved on the Practifi family record.
- Fill the investor details in the subscription agreement from the investing entity's Practifi record.
- Send it through DocuSign to the signers for that entity.
- File the executed documents to the entity's Box folder and log the commitment on Practifi.
- Open a task to confirm the position appears in Addepar after the first capital call.
What a person still does: Operations or counsel reviews the investor representations before sending. The investment decision is not the automation's.
Addepar to Practifi exceptions
Trigger: Each morning after the overnight Addepar sync to Practifi.
- List Addepar portfolios not linked to a Practifi client, and Practifi entities with no Addepar portfolio.
- Flag holdings whose value has not updated in the period you choose.
- Send the reporting analyst one exception list with links to both records.
What a person still does: The reporting analyst resolves each exception.
Family reporting pack
Trigger: Addepar data is finalized for the quarter.
- Pull each family's Addepar reports at the views your team uses, such as by entity and consolidated.
- Add the Practifi meeting agenda and open service items.
- File the pack to the family's Box meeting folder and notify the relationship manager.
What a person still does: The relationship manager and reporting analyst sign off before anything reaches the family.
Document requests from the family's other advisers
Trigger: A CPA or attorney emails a request for documents.
- Match the requester to the family in Practifi and confirm they are an authorized contact.
- Find the requested documents in Box.
- Prepare a share link with the expiry your policy sets and log the request on Practifi.
What a person still does: A person approves every external share. Who may receive a client's documents is a policy question for your CCO.
Where to start
Start with capital call and distribution notices. They arrive constantly, each one has a due date, and filing them to the right entity is a lookup a person does from memory today. K-1 season is the second pick, because it is predictable and its cost is a family's tax filing.
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 |
|---|---|---|
| Addepar and Practifi | Addepar describes the Practifi integration as linking Addepar accounts and holdings to Practifi, with portfolio data coming from Addepar on a sync that Practifi schedules. Practifi's help center describes a daily overnight sync into the household's assets. Source: Addepar integrations: Practifi. | It is one way and a view. It does not tell anyone when an entity exists in one system and not the other, and it does not touch the documents behind the holdings. |
| Box and Practifi | Practifi's Box integration adds a Box tab to the household, so the team can browse the client's Box folders and drag files in without leaving Practifi. Source: Practifi Success: Using the Box integration. | It shows the folder. Deciding which entity folder a notice belongs in, naming it and logging it on the record is still done by hand. |
| Addepar and Box | We could not confirm a native Addepar and Box connection on Addepar's public pages. | Treat filing Addepar reports to Box as a gap to test with both vendors, and ask Addepar what document delivery options your firm has. |
Tools in this stack
Caddi connects to each of these:
- Practifi: CRM of record: families, entities, service work
- Addepar: Aggregation and reporting across public and private assets
- Box: Document vault by family and entity
- DocuSign: Signature on subscription documents and agreements
- Microsoft Outlook: Where notices and requests arrive
Often around this stack, and not Caddi connections:
- Custodians and trust companies: 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.
- Fund administrator portals: Notices and K-1s often sit behind each administrator's own portal. Downloading them stays with your team; Caddi works from what lands in email or Box.
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:
- Connect to custodians, trust company systems or fund administrator portals.
- Move money or approve a funding instruction.
- Replace Addepar's reporting or your reporting analysts' judgment on alternatives valuations.
Related reading
- The RIA operations tech stack, by workflow
- Best automation tool for large RIAs
- A wealth advisory COO's guide to AI
- RIA back-office automation workflows
- Third-party investment services agreements
- Automating the Salesforce + Orion + DocuSign stack
- Automating the Wealthbox + Black Diamond + DocuSign stack
- Automating the Salesforce + Tamarac + DocuSign 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 file every capital call and K-1 to the right entity and keep Practifi and Addepar in step
Frequently asked questions
Does Addepar integrate with Practifi?
Yes. Addepar describes the Practifi integration as linking Addepar accounts and holdings to Practifi, with portfolio data flowing from Addepar on a sync schedule Practifi controls. Practifi's help center describes it as a daily overnight sync into the household's assets. It is one way, from Addepar to Practifi, and it does not cover the documents behind the holdings.
What is a typical multi-family office tech stack?
Most multi-family offices pair a relationship CRM, often Salesforce-based such as Practifi, with an aggregation and reporting platform that handles alternatives and entities, such as Addepar, and a document vault such as Box. DocuSign handles signatures. What differs from a typical RIA is the volume of third-party documents, like capital calls and K-1s, that arrive by email and must be filed by entity.
Can Caddi file capital call notices to the right entity?
Yes. When a notice arrives in the shared inbox, Caddi identifies the fund and the investing entity, files the PDF to that entity's Box folder with your naming convention, logs it on the Practifi entity with the amount and due date, and opens a task for operations. A person confirms the entity and handles any funding instruction. Every run is logged for review.
How do you track K-1s across many entities?
Build the expected list from the private holdings in your reporting system and the entities in your CRM, then tick each K-1 off as it arrives. Caddi can do the building, filing and ticking: it reads K-1s from email or Box, files them to the entity's folder, and sends a weekly outstanding list to the relationship team and the family's CPA liaison.
Does Caddi read trust documents?
Caddi can read the key fields from a trust or operating agreement saved to Box, such as entity name, type, trustees and dates, and draft the Practifi entity record from them. A person confirms every field before the record is saved. Any model step inside a run is scoped, logged and reviewable, so the team can see what was read and where it went.