02 / Use cases
Use cases
Use case
Client management in Planeward
The workspace includes people, pipelines, forms, invoices, expenses, channels, and developer tools. You can ignore what you do not use, or turn the CRM module off. Still no booking calendar, session notes, package catalogs, email sequences, or payroll.
Use case
Project management in Planeward
A project sits inside a workspace. It has statuses and tasks. The board is the default place work moves. List, timeline, and calendar show those same tasks. A canvas and task templates sit on the project. The inspector opens a task without leaving the view.
Use case
Team operations in Planeward
Team operations here means membership, roles, project access, and channels. Not HR, payroll timesheets, or OKR software. Invite by email. Sign-in is Discord or email and password. Guests can be limited to a project. Chats can be turned off.
Use case
A personal workspace in Planeward
A personal workspace is still a workspace: projects, boards, tasks. You do not have to invite anyone. The point is one product for work you are paid for and work you owe yourself.
Use case
Developer tools in Planeward
Automation lives in the workspace, not in a second product. On Pro, create an API key, register a webhook, connect MCP, or build a workflow. A workflow can include an AI agent that uses an OpenAI or Anthropic key you store. There is no Slack app, no Jira sync, and no marketplace of integrations.
Use case
Websites and funnels in Planeward
Sites are pages you build in the workspace, with versions you can roll back. A funnel is an ordered path through pages. Attach a domain you own. Tracking is Google Tag Manager, or a Meta pixel and Conversions API. Use one Meta setup, not both. Sites are on Pro.
Use case
Lead capture forms in Planeward
A form is fields, appearance, and a share link. Submissions stay in the workspace. You can generate a first draft from a description and edit it before anyone sees it. The same form can sit on a site page. People who submit are not members.
Use case
Expenses and budgets in Planeward
Invoices are what clients owe you. Expenses are what the work costs. Categories and budgets keep a period honest, and closing the books locks that period. Payments record what actually arrived. None of this is payroll, and Planeward does not take a cut of either side.
Use case
AI and MCP in Planeward
On Pro, MCP lets Claude or ChatGPT work against the workspace with the scopes you grant. A workflow can include an AI agent node that calls OpenAI or Anthropic with a key you store, and that node can call tools, including an outbound MCP server. Form drafts are separate: Planeward generates them, and you edit the result. There is no marketplace of agents.