- Does EnDAO replace our fiscal sponsor?
- No. EnDAO is the governance and operating layer — multi-signer approvals, per-project records, audit trail across the portfolio. The legal 501(c)(3) responsibilities — charitable receipts, IRS reporting, fiscal liability — stay with your sponsor. Two systems with different jobs.
- Can EnDAO issue charitable receipts to our donors?
- No — the sponsor’s 501(c)(3) issues all charitable receipts. EnDAO records the contribution on the project ledger and timestamps the approval chain, but the receipt comes from the sponsor.
- Does it work for both Model A (comprehensive) and Model C (pre-approved grant)?
- Yes. The governance structure is configurable per project — Model A projects share the sponsor’s decision policies and signer pool; Model C projects operate as their own decision group with the sponsor approving the underlying regrant. Both end up on a ledger the sponsor can audit.
- How does the sponsor see across all sponsored projects?
- Sponsors get a portfolio view: every project they host, the balance and recent activity for each, and the ability to drill into any project’s full ledger when they need to. Project leads only see and operate from within their own project.
- How are admin-fee splits handled?
- The admin fee shows up on the ledger as a line item the sponsor records against each disbursement or intake. The amount, the disbursement it was drawn from, and the project it applied to are all on the record.
- Most sponsors already run Salesforce plus QuickBooks plus Bill.com. Why change?
- Many sponsors built that stack because no purpose-built alternative existed. The result is a multi-system workflow where the governance approvals, the financial records, and the disbursement rails live in three different places — and reconciling them takes staff time every cycle. EnDAO is designed for that job from the start: project ledger, approval workflow, and sponsor portfolio view in one place. It is not a general-purpose accounting platform; it is the operating system the stack was substituting for.