Find the tools behind your work.

Organize client and brand records so the team knows who the work belongs to.

Fictional example: Forma Studio is the client and Forma / Autumn collection is the associated brand context.

Before you use it

Brand and user limits depend on plan. The sample businesses and people shown are fictional.

Give every task an owner, a deadline and the context to move forward.

Fictional example: Nour moves the Autumn launch creative brief from In progress to Review.

Before you use it

Available views and actions depend on your access. Time tracking and automations require an eligible paid plan.

Record time against the task so the work and the effort stay connected.

Fictional example: Nour records two hours of concept exploration and another hour and a half refining the direction.

Before you use it

Time tracking requires an eligible paid plan. A time entry is not automatically a billable invoice line.

Collect enquiries and structured responses in a form built around what your team needs to know.

Fictional example: Lina submits her name, email and an autumn collection project brief.

Before you use it

Lead creation is configurable; every form does not automatically create a project or lead. Sharing and response access depend on the form settings.

Build a focused page for an offer, launch or enquiry inside your workspace.

Fictional example: Forma’s collection page moves from an opening message to product details and a discovery button.

Before you use it

Publishing, domains and page access depend on workspace configuration. The example page and business are fictional.

Turn reusable templates and variable values into consistent PDF documents.

Fictional example: an Autumn launch proposal receives Forma Studio and 21 October 2026 as its variable values.

Before you use it

Documents are a paid-plan capability. The sample PDF is fictional; it is not a signed agreement or an invoice.

Map processes and relationships on a visual canvas before they become complicated work.

Fictional example: a process map connects Creative brief, Visual direction, Review and Launch assets.

Before you use it

Diagrams require a paid plan. Drawing a workflow does not itself create an executable automation.

Keep supporting material close to the task or record that gives it meaning.

Fictional example: the creative brief has an Autumn launch proposal PDF and Collection artwork attachment.

Before you use it

Preview support varies by format. Storage and upload limits apply. The website sample does not upload files.

Compose, organize and schedule social content by brand and connected account.

Fictional example: Forma Studio’s Instagram collection post is scheduled for 21 October at 11:00.

Before you use it

Publishing requires a paid plan. Supported media, post types and scheduling behavior vary by provider, account and permissions.

Review paid campaign activity alongside the rest of your brand’s work.

Fictional example: Forma Studio’s Meta awareness campaign shows a $40 daily budget and illustrative delivery figures.

Before you use it

Ads spend is paid to the provider separately. Providers expose different controls and metrics; examples are illustrative, not results or performance promises.

Explore available channel metrics with the context of your brand’s content and campaigns.

Fictional example: Forma Studio’s October report shows 32,000 reach and 2,680 interactions.

Before you use it

Metric availability, history and freshness depend on provider access and synchronization. The sample figures are fictional and do not prove attribution or ROI.

Bring supported brand conversations into a shared place for the people handling them.

Fictional example: Lina asks Forma Studio whether the collection is available in store; Nour reviews a suggested reply.

Before you use it

Inbox requires a paid plan. Supported message types, reply windows and channel capabilities vary by provider.

Keep quotations, line items and draft invoices close to the work they represent.

Fictional example: a $1,000 accepted quotation contains $750 for creative work and $250 for content planning.

Before you use it

Accepting a quotation does not automatically send an invoice or collect payment. Sample amounts are fictional.

Turn repeatable decisions into workflows your team can inspect, test and control.

Fictional example: a high-priority task entering In review is assigned to Layla by a configured workflow.

Before you use it

Automations require a paid plan. Triggers and actions are filtered by permissions, scope, connected account capabilities and configuration.

This page simulates a task-status rule locally; it does not execute a server workflow or send notifications.

Give a brand agent the context to help with conversations and choose how it behaves on each channel.

Fictional example: the Autumn collection guide supports Instagram suggestions, while WhatsApp remains Off.

Before you use it

AI requires a configured provider; availability, quotas and provider charges depend on your workspace setup. AI responses can need correction. Auto mode is an explicit configuration, not the default behavior demonstrated here.

Use a conversational assistant to help with the AMS work you are authorized to access.

Fictional example: a teammate asks, “Find the Autumn launch project,” and sees an illustrative accessible result.

Before you use it

AI needs a configured provider. Available tools vary with permissions and configuration. The visual is a website explanation, not a recorded assistant execution.

Control who can act, which project details they can change and what data they can see.

Fictional example: compare the displayed Project manager matrix with a Member view and assigned-record scope.

Before you use it

The displayed role matrix is an example, not the default of a named system profile. Access follows the configured project snapshot and applicable organization controls.

Extend supported records with the information that makes your way of working specific.

Fictional example: a task records Autumn collection, 12 assets and a Ready for review checkbox.

Before you use it

Field types and scope depend on the entity and configuration. Custom fields do not bypass record permissions.