Skip to main content
1

Start the Conversation

Located below the mode toggle, the “What should I build?” button initiates a guided interview. Instead of expecting you to have technical specs, Architect starts by understanding you.
What should I build button
2

The Interview Process

Identity Verification

First, Architect establishes who you are. This information is used to personalize the final application (e.g., adding your name to the dashboard header).
User Details

Role Analysis

Architect asks for your job role. It cross-references this with a database of common industry bottlenecks.
Role SelectionRole Context

Pain Point Discovery

This is the critical step. Architect asks: “Where does your time go?” It presents role-specific time sinks. This allows it to calculate the potential ROI of the app.
Pain Points

Stack Integration

It asks what tools you already use (Slack, HubSpot, Jira). This ensures the recommended agents aren’t siloed.
Tool SelectionExtra Context
3

The Proposals

Based on your inputs, Architect doesn’t just give you an idea—it gives you a spec. It generates 3 tailored “Agent Cards” complete with capability lists and time-savings estimates.
Final Recommendations

10h+

Weekly Time Saved

3

Tailored Solutions

1-Click

To Generate PRD