Notion Product Roadmap Creation Demo

Demosmith's AI agent was given notion.so and a prompt to build a full product roadmap from scratch — custom database, five properties, six real feature entries, and four views including a filtered high-priority table. No screen recording, no editing.

Prompt used

What the agent did

• Navigated to notion.so and opened the workspace
• Created a new page titled "Product Roadmap"
• Added an inline database to the page
• Created a Status property (select) with 5 color-coded options: Backlog (gray), Planned (yellow), In Progress (blue), Shipped (green), On Hold (red)
• Created a Priority property (select) with 4 options: P0 - Critical (red), P1 - High (orange), P2 - Medium (yellow), P3 - Low (gray)
• Created a Target Launch Date property (date)
• Created a Customer Impact property (multi-select: High, Medium, Low)
• Created an Owner property (text)
• Added 6 feature entries with all properties filled in
• Created a Board view grouped by Status, renamed "By Status"
• Created a Timeline view using Target Launch Date, renamed "Launch Timeline"
• Created a filtered Table view named "High Priority Items" showing only P0 and P1 priorities
• Demonstrated switching between all four views

How it was generated

notion.so was given as the URL along with the prompt above. Demosmith's AI agent opened the workspace, built the database, configured all properties and color options, entered every feature row, created and configured three additional views, applied filters, and navigated between them — then produced the finished video with captions. No recording software, no editing.

---

AI agent builds a Notion product roadmap with custom views and filters from scratch

A product roadmap in Notion is only as useful as its structure. Too few properties and you lose context. Too many and the table becomes unreadable. The video above shows Demosmith's AI agent building one from scratch: five custom properties, six feature entries, four views. Here's what goes into each piece.

Step 1: Create the roadmap page and database

In Notion, click the "+" next to your workspace in the sidebar to create a new page. Give it a clear name — "Product Roadmap" works because it's unambiguous when shared with stakeholders. Add an inline database using the "/" menu and selecting "Table — Inline." Inline tables keep your context (notes, headers, links) on the same page as the database, which is useful for roadmaps that need explanation alongside the data.

Step 2: Configure Status and Priority properties

Click the "+" icon in the table header to add columns. For Status, set the type to "Select" and add five options: Backlog (gray), Planned (yellow), In Progress (blue), Shipped (green), On Hold (red). Color-coding matters — it lets you read the table at a glance without parsing text. For Priority, add another Select property with P0 - Critical, P1 - High, P2 - Medium, and P3 - Low. Using a P0–P3 scale is standard across product and engineering teams, which makes it easier to communicate with both audiences.

Step 3: Add Target Launch Date, Customer Impact, and Owner

Add a Date property called "Target Launch Date." This powers the Timeline view later. Add a Multi-select property called "Customer Impact" with High, Medium, and Low options — multi-select lets you tag a feature with multiple impact levels if needed. Finally, add a Text property called "Owner" to track which team is responsible. Text works better than Person here if ownership is by team rather than individual, since Notion's Person property only works for workspace members.

Step 4: Enter features with real data

The roadmap includes six features: AI-powered search (In Progress, P0, March 15), Mobile app redesign (Planned, P1, April 1), Advanced analytics dashboard (Planned, P2, May 15), SSO enterprise authentication (Backlog, P1, June 1), Dark mode (In Progress, P2, March 30), and API rate limiting improvements (Shipped, P0, February 1). The mix of statuses and priorities is intentional — it makes the Board and filtered views immediately meaningful rather than showing everything in one column or tier.

Step 5: Create a Board view grouped by Status

Click "+ Add a view" and select Board. When prompted, group by Status. Notion creates columns for each status option — Backlog, Planned, In Progress, Shipped, On Hold. Features appear as cards in their respective columns. Rename this view "By Status" so team members know what they're looking at when they open the database. Board view is the most common way to run a roadmap review: you can see what's active, what's queued, and what shipped without opening individual rows.

Step 6: Create a Timeline view

Add another view and select Timeline. Notion will use Target Launch Date as the date field automatically. Rename this view "Launch Timeline." The timeline shows features as horizontal bars plotted by their launch dates — useful for spotting bunching (too many things launching in the same week) and gaps (long stretches with nothing shipping). You can drag bars to adjust dates directly in the timeline, though that's best done after the initial structure is in place.

Step 7: Create a filtered High Priority view

Add a fourth view — another Table. Rename it "High Priority Items." Then click the filter icon and add two filter rules connected by "Or": Priority is P0 - Critical, or Priority is P1 - High. This view now shows only the features that need immediate attention, without permanently hiding the others. It's particularly useful for engineering leads who want to see only their highest-priority work without context-switching to Jira or another tool.

How Demosmith generated this video

That's Demosmith's AI agent actually navigating Notion — not a screen recording of a human. We gave it notion.so and the prompt above. It opened the workspace, created the page, built the database, set up each property with the right type and color coding, filled in all six feature rows, created three additional views, applied the filter logic, and demonstrated switching between them. The final video came out with captions included. No screen recorder, no editing session.

Notion was a good test for Demosmith because it's not a linear flow — the agent had to work with Notion's property editor, multiple view types, and filter configuration. If you're demoing a SaaS product, the process is the same: paste your URL, describe the flow, and Demosmith handles the rest.