Home / Insights / Plans by product
Can Asana Starter handle request intake and routing on its own, or do you need Advanced?
Summary
Starter can collect requests through a form, turn responses into tasks and route them with rules. Advanced adds branching forms, approvals and proofing, and the Salesforce integration. The practical dividing line is whether every request can follow the same intake questions and process.
Follow one design request through the system
Imagine a team receiving requests for flyers and web banners. Its form collects the purpose, dimensions, due date and attachments. Each submission creates a task in the connected project, so the brief arrives beside the work instead of in a separate inbox. Forms can be shared by link or embedded on a website; access can be restricted to the company.
A rule pairs an event with an action: a form submission can trigger assignment, or a task can be moved to the next section. The Forms page and Rules page describe this intake-and-routing model. Decide the categories and owners before building rules; the software needs those choices from the team.
Where the intake needs Advanced
| Need | Plan | How to read it |
|---|---|---|
| The same questions for each request | Starter | Use a standard form and routing rules |
| Different follow-up questions for print and web work | Advanced | Branching changes questions based on an answer |
| Formal sign-off or feedback on creative assets | Advanced | Approvals and proofing are higher-tier features |
| Create Asana work from Salesforce events | Advanced | The active Salesforce app uses Asana Rules |
A simple assignment rule and a formal approval step are different features. Starter can route a task to a reviewer. The plan comparison lists the dedicated approval and proofing features under Advanced.
Rules and AI have separate allowances
Starter lists unlimited automations. AI Studio, which can interpret text inside a workflow, uses credits instead. A rule that routes a known category and an AI step that reads an unstructured brief therefore have different usage conditions. Keep the first version simple enough to test with real requests before adding AI.
For a fixed intake form and clear owners, Starter is a reasonable starting point. Choose Advanced when branching, dedicated approval records or Salesforce-driven work is part of the required process. A small team receiving only a few requests may be better served by a shared task list than by a paid intake workflow.
Sources
Facts used in this revision checked 10 October 2026. Prices use US dollars unless stated otherwise.
What changed on this page
- correction11 October 2026 Can Asana Starter handle request intake and routing on its own, or do you need Advanced? — Article title and explanation
Can Asana Starter handle request intake and routing on its own, or do you need Advanced? → Can Asana Starter handle request intake and routing on its own, or do you need Advanced?
Follow an explicitly hypothetical design request through forms and rules. Distinguish routing to a reviewer from dedicated approvals/proofing. Separate automation allowance from AI Studio credits; remove unsupported collaborator and template claims.
Every recorded change to this site is in the change log.
More in Plans by product
All of plans by product →Does connecting Asana to Slack, Salesforce, or your own systems require a certain plan?
Basic Slack and Google Workspace integrations are included in Asana’s free integration offering.
Read → Plans by productIs it cheaper to buy HubSpot one Hub at a time or as the full Customer Platform?
Starter Customer Platform is worth comparing with an individual Starter Hub because their advertised starting seat price is the same.
Read → Plans by productHow much can the free HubSpot CRM hold before you need to pay?
HubSpot’s free CRM supports up to two users and 1,000 contacts without a time limit.
Read →