A Daily Story About Client Time - CLEVER 35 | Client 0

Yesterday we held a weekly internal review of a client’s pipeline. During the review, three opportunities approaching release dates in the next several months were discussed and moved to high priority research status. One was a customer our client knew, but there had been very little information released by the agency. They could do the entire scope, and wanted to prime, but there was no apparent acquisition strategy or obvious incumbent information. So, several tasks were assigned in CLEVER to find out what is happening.

Immediately, the client’s CLEVER Support Team went to work. They had been monitoring the opportunity, but now, a full court press was in motion. They reached out to the Contracting Officer (again) with two questions (incumbent information and potential acquisition strategy) and got back just a vanilla response – we are still in the planning stages. This time the team pressed. “Thank you, but is there an incumbent and do you have any idea what the acquisition strategy might be?” After 5 back-and-forth emails the team got answers – the incumbent was XXXX and it was likely to become an 8(a) set-aside. Now it was clear why CLEVER could not find the incumbent, the work had been performed by a large business under a TO under an IDIQ. What was also now likely – our client would not be able to prime since they are not 8(a).

Since the RFI had been issued under GSA MAS, it was now possible, with the 8(a) strategy, it could also go to STARS, and if it was released on MAS it might go to the HAC SINS. Suddenly our client needed a whole new strategy, so an internal CLEVER Team meeting was scheduled for tomorrow.

This morning the CLEVER Team Lead handling the client was joined by a CleverBD Strategist. After some discussion it was clear the best approach would be to find an 8(a) with MAS, HACS, and STARS III that could do a portion of the work but not all of it. Since our client had customer intimacy, it was not necessary that the 8(a) did, only that they would have a strong contract history in part of the SOW. Our client, who could do the whole SOW, would then be able to cover the rest of the work, although a particular part of the work required a certification our client had, so it would be desirable if identified 8(a) did not cover that part. It would strengthen the story for why teaming would make sense.

In real time, using CLEVER and several other government databases, the Team Lead and Strategist identified two potential partners. They then obtained contacts (name/phone/email) at both companies for our client to reach out to. All the appropriate information was captured by CLEVER (the strategy, rationale, CO contact records, potential partner data) and an automated notification was sent to our client summarizing their support team’s actions. The current research tasks were completed, and new tasks opened to reach out to the potential teaming partners. Through CLEVER the client could message a response or schedule a follow-up strategy session with their CLEVER team.

This story will repeat itself with various client needs multiple times per day. This is why we call CLEVER a System-Wrapped-In-A-Service (SWInAS) - your pipeline is never alone.

CLEVER Team time investment – Team Lead and BD Strategist for 35 minutes

Client’s staff/time investment – 0