- Type
- Automation concept · agentic search
- Role
- Solo builder: search app, backend workflow, prompts
- Timeline
- 2026
- Client context
- Personal product · open to use
- Architecture
- Next.js frontend → n8n AI agent → Firecrawl + Hunter.io → structured output
“Job hunting and lead research are both search problems. The same agent can do both if it knows what to look for.”
The problem
Finding the right remote role or the right company to sell to still means opening dozens of tabs, reading job boards, checking company sites, and copying details into a spreadsheet. Most of the work is not decision making. It is gathering and filtering.
Stryde treats both tasks as structured search. A user types what they want, and the backend decides whether to hunt jobs, hunt leads, or both, then returns ranked results with a short explanation for each.
Before Stryde
Researchers started with a query, then manually searched job boards, company websites, and LinkedIn, copying titles, URLs, and notes into a document. Signals that a company might need automation services were easy to miss, and the same company was often researched multiple times.
What I built
A Next.js search interface posts a query to an n8n AI agent that calls Firecrawl for web search and URL scraping, and Hunter.io for domain enrichment, returning structured results.
I built a simple search interface backed by an n8n AI agent. In Jobs mode, the agent searches the web for relevant remote roles and returns each with a "Why it fits" note. In Leads mode, it identifies companies showing hiring signals for AI, automation, or process improvement roles, then enriches each company with a domain search via Hunter.io. Structured output keeps the frontend predictable.
The research stack is Firecrawl for web search and URL scraping, and Hunter.io for domain-level contact intelligence. The agent composes these tools rather than relying on a single source, so results are grounded in live pages.
- Natural-language query. The user describes what they want in one sentence instead of filling boolean search forms.
- Jobs mode. Returns remote roles with title, company, URL, and a short explanation of why the role matches the query.
- Leads mode. Returns companies likely to buy AI automation services based on public hiring signals and active company pages.
- Tool orchestration. Firecrawl handles web search and page scraping; Hunter.io enriches company domains with contact signals.
- Structured output. The agent returns strict JSON so the frontend renders cards consistently without extra parsing.
The outcome
Stryde is live as a personal product. The intended outcome is less manual research for job seekers and outbound teams, and a single search box that turns intent into ranked opportunities with reasoning attached.
Stack
Next improvements
- Saved searches. Let users save queries and get daily or weekly email digests of new matches.
- Export to CRM. Push lead results directly into a Notion database, Airtable base, or sales CRM.
- Confidence scoring. Add a relevance score to each result and let users filter by confidence threshold.
Automation flow snapshot
Stryde agentic search flow
Screens from the Stryde search interface and the n8n backend that orchestrates Firecrawl research and Hunter.io enrichment.