Their file.
Your catalog. Proven cells.
Orbid works in the spreadsheet the buyer sent you. We write cells we can prove and leave the rest blank. Not a service-proposal writer. Healthcare equipment is the first industry — not the company.
First industry: healthcare equipment. /industries/medtech
Orbid fills the spec spreadsheet the buyer sent you. Proven cells get written. Unmatched stay blank. We don’t write service proposals or construction bids, and we don’t replace regulatory or legal sign-off.
- Catalog match on the buyer’s original rows
- A source on every written cell — blank if unproven
- The original file back, not a new document
- Speed/accuracy figures are internal benchmarks — see /methodology
Proven cells write. The rest stay blank.
Orbid fills the specification spreadsheet the buyer sent you. We ingest the original workbook, bind each required row to a product you sell, and write only the cells we can prove from your catalog. If a cell has no source, it stays blank. Those empty cells are the gap list for your factory; we do not invent a number to finish the row. We refuse service proposals and works or install packs at the pack gate. We do not replace regulatory affairs or legal sign-off. Healthcare equipment is the first industry slot on the same compiler, not the definition of the company. Excel will fill every cell. A generic language model will invent a plausible value. Proposal tools write prose. Orbid writes a commitment: a catalog-backed cell in the buyer’s original columns, or an honest blank. Bring the file they sent you to a demo. We run it live — no slides — so you can see which cells write and which stay empty.
| Input | What happens | Output |
|---|---|---|
| Their locked workbook | Pack gate refuses service and install packs | The same original file |
| Each required row | Catalog match to a SKU you sell | Match, partial, or gap |
| Proven cell | Write-back with catalog evidence | Cell written in their columns |
| Unproven cell | Leave blank — no invented spec | Factory gap list |
Stay in their file, write proven cells.
Locked Excel, multi-tab, merged cells. We work in the sheet they sent — not a new document. We refuse service proposals and works/install packs.
Pack gate first. If it is not a goods-spec workbook, we do not run it. Catalog match scores each row. Speed/accuracy figures are internal benchmarks — validate on your files.
Bind every row to a SKU.
Match, partial, or gap — with the catalog evidence that supports it. A cell gets a number only when it matches a product you sell.
We bind the buyer’s row to your catalog. Unmatched rows are not filled in. An optional public-pack feed is not the product definition — write-back is.
*Internal vendor benchmarks on controlled trials—not independent guarantees. Definitions, false-positive rules, and how to validate: /methodology.
A source on every written cell.
If we cannot prove it, we leave it blank. We don’t invent specs.
Every filled cell carries catalog evidence. The original columns come back filled where we can prove it.
Empty cells are the point.
Unmatched lines stay blank. You get a gap list for the factory.
Blanks leave the factory a list, not a new spec. That parameter is the next SKU to learn.
What a goods-spec tool actually does.
Excel fills every cell. A chatbot invents a number. Service-proposal tools write prose. Orbid writes proven cells into the original goods spreadsheet — or leaves them blank.
| Capability | OrbidProven cells or blank | Excel / sheetsFills every cell | General LLMsInvents a number | GovDash-classWrites service prose | VamstarWorth-chasing intel |
|---|---|---|---|---|---|
| Catalog / SKU matchLine-level product fit vs free text | Semantic catalog match | Manual | No catalog truth | Prose, not SKU cells | Intel, not fill |
| Proven-cell write-backCatalog evidence on the cell; blank if unproven | Write proven cells; blank if unproven | Fills every cell | Invents a number | Writes service prose | Does not fill the file |
| Buyer-template exportTheir XLSX / form filled | Original file back | You are the template | Copy-paste | Proposal document | N/A core |
| Job splitWhat the product is for | Fill cells. Not go/no-go. | Anyone | Anyone | Service-proposal volume | Worth-chasing intel |
Loopio-class RFP tools write prose — secondary to this split. Healthcare equipment is the first industry, not the company. Loopio on healthcare-equipment desks stays on that industry URL.
Common questions.
We're currently using spreadsheets. How hard is it to switch?
Most teams are live within a single business day. Upload your existing XLSX — the platform normalizes columns, maps SKUs, and runs the first match automatically.
Can we migrate data from our current RFP tool?
Yes. We support bulk import from all major RFP platforms and CRM systems. Our onboarding team handles the migration — historical tenders, product catalogs, and award records.
What systems does Orbid integrate with?
The platform connects to SAP, Oracle, Salesforce, and most ERP/CRM systems via REST API and webhooks. We also support SFTP and native Slack integration.
What does Orbid check before it writes a cell?
A cell is written only with catalog evidence. If we cannot prove it, it stays blank. Sector regimes (FDA, EU MDR, and peers) are evidence on a healthcare-equipment desk — see /industries/medtech. They are not the company product.
Which languages are supported?
The matching engine operates at full parity across seven languages: English, German, French, Spanish, Italian, Portuguese, and Arabic.
Can Orbid be self-hosted?
Yes, on the Enterprise plan. We support deployment in your own cloud or on-premise infrastructure. Data residency options include EU, US, and APAC regions.
Bring their
spreadsheet.
Book a demo. We run the file they sent you and show which cells we fill, which we leave blank, and why.