Sales outreach · checked 2026-10-19

Can I vibecode SalesTouch?

KINDA· weekend project

Reading profiles and sending a handful of invites from your own browser session is an evening's work for an agent, and open-source MCP servers already do it. SalesTouch charges for the layer that keeps it alive: sends paced like a person, cooldowns when LinkedIn pushes back, a residential IP per account, queues that run while your laptop is shut, and Sales Navigator extraction. LinkedIn's help center says automation tools breach its User Agreement and can get an account restricted, so the real cost of any version, hosted or homemade, is your account. A local, read-mostly build is sensible; a mass-outreach build is not.

$39/moprice per seat

$468you'd save a year

weekendbuild time

—people replaced it

Before you start

What you need on hand.

DifficultyAdvanced · Real infrastructure or OAuth work.

TimeA weekend; keeping it working as LinkedIn changes is ongoing

Claude Code, Codex or CursorAny of them can run the prompt.
Python 3.12The prompt uses the mcp SDK and Playwright.
Playwright's ChromiumOne command downloads it; the first run needs a visible window to sign in.
A LinkedIn account you can riskLinkedIn's rules prohibit automation tools; start with read-only tools and low caps.
An MCP clientClaude Code, Codex or any client that speaks stdio MCP.

Before you buildSalesTouch has a 7-day trial (card required). Also try the open-source linkedin-mcp-server first: it already covers reading and basic sending from your own machine.

1. Install one agent: Claude Code, Codex, Cursor.
2. Make an empty folder and open it in the agent.
3. Paste the prompt below, press enter, and answer its questions as it builds.

The prompt

Build me a local MCP server that lets my coding agent use my own LinkedIn account, to
replace SalesTouch. Requirements:

- Python 3.12 with the official `mcp` SDK (FastMCP) over stdio and Playwright driving
Chromium with a persistent profile in ~/.linkedin-agent/profile. `linkedin-agent login`
opens a visible browser where I sign in by hand; never ask for or store my password.
- Read tools: lookup_profile, lookup_company, search_people (keywords, location, company),
list_inbox and read_conversation. Return structured JSON (name, headline, location,
current role, URL), never raw page HTML.
- Write tools: send_invite (note up to 200 characters) and send_message. Both stay disabled
unless ALLOW_WRITES=true in .env, require confirm=true from the agent, and are logged to
SQLite at ./data/actions.db with time, target and text.
- Pacing guard in front of every write: daily caps (default 20 invites and 30 messages), a
random 20 to 90 second gap between actions, 09:00 to 18:00 local time only, one invite per
person per 3 weeks. On a checkpoint, captcha or "unusual activity" page, stop all writes
for 24 hours and say so in every tool reply.
- schedule_message(url, text, send_at) goes into the same SQLite file and a background
worker sends it while the server runs; the laptop has to be awake.
- Local-first: no accounts, no telemetry; only linkedin.com is contacted.
- Out of scope: Sales Navigator, bulk scraping of comments or reactions, email sending,
proxies, and running on a server (a datacenter IP is the quickest way to get flagged).
- README: register it with `claude mcp add`, how to delete the profile folder, and a warning
that LinkedIn's User Agreement forbids automation, accounts can be restricted, and the
selectors break whenever LinkedIn changes its pages.

Opens your agent with the prompt filled in, you press enter. Or copy it and paste it into an empty folder.

Share on X

Max MiskowSponsoredAI agents, automations and MVPs, built for your company.Visit site ›

Then keep going

Next prompts, same folder.

The first prompt builds the core. Run these one at a time in the same folder to grow it into your own SalesTouch.

Add an approval queue to the LinkedIn MCP server in this folder. Requirements:

- send_invite and send_message no longer send: they store a pending action in SQLite with
  the target, the text and the reason the agent gave.
- `linkedin-agent review` lists pending actions in the terminal, shows the target's
  headline next to the text, and lets me approve, edit or reject each one with a key.
- Approved actions go through the existing pacing guard; rejected ones are kept with the
  reason so the agent can see what I turned down.
- Update the README.

Add a lead book to the LinkedIn MCP server in this folder. Requirements:

- SQLite tables for leads (URL, name, headline, company, stage, tags, note, last contact)
  and a history of every tool call that touched a lead.
- MCP tools: lead_upsert, lead_tag, lead_note and leads_search (by stage, tag or text).
- `linkedin-agent export` writes leads.csv in UTF-8, one row per lead, with the last
  five history entries joined into one column.
- Update the README.

Add a warm-up schedule to the pacing guard in this folder. Requirements:

- A WARMUP_START date in .env. For the first 21 days, the daily caps grow in steps from 5
  invites and 5 messages up to the configured maximum.
- Show today's cap and what is left of it in every write tool's reply.
- If a write hits a checkpoint or "unusual activity" page, restart the warm-up from day 1
  after the 24-hour pause.
- Tests for the schedule with a fake clock. Update the README.

What you lose

Sends that keep running while your computer is off
A residential IP in your country for each account
Sales Navigator searches and bulk extraction from post comments, reactions, groups and viewers
Follow-up sequences, lead tags, lead history and acceptance and reply analytics
The vendor's cooldowns and monitoring when LinkedIn pushes back

Why people still pay

Outbound is a numbers game, and a restricted LinkedIn account is expensive to lose. SalesTouch sells the pacing, monitoring and always-on queue so an agent can keep working unattended. Its success-rate figures and testimonials are the vendor's own and we couldn't check them, and we found no independent reviews.

Moatexecution polish infrastructure scale compliance & regulation

Do the math

SalesTouch or your own copy?

Seats

Over

Your usage

Count my time12h ×$/h

SalesTouch, 1 yr$468

Your own copy, 1 yr$8running + build session

You keep$461pays for itself in the first month

Estimate · It runs on your own laptop, so there is no hosting bill; the cost is token usage on your agent plan, and the risk is your LinkedIn account. A VPS would add a few dollars but also a datacenter IP, which the prompt rules out.

Leaving SalesTouch

Take your data, then cancel.

1 · Take your data out of SalesTouch

1The pages we could read give no export or deletion steps; the docs' Authentication and Troubleshooting sections were not available to us.
2Leads, tags and extraction results live in your SalesTouch workspace. The tool catalog has leads_search and scrape_result_page for paging through stored data, so ask your agent to write your lead list and extractions to CSV before you leave.
3Your LinkedIn messages and connections stay on LinkedIn itself; nothing to export there.

2 · Cancel SalesTouch

1During the 7-day trial, cancel in Stripe before day 7 and the subscription never starts.
2After the trial, cancel any time; access continues until the end of the paid period.
3To drop an extra LinkedIn account, reduce the seat count; it takes effect at the next renewal.
4The pages we read don't show where the Stripe billing link lives; look in your account settings or ask support.

Remove the endpoint https://www.salestouch.io/api/mcp from your MCP client (Claude, Codex or another) once you cancel.
If you connected a mailbox for the email channel, disconnect it under Settings, Email.
The site gives conflicting daily caps: its FAQ says never go over 80 invitations a day, a dashboard example shows 25, and the marketing copy says 30. If you build your own, start much lower.
The site claims GDPR compliance but doesn't say where data is stored or for how long; ask support to delete your workspace data if that matters to you.

Checked 2026-10-19 against SalesTouch's docs: 1, 2, 3, 4, 5

The escape hatch

Don't feel like building it? These are already free.

linkedin-mcp-serverOpen sourceApache-2.0 MCP server that reads profiles, companies, jobs and your inbox and can send connection requests and messages, all through your own browser session; installs with uvx.★ 3.9k · active Oct 2026 · one-click install
WebVisit ↗linkedin-mcp-server (eliasbiondo)Open sourceMIT MCP server that searches people, companies and jobs and scrapes profiles into structured data; it drives a Patchright browser you log in to once.★ 198 · active Mar 2026 · self-host, real ops
WebVisit ↗

The numbers

SalesTouch pricing

Plan	Monthly	Annual, per month	What you get
Monthly	$39	—	One LinkedIn account, every tool, safety controls and analytics.
Annual	—	$32.42	The same as Monthly.
Extra LinkedIn account	$39	$32.42	Another connected LinkedIn profile on the same workspace.

Free tier: A 7-day trial, limited to one LinkedIn account; a payment method is required and nothing is charged before day 7.
Billing: Monthly or annual through Stripe, which also handles invoices, automatic tax and tax IDs. Cancel in Stripe before day 7 and the subscription never starts; after the trial you can cancel any time and keep access until the paid period ends. Adding an account during the trial ends the trial.
Hidden costs: Every extra LinkedIn account costs another $39 a month. The Sales Navigator tools work through the account you connect, so they presumably need that LinkedIn subscription too; the page doesn't say. The optional email channel needs read access to a mailbox.
Source: salestouch.io

Also on the list

Apollo.io$65/mo · Sales outreachNOT REALLY

Instantly$47/mo · Sales outreachKINDA

lemlist$69/mo · Sales outreachKINDA

Questions

SalesTouch, briefly

Not answered here? Tell us and we'll add it.

Ask a question ›

Kinda. The core is a weekend build with the prompt on this page, but real gaps remain: Sends that keep running while your computer is off, A residential IP in your country for each account.

About $39 a month on the Monthly plan per seat, $468 a year (checked 2026-10-19).

Sends that keep running while your computer is off; A residential IP in your country for each account; Sales Navigator searches and bulk extraction from post comments, reactions, groups and viewers; Follow-up sequences, lead tags, lead history and acceptance and reply analytics; The vendor's cooldowns and monitoring when LinkedIn pushes back. If any of those matter to you, keep paying.

Yes: linkedin-mcp-server (open source), linkedin-mcp-server (eliasbiondo) (open source).