Prodigy Pro logo Prodigy Pro
Get started
Docs v1.0 · Guides

Everything you need to run a venture in Prodigy.

Prodigy is a single workspace for taking a venture from idea to pilot: tasks, roadmap, validation, contacts, forms, and automations, all in one place. This guide covers every part of the product, from the sidebar structure down to the individual fields on a record.

Overview

The shape of the product, in one page.

Prodigy organizes work around a venture, the company or project you are building. Every task, contact, document, idea, milestone, and automation belongs to exactly one venture, and you can run several ventures from the same account, switching between them from the venture switcher at the top of the sidebar the same way you would switch between projects in a database tool.

Inside a venture, work is split into four groups in the sidebar, in the order you would actually touch them while building:

  • Workspace: Overview, Tasks, Roadmap, Ideas, and Validation. The day-to-day view of what is moving right now.
  • Records: Contacts, Documents, and Research. The durable information your venture accumulates over time and refers back to.
  • Operate: Inbox, Automations, Forms, Analytics, and Activity. The systems that keep the venture running and the record of what happened.
  • Data: Imports and Exports. Getting existing records in, and getting everything back out, in CSV form.

The Overview page itself is a single-screen summary of the active venture: its current stage on the founder workflow (Idea, Validation, MVP, Launch), the milestone you are actively working through, tasks due soon, a validation snapshot, and a feed of recent activity across every record type in the venture.

Every workspace that holds a list of records supports list, board, or table layouts where relevant, plus saved views, filters, sorting, and grouping. Pick whichever layout matches how you think about that particular kind of data; the underlying records are identical no matter which layout you are looking at them through.

Ventures

One account, many ventures.

Create a new venture from the + button in the top bar, from the venture switcher at the top of the sidebar, or from the "All ventures" grid, which lists every venture on the account as a card with a quick stat rollup (milestones and tasks completed) so you can see the state of each one without opening it.

Each new venture starts from a template: Startup, STEM Innovation, or Social Impact, each of which seeds a sensible starting roadmap suited to that kind of venture, or you can start from a blank slate and build the roadmap yourself. A separate, more detailed set of starting structures lives under Templates (see below) for founders who want a fuller head start than the three basic options.

Switching ventures swaps every workspace to that venture's data instantly. Nothing is shared between ventures except your account-level profile, your avatar, and your account settings; tasks, contacts, documents, and everything else stay fully separated per venture.

Naming, theming, and identity

Open "Customize venture" from a venture's options menu to give it an emoji icon and a curated accent theme (Sage, Ocean, Amber, Lavender, Rose, Sky, Sand, or Slate, plus a custom color if you want one) and an optional soft cover wash. The theme shows up in the venture switcher, the Overview header, and the venture's card in the "All ventures" grid; it never recolors the rest of the product, so the workspace itself stays consistent no matter which venture's theme is applied.

Roadmap & milestones

The path from idea to launch.

The roadmap is an ordered list of milestones, for example Customer discovery, then MVP, then Pilot, then Launch. Each milestone tracks a due date, a completion state, and the tasks that make it real. Drag milestones to reorder them, and open one to see its task list, its progress bar, and an activity log scoped to just that milestone.

Milestones also drive the "Founder workflow" indicator shown on Overview: Idea, Validation, MVP, and Launch. As you complete milestones and update the venture's stage, that indicator advances, and reaching Launch (or completing onboarding, or shipping your first MVP) triggers a small celebratory moment rather than a routine notification, since those are the genuinely rare, meaningful transitions in a venture's life.

Setting a due date

Click Set date on a milestone to open the calendar picker. Clear a date at any time from the same picker. Milestones without a date still sort by their manual order in the roadmap; a date is optional context, not a requirement.

Templates

Start from a pre-built venture structure.

Beyond the three basic templates offered at venture creation, the Templates workspace holds a small library of fuller starting points, each tagged by the kind of venture it fits: SaaS Startup (tasks, milestones, and validation tracks for a software product), Consumer App (a rapid-iteration template for consumer mobile or web products), Hardware + IoT (a milestone-heavy template tracking design, prototype, and production phases), and Research Venture (a hypothesis to experiment to insight pipeline for deep-tech ventures). Applying a template seeds the relevant starting records into your venture; it does not lock you into any particular workflow afterward.

Tasks

Everything moving, in one list.

Tasks can be viewed as a list, a board grouped by status, or a table, and can be filtered, sorted, and grouped by any property, including custom properties you define yourself. Press N anywhere in Tasks to create one instantly. Every task carries a status, a priority, an owner, and an optional due date, and can be linked to a milestone so progress rolls up to the roadmap automatically as tasks under that milestone get completed.

Tasks can also be created from other places in the product: converting an idea into a task, breaking a milestone into a starter set of tasks from its inspector, or letting Ask Prodigy draft a task breakdown for you to review before it is added.

Ideas

Capture first, evaluate later.

A lightweight backlog for anything worth remembering: feature ideas, pivots, things a customer said in passing. Each idea has a stage (New, Exploring, Validated, Building, or Shelved), a priority, and an optional score, so a growing backlog can still be triaged quickly. Promote an idea into a task once it is worth acting on, or into a validation assumption once it is worth testing formally; either conversion keeps a relation back to the original idea so you can trace where the work came from.

Validation

Assumptions, evidence, and experiments.

Validation is where you track what has to be true for the venture to work. Write an assumption (the thing you are betting on), design an experiment to test it, and log the evidence you gather as supporting, contradicting, or untested. This is the same problem, build, measure loop taught in most lean-startup curricula, built directly into the workspace instead of living in a separate document.

Assumptions carry a confidence level and a status that updates as evidence comes in, so the Validation tab always reflects your current read on the venture's riskiest bets, not just a static list you wrote once and never revisited.

Contacts

Everyone connected to the venture.

Advisors, customers, investors, teammates: one record type covers all of them, distinguished by a type field rather than living in separate lists. Set follow-up reminders on a contact and Prodigy will surface upcoming and overdue ones in your notifications and on Overview, so a promised follow-up does not quietly slip.

Documents

Free-form pages for anything narrative.

Documents are a block-based editor for pitch decks, notes, and memos: headings, bullet and numbered lists, checklists, callouts, plain text, and tables, composed freely on one page per document. Blocks can link back to a task, a milestone, an assumption, or a growth metric, showing up as a small linked chip inline, so a document can reference the exact record it is describing without duplicating that information by hand.

Use "Save version" on a document to snapshot its current state. Saved versions are kept per document so you can look back at how a pitch deck or a set of notes evolved, without needing a separate version-control system for a page of prose.

Research

Structured reference material, kept separate from Documents.

Research holds sources you are collecting while validating the venture: articles, benchmarks, interview notes, competitor teardowns. Each item tracks a title, a source, an author, a status (unread, reading, or done), and free-form notes, which keeps it distinct from Documents so ongoing reference material does not get lost in a growing pile of narrative pages. A research item can be converted directly into a piece of validation evidence once it actually informs a decision.

Inbox

Drafts and things waiting on you.

Overdue tasks, upcoming follow-ups, pending reminders, form responses, and anything an automation queued up for review all land here before they go out or get filed elsewhere. When there is nothing waiting on you, Inbox simply says so; it is meant to be checked and cleared, not treated as a permanent archive.

Automations

Trigger actions automatically when workspace events occur.

An automation has three parts:

  • When: the trigger, such as a record being created, a record being updated, or a status field changing value.
  • If: optional conditions that must match for the automation to run, checked against the specific record that triggered it.
  • Then: one or more actions, such as creating an inbox item, sending a notification, or updating another record.

Use Test on any automation to run it once immediately and check the result in Run history before relying on it. Automations are evaluated server-side against your workspace data, and each run is idempotent per triggering record, so a retried or duplicate event cannot fire the same automation twice for the same underlying change.

Forms

Collect structured input from anyone, no login required.

Forms map responses directly into workspace records: a form can create a contact, an idea, or a piece of validation evidence, depending on how its fields are mapped. Share the form's public link with customers, advisors, or your team; the person filling it out never needs an account or access to your workspace, and the response arrives already structured into the right record type instead of a spreadsheet you have to reconcile by hand.

Analytics

How the venture is trending.

Analytics reports on momentum across the venture: a health score with the specific factors driving it, task velocity over time, task and milestone status breakdowns, validation progress, and growth metrics you are tracking, organized into tabs (Overview, Tasks, Milestones, Validation, Ideas, Growth, Contacts, Activity) so you can drill into whichever slice matters for a given check-in with yourself, a mentor, or an investor. Every number on the page is clickable through to the underlying records behind it, so a chart is always a starting point for a closer look, not a dead end.

Activity

The record of what happened, across every record type.

Activity is a chronological feed of every meaningful change in a venture: records created, fields changed, milestones completed, contacts added. It is the same feed that powers the "Recent activity" panel on Overview, shown here in full with more history, useful when you need to reconstruct how a decision was actually made rather than relying on memory.

Imports & exports

Getting existing data in, and everything back out.

Export any record type to CSV at any time from the Exports workspace: tasks, contacts, ideas, milestones, and more, each as a clean flat file suited to a spreadsheet or another tool. Import existing data the same way from the Imports workspace by mapping spreadsheet columns onto Prodigy fields, which is typically the fastest way to bring an existing task list or contact list into a new venture rather than re-entering everything by hand.

Integrations

Connect the tools you already use.

IntegrationWhat it does
Google DriveAttach Drive files directly to records.
Google CalendarSend tasks and milestones to your calendar.
SlackSend records and automation output to a channel.
NotionLink Notion pages to Prodigy records.
DropboxLink Dropbox files to records.

Manage connections from Settings, then Integrations. Each connection is authorized per account through the provider's own sign-in flow, so Prodigy never stores your provider password, only a scoped access token you can revoke at any time from the same screen.

Ask Prodigy

A quiet AI layer over your workspace data.

Ask Prodigy answers questions using your venture's real, live data: tasks, milestones, contacts, and validation evidence, not a generic model response, and can take actions like drafting a task breakdown or a validation plan for you to review before anything is created. It opens as a panel from the sidebar or the floating shortcut, stays out of the way until you open it, and never appears as a talking avatar inside your workspace content; it reads like a document, in keeping with the rest of the product.

Personalization

A serious workspace with a little warmth, not a costume.

Your profile avatar can be generated in one of several curated styles (Avataaars, Notionists, Lorelei, Personas, Open Peeps, or Pixel), each fully customizable down to individual features like hair, accessories, and color, with only the options that particular style actually supports ever shown to you. Change it from Settings, then Profile.

Ventures can be given an emoji icon and a curated accent theme, described under Ventures above. Meaningful milestones, such as completing a milestone, reaching your first validated assumption, or launching, trigger a brief, restrained celebration rather than a constant stream of small animations; routine actions like checking off an ordinary task stay quiet on purpose. Every celebration respects your system's reduced-motion setting and Prodigy's own motion preference in Settings, so it can be turned off entirely without losing the underlying success confirmation.

Appearance preferences, including light or dark theme, density, and font size, live in Settings, then Appearance, and apply across every workspace immediately.

Privacy & student data

Prodigy is built for students and young founders, many of them minors, so data handling is treated as a first-class requirement, not an afterthought.

Every workspace is isolated at the database level with row-level security, so a member of one workspace cannot read, list, or modify another workspace's ventures, tasks, contacts, documents, or any other record, even by guessing an ID directly. This isolation is enforced on the server for every request, not just hidden in the interface, and it has been specifically audited and hardened against cross-tenant access bugs.

Prodigy does not sell student or workspace data, does not run advertising, and does not use workspace content to train any AI model. When you use Ask Prodigy, only the specific records relevant to your question are sent to the AI provider to generate that one answer; nothing is retained by the provider for training, and nothing is shared with other workspaces.

All content entered into Prodigy, including anything typed by a student, is escaped before it is ever rendered back in the browser, closing off a common way untrusted text can be turned into a code-execution attack (stored cross-site scripting). Passwords are never visible to Prodigy staff: authentication is handled by Supabase Auth, and connected third-party accounts (Google Drive, Calendar, Slack, Notion, Dropbox) are authorized through the provider's own OAuth sign-in screen, so Prodigy holds a revocable access token rather than a password.

Educators, mentors, or program administrators who set up a shared workspace for a cohort of students can see the ventures and activity inside that workspace, the same way any workspace member can, which is what makes light adult oversight of a class or program possible without requiring a separate admin product. Students are never asked for information beyond an email address and a display name to create an account.

Any workspace member can delete a record they created at any time, which removes it from the workspace immediately. To close an account entirely and have its personal data removed, contact support at the email address used to sign up; this is handled directly by a person, not a self-serve toggle, specifically so a parent, guardian, or school administrator has a clear, accountable point of contact for a request involving a minor's data. Full detail on what is collected, where it lives, and who it is shared with is in the Privacy Policy.

Developer

API reference and workspace diagnostics.

The Developer workspace previews the REST API that is planned for a future release: endpoints for listing and creating tasks, contacts, ideas, and milestones, plus a workspace health summary, each shown with its method and path so you can see the intended shape of the interface ahead of time. Webhooks for real-time record events are planned alongside it. Neither is available yet; both are shown here clearly labeled as upcoming rather than implied to already work, and the same page also shows a live count of every record type in your current workspace as a quick diagnostic.

Keyboard shortcuts

For getting around without the mouse.

ShortcutAction
⌘KOpen the command menu
G then TGo to Tasks
G then RGo to Roadmap
G then OGo to Overview
CQuick create
NNew task (inside Tasks)
EscClose the open panel or dialog

API & data

Prodigy is built on Supabase.

Every workspace is backed by Postgres with row-level security enforcing per-workspace isolation, so your data is never visible to other accounts, even other accounts belonging to the same person. Export any record type to CSV at any time from Data, then Exports, and import existing data the same way from Data, then Imports.