Getting StartedSolveBuildIntelligenceLearnHelpWhat's New
SOLVE

Best practices

Best practices for Rocket.new Solve: frame sharper business questions, scope research well, and get actionable, structured reports you can act on quickly.

Solve produces reports that match the quality of your question. Specific, well-scoped prompts return focused analysis you can act on. Vague prompts return broad, generic summaries.

This page covers question framing, follow-up patterns, and iteration strategies that get the most out of every Solve task.

Writing good questions

Think of Solve as a research analyst. Give it context, name constraints, and define your expected output. On Full Solve, Rocket may use prompt intelligence before research begins to resolve ambiguity. Light Solve may ask conversational follow-ups in chat for vague prompts, but it does not use prompt intelligence. You can also reference previous work through @-mentions or attach files and URLs for additional context.

Weak prompts vs. strong prompts

PromptWhy it falls short
"Tell me about the SaaS market"No segment, geography, or specific question
"Who are our competitors?"Solve has no context about who "we" refers to or what market you are in
"What should we build?"No context about your product, users, or constraints
"Is this a good business idea?"No specifics about the idea, market, or success criteria
"Help with pricing"No product details, target market, or competitor benchmarks

Five ways to sharpen your prompt

Follow-up patterns

Use follow-up messages to extract more value from the initial report. Three patterns work well: drill-down, challenge, and pivot.

PatternWhen to useExample sequence
Drill-downYou want more detail on one section of the report1. "Map the competitive landscape for no-code database tools." 2. "Tell me more about Airtable's enterprise strategy. What features do they gate behind enterprise pricing, and how does that compare to Notion?" 3. "If I were building a no-code database for agencies, what 3 features would differentiate me from Airtable?"
ChallengeYou want to stress-test the conclusions1. "Build an investment thesis for vertical SaaS in healthcare." 2. "What is the strongest bear case against this thesis? What would make this investment fail?" 3. "Given those risks, how would you modify the thesis to account for regulatory headwinds?"
PivotAn unexpected finding redirects your research1. "What is the market size for AI tutoring tools for K-12 students?" 2. The report reveals the fastest-growing segment is corporate training. 3. "Pivot to the corporate training market. What does the AI-powered training market look like for companies with 500 or more employees?"

Each pattern follows the same rhythm: start broad, react to findings, then narrow or redirect. You can refine any report directly from the results page.

Iteration strategies

Combining Solve with other capabilities

Solve works well alongside Build and Intelligence.

CombinationHow it works
Solve then BuildResearch a market or feature set with Solve, then use those findings to scope a Build task. For example: "Build a pricing page based on the competitive analysis from my Solve task."
Solve then IntelligenceUse Solve to identify key competitors, then set up an Intelligence task to monitor them continuously.
Intelligence then SolveWhen Intelligence surfaces a significant change, such as a competitor launching a new feature, create a Solve task to analyze the implications.
Solve then SolveChain multiple tasks in a project: market analysis first, then competitive teardown, then pricing strategy. Each task can build on previous findings.

All tasks within a project share the same context. You can @-mention a previous task to bring its findings into any new Solve task without re-entering data.

Common mistakes

MistakeWhat to do instead
Asking multiple unrelated questions in one promptSplit into separate Solve tasks, each focused on one topic
Not providing enough contextInclude your stage, audience, constraints, and what you already know
Taking the first result as finalUse follow-ups to challenge, refine, and deepen the analysis
Ignoring the methodology sectionRead how Solve arrived at its conclusions so you can evaluate confidence
Using Solve when Intelligence is betterIf you need ongoing monitoring, set up an Intelligence task instead of re-running Solve

What's next

On this page