Methodology
The methodology page should explain how BidBlender reasons about bid/no-bid decisions, why the four paradigms matter, and how the system is designed to pair recommendation with evidence confidence instead of hiding the logic behind black-box scoring.
How the model should be explained
Four paradigms
History, Capability, Reach, and Opportunity are the core evidence classes that shape how BidBlender interprets pursuit quality.
Decision dimensions
Pursuit capacity, buyer access, delivery fit, strategic desire, and evidence confidence provide a clearer model than a single opaque score.
Traffic-light outcomes
Green, Amber, and Red give the product an action-oriented output rather than forcing users to interpret a raw number without guidance.
Confidence and blockers
The methodology should make clear that ambiguous opportunities are often about missing evidence, not middling quality, and that the system should surface blockers and movers explicitly.
Frequently Asked Questions
Should this page expose the exact scoring implementation?
It should explain the logic and the reasoning structure clearly, but it does not need to publish every internal weighting or implementation detail.
Why is methodology a trust page, not just a feature page?
Because it helps customers understand that BidBlender is structured and reasoned, not simply generating persuasive-looking summaries without a clear decision model.
Reading the site
How BidBlender labels capability status
The public site distinguishes between what is already available, what becomes useful once data is connected, and what is still part of the product direction. That keeps the story clear without flattening everything into one vague promise.
Core product surfaces and workflows that already exist in the current BidBlender experience.
Capabilities that depend on configured data sources, integrations, or customer-specific setup.
Directionally important workflows and platform extensions that are signposted carefully, not overstated as available.