The LSP Seller's Guide to On-Demand Interpreting
On-demand interpreting is no longer an upsell. For many buyers it is the deciding factor in whether they sign with you at all. This guide walks through what you are actually selling, who to sell it to, how to package and price it, how to answer the objections that come up on every call, and how to launch an account so it renews.
It is written for language service providers — agencies, community organizations, and in-house language access teams that own client relationships and need remote coverage to protect them.
Chapter 1 — The opportunity, and the risk
Scheduled on-site interpreting still matters, and it is not going away. What has changed is that no buyer expects it to cover everything. Emergency department intakes, after-hours calls, walk-ins, no-shows, and short encounters do not fit a two-day lead time.
That gap is where accounts get lost. If a buyer needs immediate coverage and you cannot provide it, someone else will provide it — and that vendor now has a foot inside your account.
Three things follow from this:
- On-demand protects your existing book. It closes the coverage gaps that give competitors a reason to call your clients.
- On-demand smooths revenue. Recurring usage is more predictable than project-by-project on-site work.
- On-demand is a fulfillment decision, not an identity change. You can offer it without becoming a call center.
Try this next: name the one account you would lose first if a competitor brought immediate coverage to them next month. Keep that account in mind through the rest of this guide.
Chapter 2 — What you're actually selling
Buyers do not buy "on-demand." They buy a specific answer to three questions: who picks up, how fast, and what shows up on the invoice. Be able to answer all three without hedging.
The offer breaks into four parts:
Modalities
- Over-the-phone interpreting (OPI)
- Video remote interpreting (VRI)
- Sign language, including ASL
- Scheduled on-site work, still coordinated in the same system
Access and workflow
- Desktop, mobile, and tablet access
- Requests submitted through customer portals rather than phone tag
- Assignment delivery to providers with confirmations and reminders
Coverage
- 24/7/365 availability
- 300+ languages supported
- A coordinated network of 7,000+ providers available for overflow
Management
- Reporting on volume, spend, fill rate, and connection time
- Credentialing and certification tracking per provider
- Billing, invoicing, and payment records tied to each encounter
Try this next: write your answers to the questions buyers ask most — What happens if my in-house interpreter is unavailable? Is sign language accessible the same way as spoken languages? What happens to a language you cannot fill? Who is on the invoice?
Chapter 3 — Who to sell it to
Before you build a list, define four things per account:
- Top use case — the specific moments this account needs interpreting for.
- Main pain point — what is costing them time, money, or risk today.
- Buying trigger — the event that moves the decision from "someday" to "now."
- Value message — the outcome they care about, stated in their words.
Two organizations in the same vertical can be entirely different conversations. A hospital running four modalities and a hospital leaning on bilingual staff are both "healthcare" and nothing alike.
By vertical
Healthcare — ED intake, consent, discharge instructions, telehealth. Pain: after-hours gaps and documentation of language access. Trigger: an audit, a complaint, or a service-line expansion. Message: immediate qualified coverage with a record of every encounter.
Legal — depositions, client meetings, court-adjacent work. Pain: confidentiality, accuracy, last-minute requests. Trigger: case deadlines and ethical requirements. Message: qualified interpreters quickly, with credentials on file.
Education — IEP meetings, parent conferences, enrollment. Pain: seasonal spikes and many languages at low volume each. Trigger: enrollment periods and district language-access reviews. Message: coverage that scales up in September without hiring.
Government and public safety — intake, field encounters, benefit interviews. Pain: unpredictable timing and rare languages. Trigger: procurement cycles and language-access obligations. Message: 24/7 coverage across 300+ languages with reportable data.
Corporate and insurance — claims, HR matters, customer support. Pain: cost control and inconsistent quality across vendors. Trigger: vendor consolidation. Message: one system, one invoice, spend you can see.
Try this next: pick the two verticals that make up most of your current book and build your case there first.
Chapter 4 — How to position the value
Match the message to the person in the room:
| Who's on the call | What they care about | Lead with |
|---|---|---|
| Compliance / risk | Defensible documentation | A record of every request, fill, and encounter |
| Operations | Fill rate and staff time | Fewer manual touches per booking; automated dispatch |
| Finance | Predictable spend | Included volume plus published overage rates |
| Department head | Their own workflow | Requests submitted and tracked in one portal |
| Executive sponsor | Coverage without headcount | 24/7/365 access without staffing a night desk |
Features do not sell. The reframe does: "automated dispatch" is a feature; "your coordinator stops making twelve calls to fill one assignment" is the sale.
Chapter 5 — How to package and price it
There are three workable structures, and most LSPs use a blend:
- Per-minute pass-through with a margin. Simplest to quote, hardest to forecast.
- Committed minimum plus overage. Predictable for both sides; rewards the buyer for consolidating volume.
- Bundled into a service agreement. On-demand included up to a threshold, then billed per minute.
Whatever you choose, price the cost you actually carry. With Eclipse, per-minute overflow rates are published by plan tier and scale as your volume grows:
| Plan | Spoken language | Sign language |
|---|---|---|
| Launch | $0.75/min | $1.75/min |
| Star | $0.725/min | $1.65/min |
| Constellation | $0.70/min | $1.50/min |
| Galaxy | $0.65/min | $1.25/min |
Two facts to build into your model: you are never charged a per-minute rate when your own providers fulfill the work, and the platform subscription is separate from overflow usage. That means your margin on in-house fulfillment is untouched, and overflow is a variable cost you control.
Try this next: before naming a price, ask "what's the biggest swing in your monthly usage, and what would make this bill feel out of control?" The answer tells you whether they need a minimum, a cap, or both.
Chapter 6 — Running the sales conversation
Most sellers open with "how many minutes do you use?" That is an invoice question, not a discovery question. Ask about the workflow instead:
- Walk me through what happens today when someone needs an interpreter and nobody scheduled one.
- Which departments request most often, and which ones avoid requesting at all?
- What happens after hours?
- How do you report language-access volume today, and to whom?
- What is your current fill rate on same-day requests — and how do you know?
The last question matters most. Buyers who cannot answer it have a data problem, and that is the easiest problem to solve in a demo.
Close on a small next step: a scoped pilot in one department, with agreed metrics, beats a full rollout you have to sell twice.
Chapter 7 — Handling objections
| They say | What it usually means | Your move |
|---|---|---|
| "We already have a provider." | They don't want to relive a vendor switch. | Position as coverage for the gaps their current vendor leaves, not a replacement. |
| "It's too expensive." | They're comparing your rate to doing nothing. | Price the status quo: coordinator hours, cancellation fees, delayed encounters. |
| "Our staff can interpret." | Bilingual staff are covering informally. | Ask what happens when that person is off, and who documents the encounter. |
| "We don't have the volume." | They fear a minimum they can't hit. | Start at the tier that matches actual volume; the plan scales as they grow. |
| "We need to see it work first." | Reasonable. | Run the pilot. Bring the metrics back. |
Chapter 8 — Objections that need proof
Quality, security, and continuity questions do not soften with a reframe. Have the evidence ready.
"How fast does someone actually pick up?" Eclipse's measured average connection time is 13.7 seconds for Spanish, 14.4 seconds across other languages, and 14.05 seconds overall.
"What if you can't fill the language?" 300+ languages are supported, with a coordinated network of 7,000+ providers available when you choose to escalate.
"Is our data secure?" Eclipse is SOC 2 Type II attested, with role-based permissions and audit records for scheduling activity.
"Will you compete with us?" Eclipse is a management platform. It does not sell interpreting services against its LSP clients, and the overflow network is opt-in — used only when you choose to escalate a request. This is the single clearest difference between a platform and a network vendor, and it is worth stating plainly on every call.
Try this next: collect your proof into one folder — connection-time data, your security documentation, a screenshot of the escalation path — before the objection arrives.
Chapter 9 — How to prove the value
Track five numbers from day one:
- Connection time — median and worst case, not just average.
- Adoption by department — where usage is real and where it stalled.
- Cost per interaction — all-in, including coordinator time.
- Fill rate on same-day requests.
- Satisfaction — from the requesters, not just the buyer.
Then build the ROI case as a comparison: current cost (staff time + interpreter fees + the cost of missed or delayed encounters) versus on-demand cost for the same volume. The gap is your pitch, and it is more persuasive with their numbers in it than yours.
Chapter 10 — Launch and grow the account
The first 30 days decide whether the account renews.
Week 1 — configure users, permissions, and request forms. Confirm who approves what. Week 2 — train the departments that will actually use it, not just the buyer. Week 3 — watch usage. Silence in a department means a workflow problem, not a lack of need. Week 4 — bring the numbers back to the buyer and agree on the next department.
Two things kill accounts quietly: a bad first experience nobody reported, and a department that never got trained and quietly kept its workaround. Both are visible in usage data if you look.
For expansion, map what you don't know — other locations, other departments, any workaround still in use — then ask about the biggest gap directly.
Appendix A — Buyer FAQ
Per-minute or subscription? Both. The platform subscription covers management; per-minute applies only to overflow usage you choose to escalate.
Do we pay per minute for our own interpreters? No. In-house fulfillment carries no per-minute charge.
What hours are covered? 24/7/365.
How many languages? 300+ supported.
How large is the network? 7,000+ providers available for overflow.
How fast is connection? 13.7 seconds average for Spanish, 14.4 seconds for other languages, 14.05 seconds overall.
Are modules extra? No. All 16+ Eclipse modules are included in every plan, with unlimited provider and customer users.
Are admin seats limited? Each plan includes a set number of admin seats; additional seats are available per seat, per month.
How long does implementation take? Most agencies are live in two to four weeks, with onboarding and implementation support included.
Is there a long contract? Cancel Anytime.
Appendix B — Email templates
After discovery Subject: Quick recap + next steps Hi [Name] — thanks for walking me through how [department] handles interpreting today. The gap that stood out was [specific gap]. Here's what a scoped pilot would look like: [one department, X weeks, metrics]. Worth 20 minutes to confirm?
After a demo Subject: The two numbers from today Hi [Name] — the pieces most relevant to [their pain] were [feature → outcome] and [feature → outcome]. Attached is the coverage and rate summary we discussed. If it's useful, I can put together a cost comparison against your current spend.
After a pilot Subject: Pilot results — ready to expand? Hi [Name] — the pilot wrapped with [X] requests, [Y]-second average connection time, and [Z]% fill on same-day. [Department] is seeing the value. Next step is [next department]. Can we find 20 minutes?
Appendix C — Why sell on-demand through Eclipse
Stated plainly, and only as facts:
- No conflict of interest. Eclipse is a management platform and does not sell interpreting services against its LSP clients.
- Overflow is opt-in. The 7,000+ provider network is used only when you choose to escalate — and never charged when your own providers fulfill the work.
- All modules included. 16+ modules in every plan, with unlimited provider and customer users. No add-on module fees, no onboarding fee.
- Measured performance. 14.05-second overall average connection time, 24/7/365 availability, 300+ languages.
- Built by the industry. Eclipse was built by professional interpreters and agency owners, and ships enhancements monthly.
- SOC 2 Type II attested, with role-based access and audit records.
- Eclipse On-Demand launches August 31, 2026.
Want this mapped to your book of business? Schedule a walkthrough and we'll build the packaging and pricing model with you.
Take this guide with you
Download the full guide as a PDF to share with your team.