Product Requirements Document

One Agentic — "Getting Started" Onboarding

Requirements for the three-task onboarding checklist shown to new users, guiding them from first login to running their first AI-powered startup screening workflow.

Status
Draft
Tasks
3 steps
Date
6 May 2026
Owner
Product · Growth

Goal

North star: Get every new user to a fully running startup screening workflow — from first message with NEO to an automated report landing in someone's inbox — within their first session.

Why 3 tasks

  • Short enough to complete in one session (15–20 min)
  • Each step builds directly on the previous one
  • Completion = user has experienced the full product loop
  • Minimises time-to-value for investors and accelerators

Target users

  • VC analysts screening inbound deal flow
  • Accelerator program managers reviewing applications
  • Angel investors managing their own pipeline

Task Requirements

3 tasks
1
Say Hi to NEO
Meet your AI agent
P0
Intent
Break the ice. New users should immediately feel that NEO is approachable and useful — not intimidating. The first interaction sets the tone for whether they'll invest in learning the platform.
Entry point
Clicking this task opens the NEO chat interface directly, pre-focused and ready to receive a message.
Proposed user experience
1
User clicks task → NEO chat opens with a warm greeting: "Hi! I'm NEO, your AI agent. I can help you screen startups, summarise pitch decks, and automate your deal flow. What would you like to do first?"
2
User sends any message → NEO responds naturally. If the user seems unsure what to ask, NEO proactively suggests: "Try asking me to summarise a startup, or I can walk you through setting up your first workflow."
3
Task auto-completes after the user sends their first message. Checkbox ticks, progress updates.
Completion trigger
User sends ≥1 message to NEO
Design notes
  • Pre-populate 2–3 suggested prompt chips (e.g. "What can you do?", "Screen a startup for me", "How do workflows work?")
  • NEO's greeting should use the user's first name if available
  • Keep NEO's tone conversational, not corporate
2
Create a form
Ask NEO to build your founder intake form
P0
Intent
Give the user a live intake form they can share with founders immediately — built entirely through conversation with NEO, with no manual field-dragging or configuration required.
Entry point
Clicking the task opens the NEO chat on the Forms screen. NEO greets the user with a prompt to describe what they want to capture.
Proposed user experience
1
NEO opens on the Forms screen and prompts: "Tell me what information you'd like to collect from founders — I'll build the form for you."
2
User describes their needs in plain language (e.g. "I need their name, email, company name, a short pitch, what stage they're at, and a pitch deck upload"). NEO visually creates the form fields in real time on the canvas as the user types.
3
User reviews the live form preview. They can ask NEO to adjust inline — "Make the pitch deck field required" or "Add a sector dropdown" — and NEO updates the canvas immediately, no manual editing needed.
4
User clicks "Publish" → form gets a shareable link. NEO confirms completion and transitions the user: "Your form is live. Ready to build the workflow that processes submissions?" with a CTA to Task 3.
Completion trigger
User publishes a form (status = active)
Design notes
  • NEO must navigate the user to the Forms screen automatically when the task is clicked — the user should never have to find it themselves
  • Form fields should appear on the canvas as NEO generates them, making the AI feel fast and visual rather than just conversational
  • The form created here is automatically available as the trigger source in the Task 3 workflow
  • Show a "Preview as founder" button so users can see exactly what submitters will experience
3
Create your first workflow
Ask NEO to build a screening & report workflow
P0
Intent
Deliver the "aha moment" — the user describes the automation they want in plain language, and NEO builds the entire workflow on the canvas without any node-dragging. A founder submits the form → an AI step screens the startup → a report is emailed automatically.
Entry point
Clicking the task opens the NEO chat on the Workflow canvas screen, with the form from Task 2 already available as context.
Proposed user experience
1
NEO opens on the Workflow screen and prompts: "Tell me what you'd like to automate — I'll build the workflow for you." It also suggests: "Want me to build a screening workflow for your founder form?"
2
User describes the workflow in plain language (e.g. "When someone submits my founder form, screen their startup using the pitch deck, generate a report, and email it to me"). NEO builds the nodes on the canvas in real time: Trigger → AI Screen → Generate Report → Send Email.
3
User reviews the canvas. Each node is labelled and shows a summary of what it does. The user can ask NEO to adjust any step conversationally — "Also send a Slack message to my team" or "Change the email recipient to my partner" — and NEO updates the canvas without the user touching a node.
4
User clicks "Activate" → workflow goes live. NEO confirms: "Your workflow is running. Every time a founder submits your form, a screening report will land in your inbox automatically."
5
Task auto-completes. All 3 tasks checked. Celebration state fires with CTAs to share the form or view the live workflow.
Workflow nodes NEO should build
T
Trigger: New submission on the form created in Task 2
1
AI Screen: An AI step that reads the submitted pitch deck and form answers, then outputs a structured screening assessment (problem, solution, market, team, traction, risks, recommendation)
2
Generate Report: Formats the AI output into a readable report document
3
Send Email: Emails the report to the user (defaulting to their signed-in address)
Completion trigger
User activates the workflow (status = active)
Design notes
  • NEO must navigate the user to the Workflow screen automatically — the user should never need to find it themselves
  • Nodes should appear on the canvas as NEO generates them, making the build feel instant and visual
  • Offer a "Test run" option so the user can submit a dummy entry and see a real report in their inbox before going live
  • Email step defaults to the signed-in user's address; adding recipients should be a simple ask to NEO (e.g. "Also send it to john@fund.com")

All Tasks Complete — What Happens Next

When all 3 tasks are checked off, the checklist transitions to a completion state:

  • Brief celebration animation (confetti or similar — keep it subtle)
  • Copy: "You're set up! Share your form and let NEO do the screening."
  • Two CTAs: "Share your form" (copies the form link) and "View your workflow"
  • The checklist section is then replaced by a compact "Your activity" summary widget showing submissions received and workflows run

Success Metrics

MetricTargetWindow
Task 1 completion (first NEO message) ≥ 85% Day 1
Task 2 completion (form published) ≥ 65% Day 1
Task 3 completion (workflow activated) ≥ 45% Day 1
All 3 tasks completed in one session ≥ 40% Day 1
Form shared externally (link copied or emailed) ≥ 35% Day 3
First real form submission received ≥ 25% Day 7

Open Questions

Q1
Should Task 2 (form) be a hard prerequisite for Task 3 (workflow), or can a user build the workflow first and connect a form later? Locking the order reduces confusion but reduces flexibility.
Q2
What is the default NEO screening prompt in the workflow template? This needs to be agreed with the product team — it defines the quality of the first report a user sees and is critical for the "aha moment".
Q3
Should the "test run" in Task 3 use a real dummy pitch deck, or let the user upload their own test file? A curated dummy (e.g. a fictional startup deck) avoids setup friction and gives a consistently impressive demo.
Q4
Does the checklist show to all team members in a workspace, or only the user who created it? If a colleague joins later, should they see the same tasks or a different "get up to speed" variant?
Q5
Should accelerators remain in scope as a target user segment? They are currently referenced in the "Why 3 tasks" rationale but may be removed — decision pending.
One Agentic · Getting Started PRD · Draft · May 2026