This edition of Product Pulse covers two of those small things we shipped recently. The kind of RFP automation improvements that don’t make headlines but define whether a platform actually fits your workflow. Neither is a headline feature. Both are the kind of detail that only gets built when a platform is treating itself as your system of record rather than a place you visit to run one task.
Search, built into Tracked Opportunities
When you’re pulling in opportunities from SAM.gov, UK Find a Tender, and eBuy as part of an automated RFP tracking workflow, your tracked list fills up fast. That’s a good problem. The bad part shows up mid-pursuit, when you know the opportunity is in there somewhere and you’re scrolling to find it again.
RFP automation is the reduction of manual, repetitive steps in the bid process, tracking opportunities, populating data fields, and managing pipeline. All so proposal teams can focus on win strategy instead of administration.
We shipped an improved search bar inside Tracked Opportunities. Type the name, find the opp. No scrolling, no hunting, no losing your place in a live pipeline. Searching across 1,200-plus tracked opportunities now takes seconds.
It’s a small change to describe and an easy one to feel. The point isn’t the search box itself. It’s that the moment you’re in, scanning a live pipeline for the thing you need right now, should not cost you a minute of friction every time.
eBuy Vehicle Name, populated automatically
The second release is even quieter. The eBuy Vehicle Name now populates automatically in VisibleThread. One less field to chase down by hand.
Before, you’d see the opportunity come in and the Contract Vehicle field would sit there empty, waiting for someone to fill it in manually. Now it arrives filled. OASIS+ Unrestricted, populated, done. One more thing your system of record just handles.
On its own, that’s a single field. But this is the part worth sitting with: every field you don’t have to maintain by hand is a field that stays accurate without anyone remembering to keep it accurate. The value of a system of record isn’t that it stores your data. It’s that it removes the burden of keeping the data right.
Why these two, in the same breath
Together, these updates reflect what effective RFP automation looks like in practice: fewer fields maintained by hand, faster access to live pipeline data, and a system that stays accurate without depending on someone remembering to keep it that way.
It would be easy to file these under “minor improvements” and move on. We’d rather be honest about why they matter together.
VisibleThread founder Fergal McGovern has a view he comes back to often: most software tells you the why. We’re going to save you time, we’re going to lift your Pwin. Nobody really believes that anymore. What earns trust is the how, shown plainly, relevant to the job in front of you. Search that works the way you’d expect. A field that fills itself in. The how, not the promise.
That’s also why we ship these as a drumbeat rather than saving them up for a launch. A platform that understands your workflow isn’t proven by one big feature. It’s proven by the steady accumulation of details that stop getting in your way. The search bar this month, the auto-filled field this month, and more sources and refinements next month.
Small things. But this is what a platform that actually understands your workflow looks like. The details add up and for GovCon teams, that accumulation of small, accurate automations is what separates an RFP automation platform from a tool you tolerate.
Product Pulse is our running log of what we’ve shipped and what’s coming next. More updates and new sources are on the way.
