Use GitLab with an AI Browser for Personalized Outreach

If you use GitLab and you regularly need to draft personalised outbound, the bottleneck is usually the same: GitLab holds part of the context, but personalized outreach 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 GitLab 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 personalized outreach when GitLab is one of the inputs. It names the GitLab surfaces involved, the signals the workflow actually needs, an example prompt you can paste, and what a good output looks like.

The job a founder or SDR sending high-intent cold email is trying to do

The goal of personalized outreach is to produce a short, specific message that references a real signal and asks one question. The success metric is concrete: reply rate above 8%, positive sentiment above 50%, meeting-booked rate above 20% of replies. That definition matters because it shapes what GitLab needs to contribute to the workflow.

What signals personalized outreach actually needs

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

• Concrete recent event (funding, hire, product, talk, post) - GitLab does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Personal angle: shared connection, mutual school, common topic - GitLab does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Company pain that maps to the seller's product - GitLab does not contain this directly. Strawberry uses the browser plus public sources to fetch it.
• Preferred channel (email, LinkedIn DM, in-person at event) - GitLab does not contain this directly. Strawberry uses the browser plus public sources to fetch it.

What Strawberry can do inside GitLab

Strawberry can read MRs, summarize issues, and trigger pipelines with approval.

GitLab surfaces Strawberry uses for this workflow: projects, merge requests, issues, pipelines, snippets.

How Strawberry runs personalized outreach with GitLab

1. Strawberry opens the GitLab projects that contains the relevant context.
2. The companion pulls related context from GitLab (merge requests, history, attached files) where it exists.
3. For the parts GitLab 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 draft email or DM with subject + 60-90 word body + clear one-line CTA.
5. A human reviews before any external action (send, update, post). Then the approved output is saved back to GitLab or your system of record.

Example Strawberry prompt

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

Read this GitLab projects and any linked context.
Then run a full personalized outreach workflow on it. Use the browser to fill any gaps not in GitLab.
Return the output in the shape we use for personalized outreach: A draft email or DM with subject + 60-90 word body + clear one-line CTA.
Do not send anything externally. Save the draft to me to review.

What a good personalized outreach output looks like

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

• Subject: Voi Germany pullout + retention
• Hey Anna,
• Saw your SuperVenture talk and the Germany news. Curious - is the retention team looking at AI-driven win-back flows yet, or still email-only?
• If interesting, happy to send a 90-second screen recording of how a comparable scooter co cut churn 18%.
• If not relevant, no worries, ignore.
• Cheers, Laurits

Why GitLab for this, and where to use a different tool

GitLab is strong for this workflow because Strawberry can read MRs, summarize issues, and trigger pipelines with approval.

Where GitLab falls short Self-hosted GitLab instances need separate OAuth config; cross-project queries can be slow.

Consider also the rest of your stack for the parts GitLab doesn't cover.

Common mistakes when running personalized outreach

• Long messages that feel automated
• Fake-flattery openers ("I love what you're building")
• Asking for a 30-min call before any context
• Obvious AI-language ("In today's fast-paced landscape...")

Connecting GitLab to Strawberry

GitLab OAuth. 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.