Marketing

Import prospects, manage status, and edit outreach drafts. Draft reset build

Tavily Lab

Company	Status	Email confidence	Segment	Fit	Score	Contacts	Drafts	Sent	Best angle
Loading prospects...

I want you to run Deep Research for RouteIQ prospecting.

RouteIQ is a warehouse-routing decision tool for ecommerce, 3PL, fulfillment, distribution, and multi-node shipping operations. We are looking for companies where warehouse routing decisions actually matter: multiple fulfillment nodes, inventory split across warehouses, 3PL client-specific rules, ship-from-store or regional fulfillment, bulky/heavy/high-cost-to-ship products, service-promise pressure, avoidable splits, backup warehouse decisions, manual WMS rules, spreadsheets, or a need to explain â€œwhy did this order ship from here?â€

Find companies that are likely good RouteIQ prospects. Prioritize:
- 3PLs and fulfillment providers
- Multi-warehouse ecommerce brands
- Distributors with ecommerce/DTC fulfillment
- Retailers or brands with regional fulfillment
- Marketplace sellers with meaningful order volume
- Companies with operational complexity where ship-from logic, split avoidance, inventory position, delivery promise, and client/channel rules may conflict

For each company, find useful contacts when possible. Prioritize operations and fulfillment contacts first:
- VP / Director / Manager of Operations
- Fulfillment leadership
- Warehouse operations
- Logistics / transportation
- Supply chain
- Ecommerce operations
- COO / Head of Ops
- Founder / CEO for smaller companies

If those contacts are not available, or if there are multiple strong contacts worth including, broaden the search to technology and systems leaders who may own or influence fulfillment routing tools:
- VP / Director / Manager of Technology
- Product leaders for ecommerce, fulfillment, order management, or supply chain systems
- Engineering leaders connected to ecommerce, WMS, OMS, logistics, or internal operations tools
- Data / analytics leaders supporting fulfillment, logistics, or supply chain
- IT / systems leaders responsible for WMS, OMS, ERP, or ecommerce integrations

Reason: operations teams may feel the routing pain, but technology/product/data teams may care because they would otherwise have to build, maintain, or explain warehouse-routing logic internally.

Output a CSV only. Return raw CSV text only. Do not wrap it in a markdown table or code block. Quote fields when needed, especially draft_body, notes, and source fields. Use exactly these headers in this exact order:

company_name,website,segment,industry,company_type,fit_tier,fit_score,fit_reason,warehouse_signals,routing_signals,pain_signals,tech_signals,source_urls,contact_name,contact_title,contact_email,contact_linkedin,contact_source_url,email_confidence,recommended_angle,draft_subject,draft_body,notes,status

Rules:
- One CSV row = one company/contact/draft pairing.
- If a company has multiple good contacts, repeat the company-level fields on each row and vary the contact fields.
- If possible, customize draft_subject and draft_body for that specific contact.
- Do not put multiple contacts or emails in one field.
- Fill every canonical field wherever possible.
- Use source_urls for evidence URLs, separated by spaces.
- Use contact_source_url for where the contact information came from.
- email_confidence should be high, medium, low, or unknown.
- Email discovery is a core goal. Search hard for named contacts and usable business email addresses.
- Prefer verified direct business emails from company pages, press releases, author pages, conference bios, public directories, or other public sources.
- If a verified direct email is not found, infer a likely business email only when there is public evidence of the company's email pattern, a masked-email clue, or a credible third-party source.
- Put inferred emails in contact_email when the inference is defensible.
- Set email_confidence to high only for emails directly shown by a reliable public source.
- Set email_confidence to medium when a credible third-party source shows the email or when the company pattern is strongly supported.
- Set email_confidence to low when the email is pattern-inferred or reconstructed from masked clues.
- Explain the email basis in notes, such as "verified on company page", "third-party source", "inferred from first.last pattern", or "masked-email clue plus company domain".
- Do not fabricate emails. If there is no verified email, credible third-party email, supported pattern, or masked-email clue, leave contact_email blank and set email_confidence to unknown.
- Do not write "unspecified", "unknown", "not found", "N/A", "none", or any other placeholder text in contact_email.
- The final answer must be raw CSV text directly in the chat message. Do not create a prose report, research memo, markdown table, Word/PDF-style artifact, or download-only output.
- Do not include an intro, explanation, summary, citations section, notes outside the CSV, or commentary before or after the CSV.
- Preserve valid CSV formatting: quote fields containing commas, quotation marks, or line breaks.
- Escape quotation marks inside fields by doubling them.
- Multi-paragraph draft_body values are allowed, but they must remain inside one quoted CSV field.
- Before final output, validate that each data row has exactly the same number of fields as the header row.
- status should usually be new unless there is a reason to mark do_not_contact or needs_review.
- fit_score should be 0-100.
- fit_tier should be A, B, C, or D.
- recommended_angle must usually be one of these supported message angles: pain_question, routing_visibility_gap, routing_governance, routing_audit_offer.
- Use pain_question for a soft opener built around a thoughtful operational question.
- Use routing_visibility_gap when the message should focus on explainability, auditability, or answering "why did this order ship from here?"
- Use routing_governance when the message should focus on control, rules, exceptions, customer/channel-specific logic, or scaling routing decisions across sites.
- Use routing_audit_offer when the message should make a clearer CTA offering a quick routing review/audit.
- For each strong contact, create 2-4 outreach variants as separate CSV rows when useful. Reuse the same company/contact fields, but vary recommended_angle, draft_subject, and draft_body.
- Do not create filler variants. Only create multiple message angles when the copy is meaningfully different and supported by the research.
- If only one angle makes sense for a contact, output one strong row rather than weak duplicates.
Research depth requirements:
- Fill out the CSV as thoroughly as possible. These fields are not administrative busywork â€” they directly drive the email copy, filtering, prioritization, and review workflow.
- Go deep on each company. Look for concrete, specific evidence about fulfillment footprint, warehouse locations, shipping complexity, product type, ecommerce/DTC activity, 3PL/client complexity, WMS/OMS/ecommerce tech stack, routing rules, inventory positioning, service promises, expansion, hiring, or operational pain.
- Prefer fewer high-quality, deeply researched prospects over many shallow leads.
- Avoid generic claims like â€œmay benefit from optimizationâ€ unless they are tied to a real researched signal.
- Every fit_reason should explain why RouteIQ specifically might matter for that company.
- warehouse_signals should include concrete evidence of warehouses, fulfillment centers, regions, nodes, 3PL network, ship-from-store, or distribution footprint.
- routing_signals should explain why warehouse-choice logic may be non-obvious.
- pain_signals should include specific operational clues, not generic ecommerce pain.
- tech_signals should include WMS, OMS, ecommerce platform, ERP, shipping, integration, data, or internal tooling clues whenever available.
- notes should include useful context, caveats, uncertainty, and why the recommended angle was chosen.
- source_urls should support the key claims.
- draft_subject and draft_body should be based on the strongest specific evidence, not generic RouteIQ positioning.
- The goal is not just to identify companies. The goal is to create a strong enough researched record that James can quickly review the prospect, understand the angle, and send or edit the email.

Draft email rules:
- Write draft_body as a ready-to-send but editable cold email from James at RouteIQ.
- 80-130 words.
- Plainspoken, curious, and specific.
- No hype.
- No spammy SaaS language.
- Avoid phrases like â€œrevolutionize,â€ â€œunlock,â€ â€œseamless,â€ â€œgame-changing,â€ â€œblack box,â€ and â€œdecision layer.â€
- Mention one or two concrete researched details.
- Make reasonable inferences only. Do not overclaim.
- Explain RouteIQ in one simple sentence.
- End with a low-pressure question.
- Include paragraph breaks.
- Sign off exactly:
Best,
James

Before producing the CSV, think carefully about fit. I would rather have fewer stronger prospects than a broad list of weak matches.