Somebody on the leadership team has decided the bid process needs fixing, probably after a deal you all thought you’d win, and it’s landed on your desk. You search for help. What comes back is a dozen names for what sounds like the same thing. Market intelligence, sales intelligence, competitive intelligence, account intelligence, RFP software, proposal management, response management, CPQ. Every vendor says it covers the whole deal.
Most of those vendors started in one part of the deal and grew outwards, so each is strong where it began and thinner the further it gets from there. It’s worth knowing what each category was built to do, where it stops and what falls in the gaps between them, before anyone books a demo.
A deal, from first signal to final price
Most competitive B2B deals go through the same five points, whatever you sell and whoever you sell it to. Something tells you a buyer might be about to move. You work out who they are, who’s involved and who you’re up against, which takes longer than anyone admits. The buyer asks how you’d do it. You price it. Then you win or lose, and you learn something from it, or you should.
Each of those points has its own category of tool, built by a different set of vendors for a different person in your team. Marketing or the sales team owns the signals, pre-sales and product marketing own the competitor material, the bid manager owns the response and finance or a deal desk owns the price. That’s how the market grew up, and it’s the reason the joins are where things go wrong.
Market and tender intelligence
This is the category that tells you something is happening before the buyer tells you, and it matters more than it used to. Gartner’s survey of B2B buyers found they spend only 17% of their buying time meeting potential suppliers, so most of the decision is made where you can’t see it. In the private sector the signals are scattered. A new finance director, a merger, a round of funding, a system going out of support, a job advert for someone to run an implementation, results that miss by enough to make the board ask questions. Companies House filings are public and free to search, and its free Follow service emails you when a company you’re watching files something new, whether that’s its accounts or a director leaving. Most of the rest comes from news, press releases, LinkedIn and whatever your sellers pick up in conversation, and the tools in this category mostly gather those into one feed and flag the ones that match your target accounts.
In the public sector it mostly means tender alerts. A tool reads the notices published on the government portals, matches them to what you sell and sends you the ones worth a look. The better ones go further back than the tender itself. Under the Procurement Act 2023, a public buyer expecting to spend more than £100m in the coming financial year has to publish a pipeline notice listing the contracts over £2m it plans to tender in the next 18 months. Contract details notices tell you who won a contract, what it’s worth and when it ends, extension options included. From January 2026 buyers also have to publish how well their suppliers are performing against the KPIs on contracts over £5m, so an incumbent that’s struggling can be visible from the outside. A re-tender you can see coming 18 months out is a very different proposition from one you find the week it’s published.
Where teams go wrong is volume. A tender alert that matches on a keyword will send you 40 notices a week, 35 of them irrelevant, and within a month nobody opens the email. The alerts that get read are the ones scored against what you actually win, sent to the one person who should act on them. Then there’s where the alert ends up. It usually lands in an inbox, and nothing links it to the account, the competitor or the bid that comes later.
Account and competitive intelligence
Once you know a buyer is moving, the questions change. Who’s in the buying group, who decides and who can say no? What do they run today, when does that contract end and how happy are they with it? Who else is bidding, and what will they say about you?
Account intelligence usually lives in the CRM, or is meant to. In practice the useful part lives in the heads of the two or three people who’ve worked the account longest, plus a few notes and an account plan that was accurate the week it was written. When one of those people leaves, most of what the business knew about the account goes with them.
Competitive intelligence is its own category, with its own tools and, in bigger companies, its own team. It watches rivals’ websites, pricing pages, product releases, hires and customer wins, and turns what matters into battlecards, the one or two pages a seller reads before a call. Win-loss analysis sits here too, talking to buyers after a decision to find out why you really won or lost, which is rarely the reason the seller put in the CRM.
The honest problem with battlecards is that most aren’t read. The ones that are read are often out of date. A rival changes its pricing or ships the feature your card says it lacks, and the card carries on saying the old thing for months. A battlecard is only as good as the last time somebody checked it against what the competitor is actually doing.
RFP and response management
Most bid teams know this one best. The core of every product in it is an answer library, the approved answers to the questions buyers keep asking, with owners and review dates so they don’t go stale. The tool takes in the buyer’s RFP, tender or security questionnaire, drafts from the library and sends the questions it can’t answer to the people who can. Most now use AI to write the first draft, and the good ones show you which approved answer each sentence came from.
Our guide to RFI, RFP, RFQ and ITT covers the documents themselves. What matters here is what these tools don’t know. A response tool knows your answers. That’s all it knows. It doesn’t usually know that the buyer’s new director came from a customer of your competitor, that the incumbent’s contract has been going badly, or that your price has to come in under a number the buyer mentioned in passing six weeks ago. The answers get written well and still miss the point of the deal.
The library also has a habit of learning only from wins. A bid you lost on price, where the buyer scored your quality answers top, is just as strong a response set, and most teams never go back to it.
CPQ and pricing
CPQ stands for configure, price, quote. It started with companies selling products that come in a lot of options, where the hard part is making sure the configuration is valid and the price follows the price book. A seller picks what the customer wants, the tool applies the list prices and the discount rules, anything outside the rules goes for approval and out comes a quote document. Deal desks use it to stop sellers giving away margin in the last week of the quarter.
That works well for licences, subscriptions and anything with a SKU. It’s less good at the part of a software deal that decides whether you make any money, the services. How many days will the implementation take? How many sites, integrations and data migrations are there, and how confident are you in each number? In most teams that estimate lives in a spreadsheet somebody built years ago, with a tab per project, formulas nobody quite trusts and a contingency figure added at the end to cover the doubt.
Price optimisation is a separate category again, mostly for companies with thousands of products and transactions, where software can learn from past deals what the market will bear. For a team pricing 20 competitive bids a year, the useful inputs are narrower. What does the work actually take, what do your rules allow and where is the competitor likely to come in?
The handoffs where deals are lost
Every category above does its own job reasonably well. The deals that get lost for avoidable reasons are usually lost between them, when something one tool knew never reached the person using another.
Some of it is timing. A tender alert arrives in marketing’s inbox on a Monday and reaches the seller on Thursday, after the clarification window has closed. Some of it is knowledge that was in the building and in the wrong place. The competitor’s price cut made it onto the battlecard and never reached the quote. Your RFP response promised an integration with the buyer’s finance system that nobody remembered to put in the services estimate. Or the security questionnaire said the backups were in Ireland and the proposal said the data stays in the UK.
And some of it is what happens after the decision. You lose, the seller records “price” in the CRM, and nothing else changes. The battlecard doesn’t learn what the competitor offered, the answer library doesn’t learn which answers the buyer scored well and the pricing spreadsheet doesn’t learn that your implementation estimate was 40 days more than theirs. The next bid against the same competitor starts from exactly the same place.
None of this is fixed by buying more tools. Every new tool is another place a fact can sit without reaching anybody.
What fixes it is deciding where each fact lives, who’s told when it changes and what it updates when it does. That’s a process decision first and a software one second.
What does a team of each size actually need?
A small team, a handful of sellers with no dedicated bid manager, rarely needs a specialist tool in any of these categories. A CRM kept properly, free tender alerts from the government portals, a shared folder of good past answers and a pricing spreadsheet with its assumptions written down will get you a long way. The thing to protect is what the founder or the lead seller knows, so write it down against the account while it’s still in one head.
Once there’s a bid manager and more than one live bid at a time, the answer library usually starts to pay for itself, because the same questions keep coming back and people are rewriting them from memory. Paid tender intelligence makes sense at this point too, if public buyers are a real share of your pipeline. Competitive intelligence often stays as a folder of battlecards that one person looks after.
Larger teams, with pre-sales, a bid team, a deal desk and several competitors that matter, end up with most of the categories, and usually with a different owner for each. At that size the tools aren’t usually the problem. The problem is the gaps between them, and the time good people spend carrying facts from one system to the next instead of deciding what to do about them.
Whatever size you are, don’t start with the category that has the best demo. Go back over the last three or four deals you lost, and for each one ask where it actually went wrong. A tender found too late is a signals problem. If the seller walked in without knowing who the incumbent was, that’s the account record. And if the answers were fine and the price was 20% out, no answer library in the world will fix it. You’ll usually find the same gap more than once. Buy for that one first.
How Dajemano does this
Dajemano puts these categories on one record, so a fact found in one place reaches the work it affects. Sense watches the market and the tender portals. Enable keeps each account and competitor, sourced and dated, with battlecards your people approve before they change. Respond drafts bids from approved answers, and Calibrate has agents size the work from the buyer’s requirements while code calculates every figure from your rate card, with anything outside your rules sent to an approver. Each deal’s outcome goes back onto the record for the next one. Dajemano launches in 2027.
Sources
- Procurement Act 2023, section 93, Pipeline notices
- Procurement Act 2023, section 53, Contract details notices and publication of contracts
- Procurement Act 2023, section 71, Assessment of contract performance
- Follow companies for free, Companies House, GOV.UK
- The B2B buying journey, Gartner, archived January 2023