The charter, in full.
Five articles, and every clause the workspace actually honours. Nothing on this page is a roadmap item — if it is written here, it ships today.
IPlan the work
Four task statuses. Four task types. Everything else was deleted on purpose.
- Projects
- Per-project boards, files, calendar, timeline, team and settings — with per-project roles, not one global hierarchy.
- Kanban boards
- Drag between To Do, In Progress, In Review and Done; the same pipeline rules apply whether you drag or click.
- Sprints & backlog
- Optional sprint planning with a backlog view, for the teams that want cadence — off for the ones that don't.
- Calendar & timeline
- The same tasks, seen by date or by dependency-free schedule bars.
- Recurring tasks
- A completed recurring task spawns its next occurrence — repeat the work once it's actually done.
I.1
I.2
I.3
I.4
I.5
IIMove work through review
A pipeline with a spine: employees move work forward, managers sign it off.
- Review gates
- Anyone can start and submit work; only a manager can approve it out of In Review — and sending it back requires a written reason.
- Approvals that follow the org chart
- Approval requests route up the requester's real reporting line — never to a peer, never to their own report.
- Client review
- Work that needs the client's sign-off asks the client, from their own portal login.
- Assistance requests
- Ask a person or a whole team for help from any comment thread; the request becomes a real subtask.
- Audit trail
- Every status change, assignment and deletion is logged with who did it — an audit log you can't quietly edit.
II.1
II.2
II.3
II.4
II.5
IIIServe clients like it's the product
Client work is first-class — not a guest badge on an internal tool.
- Client records
- Companies, contacts, account managers and per-client activity in one place.
- Client portal
- Clients get a purpose-built dashboard, not a stripped-down admin view. You control which sections exist for them — closed by default.
- Per-task visibility
- Hide any single task from the client, or show it — a tri-state switch on the task itself.
- Campaigns & intake forms
- Campaign briefs and product-intake forms that land as structured, assignable work.
III.1
III.2
III.3
III.4
IVAsk, don't dig
An assistant that answers from your workspace and acts under your permissions.
- Grounded answers
- "What's blocked on WEB and why?" — answered from your actual tasks, comments and docs, by meaning rather than keyword.
- Real actions
- Create, assign, move and comment by asking. Destructive actions always show a card and wait for your click.
- Private inference
- The model runs on FuturnFlow's own GPUs. No task, comment or client record is ever sent to a third-party AI provider.
- Attributed work
- Everything the assistant does is logged as you, via the assistant — the answer to "who did this?" is always a person.
IV.1
IV.2
IV.3
IV.4
VRun the workspace
Simple defaults, real controls underneath.
- Four roles + custom roles
- Owner, Admin, Member, Client — plus custom roles that grant exactly the permissions you tick, never permissions guessed from a name.
- Teams
- Team membership is an invitation with accept/decline, and project access follows the teams you've accepted.
- Modules
- Ten optional modules, off by default — clients, campaigns, intake forms, approvals, sprints, docs, time tracking, automation, custom fields and the AI assistant.
- Themes
- Light, dark or system, times six accent colours — picked per person, applied before first paint.
- Docs, reports & search
- Lightweight docs in spaces, cross-project reports, and search that spans work, people and files.
V.1
V.2
V.3
V.4
V.5
The fastest way to evaluate it is to use it.
14 days of Professional, 10 seats, no card.