Rabbithole CLIENT PORTAL
WZWanda Zambrano JRJuan Rivera Pérez ← Sign out

Architecture

How your portal connects to your stack

The client portal sits on top of the systems Rabbithole CPA already runs. Nothing is ripped out — the Rabbithole Sync API reads from your tools and writes client changes back, so every system you trust stays the system of record.

Your existing stack Sync layer Portal Rabbithole Sync API INDEX · QUEUE · WEBHOOKS synced 4 min ago Client Portal This demo · Juan's view Admin Portal Staff workspace · planned Front.com — view integration detail Front.com Shared inbox › Gmail — view integration detail Gmail Client email › ShareFile — view integration detail ShareFile Document storage › Jotform — view integration detail Jotform New-client intake › PandaDoc — view integration detail PandaDoc Engagement signing › Internal Server — view integration detail Internal Server System of record ›
Read — the portal pulls a copy-free index Write — client actions queue back to your systems Planned — part of a future engagement phase
Built by Rabbithole Consulting
Integration architecture · Rabbithole CPA Group client portal
Nothing is migrated

Your six systems keep running exactly as they do today. The portal is an additional surface for your clients — not a replacement for any tool.

Nothing is duplicated

Records are referenced by ID, not copied. ShareFile keeps the files, Gmail keeps the mail, and your internal server keeps the source of truth.

Nothing is locked in

The Sync API is a thin, documented layer. Switch it off and your stack is exactly where it started — untouched and fully yours.