Crafting Effective Queries

The quality of your Smart Match results depends on how well you describe your situation. This guide shows you how to write queries that get you the right stack.

Be Specific About Your Use Case

Instead of "I need AI for work," try: "I need AI to write marketing emails and social posts for a 3-person startup. We use Notion and Slack."

The more context you give — role, team size, tools you already use, budget — the better the recommendations. Generic queries return generic stacks.

Use the Context Pills

When Smart Match offers context pills (budget, role, team size), click them. They feed structured data into the system and improve ranking. You can also type freely; pills are shortcuts, not requirements.

Mention Your Budget

Budget is one of the strongest signals. Say "free only," "up to $50/month," or "enterprise budget." The system filters and ranks tools accordingly. Omitting budget often returns a mix that may not fit.

Describe Your Current Stack (If Any)

If you already use certain tools, mention them. "I use ChatGPT Plus and want to add a coding assistant" helps the system avoid overlap and suggest complementary tools.

Answer Follow-Up Questions Fully

The AI may ask 1–5 follow-up questions. Answer each one. Skipping or giving vague answers reduces recommendation quality. If you're unsure, say so — the system can still work with partial context.

Avoid Overly Broad or Vague Language

Vague: "I need the best AI"
Better: "I need AI for code review and documentation. Solo dev, $30/month budget."

The Bottom Line

The best Smart Match sessions are specific: use case, budget, role, team size, and existing tools. Give the system enough signal and you get a stack that actually fits.