# SaaS & Client Portal Foundation — planning brief

Status: planned product; software not released. Version 1.0, 2026-09-29.

Accounts, roles, billing and admin screens are repeatedly rebuilt before the real business workflow gets attention. Poorly separated tenant data becomes expensive to fix later.

## First workflow

A customer creates a workspace, invites a teammate and completes a core task. An owner manages access and billing while an operator handles support through a scoped administration interface.

## Proposed first release

- [ ] Workspace accounts, invitations and role-based permissions
- [ ] One core business workflow and a customer-facing dashboard
- [ ] One billing provider integration in test mode, where required
- [ ] Administrative tools, audit events, setup documentation and deployment configuration

## Extension points

- [ ] Keep domain features separate from identity, workspace and billing modules
- [ ] Use explicit tenant identifiers and documented API contracts
- [ ] Add branding, roles and domain modules without forking the whole application

## Acceptance checks

- [ ] Two test workspaces cannot access each other’s records
- [ ] A revoked member loses access on the server
- [ ] Duplicate billing events produce one consistent subscription state
- [ ] A second developer can set up the application from the handover instructions

## Boundaries

A finished downloadable starter does not exist yet. Marketplace, complex metered billing and multi-region infrastructure require separate scope.

## Decisions to fill in

- Business owner:
- Intended users:
- Data sources and retention:
- Existing systems:
- Integrations:
- First release exclusions:
- Deployment owner:
- Acceptance owner and evidence:

## Reuse

You may copy and adapt this planning document for your own or client projects. It contains no software license or promise of implementation.

Discuss a custom build: https://fone.cc/contact/