Insights
A weekly pipeline summary
Flow runs the task every Monday and each run opens its own thread, so the team reads the same figures.
Insights
Your win rate and pipeline,in one place.
Insights shows what your team submits and wins. Flow, the Tendersight agent, answers questions about the numbers and summarises them on a schedule.
Win rate from submitted and won bids
Total and qualified pipeline value
Answers grounded in your data
The overview shows the numbers. Flow answers the questions behind them.
Ask about your pipeline, a buyer or a competitor. Flow reads your pursuits and public procurement data and replies with figures, a chart or a file that lists its sources.
What a bid team reports on.
The same questions come back every week, from the team and from management.
Win rate
How many submitted bids were won, and how the rate moves from quarter to quarter.
Pipeline value
What is in play, in total and after qualification.
Submissions due
What closes in the next seven days, and how complete each bid is.
Team contribution
Who submitted which bids over the year.
Buyers
Which contracting authorities buy what you sell, and how often they publish.
Competitors
Who bids on the same CPV codes, and where they win.
How Flow reads your numbers.
The overview holds the charts. Flow answers the questions around them and prepares the review.
Win rate, pipeline value, win rate by quarter, team bid contribution, the bid pipeline from new to won, and bids submitted against won.
Ask in plain words. Flow reads your team's pursuits and answers in the conversation with figures and a chart grounded in that data.
Flow reads contracting authority and company statistics: frequent CPV codes, market share, regional coverage, main competitors and participation over time.
Flow produces the review as Excel, PDF or Word. Spreadsheets list their sources and assumptions, and each file is marked internal working.
For a quarterly review Flow writes the plan first, gives research to side agents and waits for your approval before it starts.
Questions you can ask Flow.
Examples from sales and bid managers who report on public sector sales.
- Pipeline
Summarise our pipeline by stage and show the qualified value for Q4.
- Win rate
Chart our win rate by quarter for this year and last year.
- Buyers
Show the contracting authority statistics for the Vienna hospital association and the CPV codes it buys most.
- Competitors
Who are the main competitors on CPV 90910000 in Austria, and how has their participation changed since 2023?
- Schedule
Every Monday at 08:00, summarise the pursuits due in the next 7 days and their completion.
- Report
Build a spreadsheet of this year's won and lost bids with their estimated values, and list the sources.
Reporting work Flow takes over.
Weekly summaries, buyer research and the figures management asks for, each set up in a conversation.
Open tenders from the buyers you know
Ask for a buyer's tenders by name. Flow filters the catalogue by contracting authority, value and deadline.
Figures from your own pursuits
Win rate and pipeline value come from each pursuit's status and estimated value. Keep them current and the reports stay accurate.
Missing values, filled from the offers
Standalone pursuits without an estimated value are left out of pipeline totals. Flow proposes values from their financial offers and waits for confirmation.
A summary for management, drafted
Flow writes the email with the quarter's figures. You open it in your email client and send it.
Where each number comes from.
Every figure is calculated from your pursuits or from public procurement data, and Flow can answer questions about any of them.
Current win rate
- Calculated from
- Bids won against bids submitted
- A question for Flow
- What is our win rate this year?
Pipeline value
- Calculated from
- Estimated value of pursuits, total and qualified
- A question for Flow
- What is in our qualified pipeline?
Bid pipeline
- Calculated from
- Pursuits from new to analysed, qualified and won
- A question for Flow
- How many pursuits did we qualify this quarter?
Submissions due
- Calculated from
- Pursuits with a deadline in the next 7 days
- A question for Flow
- What is due this week?
Team bid contribution
- Calculated from
- Bids submitted by each member
- A question for Flow
- Who submitted the most bids this year?
Buyer and competitor statistics
- Calculated from
- Public procurement data from TED and national portals
- A question for Flow
- Who wins cleaning tenders in Vienna?
Bring your pipeline to a demo.
We set up pursuits from tenders you follow and ask Flow to summarise the numbers with your team.
Insights starts in Discover
Tenders you find in Discover become pursuits, and pursuits feed the win rate and pipeline in Insights.
Related
Questions about bidding analytics
Which numbers does Insights show?
The team overview shows awarded value this quarter, submissions due in the next 7 days, the current win rate, total and qualified pipeline value, the win rate by quarter, team bid contribution, the bid pipeline from new to won, and bids submitted against won.
How is the win rate calculated?
From your pursuits: bids won against bids submitted. The figures are as accurate as the status and estimated value your team records on each pursuit.
Can Flow answer questions about our performance?
Yes. Ask about your pipeline, deadlines or results in plain words. Flow reads your team's pursuits and answers in the conversation, with charts grounded in that data. It stays inside your team's data.
Can we see how buyers and competitors behave?
Yes. Flow reads contracting authority statistics and company statistics from public procurement data, including frequent CPV codes, CPV market share, regional coverage, main competitors and participation over time.
Can reports be exported or shared?
Flow produces PDF, Word and Excel files, and spreadsheets list their sources and assumptions. A scheduled task can summarise the numbers every week in a new thread. Flow drafts emails but does not send them.
Put your bidding numbers in one place.
Start free, record your pursuits and ask Flow to summarise the pipeline.