SalesShift
Get started

Solutions · Dev tools

Outbound for developer tools and infrastructure

Selling infrastructure to engineers is unusual in two ways. The buying signals are public and technical — postings naming a stack, published migrations — and the buyer is unusually sensitive to how their data is handled, which makes where your sales tooling runs part of the pitch rather than an internal detail.

What this team is actually trying to do#

  • “Find companies hiring for the stack we integrate with.”
  • “Drive the whole thing from an API and a CLI, not a form.”
  • “Use our own model key, not a vendor's.”
  • “Keep prospect data on infrastructure we control.”

Your signals are unusually legible#

Technical hiring is the most informative kind. A posting that lists a stack tells you what a team runs today, and a posting for the first platform engineer, or the first SRE, tells you a threshold was crossed — the point at which something that used to be someone's side responsibility became a role.

That specificity is what makes a first line work with an engineering audience. A message that names the thing they actually operate is a technical conversation; a message about digital transformation is deleted before the second line.

The buyer will ask where the data goes#

Engineers are the buyers most likely to ask which subprocessors touch their data, and the most likely to notice when the answer is vague. Selling to them from a stack you cannot describe is a self-inflicted objection.

Two answers help. That the model calls go to a provider you have a contract with, using your own key, rather than to a vendor's account. And that the work layer — sending, crawling, background jobs — can run on infrastructure you control.

An interface engineers will actually use#

Technical teams automate their own workflow. The tool that survives is the one whose entire surface is available programmatically, so a rep's list can be assembled by a script and a signal can trigger a job in something else.

The practical test is whether the API is the same one the interface uses, and whether a command-line client exists that is not an afterthought. A REST API that lags the UI by six months is documentation for a product that no longer exists.

Founder-led motion, then a first hire#

Most infrastructure companies run outbound from the founders for longer than they expect, then hand it to a first commercial hire. The handover is where tooling usually breaks: the record of what was said lives in someone's mailbox, and the new person starts blind.

Keeping the conversation, the deal and the paperwork on one record from the first email is what makes that handover a morning rather than a quarter.

What carries the workflow#

REST API, CLI and SDKs
The documented REST API, the vxcli command-line client and published SDKs cover the same surface the interface does, so the workflow can be scripted rather than clicked.
Bring your own model key
Assistive features call OpenAI, Anthropic or a local Ollama using the key you connect. With no key configured they fall back to a deterministic template and say so.
Run the work layer yourself
On the Self-Hosted plan the node is yours: sending, crawling and background jobs run on your machine, using your mailboxes and your key.
Technical hiring signals
Public postings arrive as signals with a source URL and a relevance score, so a stack mentioned in a requisition is one click from the page it appeared on.
A REST API and a CLI
Every record the interface touches is reachable over the REST API, with vxcli and five SDKs on top — so a signal or a reply can be pulled into the systems you already run on your own schedule.

Every one of these is documented at /docs.

Questions#

Yes — a documented REST API, the vxcli command-line client and published SDKs, covering the same surface as the interface. The reference and the CLI documentation are generated from the running system rather than maintained by hand.

Terms used on this page#

Hiring signalBring your own keySelf-hosted nodeTrigger eventSending identity

The full vocabulary is in the glossary.

Go deeper#

Self-hosting your sales dataWhat it means to run the work layer of a sales platform yourself: what stays with the vendor, what moves to your machine, and what it costs to operate.Signal-based prospecting: how to find a reason to write todayBuild outbound from public buying signals — hiring posts, funding notices — rather than volume: what counts as evidence, how to rank it, how to work it.

Other kinds of team#

Outbound for recruiting and staffingJob postings are your market and your signal at once: work open roles as a live feed, reach the hiring manager, keep the placement on one record.Outbound for agencies and consultanciesRun outbound across several client domains without their reputations colliding: separate sending identities, per-mailbox health, and honest reporting.Founder-led sales, and your first hundred emailsOutbound before there is a sales team: a small list you can defend, one mailbox sent carefully, and the whole record in one place for your first hire.

Run it on one record

Signals, prospect search, sequences, deliverability, pipeline, e-signature and invoicing.

Get startedSee pricing