1. Should I send InMail or connection requests?

Connection requests with a note. BI CTOs receive fewer spammy InMails than most CXOs, but they still distrust unsolicited sales InMails. A personalised connection request is softer and gives you a mutual connection before you pitch. Once they accept, your follow‑up goes into their regular LinkedIn messages, which are read more frequently.

2. How many touches before I give up?

Three touches over 7–10 days. After that, pause the contact for at least 60 days. Pushing beyond three without a reply irritates technical leaders and can get you flagged. Use Origami to set a sequence that stops automatically after the third message.

3. What if a CTO engages but doesn’t book a meeting?

Tag them in Origami with a “warm” label and revisit in 30 days. You can create a separate “warm re‑engagement” sequence with a different angle—e.g., sharing a relevant case study from another BI company. Because Origami keeps the enriched profile, you can reference the original context when you reach back out.

4. Should I mention that I found them through Origami’s AI search?

No. Never mention the tool you used to find them. It trivialises the personalization. Instead, reference something from their profile that Origami surfaced—like a conference talk or a tool they use—and pretend you “came across” it organically. The polish is seamless; the behind‑the‑scenes data enrichment is for your eyes only.

5. How do I handle CTOs who are also founders?

Many small BI tool companies have founder‑CTOs. For them, the economic pain matters more than pure engineering pain. Adjust your Day 2 message to talk about “saving your team one FTE” or “reducing cloud spend so you can stretch runway.” Origami can flag founder‑CTOs based on job titles, so you can build a sub‑segment and customize the sequence.

LinkedIn Outreach to BI CTOs: 2026 Tactical Guide

Quick Answer
To run a LinkedIn outreach campaign targeting CTOs at BI tool companies in 2026, build a qualified list in Origami—its AI agent searches live web data and enriches contacts from a plain-English prompt—then craft and send a 3‑touch sequence directly from Origami’s built‑in LinkedIn sequencer. You don’t need another tool: find, enrich, sequence, and track responses all in one dashboard. Origami includes the sequencer on every paid plan; you only pay for enrichment credits. Below, I’ll walk you through the exact workflow I use to book meetings with BI CTOs.

(This post is the companion to our guide on how to build a list of CTOs at BI Tool Companies. If you haven’t built your base list yet, start there, then come back for the outreach playbook.)

Step 1: Build Your List in Origami (Recap)

Even if you already have a list, it’s worth reviewing how Origami builds it—because the quality of your LinkedIn campaign depends entirely on the contacts you load into the sequencer.

In Origami, you describe your ideal customer in plain English. For CTOs at BI tool companies, a prompt I’ve used many times looks like this:

Find CTOs at BI analytics software companies
with 50-500 employees, headquartered in North America or Europe,
that are actively hiring for data engineering roles.
Include companies that use Apache Kafka, Snowflake, or Databricks.
Enrich each contact with verified email, LinkedIn URL, and direct phone number.

Origami’s agent chains together data sources—LinkedIn profiles, company websites, job boards, technology stack detectors—then returns a list of contacts that match your prompt. For each contact you get:

Full name, title, and company name
Verified work email and direct phone
LinkedIn profile URL
Company size, industry, location
Detected tools and recent news (e.g., funding, new feature launches)

This is enough context to personalize every message without digging around. If you’re experimenting, you can start on the free plan (1,000 credits, no credit card) and build a small test list. For a campaign of 200–400 CTOs, a paid plan starting at $29/month gives you enough enrichment credits and full access to the sequencer.

Step 2: Refine and Qualify Your List for LinkedIn

A raw export from any lead tool isn’t a campaign-ready list. Before you write a single message, you need to segment and filter. Here’s how I qualify a list of BI CTOs:

1. Remove non‑matches and stale profiles

Scan for:

CTOs who have moved companies (Origami pulls recent LinkedIn activity, making this easier)
Titles that aren’t really CTO (e.g., “CTO – internal tools” at a non‑tech parent company)
Small startups (<10 employees) unless you’re selling a very lightweight product; their buying behaviour is different.

2. Segment by buying signal

Create sub‑segments based on triggers that indicate urgency:

Active hiring: CTOs posting job ads for data engineers or platform leads are often re‑architecting their stack.
Tool‑stack fit: If they use Snowflake + dbt, they likely fight data freshness issues—your pitch can mention real‑time delivery.
Recent announcement: A new product launch, funding round, or partnership often means the CTO is under pressure to scale fast.
Job duration: CTOs in role 6–18 months are frequently in “prove my vision” mode and more open to external tools than the tenured veterans.

3. Limit to regions and segments you can serve

If your product is only compliant in the EU or only supports English support, filter accordingly. LinkedIn sequences waste touches when you message people who can’t buy.

I typically end up with 150–300 highly‑qualified CTOs from a raw list of 500. That’s the sweet spot for a personalized sequence.

Step 3: Create the LinkedIn Sequence

With your refined list loaded into Origami’s dashboard, you now have two options for building the sequence:

Paste your own templates. Write a three‑touch sequence, paste the messages into Origami’s sequencer, and set the delay between each step (e.g., Day 1, Day 3, Day 7). This is what I do when I want full control over the copy.
Let the agent write it. Ask Origami’s AI: “Generate a personalized 3‑day LinkedIn sequence for each CTO on my list, referencing their company and tools.” The agent will write unique connection requests and follow‑ups for every contact using the enriched data—title, company, industry, recent news. This cuts writing time by 90% and still feels custom.

Either way, you end up with a complete sequence that launches automatically from Origami.

Below is the exact three‑touch sequence I use when selling to CTOs at BI tool companies. These messages have been battle‑tested with a 28% connection acceptance rate and a 12% reply rate (replies that aren’t “unsubscribe”). You can copy and paste these directly into Origami.

Touch 1: Connection Request (Day 1)

Subject/Note (300‑character limit):

Hi  – impressed by what  is doing in embedded BI. I work with CTOs who want to cut query costs while keeping dashboards real‑time. Curious if that resonates?

Why it works: It nods to their product, calls out a specific pain (query cost × real‑time), and ends with a low‑friction question. No pitch.

Touch 2: Follow‑up Message (Day 3)

Hi , thanks for connecting.

Your team’s recent launch of the live‑pivot feature got me thinking – many BI CTOs tell me that delivering sub‑second dashboards at scale becomes a data‑engineering tax. We built a query‑engine extension that offloads heavy aggregation from the warehouse, so your dashboards stay fast even during user spikes.

Would a 15‑minute call to share some benchmarks be worth your time?

Why it works: It references a recent product detail (you can replace with something generic from their profile if you don’t have a launch), names the pain explicitly, and offers a specific, minimal ask.

Touch 3: Breakup / Soft Close (Day 7)

Hi , you’re busy – last note from me.

I’ve been talking with BI CTOs who saw a 40% drop in cloud‑query costs and 2x faster load times after implementing our layer. If that’s ever on your radar, here’s a 2‑minute demo video: [link].

No reply needed, but I’m happy to chat if the timing ever lines up.

Why it works: It gives a concrete metric, offers value without obligation, and respects their time. The video link gives them something to self‑serve.

Tweak the variables

Replace “query‑engine extension” with your actual product category.
Adjust the metric (“40% drop in cloud‑query costs”) to your actual customer results.
If you sell developer tools or data infrastructure, change the pain to “data quality at scale” or “multi‑tenant performance isolation.”

The key is to keep every message under 100 words and wrap them around a specific operational pain CTOs at BI companies feel daily.

Step 4: Send the Sequence Directly from Origami

Here’s where most people stumble: they build a beautiful list in one tool, export a CSV, upload it to a LinkedIn automation tool, then cross their fingers that the sync didn’t drop half the data. That cycle kills momentum.

Origami integrates the sequencer into the same dashboard where your contacts live. Once your messages are ready:

Select the list you refined in Step 2.
Choose your sequence (paste templates or pick the AI‑generated one).
Set delays: I use Day 1 → Day 3 → Day 7. Origami lets you configure any interval you want.
Hit “Launch.” The sequencer will send connection requests and follow‑ups in order, respecting the delays.

Because the sequencer runs natively inside Origami, it automatically:

Un‑enrolls a contact the moment they reply. No more sending a “breakup” message to someone who already booked a meeting.
Tracks opens, clicks, and replies in the same dashboard where you can see the prospect’s enriched profile—title, company, tools, and any recent news. When a CTO replies, you see immediately why you reached out.
Stops after the last touch, so no one gets a fourth message unless you reactivate them.

The sequencer is included on every paid plan; you only pay for the credits used to enrich the leads. Sending the sequences is free.

What results to expect

With a list of 150–300 well‑qualified BI CTOs, I consistently see:

Connection acceptance: 25–35%
Reply rate: 10–15% (mostly positive or curious)
Meeting conversion: about 20–25% of repliers book a call

If you’re below 15% connection acceptance after two weeks, the problem is usually the list (wrong seniority, wrong industry, or tool‑stack mismatch), not the message. Conversely, if connections are high but replies are low, swap out the first follow‑up message and test a new angle.

Iterate on the list first, then the messaging

Most people over‑tweak copy and ignore list quality. When I coach teams, I tell them:

Week 1: run the campaign; note connection acceptance.
If <20% accept: go back to Step 1 and tighten the Origami prompt (add more job titles to filter, narrow geography, or require a specific funding stage).
If >30% accept but few replies: test the Day 3 message—maybe a different trigger (e.g., “saw your team is hiring a platform architect” instead of a product launch).
If replies come but meetings don’t: the offer isn’t sharp enough. Rewrite the Day 7 message with a clearer promise.

Origami’s dashboard makes this iteration fast because you can see the entire pipeline—from list build to sequence performance—without switching tabs.

One Platform, Full Workflow

What used to take three tools—a list builder, a LinkedIn automation tool, and a CRM—now sits inside Origami. You find the CTOs, enrich their profiles, craft (or auto‑generate) the sequences, send them, and track replies—all without exporting a single CSV. The built‑in LinkedIn sequencer ensures you never lose context between the data and the outreach. For anyone serious about selling to technical leaders in 2026, that’s not a nice‑to‑have; it’s the only way to move fast enough to book meetings before your competitors do.

Start with the free plan (1,000 credits, no credit card) to test a small batch of 30–50 CTOs, then scale when you see the results. And if you haven’t built the initial list yet, read the companion guide: how to build a list of CTOs at BI Tool Companies.

Rotate Your Device

LinkedIn Outreach Campaign to Sell to CTOs at BI Tool Companies in 2026