Company stories
Speya: From Supplier Discovery to RFx
A buyer-focused look at Speya’s supplier discovery, research and RFx workflow, with questions to test before a sourcing pilot.
On this page
Speya, formerly Find My Factory, presents a sourcing workflow that begins with a buyer’s description of what is needed and continues through supplier discovery, research, RFx and monitoring. Its public materials position AI as a way to bring candidate research and the next sourcing step into one workspace.
That sequence is a useful frame for evaluation, but a buyer should test each transition. A promising supplier profile is not the same as a verified fit, and an RFx sent to the wrong entity or with incomplete requirements can create more work than it saves.
Where Speya fits in the sourcing journey
Speya’s overview ↗ describes an ask → discover → research → RFx → monitor progression. A buyer can start with a natural-language need, review possible suppliers, collect research and move selected candidates into an information, proposal or quotation request. Its RFx feature page ↗ describes response timelines and comparison of replies.
The product therefore spans candidate generation and early sourcing execution. It does not remove the buyer’s responsibility to define the specification, decide which suppliers deserve an invitation, approve outbound requests or evaluate a final offer. For a broader market view, see the supplier-discovery AI guide.
Check supplier identity before using a generated shortlist
Ask Speya to work on a real category where your team knows several suitable and unsuitable suppliers. Inspect the legal entity, actual capabilities, relevant geography, recent evidence and source date behind each suggested match. Speya describes source-backed supplier profiles, but the buyer should verify how each statement was obtained and whether it refers to the product, parent company or a different operating unit.
Include a near match: a company that uses the right terminology but cannot meet a must-have material, certification or delivery region. A useful system should expose the gap instead of turning keyword overlap into confidence. Our supplier discovery verification worksheet provides a repeatable test set.
Follow one candidate into an RFx
| Step | Ask Speya to show | Buyer decision |
|---|---|---|
| Define the need | Mandatory requirements, optional preferences and missing information. | Approve the brief before supplier search. |
| Review candidates | Source evidence and reasons for inclusion or uncertainty. | Select the legal entities to invite. |
| Prepare RFx | Questions, recipients, response dates and version history. | Approve exactly what suppliers will receive. |
| Compare replies | Missing answers, comparable terms and source documents. | Resolve gaps before ranking offers. |
| Monitor | What changes after selection and who receives an alert. | Decide whether a new fact requires action. |
Test a supplier reply that uses a different unit of measure and another that omits a mandatory requirement. The system should preserve the original response and make the comparison gap visible. Ask which actions are automated and which wait for buyer approval.
A useful first pilot is narrow and evidence-rich
A good pilot has a defined category, known specification, a small reference set of suppliers and an RFx the team already needs to run. Track useful candidates found, false matches, source corrections, time to an approved RFx and effort to compare responses. Do not treat a larger generated list as success on its own.
Confirm Speya’s current data sources, geographic coverage, supplier communication method, integrations and permissions in a live demonstration. Review the official Speya website ↗ and its ProcurementAI company profile for the published starting points; the profile still uses the original directory slug.