01
RFQ + quote
When a request and an observable quote can be matched defensibly, request-to-quote timing becomes measurable.
RFQ INTELLIGENCE · SELLER SIDE
Requests come in.
Quotes go out.
Your ERP knows what was processed. Your mailboxes know what was requested. Those sets are not necessarily identical. Palvexa measures the observable gap using only the sources you approve.
SEE THE MODEL ↓01 / THE MODELMatch what comes in
Match what comes in
to what goes out.
V1 takes one bounded RFQ workflow, observes requests and quotes visible in approved sources, and reconstructs only what the evidence supports. Everything else remains explicitly unknown.
02
Quote with no observable origin
Palvexa reports “no observable inbound origin.” It may have come from a portal, phone call, personal mailbox or another unconnected source. The system does not invent the origin.
03
RFQ with no observable quote
This is an unresolved case and a potential leak to validate — never automatically a “lost” request. A no-bid, duplicate, handoff or off-email response may still explain it.
02 / COVERAGEA metric without coverage
A metric without coverage
does not tell the whole story.
Timing is calculated only on the matched subset. Every readout should show what share of issued quotes is covered by timing metrics and how many quotes have no observable inbound origin.
01
Defensible timing
Response-time metrics only when the necessary events are observable and matched correctly.
02
Open cases
Requests without an observable quote are surfaced for validation instead of being labelled automatically.
03
Visible unknowns
An unconnected source creates a measured unknown. It does not disappear silently from the analysis.
04
Traceability
Findings retain provenance so a manager can understand what evidence supports them.
03 / CLIENT EXPERIENCEYour tools stay in place.
Your tools stay in place.
Palvexa observes above them.
V1 is not a new CRM, an ERP replacement or a daily employee application. It starts with the minimum approved Microsoft 365 sources and relevant attachments, then produces passive management visibility.
01
Bounded scope
One precise workflow, a minimal approved mailbox set, a known observation window and explicit coverage rules.
02
Baseline
Volume, matched-subset timing, open-case age, trends and observable anomalies without asking the team to adopt a new daily routine.
03
Recurring readout
Facts, signals and hypotheses are separated clearly and paired with confidence instead of invented causality.
04 / FOUNDING PARTNERThe first validation sample
The first validation sample
is intentionally narrow.
Palvexa is currently validating this model with parts distributors and suppliers, seller side, where RFQs recur and a sufficiently high share of issued quotes is observable through approved email sources.
01
Good fit
Economically meaningful RFQs, recurring volume, multiple people or steps and imperfect management visibility.
02
Technical gate
Discovery measures where RFQs arrive and where quotes are issued before any coverage promise is made.
03
Not email-only at any cost
If many quotes bypass email through a portal, EDI or ERP, email-only V1 is not the right boundary or a second source must be justified.
04
Evidence before expansion
A source or workflow is added because a measured unknown justifies it, not to pre-build a generic platform.
IS YOUR RFQ FLOW OBSERVABLE?
Start by
measuring the boundary.
A few questions about RFQ channels, quote delivery and volume are enough to determine whether V1 can produce a credible readout.
Evaluate your RFQ flow