Agents

The specialists

Iterel uses specialized AI agents for different parts of the product workflow. Each agent has a distinct perspective and area of expertise.

Researcher

The Researcher surfaces real user needs, market dynamics, and competitive context. It is deliberately skeptical — it demands evidence and pushes back on assumptions that are not grounded in data.

What it produces: market analysis reports, competitive landscape maps, user personas with demographics and pain points, hypothesis frameworks, interview scripts, and insight cards.

When to use it: when the evidence layer is weak, when you need to validate assumptions, when entering a new market, or when existing research is outdated.

Best input: tell the Researcher what you need validated, not just "do research." For example: "Research whether small business owners would pay for automated invoicing" is better than "research invoicing."

Strategist

The Strategist turns evidence into positioning, product bets, and decision-making structure. It connects dots across research findings and finds winning angles.

What it produces: elevator pitches (multiple versions), business model canvases, product bets with risk assessment, strategic positioning maps, go-to-market plans, success metrics, and decision rationale documents.

When to use it: when you need to decide what to build, who to serve, how to differentiate, or how to prioritize.

Best input: tell the Strategist what decision you need to make. For example: "Help me decide between a freemium model and a paid trial" gives better results than "make a strategy."

Creative Director

The Creative Director shapes naming, tone, brand direction, and overall creative coherence. It works from strategy to create a consistent identity system.

What it produces: brand name options with analysis, color palettes with usage guidance, typography selections with hierarchy, voice and personality guidelines, imagery direction, layout and motion principles, logo concepts, and component pattern guidelines.

When to use it: when the brand identity needs to be established or refined, when visual direction needs to stay consistent across screens, or when the product voice needs definition.

UX Designer

The UX Designer defines flows, interaction logic, and product structure. It focuses on user-centric problem framing and journey mapping.

What it produces: user flow diagrams with screen sequences, decision points, interaction patterns, and architecture summaries showing how screens connect.

When to use it: when the user journey needs mapping, when screen relationships are unclear, or when the experience logic needs restructuring.

UI Designer

The UI Designer turns product direction into refined high-fidelity interfaces. It brings visual craftsmanship and attention to detail.

What it produces: screen layouts, component designs, responsive variations for mobile, tablet, and desktop, visual hierarchies, and design system elements.

When to use it: when the interface needs to be created or polished, when consistency across screens matters, or when preparing for engineering handoff.

Engineer

The Engineer generates implementation with awareness of the full product context — research, strategy, design, and architecture.

What it produces: project scaffolding, component code, API implementations, database schemas, full-stack features, and progressive code generation across phases.

When to use it: when the product direction is clear enough to build, when you need to see how design translates to code, or when iterating on implementation.

Best input: tell the Engineer what behavior to implement, not just "write the code." For example: "Implement the signup flow with email verification using the auth service from the backend plan."

Conductor

The Conductor orchestrates all of the above and helps route work between them. It is the conversational interface you interact with most directly. See the Conductor guide for full details.

How agents collaborate

Agents do not work in isolation. When a task benefits from multiple perspectives, specialists collaborate before delivering output. The depth of collaboration depends on the current mode: more rounds in Explore, fewer in Deliver.

Getting better output

If output feels generic, the fix is usually more context, clearer goals, or better constraints. Each specialist works best with specific, actionable input.

• For the orchestration layer, read Conductor.
• For evidence and direction, read Research and strategy.
• For creative identity, read Creative direction.