Use Twenty CRM with an AI Browser for Prospect Research

If you use Twenty CRM and you regularly need to research a prospect, the bottleneck is usually the same: Twenty CRM holds part of the context, but prospect research also needs signals that live outside it - on the public web, in LinkedIn, in news, in other connected apps. Strawberry is built to combine the Twenty CRM context with the rest of the browser, and run the full workflow as a companion you can re-trigger every week.

This page describes specifically how Strawberry handles prospect research when Twenty CRM is one of the inputs. It names the Twenty CRM surfaces involved, the signals the workflow actually needs, an example prompt you can paste, and what a good output looks like.

The job a sales rep, founder, or account executive is trying to do

The goal of prospect research is to decide whether a prospect is worth a calendar slot and prepare a personalised first touch. The success metric is concrete: first reply rate above 8% and a meeting booked in under 14 days from first touch. That definition matters because it shapes what Twenty CRM needs to contribute to the workflow.

What signals prospect research actually needs

For each signal below, here is whether Twenty CRM can contribute directly or whether Strawberry has to find it via the browser:

• Role tenure and seniority on LinkedIn - Twenty CRM stores or surfaces this directly. Strawberry reads it through the connected integration.
• Recent funding rounds or M&A activity - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Headcount growth or layoffs in the last 6 months - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Tech stack and procurement signals - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Recent content the prospect has published or commented on - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Open job postings that reveal team priorities - Twenty CRM does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

What Strawberry can do inside Twenty CRM

Native Strawberry integration with read + write across all core objects; ideal for CRM hygiene, batch enrichment, and pipeline triage.

Twenty CRM surfaces Strawberry uses for this workflow: people, companies, opportunities, notes, tasks.

How Strawberry runs prospect research with Twenty CRM

1. Strawberry opens the Twenty CRM people that contains the relevant context.
2. The companion pulls related context from Twenty CRM (companies, history, attached files) where it exists.
3. For the parts Twenty CRM does not store, Strawberry uses the browser - web search, LinkedIn, news, the prospect's website.
4. Strawberry synthesises the output in the shape this workflow needs: A one-page brief.
5. A human reviews before any external action (send, update, post). Then the approved output is saved back to Twenty CRM or your system of record.

Example Strawberry prompt

Paste this in a new Strawberry chat with Twenty CRM connected. Adjust the specifics to your actual ICP, role, or topic.

Read this Twenty CRM people and any linked context.
Then run a full prospect research workflow on it. Use the browser to fill any gaps not in Twenty CRM.
Return the output in the shape we use for prospect research: A one-page brief: name, role, company, ICP fit (yes/no with reason), top 3 talking points, suggested first message, 1-2 source links.
Do not send anything externally. Save the draft to me to review.

What a good prospect research output looks like

Here is what a finished output for prospect research should look like in practice. The specifics will change for your use case, but the shape should look similar:

• Anna Lindqvist - VP Marketing, Voi Technology
• ICP fit: yes (Series D scooter co, EU expansion, 1500 employees)
• Talking point 1: hired 4 paid-acquisition managers in last 90 days - clear shift toward performance marketing
• Talking point 2: spoke at SuperVenture last month on scooter unit economics
• Talking point 3: company just announced Germany pull-out - retention focus is likely a priority
• Suggested first message: short, references the SuperVenture talk, asks one specific question, no calendar link

Why Twenty CRM for this, and where to use a different tool

Twenty CRM is strong for this workflow because Native Strawberry integration with read + write across all core objects; ideal for CRM hygiene, batch enrichment, and pipeline triage.

Where Twenty CRM falls short Some create endpoints require sequential calls (~800ms apart) to avoid rate limits; certain custom-field updates must go through update_record.

Consider also LinkedIn or ZoomInfo.

Common mistakes when running prospect research

• Researching prospects who don't match ICP - the brief is wasted
• Generic talking points ("impressive growth") that don't reference any real signal
• Copying public bio text instead of synthesising fit

Connecting Twenty CRM to Strawberry

Twenty CRM is a connected app; uses API key. Once connected, the companion can read the surfaces above without re-authenticating, and any write action still requires explicit human approval the first time the workflow runs.

Caveats

Do not let any AI agent send emails, update CRM records, or change shared systems without a clear approval step. Strawberry is strongest when the workflow combines browser context with connected-app context and a human review for sensitive actions.

When Twenty CRM + Strawberry is NOT the right fit for prospect research

Skip this setup if any of the following is true:

• You don't actually need Twenty CRM signals. If everything you need lives on the public web, drop the Twenty CRM step and let Strawberry run on URLs alone - it's faster.
• A known Twenty CRM constraint blocks the speed gain: Some create endpoints require sequential calls (~800ms apart) to avoid rate limits.
• The buyer (sales rep, founder, or account executive) doesn't own the decision. If the brief gets handed to someone who'll redo the research, the audit-trail-in-Strawberry advantage is wasted.

3 mistakes that kill this workflow

1. Researching prospects who don't match ICP - the brief is wasted. Twenty CRM is one input. Strawberry's edge is combining it with everything else. Stop at Twenty CRM-only signals and you'd have been faster with native Twenty CRM reports.
2. Generic talking points ("impressive growth") that don't reference any real signal. Pre-check Twenty CRM for a recent touch or duplicate before Strawberry acts on the output. A duplicate hit burns the relationship.
3. Copying public bio text instead of synthesising fit. Strawberry is built so a human reviews before any external action. Skipping that review to save time is how you ship a wrong fact to a real person.

Honest tradeoff vs alternatives

You could research a prospect inside Twenty CRM alone using its native features, or with a dedicated prospect research tool. Twenty CRM alone gives you tighter data fidelity but misses every signal that lives off-platform. A specialised prospect research tool gives you better dashboards but its scope ends where its integrations end, and most of the real signal still lives on the open web.

Strawberry's edge with Twenty CRM: Native Strawberry integration with read + write across all core objects; ideal for CRM hygiene, batch enrichment, and pipeline triage. The price you pay: an agent run takes 30-90 seconds; a native Twenty CRM action loads in 2. For a one-off question you already know the answer to, use Twenty CRM directly. For an output you'll redo every week or every account, route it through Strawberry as a saved routine so the synthesis happens once and re-runs automatically.

What a real output looks like

• Anna Lindqvist - VP Marketing, Voi Technology
• ICP fit: yes (Series D scooter co, EU expansion, 1500 employees)
• Talking point 1: hired 4 paid-acquisition managers in last 90 days - clear shift toward performance marketing
• Talking point 2: spoke at SuperVenture last month on scooter unit economics
• Talking point 3: company just announced Germany pull-out - retention focus is likely a priority
• Suggested first message: short, references the SuperVenture talk, asks one specific question, no calendar link