A customer clause says you have to be compliant, but it may only ask for progress at award. Jason Ford of Steel Patriot Partners explains how an assessment and roadmap show what is required before money or team time is committed.
Jason Ford, Co-Founder & CEO at Steel Patriot Partners, talks with Sean Martin about what to do when a customer sends a contract clause saying you have to be compliant to win the deal. Sean's opening point is that it is worth checking whether that is true before anyone spends a dollar or a month meeting the requirement.
The conversation covers where these requests come from and who feels them. Ford says they usually surface from sales and business development, or from operations at a re-compete or an option year. He says the decisions are often made in vacuums by sales, a CFO or a CEO, without weighing the impact on HR, finance, operations and especially customers. Users who are not expecting a new requirement, he says, will not like the company for it.
Ford then describes why each organization is its own case. Clients arrive with a predetermined solution that is usually not right, and it comes with cost, time and wasted energy. What worked for fifty others may not fit, and Ford says an AI chatbot cannot supply that judgment. Sean offers a dartboard picture and asks how often an organization arrives pointing at the dot in the middle. Ford answers "Never." They bring the whole dartboard or the wall it hangs on, and he names perfectionism as the number one killer.
The conversation closes on timing. Ford says flow-down requirements such as a DFARS clause, FedRAMP or GovRAMP are usually not required at contract award, only progress toward them, though sometimes they are. A letter saying an outside firm has been engaged can sometimes be enough to get in the door. His approach is to assess where you are against a standard, then build a roadmap, with illustrative milestones such as fifty percent in six months. Sean adds that demonstrating action is much more powerful than saying you take security seriously on a website.
This is a Brand Spotlight. A Brand Spotlight is a ~15 minute conversation designed to explore the guest, their company, and what makes their approach unique. Learn more: https://www.studioc60.com/creation#spotlight
GUEST
Jason Ford, Co-Founder & CEO at Steel Patriot Partners
On LinkedIn: https://www.linkedin.com/in/jason-ford-5ab206/
RESOURCES
Find Your Path | https://www.steelpatriotpartners.com/find-your-path
GovRAMP | https://govramp.org/
FedRAMP Marketplace - FedRAMP Consolidated Rules for 2026 | https://www.fedramp.gov/2026/marketplace/
Learn more about Steel Patriot Partners: https://www.steelpatriotpartners.com
▶︎ Want your brand on ITSPmagazine? Explore all of the options here: https://www.itspmagazine.com/advertise
KEYWORDS
Jason Ford, Steel Patriot Partners, Sean Martin, brand story, brand marketing, marketing podcast, brand spotlight, Find Your Path, compliance, contract compliance clause, FedRAMP, GovRAMP, DFARS, SOC 2, compliance assessment, compliance roadmap, flow-down requirements, cybersecurity compliance
Read the full story on ITSPmagazine: https://www.itspmagazine.com/blog?p=compliance-clauses-often-ask-for-progress-at-award-not-completion
More from Steel Patriot Partners on ITSPmagazine: https://www.itspmagazine.com/blog?brand=steel-patriot-partners
Compliance Clauses Often Ask for Progress at Award, Not Completion
[00:00:18] Sean: Hello, everybody. Thanks for joining us for Brand Story. Every organization starts off a program somewhere and is oftentimes headed somewhere different, there's clearly no straight line along that journey from A to Z. Though, Steel Patriot Partners has been on nearly every version of that journey, and on their website, they can actually help you find your own path in a location on the site called Find Your Path. Today's path starts with a message the inbox. Customer sends you a contract clause and says, "In order to get this deal, you have to be compliant." And before you spend a dollar or a month or wasting... Not wasting, but putting team's time on meeting that requirement, worth checking to see if it's true or not.
And that particular path is called checking the path you're on. Today, we're gonna look at how often those requests are right, where the ask and the actual requirements drift apart where the honest answer sits so that you can actually meet what you're required to actually win the deal. And I'm thrilled to have Jason Ford on. He's a co-founder of Steel Patriot Partners, and we're gonna talk through this particular journey. Jason, good to see you.
[00:01:36] Jason Ford: Good to see you too
[00:01:38] Sean: And I'm sure you've experienced a lot of these journeys and a lot of these paths with folks that said, "We need to do this, and we need to do it fast because we have a deal on the table." Before we get into what that looks like and sounds like across the different things you've seen maybe a quick overview of Steel Patriot Partners and what you and the team are up to these days
[00:02:01] Jason Ford: Yeah, sure. So like Sean said, Jason Ford, CEO, co-founder of Steel Patriot Partners. We kinda founded this with kinda three lenses. You know, the business owner is first with the return on investment and trying to figure out is is something that you're being asked to do or something you're trying to do is the right approach.
Second one is engineering. You know, the more complex, the better for us in a lot of ways. Trying to solve technical challenges to an outcome that you're trying to deal with. And sometimes it is exactly what Sean just mentioned, is that someone sent you something, and you're like, "How do I deal with that?"
And then the last piece of that is cybersecurity and compliance, right? So a lot of times that is the outcome that someone's looking for. And it really becomes an advise, deploy, and operate type model, whereas, you know, we can really inject anywhere you need us to inject, and we're really agnostic on tools, we're agnostic on processes and even infrastructure where you are in your maturity curves.
So kinda meet you where you are, right, is the idea. And a lot of times people don't know where they are, right? Or they think that they know where they are, and they really aren't, right? That's the other thing that we see.
[00:03:13] Sean: Yeah. Meet you where you are and yeah, I continuously hear that guys are great partners along the path from A to Z, and then there's a new round of A to Z as they continue to grow the business and expand into new markets and new areas of operations as well. Let's be honest. People are smart. They've done things before. They have their own experiences. Have strong teams around them. Doesn't mean they know everything all the time. And then the realities are that technologies and can be difficult. Federal, legal, whatever compliance requirements change, and staying on top of that is different.
The threats change, Cloud environments change. Being smart in depth in everything is difficult. So when something like, "We need you to be compliant with or have a SOC 2 or a FedRAMP auth," or whatever it is that, coming along to, in order to close a deal, they know their business. Doesn't mean they know what it takes to actually achieve the things they're being asked to achieve. I think as I talk to a lot of the team, the scope is a big issue of understanding as well. So let's start there with do you see the understandings align well or kind of run off the tracks when people come to you and say, is what we need. This is where we think we need to go. Help us"?
[00:04:51] Jason Ford: Yeah. It really comes to the first thing that happens is that they have a predetermined solution already for that problem, right? And most of the time that's a good thing, right? 'Cause that means you put some thought and process into it. But the issue is that most of the time that predetermined solution isn't right.
And it is coupled with cost, time, and wasted energy, right? And not saying that, you know, finding the wrong solution or maybe not the full right solution is a bad thing to do. You do have to go through that process to sometimes figure out the maturity and where you need to go. But trying to take what that requirement is and then figuring out, you know, how does that best apply to you, right?
'Cause you are a snowflake, right? As an organization. And what may work for someone else may not work for you, right? And that's really the issue is that, you know, you as the organization have legacy experiences, how your customers interact with you, how you do you. And not always does someone coming with a, "Here's a solution that worked for fifty other people," is that gonna work for you or not, right?
And in particular cases with whether it's a compliance outcome or it's an AI initiative or doing a cloud migration or how someone's going to do some kind of security program, put that in place. All those things are different for each person, even though the, maybe the program should look the same when it comes out, but how you apply it and how you put it in for you is unique, right?
And that's the part that requires a little bit of thought upfront. That's something that an AI chatbot can't tell you, right? It's something that, you know, it doesn't know people. It can't think in that way, doesn't think. And it just gives you an answer that you wanna hear, right?
Instead of something that may work, right? Or will work from that perspective.
[00:06:54] Sean: Yeah. The experience of a human we haven't matched that yet with AI.
[00:07:00] Jason Ford: Yeah
[00:07:02] Sean: Yeah, even just simple queries of how does this particular piece of the tech stack work could be inaccurate and send you of, send you off spinning implementing and deploying and configuring and things in a wrong way. So a lot of what you do is connected to the cloud, obviously many times driven by some compliance requirements. And those are both technical, in my opinion, but kinda miss the point of the business. So the initial thrust might be there's a business opportunity, it... My experience, that's where the business kind of gets left behind, right?
[00:07:49] Jason Ford: Yes,
[00:07:49] Sean: Need, we need to get this deal, now what? And it's the "now what" that gets the attention. What do you hear and how do those conversations sound like as you're kinda walking through that nuance?
[00:08:02] Jason Ford: Yeah. And usually these things do come from the either the sales BD arm of the organization typically is where they get surfaced up. The other part comes from operations. You know, they already have a system in place, or they're already operating in some way and, you know, you're up for re-compete, right?
Or your contract is coming up for an option year, and now there's another, you know, requirement that's thrown in front of you. And, you know, that's really where a lot of this comes into play is that how are we gonna meet this so we don't churn the revenue or we lose the opportunity to get the ROI...
You know, and that's where the ROI comes in, right? So is the opportunity large enough? Is the opportunity is the dollars making sense to chase after for this amount of effort that you're gonna have to do, right? And a lot of times these decisions are made in vacuums, right? So the problem is that whenever sales or a CFO or even a CEO makes a decision, they may not take into consideration all the impacts it's gonna have on HR or finance or operations in general, or even just, you know, how your user base is gonna take it, right?
'Cause some of these requirements are heavily tied to having, you know, certain things in place that your user base, if they're not expecting it, they're not gonna like you for it. And then you're gonna have upheaval from your customers, right? So having that kind of viewpoint into these things has to be...
We always look at that as that's a must-have, but most people don't think of it that way, right? Because those impacts are not just your organization, but it's also to your customers you're serving, right? And those can be even more impactful to you than even your employees and how they're doing stuff.
[00:09:57] Sean: Yeah. So that's the kind of the back up and out, the impact there. And I want to get your thoughts on, 'cause you said a lot of people have an idea of what the solution looks like, and I kind of touched on the scope earlier. There's... Can either view it as a slider, right? There's the extremes on both ends, and hopefully you get somewhere in the middle where it's the right mix of things. But in reality, it's probably more like a dartboard, right?
[00:10:28] Jason Ford: It is, yeah
[00:10:30] Sean: Rings and you can end or maybe a magic quadrant if you want to go into an analyst view. So where do you sit? Do you want to be in the upper right, in the middle?
[00:10:38] Jason Ford: Yeah
[00:10:38] Sean: Based on risk, based on what you're trying to achieve and all these different things. A lot goes into making that decision and understanding how the business is going to tackle that problem. How often do organizations come to you with the dot in the middle or the dot in the place that they want to target that
[00:10:59] Jason Ford: Never.
[00:11:01] Sean: 'Cause-
[00:11:02] Jason Ford: It's, usually it is the whole dartboard or it's the wall that the dartboard is hung on, right? It's it's usually the place that they're at.
[00:11:08] Sean: Yeah
[00:11:09] Jason Ford: All they know is that they have this requirement, right? And they may have done some initial research on it. They may have tried to think about how they're best gonna, again, come with a predetermined solution that they think is gonna solve it.
Sometimes, you know, it is a predetermined solution. They've tried it and they failed, right? And, or it was half implemented and only got partially the way there. There is the, you know, the concept of, you know, gold plating obviously that, you know, going above and beyond what you need to do. That's not always the right choice for a, for an entity to go down, and that's usually perfectionism is the number one killer.
For any business idea or anything that you're getting put in front of you not saying do it just to the mark, but you should be looking... You don't need to gold plate is the point. So being realistic. And that's why it's never just, "This is where we wanna be," right? Is where they come to, you know, in the conversation initially.
It's usually like, "Well, we have a general direction that we're trying to go, and we think that this is what it is," or, "We've tried this and it didn't work. That's why we're talking to you." And it really doesn't matter what that outcome is. That's just transformation in general.
It could be, you know, again, a compliance outcome. It could be, you know, I have, you know, look, AI has been dominating most things that everyone's talking about in this space in general. You know, how do you govern that? How do you implement that? How do you oversee it, right? So it could be a technology force upon you, it could be a requirement force, it could be, you know, again, it's the stick hitting you instead of the carrot, right?
And that's kind of what we see.
[00:12:51] Sean: Yeah. And ultimately it's a journey, and I think what I'm picturing in my head, I like to visualize things, you can tell. There's the requirement from the prime, the customer that says, "We need you to do this." Then there's probably some standard or framework or something that's gonna help you achieve that, but that that's over here and has its own things. Which path do you take? And are there overlaps in that? And understanding that and making sense of it, and then acting on it are different things. And how do you help folks kind of say, "Are we in the right starting point?" And help them understand a path to achieve whatever the right endpoint is, 'cause it may not... I've heard some stories of the customer wants you to achieve this, but the reality is if you can get close to that's good enough now with a view that you are actually taking another six months or twelve months to get closer to where they really want you to be. So how do you help organizations navigate the realities of what's possible and what's acceptable? Not gold plating, but just realizing what's really needed.
[00:14:17] Jason Ford: Yeah, it really does come down to the need, the scope, and the desire, right? So and the revenue that is going to drive that, right? So those three or four things you kind of have to look at holistically. And the only way you can do that is kind of go through an assessment path and figure out, like, what do we have?
Where are we? And then measure that against an, a standard that you've either created because of the requirements you're given, or they may be given to you. And that requirement then becomes the standard you're going to write that assessment against. And that doesn't matter if it's, again, a compliance outcome, a new technology a security tool rationalization, whatever that is.
You know, are you meeting to that standard, if you will? Again, that could be something you create yourself. But that is the important piece. Without knowing that and then creating from that assessment a roadmap out of that to say, "Look, this is how you go from where you are to where you want to be for this standard."
And to your point, like, it could be I'm ninety percent of the way there, or I'm fifty percent of the way there in six months. I'm eighty percent of the way there in twelve months, and then I'm, you know, close to being there in, like, eighteen, right? 'Cause a lot of times, if a compliance outcome is what's driving this, if you win a contract, right, and there's a flow down clause in there that you have to be something a DFARS clause, or if it's a, you know, you have to be FedRAMP authorized or GovRAMP or whatever that is from a compliance perspective those things are not usually at contract award.
Sometimes they are, but they don't always have to be at contract award, right? They could be something that is you have to show progress towards. So maybe it's I'm gonna become, you know, in the FedRAMP space, Class A, and then you want to be Class C. And then later on, you know, maybe you're gonna spin off into state and local, and you have to do GovRAMP, right?
Something along those lines. But again, most of the time, that isn't something out of the gate you have to have, right? You just have to show that you're progressing towards it. And sometimes a letter saying, "I've engaged an outside firm to start down this path," is enough to get you in the door, right? From a, from an ROI perspective, as long as you can see it, right?
You can prove that you have that whether that's a contract or a letter or whatever that is.
[00:16:48] Sean: Yeah. I think demonstrating is much more powerful than, just saying we take security seriously as a thing on the website. I'm making fun of that. But yeah, I think the mindset, the culture showing that you're taking action and working with a trusted partner to help you achieve that end goal, all help to show that you mean business when doing business securely. And as we started off with, every starting point is different, every destination is different. All the stuff in the middle, is where you and your team have experiencing... Have experienced something, many things that are gonna map to a current project, and you'll pull from your collection of experiences and programs you've been involved with to kind of find the right mix from A to Z for each client that you tackle. So good, Jason. And keep up the good work. A whole or a page on your website, steelpatriot.com. Steel steelpatriotpartners.com/findyourpath, where put in a few answers to a couple questions, and help you kinda connect with the Steel Patriot Partners team to find your own path and to have a nice starting point to have a good conversation with you and your team help you along the journey. So good stuff. So thanks, Jason. Thanks everybody for watching, and tuned. There's many more paths to cover as everybody looks to tackle their own journey
[00:18:36] Jason Ford: Thanks for having me