Karisha Stanley and Michele Raymond decided to build a stronger process rather than hope for a better result next time. With VisibleThread, they focused on hot buttons, the shred, the compliance matrix, and gap analysis. Here is what changed, and what the team learned along the way.
CMS Contract Management Services ensures affordable properties across the nation are compliant with federal HUD requirements. CMS first used VisibleThread for Doc Compare on HUD compliance reviews, then pulled the thread further into business development. When a tight RFQ landed with the BD lead on PTO, the team fell back on old habits. After that experience, Karisha and Michele took the opportunity to build a stronger process with VisibleThread and focused on hot buttons, the shred, the compliance matrix, and the gap analysis.
The Challenge
Every pursuit is an opportunity to help more residents afford their housing, so a scramble to the finish line was more than an inconvenience. Pressure exposed a process that relied on habit, not structure.
Falling Back Under Pressure
With the BD lead out and a tight deadline, the team leaned on old content, campaigns, and visuals. Quality reviews had little time for follow-up action.
Writing Without Guardrails
Technical writers had to jump in and hope they were interpreting the requirements correctly. There were only 10 days to respond, and it could have been helpful to have more ways to know that all requirements were being covered.
Reading Between the Lines
Sometimes the things that matter most to a customer are not expressed directly. Finding them, and turning them into win themes, takes more than a read-through.
From Chaos to Structure
After returning from PTO, Karisha did an after-action review of the process and took the opportunity to lay out what the next solicitation response would look like.
This is your section, here's a prompt, and here's what a response an evaluator would score highly looks like.
Capabilities in Action
Win Themes From What the RFP Doesn't Say
Using VisibleThread's AI as a research assistant, Karisha surfaced three unstated concerns: processing accuracy, transition risk, and staffing stability. She prioritized them by risk, then handed the resulting win themes to writers.
From Shred to Compliance Matrix
The team shredded the must, shall, and should statements to understand what was being asked. The shred became the compliance matrix, with every section assigned to a writer alongside guidance on a good response.
Gaps and Unsupported Claims, Caught While Writing
Responses were rated by evaluation section and by requirement, from outstanding to weak. Vague claims, like an unproven backup processor protocol, were flagged so writers could add the evidence.
The Impact
A structure the whole team could follow
In the after-action review, VisibleThread and the compliance matrix were repeatedly cited as valuable tools. Writers valued having something to rely on that shaped and prompted their writing.
Writers who would do it again
After the Utah RFQ, the reaction was "I never want to do this again." After the OHFA pursuit, it became "Yes, I would do this again. Sign me up."
Claims backed by evidence
The unsupported claims review gave the team a neutral third party that doesn't care whether they win or lose, backing up the call for proof points.
Learning from every outcome
The Utah RFQ ended in a win. The OHFA pursuit came down to cost, so the team requested the winning proposal and compared it to their own. They tied on system familiarity and learned where to describe their processing work better.
"The customer support was fantastic, and we really appreciate you helping us through that difficult process. You helped us get to a win."
Why VisibleThread
Proposal teams need structure that holds when the pressure is on. VisibleThread gives every stage a guide, and keeps people in charge of the decisions.
Deterministic Engine
Shredding for any term, compliance matrix creation, and Doc Compare. Rules-based and repeatable.
AI With Guardrails
Hot button discovery and gap analysis grounded in the RFP and your own documents. AI supports the decision; people make it.
Workflow in One Place
Assign sections, comment, review, and track progress against the deadline, all in one shared view.
The WPS story is not about adding process. It is about removing the guesswork between stages. Once BD, capture and proposals were working from the same requirements, the same win themes and the same solution, the handoffs stopped being a risk and started being a strength.
If your teams are still rebuilding each other’s work at every stage, a shared system of record is the shortest path to fixing it.