SaaS · Practice management · 2025—
Groundwork
Groundwork manages schedules, contacts, intake forms, media, and writing. It can securely provide the appropriate public information to any compatible site we build.
Our role
Schema contract · Public content feed · Site integration

Client dashboard
A personal dashboard with programs, prompts, media, and a shared journal.
1 / 5

Client management
The people who need attention surface first in one organized client list.
1 / 5

Content and course delivery
Build a course or client program from guided questions or an existing document.
1 / 5

Secure messaging
Private one-to-one client messaging, including voice notes.
1 / 5

Billing
Paid, unpaid, and overdue invoices tracked in one place.
1 / 5
Why it matters
A redesigned website does not solve disconnected operations on its own. Groundwork lets the public site and internal workflows use records the organization already owns and manages every day.
The contract
Every FireKeeper Designs site reads public content through a single feed and writes only through guarded endpoints. No site-specific tables, no second copy of a Groundwork concept, no divergent data shapes.
When a site needs a capability Groundwork does not yet support, we extend the shared contract instead of creating an incompatible copy for one project.
The client portal API
Groundwork exposes a client portal API that any compatible site we build can consume directly. A practitioner's website becomes more than a brochure: it gains a private, authenticated space where clients log in to their own portal.
Through the portal, clients have access to completely secure direct and group messaging — one-on-one conversations with the practitioner and shared threads with a cohort, care team, or community, all scoped to the right participants at the data layer.
The same API delivers scheduled content: newsletters and course material released on a schedule or gated to a client's program. A practitioner can author a course once, sequence the delivery, and each enrolled client receives the right material at the right time through the same portal they already use to message and manage their work.
Because the portal is an API rather than a bolted-on tool, it inherits the same security model as the rest of the system. Messages, content, and client records stay under the practitioner's control — not routed through a third-party platform with its own access to the data.
Outcomes
- One schema across every practitioner site
- New capability compounds instead of forking
- Practitioners keep their own data
- Secure client portals with messaging and scheduled content delivery on any site
