Prepare a Supio quote request with a workflow-scope worksheet covering document analysis, provider outreach, communications and integrations.
What can you verify about current Supio pricing?
What does Supio cost? On October 23, 2026, Supio’s pricing URL redirected to its request-a-demo page, where no numeric rate or current plan table was visible. That observation does not establish what a particular sales quote includes. Ask for a dated proposal tied to your firm’s work. An older price anecdote cannot tell you which products, volumes, services or terms apply to your purchase.
For a small PI firm, the first useful number is the workload the proposal covers. Eighteen active matters, eighteen uploaded files and eighteen outbound tasks describe different things. Do not assume they use the same billing unit. The worksheet below is an original purchasing aid from VerifyMD, not a hands-on Supio review or a claim about how Supio currently meters its contracts.
Describe the workload before asking for a package
Supio’s Case Communications page describes provider and carrier calls, records requests and client-facing work across several channels. Its Case Ledger page describes document-derived financial line items and source links. Its integrations page lists connections across case, document and communication systems. Those descriptions identify scope to discuss; they do not establish which capabilities are bundled into your quote.
Start with work your team actually assigns. Count open matters separately from new matters, incoming document batches and requested contacts. For each workstream, name the outcome you need and the person who will review it. A firm seeking a better bill ledger should not accidentally approve client outreach simply because both appear in the same product presentation.
Build a quote packet with separate workstreams
Complete the first two columns before the demo. Ask the vendor to complete the quote column in writing, including items described as included or unavailable. These are proposed purchasing questions, not asserted Supio billing units. Preserve a blank or unknown answer as an open decision instead of converting it to zero cost.
Swipe across the table to see every column. Keyboard users can focus the table and use the arrow keys.
| Workstream | Your forecast and deliverable | Vendor answer to record |
|---|---|---|
| Document analysis | Matters, incoming batches and the reviewed output needed | Quoted product, billing unit, included quantity and reprocessing treatment |
| Provider outreach | Recipient offices, requested tasks and completion evidence | Covered channels, follow-up scope and treatment of unresolved tasks |
| Carrier or client communication | Separate recipient groups; enabled and excluded actions | Included capabilities and process for approving a scope change |
| Integrations and support | Named systems, data direction and responsible staff | Included setup, ongoing support, optional charges and prerequisites |
A fictional workload mix for the sales conversation
Fictional planning example: a two-paralegal firm has eighteen active matters, expects four new document batches, needs six provider follow-ups and wants two carrier status checks next month. It does not want client outreach enabled. These are workload estimates, not customer results or a recommended package. Give the vendor this mix and ask it to identify the actual charge-triggering events, any minimum commitment and what happens when a task stays unresolved.
Then change one variable. Keep the eighteen matters but add a second provider request on one matter. Ask whether that changes the charge, consumes an allowance or stays within the quoted scope. Next, ask the same question about adding a connector or enabling a previously excluded communication workflow. This exposes scope dependencies without presuming that price follows matters, seats, tasks or documents.
Name the deliverable and the reviewer
Keep the requested deliverable precise. A records request submitted, a file received and a file reviewed are separate events. A document-derived ledger and a fresh provider response also answer different questions. The Supio Case Ledger reconciliation checklist helps define the review work that remains after financial information is extracted. Your quote packet should identify which event satisfies each purchased task and how exceptions appear in the matter.
Assign a reviewer to every quoted line. The operations lead can confirm workload, the case-team lead can approve task boundaries, and the person responsible for systems can review access and support. The Supio contact and approval map is useful for deciding which recipient groups and actions belong in the initial scope. Adding a feature to a proposal should not silently grant permission to use it.
Account for implementation and later scope changes
Ask for implementation work on its own line: configuration, staff training, migration, connector setup and ongoing support. Record who supplies each prerequisite and how a blocked launch affects the agreed start date. For integrations, request the named connector, data direction, included outputs and support owner. A connector appearing on a website does not answer what your agreement includes.
Before signing, reconcile the final order form against the completed worksheet. Ask which terms govern renewal, a scope change, excess usage, cancellation and access to retained records. Save the proposal version and the vendor’s answers together. If a verbal answer changes a material term, obtain the corresponding written clarification rather than leaving future staff to reconstruct the conversation.
A short quote request you can adapt
You can send a compact request: “Please quote the attached workload by product and included service. Identify the actual billing unit, commitment, included quantities, excluded workflows, setup responsibilities and exception treatment. Mark which changes require a new price or approval. Our initial scope excludes client outreach. Please return a dated proposal and identify any assumptions we must confirm.” Replace the example scope with your firm’s decisions before sending.
Compare the provider task on its own terms
If the immediate gap is a narrow provider check, compare that task separately. VerifyMD’s pricing and case-cost scope publishes a standard $10 USD charge for one completed requested verification for one provider and case, supported by evidence and your team’s approval. Calling limits, permissions and service terms are agreed before activation. Applicable tax and separately scoped work are confirmed in advance. This is a different unit of work, not a price comparison with an unquoted Supio package.
Keep the supplier purchase separate from any decision to charge a client. A software subscription or task invoice does not become automatically recoverable because it relates to a case. Your firm pays the supplier under its agreement; client-expense eligibility and actual collection require separate review. To assess the provider-call portion, explore VerifyMD’s balance verification workflow, then bring a specific task and approved scope to the demo. Buy the work you have defined and retain the questions the quote has not answered.
Explore provider follow-up and source review for your firm. Live calls require agreed setup and activation.
Book a demo