Figma Specs vs Notion: which fits a small business

What Figma launched and whether to act this month

Figma launched Specs on October 15, 2026, according to Figma (2026), as a Markdown document that lives on the Figma canvas beside the frames and FigJam boards it describes. For a small B2B software team, the change is where written product intent sits and how a coding agent reads it, but Specs is in open beta and listed on paid seats only, so this month the sensible step is a scoped pilot rather than a move of the whole documentation stack.

TL;DR: Specs keeps a spec on the canvas next to the frames, FigJam boards and code layers it refers to, and it exposes that context to coding agents through Figma's MCP server. The pricing page names no separate Specs price, and the vendor has not published when the open beta ends.

Key Takeaways

• Specs is a Markdown spec on the Figma canvas. It is in open beta, available on paid seats, and not included in the free Starter plan.

• Agents reach a spec through Figma's MCP server. Writing to the canvas through the remote server requires a Full seat, is free during the beta, and will eventually become usage-based.

• Budget from the Full seat price on Professional, shown in the pricing section below, but confirm the billing basis, because the pricing page does not state it clearly.

• Against Notion, the deciding question is where your designs live. Against a Markdown-in-Git setup, it is whether people outside engineering need to edit the spec.

• Rate limits differ by seat type and plan, so measure your real agent usage in a pilot before you plan around it.

• The vendor has not published Specs-specific limits, a beta end date or regional availability. Those gaps are the reason to pilot before any migration.

How we evaluated these tools

We weighted six criteria against the decisions a small software team faces this month. The weights are our own judgment as an informed buyer, not a scoring method published by any vendor. Each factor is scored only from the vendor pages and independent sources cited in this article, and where a page was silent we say so instead of filling the gap.

We also considered Atlassian's Confluence as a second documentation rival. Its pricing page did not show per-user figures in our session, so this comparison leaves Confluence out of the price table rather than estimate its cost.

What the Specs launch includes

Each point below comes from Figma's launch post.

• Creation: press "D" on the keyboard or click the Specs icon in the toolbar in Figma or FigJam (launch post).

• Import: drop any .md file onto the canvas to turn it into a spec (launch post).

• Embedding: place a FigJam file, a frame or any canvas node inside a spec so text and design sit side by side (launch post).

• Duplication: copy a spec on the canvas so teammates can work on separate versions before they align (launch post).

• Connectors: the GitHub connector drafts a technical spec from a codebase, and the Hex connector runs an analysis and leaves the answer as a comment (launch post).

• Agents: Figma's agent can reply to comments in a spec, and a coding agent can read a spec through the MCP server and update it (launch post).

• Code layers: the post says code layers moved into open beta (launch post).

• Availability: the post says Specs is available on web, desktop and mobile, rolling out in open beta to paid plans (launch post).

For the following, the vendor has not published this: file-size caps, the number of specs per file, regional limits and the date the open beta ends. Figma's pricing page likewise shows no separate Specs price, only a note that the Specs beta is available on paid seats.

The change for buyers is where context sits. The launch post says Markdown files "tend to be single player on local computers, with brittle relationships to each other," and Specs is built to hold those links on the canvas. That is a claim about workflow. The post offers no measured results.

Specs against the stack you use now

Most small software teams keep product specs in one of three places: a Notion workspace, Markdown files in a Git repository, or comments on design files. Specs competes most directly with the first two for written intent and with the third for links between text and designs. We use Notion as the main rival for documents and a Markdown-in-Git setup as the baseline for engineers.

The matrix turns on one question: where the designs live. If your frames, FigJam boards and code layers already sit in Figma, Specs removes the screenshot-and-stale-link step the launch post describes, and the MCP link lets an agent read design context alongside the text. If your designs live elsewhere, Specs asks you to add a second home for context, and that cost usually outweighs the benefit.

For text-heavy teams, Notion is the closer comparison. Business plan: $20 per member per month according to Notion (2026), and the same page lists Plus at $10.

When NOT to use US Tech Automations: if the team has no Figma seats and writes specs only in Notion or Git, a plain Notion workspace or a folder of Markdown files in a repository is the simpler choice, and a workflow layer adds moving parts someone must maintain. The same is true when only one person owns the spec, because the handoff problem that Specs and automation both address does not yet exist.

Pricing and seat math

Pricing checked October 17, 2026. Figma's Starter plan does not include Specs, and the Professional, Organization and Enterprise plans price seats by type. Figma's Professional plan has a monthly and annual toggle, but the page does not clearly state which billing basis its seat prices use, so confirm that before you budget.

Professional Full seat: $16 per month according to Figma (2026). The same page lists the Dev seat on Professional at $12 and the Collab seat at $3, and it lists the Organization Full seat at $55 and the Enterprise Full seat at $90, both billed annually.

GitHub's Team plan is listed at $4 per user per month, with a first-12-months asterisk whose footnote the captured page did not include, and its Enterprise plan at $21 per user per month, according to GitHub (2026).

The table below collects each listed figure in one place.

Worked example: a five-person product team on Figma's Professional plan buys two Full seats for the people who write specs and drive agents, and three Collab seats for reviewers. Using the Full and Collab prices cited above, two Full seats at $16 per month come to $32, and three Collab seats at $3 per month come to $9, so the Figma seat total is $41 per month before tax. If the team also pays Notion's Plus plan at $10 for five members, that adds $50 and brings the two-tool total to $91. When an agent drafts that spec from a frame, it calls get_design_context, which Figma's tools page classifies as a read tool that pulls variables, components and layout. Two assumptions carry the math: the Collab seats can review the spec, and the vendor has not published whether a Collab seat can create or edit one, so test that before buying.

If the listed figures are annual-rate rather than monthly invoices, the cash amount changes, so check the billing toggle before you budget.

Agent access and call limits

Figma's rate-limit page sets separate daily and per-minute caps for each seat type and plan, and it gives View and Collab seats a monthly cap, which is the limit to check for a review-only seat (Figma rate limits). A review pass that calls the MCP server many times in one session can hit the per-minute cap before the daily one.

Developers using or planning AI tools: 84% according to Stack Overflow (2025). The same survey finds 46% of developers distrust AI accuracy, according to Stack Overflow (2025), so a human review step is not optional for spec-driven work.

Figma's MCP overview says writing to the canvas through the remote server requires a Full seat to write outside drafts, is free during the beta period and will eventually become usage-based. The vendor has not published the future price (MCP overview). Figma's tools page sorts get_design_context under read tools and use_figma under write tools, which is the split to check when you set agent permissions (tools page).

Where automation fits, and where it does not

Most small teams that connect these tools by hand start in Zapier, Make or n8n, or they write a small service in-house. Those routes can keep run histories, retries, error branches and audit evidence when they are configured well. What the buyer still designs and owns is idempotency, escalation paths, access controls and upkeep when an API changes. A US Tech Automations build could configure run logs, an approval step before any write, and a named owner for each failed run, which is the part a hand-built flow often skips. If your review step ends in a chat message, the trigger-to-notification pattern in our monday.com to Slack walkthrough is the closest existing example, and our monday.com review covers the board tool behind it.

A configurable US Tech Automations workflow for spec review would start when a new comment is posted on a spec, if Figma's API exposes that event, so confirm the trigger before any build. It would read the spec through Figma's MCP server, draft a list of open questions, and post that list to the team's Notion page through the Notion API, which addresses a page by its page_id path parameter (Notion API reference). The output is a draft summary, not an edit to the spec. Prerequisites: a Full seat on the account that writes, an MCP-enabled workspace, and a Notion integration shared with the target page. Human review point: a product lead approves the summary before it is posted.

A second proposed workflow runs the other way. When a status property on a Notion requirements page changes to ready for design, US Tech Automations could read the page, use last_edited_time to skip pages already processed, export the content as a Markdown file, and log the run to a tracking sheet. Specs imports .md files, so a designer then drops the file onto the canvas. Prerequisites: a Markdown export path from Notion, confirmed against Notion's documentation before build, and an integration with read access. Human review point: a designer checks the imported spec before the work moves to engineering.

Signal vs Speculation

• Signal: Specs is in open beta and available on paid seats, per the launch post and Figma's pricing page.

• Signal: Specs is not on the free Starter plan, according to PricingSaaS (2026), which reports the pricing page.

• Signal: writing to the canvas through the MCP server requires a Full seat and is free during the beta period, per the MCP overview.

• Not published: file-size caps, specs per file, regional limits, the beta end date and any Specs-specific price. The vendor has not published this.

• Speculation: Specs will replace Notion pages for most product teams. We have no usage data for that, and we do not make the claim.

• Speculation: Collab seats will be enough for reviewers. The vendor has not published this, the scenario above assumes it, and a pilot should test it.

Who this is for

Specs fits a small software team whose product context already lives in Figma files, whose designers and engineers both work on the canvas, and whose engineers already run coding agents against design context. Notion fits a team whose specs are mostly text and whose designs live in other tools. A Markdown-in-Git setup fits a team where engineers own the spec and nobody outside engineering needs to edit it.

Red flags: nobody on the team has a Full seat or plans to take one, the team's designs live outside Figma, or the team needs a fixed feature set that will not change during the beta.

A parallel buyer's guide built on the same kind of criteria is our property management vendor automation platform comparison.

Common mistakes

• Treating the $16 figure as a monthly cost without checking the billing toggle on Professional.

• Buying Full seats for every reviewer. The MCP write path needs a Full seat, but review-only work may not.

• Assuming agent calls are unlimited. Limits differ by seat and plan, and the per-minute cap can bind before the daily one.

• Moving every PRD before the beta ends and the limits are published.

• Letting an agent edit a spec with no named person who approves the change.

Decision checklist

• Are your frames, FigJam boards and code layers already in Figma?

• Does at least one person on the team need a Full seat for agent writes?

• Have you confirmed the billing basis for the Professional price?

• Have you named a human owner who approves every agent edit?

• Can the pilot run without depending on a Specs-specific limit the vendor has not published?

Questions buyers ask first

Is Figma Specs available on the Starter plan?

No, Specs is listed on paid seats only and is not part of the free Starter plan (PricingSaaS).

What does Specs cost per seat?

Specs has no separate price on the pricing page, so budget from the seat prices in the table above, and note that the vendor has not published a Specs-specific price.

Can a coding agent read and update a spec?

Yes, the launch post says a coding agent can read a spec through Figma's MCP server and update it, and the MCP overview says writing to the canvas requires a Full seat.

Should a small team move its PRDs out of Notion this month?

No. Run a pilot on one product area first, because the vendor has not published the beta end date or Specs-specific limits.

Is Specs stable enough for a process your team depends on?

Not yet, in our judgment, because it is in open beta and the vendor has not published when that ends. Keep the source of record where it is until the beta ends and limits are published.

Bottom line for this month

Specs is a real change for teams whose designs and specs already sit in Figma, and it is a pilot decision for everyone else. Start with one product area, confirm the billing basis and which seats can write to the canvas, and keep Notion or your Git repository as the record until the beta ends. If you want a review step built around it once the pilot shows where handoffs stall, see how US Tech Automations configures this.

Sources: Figma launch post, Figma pricing, Figma rate limits, Figma MCP overview, Notion pricing, GitHub pricing, Stack Overflow 2025 AI survey, PricingSaaS