Connectors that explain why the product works
Connectors should not look like a random list of logos. BidBlender groups them into four paradigms that explain why the data matters: History, Capability, Reach, and Opportunity.
Why the connector model matters
History
Past deals, contacts, and win/loss data from your CRM. Powers technical fit scoring, past-bid comparison, and buyer relationship context. e.g. HubSpot, Salesforce — your deal history and contact records.
Capability
Skills, certifications, and training from your HCM or LMS. Powers capability matching and resource allocation for bid teams. e.g. Workday, BambooHR, Cornerstone — who can do what.
Reach
Relationship intelligence — who knows whom, decision-maker proximity, network strength. Powers the Network section and SWOT analysis. e.g. LinkedIn, Apollo, ZoomInfo — your relationship graph.
Opportunity
Active tenders and RFPs from boards and panels. Powers opportunity discovery, due-date tracking, and the opportunity explorer. e.g. TenderLink, AusTender — what’s in market.
What settings should let the user control
The settings story matters because connected data should be intentional. Users need to understand what is included, what is optional, and what each connection improves.
Opportunity sources
Users should be able to choose the tender boards and procurement sources that define their market view so discovery reflects the sectors and channels they actually care about.
History sources
CRM and deal-memory systems should be added because they improve commercial memory, buyer familiarity, and prior-pursuit comparison, not because more integrations automatically look impressive.
Reach and capability sources
Relationship and workforce systems should be introduced carefully so users can see exactly how access posture and delivery readiness change the recommendation quality.
Truthfulness about status
The site and product should use the same language for availability: live now, connected via integration, or planned. That keeps the story commercially useful without pretending unfinished work already exists.
Connector Explorer
Explain the why, not just the integration
Placeholder for an interactive module where visitors switch between History, Capability, Reach, and Opportunity to understand what data each category contributes and how it changes product outputs.
Poster state for a future interactive module.
Comparison
Why connected evidence beats a tender-board-only workflow
Placeholder for a visual comparison showing how tender discovery becomes more useful once it is paired with internal history, capability, and reach.
Poster state for a future product walkthrough.