Your RFQ data is your balance sheet
The inquiries you've received are the clearest picture of your demand that exists. The question is whether that data is yours to read, export and keep.
Every exporter keeps a ledger of what they sell. Almost none keep a ledger of what they’re asked for — and that’s a mistake, because the RFQs you’ve received are the closest thing your business has to a demand forecast written by the market itself.
Think about what an inquiry contains. A buyer has told you, unprompted and in writing: what product they’re interested in, at roughly what specification, with what volume in mind, from what company and country. Stored over a year, that’s a map of your demand — which lines are pulling, which regions are waking up, which inquiries turned into orders and which died at the quoting stage and why. A marketplace or a shopping-cart platform that quietly warehouses that history for you is holding your balance sheet. The question this post is about is whether you can actually get it back.
The data you think you have versus the data you can reach
Here’s a small experiment worth running. Open your current sales channel and try to answer three questions:
- How many inquiries did you receive last quarter, by product line?
- Which three buyers have asked the most without ever ordering — your best future pipeline or your biggest time sink?
- Can you export that entire history, with contact details, into a file you control?
For most exporters I talk to, the first question is guesswork, the second is a hunch, and the third is where the conversation stops. It’s not that the data doesn’t exist — it’s that the platform that collected it decides whether you may have it. That decision is the whole game.
I wrote earlier about where an export RFQ actually lands and why a marketplace’s incentives point it toward holding buyer contacts close. This post is the follow-through: what that holding costs you, in a way you can feel on your own spreadsheets.
Why portability is the real test of ownership
People use the word “your data” loosely, and the looseness is expensive. Ownership is not a feeling; it’s the ability to leave. If you can take your inquiry history to a spreadsheet, a CRM, or a different provider without asking permission, you own it. If you can’t, then whatever warm language the platform uses, the asset is theirs.
That test — can I export, and is the export complete? — is the one worth applying to every tool your business depends on. It’s the reason our data export guide opens by listing exactly what an export contains, rather than promising “full data access” and hoping nobody asks for a definition. An export that quietly omits buyer contact history isn’t a feature; it’s a euphemism.
The uncomfortable truth is that some platforms can’t give you a clean export even when they want to, because the data was never cleanly yours to begin with. Inquiries are stored in one system, order history in another, product listing data in a third — and your “history” is whatever their reporting layer happens to expose this quarter.
What a dedicated database changes
This is where the architecture of where your business runs stops being a technical detail and becomes a commercial one.
On a shared, multi-tenant system — a marketplace, a big cart SaaS — your data lives in a database shared with thousands of other businesses. That’s not inherently bad; it’s how scale works. But it means every decision about your data is made for the average of all tenants, and the platform’s business model is part of that average. When the platform monetises the buyer relationship, “how much inquiry data can the seller export” is answered by a spreadsheet that includes the platform’s revenue.
On a dedicated instance, the calculation changes completely. Your catalog, your inquiry history and your configuration live in a database that is yours alone. There is no other tenant whose data an export would have to be careful around, and no business model that rewards defining “your data” narrowly. The export is triggered by you and contains everything — because nothing about keeping it from you serves anyone. If you want the structural argument in full, my post on dedicated versus shared infrastructure goes through it without the hype.
Building the ledger you actually need
None of this requires a dramatic platform exit tomorrow. What it requires is a habit, and the habit is cheap:
- Run a quarterly export of your inquiry data from every channel you use, and keep it somewhere you control — your own drive, your own cloud, your IT team’s backup.
- If a channel won’t export, treat that as a finding about the channel, not an inconvenience. Write down what you can’t retrieve; it’s the truest measure of what that platform really is to you.
- Ask what a buyer relationship is worth to you before a platform answers for you. The first RFQ from a new market is worth little. The fiftieth, with a year of follow-up behind it, is worth a great deal — and that value should accrue to your company, not to the queue it arrived through.
There’s an exit-insurance angle to all of this that deserves its own treatment, and I wrote it up separately: what happens to your business if your SaaS shuts down tomorrow. The short version is that a business is only as durable as its ability to leave the tools it runs on.
The question to sit with
Forget the dashboards for a minute. If your largest buyer’s procurement team emailed you directly tomorrow with a spec that exactly matched an RFQ you received nine months ago and never closed, would you know? Would you have the record, the contact, the context — or would it be sitting in a platform’s archive that you can look at but never take?
That’s what “your RFQ data is your balance sheet” means. Not that you should love spreadsheets. But the demand signal your business generates is the most valuable thing you don’t currently own — and the first step to owning it is noticing, clearly, that you don’t.