AboutHow It WorksPricingFAQSign inGet started
Tree

What this app is, what it became, and what it should be.

This page is the clean map. It shows the current route tree, the workflow spine, the agent system, and the proposed ship-ready structure. No renaming happens here. This is for clarity before any restructure work.

Red = current confusion
Blue = routes and tree
Teal = workflow spine
Purple = agents
Green = proposed ship path
Current Read

The product is strongest as a workflow tool, but the current URL tree still presents multiple competing centers: dashboard, workflows, live, onboarding. That is what creates confusion.

`/dashboard` reads like one app.
`/dashboard/workflows` reads like another app.
`/live` reads like another front door.
`/onboarding` reads like another product layer.
Flow View

This is the product as a flow, not just as a tree. The user gives inputs, the workflow and agents act on them, outputs are produced, and the runtime tracks what happened.

Inputs
offer link
niche
objective
offer type
audience
platforms
brand inputs
affiliate link
creative references
run settings
→
Workflow Actions
research
hook generation
offer shaping
script writing
creative assembly
landing page build
distribution prep
agent decisions
→
Outputs
hooks
scripts
reels
images
landing pages
offers / CTAs
DM + email copy
ad packages
→
Runtime / Tracking
metrics
run history
agent log
prompt layer
event bus
task queue
worker cycles
quota / billing
The missing clarity was this: the tree shows where things live, but the flow shows how the product actually behaves. Investors need both.
Current Trunk

This is the present top-level shape of the product story.

/
  marketing
  dashboard
    many tools
    workflows
  live
  onboarding
  pricing
Proposed Trunk

This is the structure that best matches what the product actually is.

/
  pricing
  workflows
  settings

workflows/
  input
  canvas
  runs
  outputs
  metrics
  agents
Current App Routes

These are the user-facing app routes that currently exist.

/
/about
/brand
/brand2
/brand3
/checkout
/contact
/dashboard
/dashboard/accounts
/dashboard/affiliates
/dashboard/analytics
/dashboard/approvals
/dashboard/audience
/dashboard/brands
/dashboard/campaigns
/dashboard/copy
/dashboard/creatives
/dashboard/dms
/dashboard/email
/dashboard/growth-command
/dashboard/intelligence
/dashboard/landing-pages
/dashboard/leaderboard
/dashboard/library
/dashboard/marketplace
/dashboard/native-ads
/dashboard/nurture
/dashboard/offers
/dashboard/outreach
/dashboard/pipeline
/dashboard/pipeline-crm
/dashboard/profile
/dashboard/research
/dashboard/revenue
/dashboard/settings
/dashboard/solo-ads
/dashboard/teams
/dashboard/viral
/dashboard/vsl
/dashboard/workflows
/demo
/faq
/how-it-works
/legal
/live
/login
/mindmap
/onboarding
/pricing
/sitemap
/support
API Groups

These are the major backend route families sitting under `/api`.

/api/admin
/api/ads
/api/agents
/api/auth
/api/chat
/api/checkout
/api/copilot
/api/cron
/api/data
/api/flow-runs
/api/flows
/api/live
/api/observe
/api/onboarding
/api/stripe
/api/teams
/api/uploads
/api/webhooks
/api/whop
Workflow Spine

This is the actual operating chain of the product.

UI
  -> workflows canvas
  -> workflow engine
  -> event bus
  -> task queue
  -> worker
  -> agents / teams
  -> results / metrics / outputs
What The Product Really Is

Under the current surface clutter, the core product is already clear.

A workflow canvas
A flow execution engine
A metrics and outputs layer
An event-bus and task-queue backend
A set of specialist agents and teams
A billing gate controlling flows
Agent Tree

These are the major agent groups operating behind the app.

Research / Discovery
trend-agent
market-intelligence
research-team
cross-niche-agent
b2b-hunter-agent
Content / Creative
hook-agent
script-agent
media-agent
creative-team
production-team
variation-agent
vsl-agent
persona-agent
audience-clone-agent
Offer / Monetization
offer-agent
offer-architect
affiliate-agent
marketplace-agent
native-ad-agent
solo-ad-agent
deal-flow-agent
Distribution / Outreach
publish-agent
distribution-team
outreach-agent
nurture-agent
messaging-gateway
sales-team
Analytics / Optimization
analytics-agent
revenue-forecast-agent
amplification-agent
leaderboard-agent
ab-testing
intelligence-team
Retention / Lifecycle
cart-rescue-agent
reactivation-agent
retention-agent
digest-agent
expansion-agent
System / Orchestration
conductor
provisioning-agent
account-provisioner
memory
activity-bus
gemini
llm
Keep

These belong in the investor-facing product structure.

`/` marketing
`/pricing` pricing
`/workflows` product trunk
`/settings` configuration
Demote

These should stop acting like primary product centers.

`/dashboard` summary only
`/live` secondary proof
`/onboarding` setup layer, not product trunk
Integrate

These should live inside workflows, not beside it.

Link input
Canvas
Runs
Outputs
Metrics
Agents
Ship Proposal

This is the clean direction to ship against today without pretending the product is multiple separate apps.

/
  pricing
  workflows
  settings

workflows/
  input
  canvas
  runs
  outputs
  metrics
  agents
The product should open on workflows, not split attention between dashboard and workflows.
The first visible action inside workflows should be: paste your link.
Metrics should be attached to the workflow surface, not isolated as a competing home.
Agents and event-bus behavior should be visible inside the workflow context, not hidden in scattered surfaces.
Complete Proposal

This is the full ship proposal, not just the URL trunk. It includes the front door, the workflow surface, the agent layer, the LLM layer, and the runtime that actually powers the product.

/
  pricing
  workflows
  settings

workflows/
  input
  canvas
  outputs
  metrics
  runs
  agents
  prompts

system/
  llm layer
  agent teams
  event bus
  task queue
  worker cycles
  billing / quota
  storage
What Must Be Visible

If investors are evaluating the product, these layers must be legible in the structure and in the UI.

Input: paste link, choose objective, start workflow
Canvas: the workflow itself is the product surface
Metrics: performance lives with the workflow, not in a detached dashboard
Agents: visible specialist systems working inside the workflow
LLM: prompt and reasoning layer powering research, scripts, offers, and decisions
Runtime: event bus, queue, worker cycles, quota, and storage underneath
Workflow Outputs

This is what a workflow must visibly produce. Without this layer, the proposal is incomplete.

outputs/
  hooks
  scripts
  reels
  images
  landing-pages
  offers
  affiliate-links
  dm-copy
  email-copy
  ad-packages
  reports
  decisions
What The User Gets

The workflow is not the deliverable by itself. The user is buying the outputs the workflow generates and the metrics tied back to them.

Content outputs: hooks, scripts, reels, images, landing pages
Monetization outputs: offers, CTAs, affiliate links, ad packages
Sales outputs: DM copy, email copy, nurture material
Operational outputs: run history, reports, agent decisions, performance metrics