An operations manager at a US company with 80 employees is not hunting for a BPO. They're dealing with a support inbox that's backed up by Wednesday, a billing team that is a person short, or a data-entry task that is eating a salary. A small outsourcing company wins by offering to take one of those queues for 30 days, for money, with the security questions already answered.

This guide covers what US firms will and won't outsource, how to pick one function, how to find operations leaders, and the two documents to send with the first email: a pilot scope and a security answers sheet.

What US firms outsource and what they won't

Small and mid-size US companies will usually outsource repetitive, well-defined work with clear instructions and measurable output: tier-one support tickets, order processing, data entry, invoice matching, appointment scheduling, claims intake, lead qualification calls. They hesitate to outsource anything that involves judgment calls with legal exposure, customer-facing escalations that need authority to make exceptions, or data under strict regulation.

They worry about three things. Quality (will customers notice the difference?), security (who can see our data?), and control (what happens when we need a change today?). A pitch that ignores these three fails; a pitch that answers them in the first email stands out from the dozens that start with "cost savings of up to 70 percent."

Pick one function and say it

A small BPO that claims to do support, billing, data entry, scheduling and collections sounds like it does none of them well. Pick one: support for online stores, medical-office scheduling, accounts payable processing, or real-estate transaction coordination. One function lets you build scripts, a quality checklist and references that actually fit. Say it in the first sentence of every email.

For practice-specific adjacent services, see how medical billing companies and payroll companies find clients, and virtual assistants for the individual version of the work.

Finding operations leaders by name

The buyer is the VP of operations, the operations manager, the head of customer support, or the owner at a small company. Triggers are visible. Repeated job postings for the same support or back-office role suggest turnover. A seasonal business that posts temporary roles every autumn has a volume spike. A company whose reviews complain about slow responses has a queue problem. Build a list of 40 with names, the function you can take and the visible trigger. The decision-maker guide covers how to confirm the right person.

A first email to an operations manager

Subject: Taking your support inbox for 30 days, with a quality report each week

Hi Gwen, I saw Larkfield Home posted a customer support role for the third time this year. We staff email support for online stores, with a US-based team lead and agents working a 7 a.m. to 11 p.m. Eastern schedule. I'd like to take your first-tier tickets for 30 days as a paid pilot: a fixed volume, a response-time target, a quality score on every ticket, and a weekly report. A pilot scope and a one-page security answer sheet are attached. Arjun Rao, Tidewater Support Services, [mailing address]. Reply "no" and I won't write again.

The email mentions the posting that triggered it, states hours that cover US time zones, and attaches two documents. A buyer reading it already has what they need to pass to their manager and their IT lead.

The pilot scope on one page

A scope turns "let's try it" into something both sides can say yes to. Include:

  • The queue. First-tier email tickets: order status, returns, shipping address changes, product questions.
  • Volume. Up to 1,500 tickets over 30 days.
  • Price. $2.80 per resolved ticket, billed at pilot end. 1,500 times $2.80 is $4,200, the most the pilot can cost.
  • Targets. First response within 4 business hours. Quality score of at least 90 percent on a review of 10 percent of tickets, scored by the client's own checklist.
  • Escalation. Anything about refunds above a set amount, legal threats or safety goes to the client's named contact within one hour.
  • Reporting. A weekly one-page report: tickets handled, response time, quality score, top issues, suggested fixes.
  • Exit. Either side can end the pilot with 5 days' notice.

The price is per ticket, not per hour, so the client's risk is bounded. A cap of $4,200 is a number an operations manager can sign without asking the CFO.

Answering the security and quality questions early

Send a short sheet. Answer honestly and in plain words. A sample for a pilot that does not handle payment cards or health data:

  • Agents use the client's help desk with accounts the client creates and can remove at any time. No client data is downloaded or kept on agents' own devices.
  • Agents work from company-managed laptops with multi-factor sign-in and screen locks.
  • Every agent signs a confidentiality agreement and has had a background check; ask us for the terms.
  • We do not handle full payment-card numbers, Social Security numbers or health information in the pilot. If your work requires them, we'll tell you what controls we can and can't provide before starting.
  • We do not hold certifications we don't have. Here is what we do and what we plan to add.

Honesty matters here, because a buyer's IT team will check. For regulated data, legal and compliance review is the client's call and general information like this is no substitute for it.

On time zones: say your overlap hours and the number of agents on shift at each hour. On quality: describe how you score tickets and who reviews the scores. A buyer who can see the scoring method trusts the number.

Following up with a paid pilot

Three days after the first email, send the scope again with one change: "I can start next Monday if we agree this week." Ten days later, ask a question rather than push: "Is support volume heavy before the holidays? I can add a second shift at the same per-ticket price." If the buyer says no, ask what would make a pilot easier to approve. Often the answer is a smaller volume or a different queue.

Reporting that keeps the contract

The weekly report is the product after the pilot ends. Send it on the same day each week, include the one thing that went wrong and what you changed, and review it live with the client in the third week. At day 25, send a proposal for the next three months with the per-ticket rate, a volume range and a monthly minimum. Clients renew when the report has been honest.

Many such buyers sit on lists that are too long to chase by hand. Rocketship finds operations leaders by name, emails them from your own Gmail, follows up, and books the call on its own. Plans that get you customers start at $24.99 a month (Launch), and both Launch and Frontier start with a 7-day free trial, card required. See the AI workers.