The company
C'Bay Technologies
C'Bay Technologies is a service-disabled veteran-owned IT firm founded in 2003. It grew from computer repair into managed cloud and cybersecurity services for government buyers.
Before SamSearch
Four systems, and no two of them agreed
C'Bay found work in several separate subscription tools, then retyped whatever looked real into a general-purpose CRM so tasks could be tracked against it. Awarded contracts were held somewhere else again, and the internal documents, the past performance write-ups and the price backup, lived in Microsoft SharePoint. Each system was accurate on its own terms. None of them reconciled with the others, so answering where a pursuit actually stood meant opening four of them and trusting whichever had been touched most recently.
How they use SamSearch
The capture workflow
C'Bay runs the deepest pipeline on SamSearch: 376 pursuits on one Journey Hub board, fed by 629 recommendation runs that screened 19,365 solicitations down to 6,515. Federal and SLED sit on the same board, 131 of those pursuits state and local, pulled from 50,000+ state, county and municipal sources rather than a list of bookmarks. A journey opens with the notice, its attachments and the dates already in it, which removes the manual import step entirely. Tasks, comments, contract records and the documents that used to live in SharePoint sit on the pursuit they belong to, written into a shared record as the team works rather than filed afterwards.
By the numbers
C'Bay Technologies in SamSearch
Solicitations screened
19,365
Read by the recommendation engine
Worth a human look
6,515
Surfaced as relevant
Cut before review
66%
Removed as poor fit
Hours returned (est.)
857
Analyst time, platform estimate
From the market to the shortlist
How many solicitations the engine read for C'Bay Technologies, how many it removed, and how many made it to capture review.
19,365
Screened
100%
12,850
Cut
66% removed
6,515
Shortlisted
34%
Screening volume by week
Weekly solicitations screened versus the smaller set returned as relevant. From live recommendation activity.
Hours returned uses a platform estimate of 4 minutes per solicitation filtered out. Not a stopwatch measurement for this account.
Capabilities in play
What they run in the platform
Manage
376 pursuits on one Journey Hub board, federal and SLED together, each carrying its own tasks, documents, contacts and contract record. The deepest customer pipeline on the platform.
Capture
629 recommendation runs screening 19,365 solicitations, including SLED work from 50,000+ state, county, and municipal sources, not just SAM.gov.
Old way vs. SamSearch
What changed in the pursuit process
| Before | With SamSearch | |
|---|---|---|
| Where a pursuit lives | Opportunities in several search tools, tasks in a general-purpose CRM, contracts in another system, internal documents in SharePoint. | One journey holding the solicitation, the tasks, the documents, the contacts and the decisions. |
| Getting work into the pipeline | Found in one tool, then retyped by hand into another. | A journey opens already populated, because SamSearch found and read the opportunity in the first place. |
| Who is working which pursuit | Ask the person, or check every system and hope one of them is current. | An owner and assignees on every journey, filterable by either, with an activity log of what changed and who changed it. |
| Pipeline reporting | A status round-up assembled by hand ahead of the meeting. | Dashboards by stage, customer and business line, read off the same board the team is working. |
| SLED coverage | State, county, and municipal sources scattered across thousands of portals. | 131 SLED opportunities actively pursued from 50,000+ sources in one feed. |
Platform note
Reporting nobody has to be asked for
SamSearch builds its dashboards out of the journeys a team is already working, so pipeline by stage, by competition type, by customer and by business line is a read of the live board rather than a round-up somebody assembles the day before. Every journey carries an owner, its assignees and an activity log of what changed and who changed it, which is how leadership sees who is on which pursuit without having to ask. Values are spread across the period of performance instead of landing whole in the award year.
FAQ
What does C'Bay Technologies use SamSearch for?
C'Bay runs the deepest pipeline on SamSearch: 376 pursuits on one Journey Hub board, fed by 629 recommendation runs that screened 19,365 solicitations down to 6,515. Federal and SLED sit on the same board, 131 of those pursuits state and local, pulled from 50,000+ state, county and municipal sources rather than a list of bookmarks. A journey opens with the notice, its attachments and the dates already in it, which removes the manual import step entirely. Tasks, comments, contract records and the documents that used to live in SharePoint sit on the pursuit they belong to, written into a shared record as the team works rather than filed afterwards.
What results are documented here?
376 pursuits tracked, the highest pipeline volume on the platform; 131 state and local (SLED) opportunities actively pursued; 4 → 1 systems consolidated onto a single Journey Hub board.
How were the results verified?
Platform activity comes from SamSearch production data. No award dollars are claimed where a matching public record is unavailable.