A workspace you shape around the work

A workspace holds projects. A project holds statuses and tasks. The board is the live view: columns are statuses, cards are tasks. List, timeline, and calendar show those same tasks. A canvas sits on the project for the sketch that is not a task yet. Templates start the next card from work you already shaped. Opening a task uses the inspector so you stay on the view.

Keep the people you work with next to the projects. A customer is the account. Contacts are the people on it. Tags group both. A pipeline is a board of opportunities, and each card is a deal. You can turn this off in workspace settings if you only want projects.

Draft an invoice, finalize it, and send a pay link. Record the payment when it lands. Track expenses against categories and budgets, then close the period. Clients open their invoices from a magic link. They do not join the workspace. Card, PayPal, Wise, and bank details belong to that workspace. Planeward does not take a cut.

Forms live with the clients, not in a separate form tool. Build the fields, set the appearance, and share the link. Submissions stay in the workspace. You can generate a first draft of the form from a description. A form can also sit on a site page.

Build pages in the workspace, keep versions, and publish when the page is ready. A funnel is an ordered path through those pages. Attach a domain you own. Add Google Tag Manager or a Meta pixel and Conversions API on the site. Use one of those for Meta, not both. Sites is on Pro.

Public and private channels sit next to the projects. Threads and reactions stay in the channel. A project can have a linked channel so the conversation about that work has a home. Turn chats off if the team already talks somewhere else.

Build a workflow for a job you already repeat: a trigger, a branch, a wait, a note to the team. Triggers include a manual run, a webhook, a schedule, and events from the workspace. An AI agent node calls OpenAI or Anthropic with a key you store, and it can use tools including an outbound MCP server. Separately, create a scoped API key, register a webhook, or connect Claude or ChatGPT to the workspace over MCP. There is no Slack, Zapier, or Jira app.

Enterprise workspaces can embed a project for external users. They work in that project through the embed. They do not get the rest of the workspace. We provision Enterprise. It is not a self-serve checkout.