CauseWorkHub 2.0 is the result of learning where the original vision was right, where its architecture was wrong, and what nonprofits actually need CauseWork to own.
The original Cause Work launch tried to solve nonprofit fragmentation by assembling a broad collection of third-party services, creative tools, AI utilities, forms, integrations and adjacent offerings behind one doorway. The intention was right: nonprofits should not have to juggle disconnected products or pay enterprise prices for basic operational capacity.
We learned that CauseWorkHub could not be accountable for security, flow, support and auditability while essential product functions remained outside our ownership and control. CauseWorkHub 2.0 brings those critical functions into one product architecture with one accountable product owner.
We were promising one system while parts of that system remained somebody else’s software. That was not good enough.
CauseWorkHub 2.0 is a product—not a bundle. CauseWork owns and controls the Hub architecture, the connected workflows, the first-party forms and website chat, the product roadmap, the installation and licensing path, and the security decisions that hold the system together.
Each nonprofit receives one complete CauseWorkHub product in an isolated environment under that organization’s control. CauseWork.io can sell, license, update and support the product without becoming the warehouse for nonprofit operational data.
The CauseWorkHub plugin is the operating system. Nonprofits are not asked to assemble a fragile WordPress stack.
Forms, chat, cases, projects, governance, CRM, files, HR, grants and accountability are designed to connect.
The nonprofit selects its host and controls its installation, identities, permissions and operating data.
Available, production configuration, committed development and future direction are clearly distinguished.
The original platform treated AI creation tools as a headline capability. CauseWorkHub 2.0 does not.
Current generative services do not automatically fit the privacy, control, provenance, cost and audit boundaries required by a nonprofit operating system. A convenient writing or image button is not worth creating an unclear data path or an architecture we cannot defend.
For now, AI creation tools are outside the core product. Future AI connections may be offered where an organization deliberately enables them, controls the credentials and understands the data boundary. Local or self-hosted options may become appropriate. AI must conform to CauseWorkHub’s architecture; CauseWorkHub will not distort its architecture to chase AI.
They are the product spine. CauseWorkHub connects who acted, what changed, which role permitted it, what work followed, which funding or requirement governed it, what evidence supports it and what result came from it. Sensitive work remains separated by role and purpose. Access is deliberate. Activity is preserved. Files belong in controlled storage—not scattered through ordinary WordPress uploads. Support is authorized, not assumed.
That is why cases connect to projects and files; grants connect to requirements, approvals and outcomes; governance connects to agendas, votes and evidence; finance surrounds QuickBooks with purpose and accountability; and forms connect intake to real organizational work.
CauseWork did not begin with a generic CRM and search for a nonprofit market. The product grew from the daily reality of mission-driven organizations: limited budgets, complicated grants, serious privacy duties, governing boards, staff and volunteers wearing several hats, sensitive records, fragmented evidence and software priced as though every nonprofit were a national institution.
We believe enterprise-grade control should be available at the nonprofit’s level. CauseWorkHub costs $300 per year for unlimited users and unlimited use because affordability is part of the architecture—not a promotional discount.
We also build in public. The working demo shows the product. Research connects laws and operating pressure to the sections that solve them. The installed base helps direct development. When something is planned rather than available, we say so.
Privacy rights, grant controls, cybersecurity expectations, accessibility requirements, audit thresholds and electronic reporting increasingly reach into ordinary nonprofit workflows. At the same time, organizations are paying separately for CRM, forms, case management, files, projects, governance, communications and fundraising tools that barely acknowledge one another.
Nonprofits do not need another narrow subscription. They need an accountable operating backbone that connects the work while leaving the organization in control.
Your criticism, operating experience and willingness to test real workflows helped turn an ambitious bundle into a product we can own, explain and defend.
Release news, product commitments, nonprofit research and the path to purchase—sent deliberately, never constantly.