Skip to content
Servers, sending and prospect data included · a VxCloud product

Sales and marketing,
on infrastructure we run for you.

Find the company, email the buyer, sign the contract, get paid — on one record that never gets re-keyed. The sending servers and the prospect data come with it, at the price on the box. AI drafting runs on your own model key, at no markup, and you can bring your own SMTP or enrichment too.

Managed SMTP · verified prospect data · your own domain · your own model key

salesshift.vxcloud.io/leads
SalesShift prospect pool in dark mode: a filter rail with seniority, email status and location facets carrying live counts, and a results table of people with job title, company, email, phone, employee count and fit score.

Find the company before you know the person

A shared pool of companies and people, filtered by seniority, department, country, headcount and whether an address is confirmed. Every facet carries its own count, so you can see the size of a segment before you commit to it.

01 / 10

Click a stage, or use the arrow keys. Captured from the running application. On a narrow screen each stage shows a region of its capture rather than the whole screen, so the interface stays readable.

What the product actually talks to

SMTPIMAPSendGridMailgunOpenAIAnthropicOllamaHunter.io

Sending and prospect data are provisioned with the plan; swapping either for your own account is a field in settings, and we take no margin when you do. The three model providers are the other way round — those you connect, on every plan. Gmail and Outlook connect over OAuth too — see the last question below for exactly how far that one is proven.

The whole argument

Four tools that don't speak to each other, replaced by one that does.

The prospect you found, the sequence that reached them, the meeting it booked, the contract they signed and the invoice they paid are the same row in the same system. Nothing is re-keyed, and nothing quietly disagrees.

salesshift.vxcloud.io/overview
SalesShift home dashboard: summary tiles for contacts, pipeline value, emails sent, meetings and contracts, above an email-activity line chart, an isometric open-value-by-stage chart and an envelope-status donut.

The home dashboard of a demo workspace. Every figure on it was computed by the product from that workspace's own data — they are not customer results, and they move between captures. On a narrow screen this is a region of that capture, not the whole screen.

One record

First search to signed invoice, without an export in the middle.

Your domain

Connect your own mailbox and mail is signed by your domain — or send over our managed relay instead.

One bill

Servers, sending and prospect data in the plan price. Nothing to assemble.

The platform

Everything a deal touches, in one place.

Not a suite of adjacent apps sharing a logo. One data model, one inbox, one audit trail — and one bill, from the company that runs the infrastructure underneath it.

Every photograph below is a region of a real capture, at detail scale. The one drawing is labelled as a drawing.

A sending pool that is graded, not guessed

Every connected mailbox carries its own health score, daily cap and bounce, complaint and reply rates. Go past the cap and the queue waits for tomorrow instead of burning the domain.

SalesShift deliverability settings: sending-pool cards per mailbox showing health grade, sends against daily cap and bounce, complaint and reply rates, above a workspace sending ceiling, a domain-record check and a placement test.

Cadences with real waits

Email, call and LinkedIn steps with explicit waits, merge tags and per-step A/B variants.

SalesShift sequence builder: a five-step outbound cadence listed on the left with channel badges and wait intervals, and the step-one email editor open on the right showing delay, subject with a merge tag, and body text.

Invitations, not links

Meetings arrive as genuine ICS invitations, so accept and decline come back to the record.

SalesShift calendar in week view: meetings laid out across Monday to Friday of a working week, with a mini-month, event search, calendar toggles and booking links in the left rail.

Signature fields where you drop them

One colour per signer. Positions are stored as a percentage of the page, not as pixels.

SalesShift e-sign preparation screen: a Master Services Agreement with signature, full-name and date-signed fields placed on the page for two signers, colour-coded amber and blue, beside a palette of draggable field types.

Invoices that close themselves out

Line-item discounts and tax, a PDF you send from the record, and partial payments booked against the balance until it clears.

SalesShift invoice detail screen: bill-to and invoice-detail panels, a line-item table with discounts and tax, and a right-hand column showing amount due, a recorded payment and a Stripe payment-link action.

The inbox beside the room

Channels, team rooms and direct messages next to the mail client, with read receipts, scheduled sends and audio or video calls from the room header.

SalesShift team messaging: a channel and room list on the left and an open direct-message thread on the right, with read receipts, a message composer, and audio- and video-call buttons in the room header.

A workflow engine that means it

Branch, wait, re-join. Independent branches execute at the same time in a Go runtime rather than queuing behind one another.

startenrichnotifyjoin
Schematic — not a screenshot. The red dot is the branch; both lit edges run at the same time.

Prospecting is the one surface not pictured here

It is in the product — Leads, Enrichment and Opportunities sit in the sidebar of every full screen shown above. Search the shared pool, reveal only the records you need, and convert them straight into contacts.

Two different things, priced two different ways. Revealing a pooled record spends a monthly allowance included with the workspace, and stops when the allowance is gone. Enriching a record — crawling a domain, verifying an address — runs on the provider key you supply, so that provider bills you directly at their price.

  • Hunter.io

    email discovery and verification

  • Domain crawl

    public company pages, fetched and parsed

  • Your account

    the provider invoices you, not us

Privacy

We run the infrastructure. You keep the data.

Being the provider is what lets us answer this question at all. The servers and the sending relay are VxCloud's, so there is no third party in the mail path we would have to speak for — and your pipeline, your threads and your customers' details are yours, in a workspace nothing else reads.

Where a model is involved the answer is shorter still: the key is yours, so the account the text reaches is one you opened and can revoke. Nothing you write, send or store is used to train anything by us. Credentials live in Vault rather than the database, and the rest of the stack has the same escape hatch — your SMTP, your enrichment provider, or a dedicated node of your own.

  • Your data is never training data, ours or anyone else's
  • Connect your own mailbox and mail is signed by your domain
  • Credentials encrypted in Vault, never written to the database
  • AI runs on your own model key — no markup, and none of it stored by us
  • Local models supported — nothing has to leave your network
  • Export everything, any time, and take the domain with you
Security and compliance at VxCloud
Who holds what4 subsystems

Sending

Managed SMTP · IMAP · SendGrid · Mailgun

Our relay, or the mailbox you connect — graded and capped either way

Prospect data

Pool search · verification · domain crawl · Hunter.io

Revealed records are copied into your workspace only

AI

OpenAI · Anthropic · Ollama

Your key, your account — we store neither the prompt nor the output

Invoicing

Quotes · contracts · invoice PDFs · recorded payments

Issued, emailed and reconciled here; card collection is not connectable yet

Diagram — not a screenshot. The real screen is Settings → BYOK Integrations.

Documentation

No logo wall. The docs are the proof.

There are no customer names, testimonials or uptime figures on this page, because we have not earned them yet. What there is instead is a reference generated from the running API — and it tells you, operation by operation, how well we actually know the thing works.

379
API operations
302
paths
28
modules
116
schemas

Counted from the inventory generated 13 August 2026. Clients: Go · Python · TypeScript · C++ · Java.

GET /statsdemonstrated
curl -s https://api.vxcloud.io/api/v1/salesshift/stats \
  -H "Authorization: Bearer $SALESSHIFT_TOKEN"

Generated from the source, not from memory

Routes, parameters and schemas come from the framework's own route objects. Error responses come from walking the handlers for every exception they can raise. If something is not in the generated inventory, it is not documented — which is why nothing in the reference describes an endpoint that does not exist.

Every operation says how well we know it

Each one carries a marker — demonstrated, partial, or undemonstrated — plus the basis for it: called live during the inventory run, verified earlier in the session, or read in source and never executed. Undemonstrated is not the same as broken, and the docs are not allowed to blur the two.

Generated, not written

The reference is produced from the running application rather than maintained by hand, so it cannot drift from the code the way a written page does. Every endpoint arrives with its real request and response shape, and the marker beside it is set by what the inventory run actually observed — which is why the counts above are read at build time instead of typed in.

Free on every plan

Public buying signals, free to read on every plan.

One pool of public hiring, funding and services signals, searched by every workspace. Reading it is not metered anywhere: the service behind the feed carries no plan check, no allowance and nothing that can answer payment required — on the free Self-Hosted plan exactly as on a paid one.

What the rest of it costs

  • Reveals. Unmasking a person in the prospect pool draws on a monthly allowance — 5,000 a month on the free plan, up to 100,000 on Organization.
  • Sending. Connect your own mailbox on any plan, including the free one. A paid plan adds our managed relay and the reputation behind it.
  1. Find the signal

    Companies say what they are about to buy in public — the role they posted, the contract they put out, the round they closed. Those posts are collected into one pool every workspace searches: what the signal is, what it implies, which source it came from, and whether an address came with it. Filter by source, search by company, title or skill, and put the contactable ones first.

    salesshift.vxcloud.io/opportunities
    SalesShift opportunities feed in dark mode: source tabs carrying their own counts above a table of public hiring signals, each row showing the company and role, an intent tag, the source it was scraped from, a contact address, and whether this workspace has emailed it yet.
  2. Work the ones worth working

    The same feed as cards, for when you are judging rather than scanning. Each card carries its source, its intent and how much is actually known about it, then a piece of the posting itself, so you can tell a real buying moment from a keyword match without opening anything. The address is on the card, and one action turns the signal into a lead on your own CRM.

    salesshift.vxcloud.io/opportunities
    SalesShift opportunities feed in card view: a grid of signal cards, each with source, intent and data-quality chips, a snippet of the original posting, a contact address, and an action that turns the signal into a lead.
  3. Reach them

    Open the composer on a signal and the draft is already about that posting. Choose which mailbox it leaves from, edit the subject, and merge tags resolve against the CRM contact the send matches or creates. If your workspace has written to that address before, it says so before you press send — and caps and suppression are enforced on the server, not in this dialog.

    salesshift.vxcloud.io/opportunities/[id]
    SalesShift email composer open on an opportunity signal: a sending-mailbox selector set to rotate across the workspace's mailboxes, the recipient address, an amber warning that this workspace has emailed the address before, a subject line, and a message body beginning with a first-name merge tag.

Three captures of the running application at /opportunities. The figures on them belong to a demo workspace and move between captures. On a narrow screen each one shows a region of its capture rather than the whole screen.

Pricing

One price per user. Everything a deal touches is in it.

The servers, the sending infrastructure and the prospect data are ours, and they are in the price — not a marketplace of add-ons you assemble afterwards. The model is the one thing we do not supply: AI runs on a key you connect, at that provider's price and with nothing added. There is one free tier, and it is free for exactly that reason reversed: on Self-Hosted you run the infrastructure, so there is nothing for us to charge you for.

Paid prices are per user, per month · every plan includes the whole platform

Starter

A founder or a first sales hire running the whole motion alone.

$105per user
per month
Get started
Emails sent
50,000 / mo
Prospect reveals
12,000 / mo
Sending mailboxes
3

Everything to run a full cycle

  • Pipeline, contacts, tasks and activity history
  • Prospect search, enrichment and verified reveals
  • Sequences, campaigns and reply detection
  • Meetings, quotes, e-signature and invoicing
  • Managed SMTP relay on our infrastructure
  • Deliverability grading and per-mailbox caps

Professional

Most teams

A team that has found the motion and now needs it to run without them.

$238per user
per month
Get started
Emails sent
100,000 / mo
Prospect reveals
40,000 / mo
Sending mailboxes
10

Everything in Starter, and

  • Workflow automation across the whole record
  • A/B variants per step, weighted and sticky per enrollment
  • Inbox rotation across the pool, capped and scored per mailbox
  • Calls with recording
  • REST API, webhooks, vxcli and the five SDKs
  • Unlimited stored contacts and workspace users

Organization

A revenue org where mail volume, data residency and access control are somebody's job.

$357per user
per month
Get started
Emails sent
Unlimited
Prospect reveals
100,000 / mo
Sending mailboxes
Unlimited

Everything in Professional, and

  • Dedicated infrastructure on VxCloud, region of your choice
  • No monthly send cap — volume limited only by daily sending guardrails
  • Workspace roles, permissions and activity trail
  • Priority routing on the VxCloud help desk
  • Migration and onboarding run with your team

Self-Hosted

free, permanently

You run the node, the mailboxes and the model. We run the record.

$0no card
no trial clock
Start self-hosted

You bring

Your node
A vxnode container on your own machine, in your own region
Your mailboxes
Google, Microsoft 365 or any SMTP server — 2 identities
Your model
OpenAI, Anthropic or a local Ollama — the same on every plan

Not a trial, and not a demo

It is the same application the paid plans run, with the parts that cost us money left out rather than turned down. There is no expiry, no feature that stops working on day fifteen and no card on file to forget about.

Your node answers a handshake with your own workspace id before we will dispatch anything to it, so nobody can point us at a machine they do not control — and our prospect pool is never queried from a box we do not run.

Included

  • The whole CRM — pipeline, contacts, tasks, activity history
  • Sequences, campaigns, reply detection and the shared inbox
  • Quotes, invoices, contracts and e-signature
  • 5,000 prospect reveals a month from the shared pool
  • Unlimited stored contacts · 2 users
  • REST API, webhooks, vxcli and the five SDKs

Not included: our sending relay, the reputation behind it, the node we would otherwise run for you, and everything else with a bill attached to it. The model key is not on that list — it is yours on the paid plans too.

Need more volume than Organization, or an air-gapped deployment? Talk to VxCloud

What the price covers

We are the provider, not the wrapper.

Every plan lands on infrastructure VxCloud operates. The relay the mail leaves from, the pool the prospects come out of and the machines underneath both are ours, so you are not asked to open three vendor accounts before the first email goes out, and you are not paying us to forward a bill somebody else wrote.

The exception is the model, and it is an exception on every plan including the paid ones: AI drafting runs on an OpenAI, Anthropic or Ollama key you connect, and that provider bills you at their price with nothing added by us. Sending and enrichment can be swapped for your own accounts the same way, any time — there it is an option about control rather than the price of admission.

Who runs itthree of four are ours

Sending

included

Managed SMTP relay, IMAP sync and reply detection, run and monitored by us

Or connect your own SMTP server, SendGrid or Mailgun

Data

included

The prospect pool, enrichment and verification, metered as reveals

Or connect your own Hunter.io key

Infrastructure

included

Servers, storage, backups and region on VxCloud — nothing for you to run

Or take a dedicated node on Organization

AI

your key

Drafting and rewriting run on a model key you connect — OpenAI, Anthropic or a local Ollama. You use as much as you need, with no allowance to run out of

That provider bills you directly, at their price, with nothing added by us

Our margin on a provider you connect yourself: none.

Compare

Line by line.

Volumes are per user, per month, and pool across the workspace. Self-Hosted is a flat workspace allowance — there are no seats to multiply.

FeatureSelf-HostedFreeStarter$105/userProfessional$238/userOrganization$357/user
Prospecting and data
Prospect pool search
Verified reveals per user5,000 / mo12,000 / mo40,000 / mo100,000 / mo
Enrichment and crawl-based lookup
Stored contactsUnlimitedUnlimitedUnlimitedUnlimited
Signal and opportunity feed
Sending and deliverability
Emails per userYour server50,000 / mo100,000 / moUnlimited
Sending identities per user2310Unlimited
Managed SMTP relay on our infrastructure
Send from your own domain — connect a mailbox or SMTP server
Deliverability grading and per-mailbox caps
Automated warm-up ramp on a new mailbox
Inbox rotation, health scoring and automatic pause
Domain authentication check — SPF, DKIM, DMARC, MX
Engagement
Sequences and campaigns
Shared inbox, threading and reply detection
Meetings, calendar and real invitations
Calls with recording
A/B testing and multivariate steps
Workflow automation engine
Revenue
Deals, quotes and products
Contracts and e-signature
Invoices, PDFs and emailed copies
Payments recorded against the balance, in part or in full
Reporting and attributionStandardStandardAdvancedAdvanced
AI
Model keyYoursYoursYoursYours
Drafting and rewriting on your connected key
OpenAI, Anthropic or a local Ollama
Local model support — nothing leaves your network
Call transcription and summary
Platform
Users2UnlimitedUnlimitedUnlimited
Roles, permissions and activity trail
REST API, webhooks and vxcli
Dedicated infrastructure and region choiceYour server
SupportDocs and communityVxCloud help deskPriorityPriority + onboarding

The one dash that runs the whole width is the honest one: no plan bundles model usage, because every plan runs AI on a key you connect. What that buys you back is the absence of a second meter to watch — and no markup on the first.

Rows we deliberately do not print: uptime percentages, compliance certifications and anyone else's prices. Two of those we have not earned yet, and the third is not ours to publish.

Questions

Before you ask.

And if it isn't here, it is in the documentation — or in the product. Create an account and look.

We do, with one exception we would rather name than bury. SalesShift is a VxCloud product, and VxCloud is an infrastructure company — the servers, the storage and the SMTP relay are ours, operated by us, and included in the plan price. The prospect data is ours too, metered as reveals. You do not open a vendor account to send the first email. The models are the exception: those are yours, on every plan, and the next answer is about that.

For sending and enrichment it is an option, not the price of admission: on any plan you can point mail at your own SMTP server, SendGrid or Mailgun, and enrichment at Hunter.io. When you connect one, that provider bills you directly at their price and we add no margin — the usage simply stops drawing on your plan allowance. For AI it is not an option, it is the arrangement: drafting and rewriting run on an OpenAI, Anthropic or Ollama key you connect, there is no bundled allowance on any tier, and with no key connected the draft endpoints answer with an editable template that says so rather than pretending to have written something.

Three paid plans, priced per user, per month: Starter at $105, Professional at $238 and Organization at $357. Every plan carries the whole platform — pipeline, prospecting, sequences, meetings, contracts, invoicing — and what separates them is volume, sending controls and support. Below them is Self-Hosted, which is free permanently.

Because it costs us nothing to run. On Self-Hosted you bring the node it runs on and the mailboxes it sends from, so the two things we would otherwise be paying for — compute and sending reputation — are yours. What is left is the application and a row in our database. It is not a trial: there is no expiry, no card and no feature that stops working on day fifteen. What it does not include is our sending relay and the reputation behind it, and the prospect pool is metered at 5,000 reveals a month, because that data is ours to pay for. The model key is not on that list — it is yours on every plan, so it is not part of what going free costs you.

One container. vxnode is a single Docker image; you give it your workspace id and a hostname you can reach over HTTPS, and register that address in Billing → Self-hosted. We call it back to confirm it reports your workspace id before anything will dispatch to it, so nobody can point us at a machine they do not control. After that it handles sending, scraping and agents for your workspace. The prospect pool is never queried from your node — that stays on our side.

Yes — when you connect your own mailbox or SMTP server, which every plan can do including the free one. The message then goes out authenticated as that mailbox, so your provider signs it, your domain is in the headers and your reputation is the one being built. Each connected mailbox is graded and capped separately, and reply detection reads the mailbox back over IMAP and stops the sequence. Our managed relay is the alternative when you would rather not run any of that — it sends on our infrastructure and our domain.

No — that is the point of the product. A quote becomes a document you send for signature with the fields placed where you want them, and the signed document becomes an invoice: line items with per-line discount and tax, a PDF, an emailed copy, and payments tracked against the balance — part payments included — until it clears. Quote, signature, invoice and payment history all stay on the same record.

Pricing is per user, per month, and so are the allowances — a second user on Professional brings another 100,000 sends, 40,000 reveals and ten more sending mailboxes with them. Allowances pool across the workspace rather than being trapped per person, so one heavy sender and one light one balance out instead of one of them hitting a wall. There is no AI allowance to multiply: that runs on your key and your provider bills you for it directly.

No. Nothing you write, send, store or generate is used as training data by us, and your workspace is not readable by another tenant. Because the model key is yours, the account any prompt reaches is one you opened, under whatever terms you agreed with that provider — we are not a party to it and we keep neither the prompt nor the output. Credentials you add are encrypted in Vault rather than written to the database. If you would rather the text never reach a hosted model at all, point AI at a local Ollama and it does not leave your network.

You export it. Contacts, threads, documents and invoices are all exportable, the sending domain was always yours to point elsewhere, and the model key was always in your own provider account — so leaving costs you a migration, not your mail history or your customer relationships. Money never ran through us either: there is no platform balance to withdraw, because collection already happens in your own bank or processor and this is where it is recorded.

Every screenshot on this page was taken from the running application against a real workspace; the names in them were replaced, the numbers were not. The surfaces they show all exist today — the pipeline, sequences, the sending pool, the calendar, e-signature, invoicing and team messaging — as do three that are not pictured: prospecting, the mail client and the workflow engine. Integrations that are not wired end to end are shown as unavailable in settings rather than accepting a key we would never use.

Nothing to provision. Start sending.

Authenticate a domain, search the pool, and take one record all the way to a paid invoice — on infrastructure that is already running.