The ITSPmagazine Podcast

Why Customer Contracts Pull Offshore Development Back to US Soil | A Brand Spotlight Conversation with Jason Ford and Studio C60 of Steel Patriot Partners | Hosted by Sean Martin

Episode Summary

Customer contracts, not compliance frameworks, are what push development and data work onshore, says Steel Patriot Partners CEO Jason Ford. He tells Sean Martin the response starts with an assessment of your requirements and what you already have.

Episode Notes

Jason Ford, Co-Founder and CEO at Steel Patriot Partners, joins Sean Martin for a Brand Spotlight conversation in the Find Your Path series about a problem that tends to show up after the signature: a customer contract that limits who can touch the work.

Sean pictures a core US team with offshore developers on one app, then a new customer whose requirements bar offshore staff. Ford says that is the scenario he sees most. Offshore or nearshore development now has to fit a delivery method limited to US persons or US citizens because of data classification or CUI (controlled unclassified information) tags. He says the requirement may be new, pushed down contractually, or signed without being noticed, and that the response may mean bringing work back onto US soil, possibly through a clearance.

The conversation also covers where data sits once hyperscalers are involved. Ford uses his Northern Virginia home as an example: which of the thirty-five AWS data centers holds your data? He also says the first thing that trips people up is signing to get revenue without understanding the level of effort, until a False Claims Act action or an SEC filing arrives. He says fines can exceed revenue.

On the cost of ramping up internally, Ford says teams new to this work typically need two to three months to get comfortable, which could add one to three months to the cycle. His starting point is an assessment: what your requirements are, what you have, and the time, effort and cost to rectify. Sean notes that this is where the business-owner view matters, including the option to decide it is not fiscally feasible right now.

If you sign customer contracts that carry data or staffing terms, this conversation gives you the questions to ask before the next one arrives.

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 and 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
CMMC Resources & Documentation - DoW CIO | https://dodcio.defense.gov/CMMC/Resources-Documentation/
SPRS Cybersecurity Maturity Model Certification (CMMC) | https://www.sprs.csd.disa.mil/cmmc.htm

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, onshore development, offshore development, nearshore development, customer contracts, CUI, controlled unclassified information, CMMC, SPRS, False Claims Act, data sovereignty, compliance assessment, US citizens

Read the full story on ITSPmagazine: https://www.itspmagazine.com/blog?p=contracts-not-frameworks-pull-offshore-work-back-to-us-soil

More from Steel Patriot Partners on ITSPmagazine: https://www.itspmagazine.com/blog?brand=steel-patriot-partners

Read the full story on ITSPmagazine: https://www.itspmagazine.com/blog?p=customer-contracts-not-frameworks-pull-offshore-development-back-to-us-soil

Episode Transcription

Customer Contracts, Not Frameworks, Pull Offshore Development Back to US Soil

[00:00:18] Sean: Thanks everybody for joining us for Brand Story where every organization gets to start somewhere different and head somewhere different. And no no surprise here to anybody, but the journey that sits in between A to Z is rarely a straight line. There's a lot of stuff going on in there. Thankfully for you, Steel Patriot Partners has been on nearly every version of the path from A to Z. And on their website, they can help you find your own path in a location called Find Your Path. Today's path is gonna be looking at ending up with a good partner, either as a partner that runs alongside of you or as a partner that comes on site with you, and more specifically, when that partner to be on grounds, so not offshore. And for some of the work, especially in a lot of government environments staffing is very particular in what's what's required and what you can get away with. Many teams and firms think they can handle it, but, there are a lot of specifics to consider. So thankfully, I have Jason Ford, he's the CEO and co-founder of Steel Patriot Partners, on with me. We're gonna talk about some of these restrictions and requirements and all the nuances that live within it. Sometimes as a business, you feel you have to make decisions, you have to balance priorities, make trade-offs. Sometimes contracts don't allow those trade-offs to happen. But we're gonna get into all that fun stuff.

Jason, thanks for joining me.

[00:01:59] Jason Ford: Thanks for having me, Sean

[00:02:01] Sean: And before we get into the path of finding a partner that's either alongside you or with you in, inside the office tell us a little bit about your own team at Steel Patriot Partners. What's going on?

[00:02:15] Jason Ford: Yeah. So we've been doing, you know, really this type of work for more time than I wish to count, right? It's multiple decades. So a lot of us have federal experience, you know, especially from a compliance outcome. But our focuses have really come down to we're business owners first and trying to look at things through that as a first stop to figure out whether or not this path is right for you or not.

And then the second one of that is engineering. So more complex problems, the better trying to solve outcomes that you're trying to achieve and putting those things, those technical solutions in place. And a lot of times they go across boundaries, not only from a technology perspective, but into other departments.

And then the last piece of that is cybersecurity and compliance, right? So having those three lenses to look at any kind of journey that you're trying to go through gives us the ability to kind of make a holistic path for success to get to your outcome that you're trying to achieve.

[00:03:14] Sean: I'm gonna kick it off with this 'cause there's been the idea and term of sovereignty has gotten a lot of attention, and I think traditionally in the context is around having, an instance of a cloud or an instance of a dataset a local environment, even if the company managing that,

[00:03:41] Jason Ford: Yeah

[00:03:42] Sean: and/or hosting the data happens to be a US company. But there's... I think there's a lot of attention in the reverse sovereignty where US businesses, specifically in critical infrastructure and in government entities, is important there as well. What are you hearing on that front?

[00:04:03] Jason Ford: Yeah, it really is important because if you wanna keep the data where it needs to be, right? And you have to be able to account for it for where it is. And that became a lot harder whenever hyperscalers started showing up, right? And where is my stuff? I mean, just generally, you have a general location maybe where that region is but you don't know exactly, right?

You don't know what building. I mean, I'm in Northern Virginia, so kind of, you know, data center alley, if you will, for everything that it is hyperscaler. Which building of the thirty-five AWS data centers are you in? Who knows, right? I mean, it's somewhere within a probably fifteen, twenty-mile radius.

So having, you know, that data sovereignty piece, as long as it's within the US you know, that, we see that with not only federal compliance outcomes, but also in the financial space some critical infrastructure as well. You know, just having people who are working on these things that are inside and, you know, they Those resources typically have to go through some screening as well, depending upon what data classifications and what contracts are requiring, right?

So it comes down to what is your requirements in order to do that work, and what are you being asked to do, right? And sometimes that creates more questions than answers for an organization

[00:05:27] Sean: So what are some of the triggers? I don't know if that's the right way to put it, but you sign deals to do business with different companies, and you have contracts and clauses and a bunch of requirements and sometimes compliance requirements drive the need for certain things. What, are the, I don't know, what are the signs or triggers within those things that trip companies up and they might be doing something they shouldn't be doing or doing too much, or I don't know. What are your thoughts on that?

[00:06:02] Jason Ford: Yeah. Look, it, that answer is different per outcome as you would expect, right? I mean, if we're looking at you know, critical infrastructure, we're looking at financial services, that's gonna be much more well-defined, I think of what trips people up, and I'll get to those in a second. But like things like in the federal space, let's use like CMMC with SPRS scores, right?

That has been a whole another thing. People just sign and say that they're doing something a lot of times, and they're really not, right? So it becomes this fidelity piece of how truthful are the things you're doing if there's no way to put governance on top of that, right? To prove it. Or if a governance agent that's on top of that isn't doing that, right?

And that's and I think that's the first thing that trips most people up, is that they will just sign to sign to get the revenue and not understand what they're signing, right? They don't understand the level of effort in order to meet those things until, you know, either a False Claims Act comes against you or an SEC filing or something, right?

Some governance did find you, and now they're knocking on your door saying, "Prove it." Right? And most of the time, those are lethal blows to you from a PR perspective or worse, financial perspective, 'cause those fines could be more than your revenue. And we've seen that pretty consistently over the last, you know, I'd say twelve months, especially in the federal space and really over the last couple of years.

In the commercial space, you know, it really does come down to, you know, how rigorous is someone's third-party risk management program to vet you, right? And it does come down to that. You know, if you're working with a Fortune one hundred company, it's gonna be very different than you're working with a startup or a hundred-person company or a two hundred and fifty-person company.

And I think that's where the nuances come in, is, you know, which one of those things is currently gonna apply to you.

[00:08:09] Sean: And I'm just picturing different environments here where, I don't know, we have our core team. They're also in Virginia. We're using to help us stand things up and manage the business, and they're also in the US. But there's this one app that we build, and bring in some folks from India or Eastern Europe or wherever, Western, I don't know, wherever. Turns out we wanna now tackle some new business, and that part of the application falls under some regulation or requirements from our customer that says can't have any offshore folks. That's one thing that I see might happen. But how, what are some other ways that organization may be cruising along and then all of a sudden, oops, the way we currently operate isn't gonna fly anymore?

[00:09:07] Jason Ford: Yeah, that's the one we see the most is what you just described, right? Is it is we do offshore nor-nearshore development. How do I get my application into a boundary that has you know, or into a contract delivery method that has US persons or US citizens only that can touch that due to data classification types, right?

So or CUI tags. So if there's no foreign contact tag on it or, you know, something that is limiting the ability to have a non-US person, non-US citizen administer it, see it unencrypted, then that's something that they could change, right? For an organization, because again, it comes down to, do I have a new requirement that comes onto me?

Or is it something that is contractually being pushed on me, or did I sign something and I didn't realize I signed it? And that's all those things can lead back to how do I go and deliver this now, right? So thinking about the journey in general you have to go back and then assess how much is how much time, effort, and cost is it gonna be for me to rectify this and figure out how to put this in place, right?

And unfortunately, it is again very snowflakey from the perspective of There is no one general guiding rule here, right? You have to kinda look at it in context and say, you know, "I have these things, I have these compensating controls maybe, I have these compensating ways that my business runs.

Maybe I'm doing a different deployment method for this type of solution, or maybe I have an outside firm to do that for me because I can't do it because I don't have the staff, I can't hire them, they're too costly, there's not enough work for them to do," things of that nature, right? So it becomes what makes sense for one person may not make sense for another

[00:11:05] Sean: Yeah. And I want, I wanna talk about that 'cause what makes sense and how you approach and approach the problem, plan to solve it, and actually implement a plan that achieves success. I did it myself just now. I went straight to how do you build a team that meets the requirements?

It's a, it's an operational thing, and I skipped right past the business, and that's where you guys really shine. Well, you shine in many areas, but you shine around business owners first 'cause you understand what's the opportunity, how do you obtain that opportunity with the least amount of risk, the least amount of impact to the business operations as possible, and maybe even make a decision that says it's just not, fiscally feasible right now. Maybe wait six months or a year or until you can move some of these things. And then where I think the other shining point is if you do have to not just staff a team to run, but staff a team to build, you have staff augmentation to help with both of those, right? Getting through the compliance, getting through the implementation, engineering stuff engineering new parts of the program or even parts of the business if necessary. So talk to me about, I don't know, maybe that's a good time to pull a customer case study or something out where you helped an organization kind of realize everything that's involved from business to ops to staffing to engineering to successful delivery with security and compliance in tow.

[00:12:51] Jason Ford: Yeah, and that's obviously our favorite place to be in if we can do all of it because it makes the timelines To do all this stuff much more condensed and a higher chance of success, right? So the more that you have different entities and different parties involved it becomes more complex to manage, right?

And again, that comes back to maturity of the organization. What are they able to sustain, right? And maintain from that perspective, 'cause it could be internal teams doing part of the process or outsourced to someone like us for, you know, other pieces of that process. But at the end of the day, all the pieces need to be done, right?

So however you need to get there you do need to look at it holistically from the perspective of, you know, what is this gonna do to us as an entity, right? Because you may have to make a decision that, you know what, we're not nearshoring or offshoring anymore, right? And we need to bring that back on US soil and with US citizens or US persons in order to complete this work, right?

Because they may have to go through a clearance to get there, right? And those clearances that you have to do require... Again, it comes down to the contract, right? It's not the framework that's driving it is the contracts that would be driving it, right? And those things would be on the terms and conditions that you would have to walk through.

[00:14:18] But from our perspective, we like seeing, you know, everything from assessment to operations as being, you know, in one piece or even if we're over top of the governance piece of all the processes, we can ensure that those pieces are still getting done, and right. And if there's something internal teams aren't able to do, we can pick those up and keep them moving forward if that's something that the organization wants to do, right?

So it comes down to how much time, right? Do you have time to ramp up internal teams in order to do some of this stuff? Because they've never seen it before, potentially, or maybe they've seen some form of it before where it's gonna take two to three months for them to get comfortable with it typically with whatever that thing is and build it and get it to a place where it needs to be.

Not to say that can't be happening in parallel with other things going on, but that could add one to three months to the end of the time cycle of and you might be missing it, your opportunity from, you know, three to four months because of that reason. So it really comes down to, you know, what...

That's always the first questions we ask. Like, what is your requirements? What are you being asked to do, right? And then what do you have, right? It's, again, it's that assessment mindset and try to figure out like, okay, where do you where do we need to get you to? And then ask the questions: what do you have?

What do you wanna use? Or is those resources too highly utilized, and you need us to augment you, right? So it becomes this give and take, and we fit in wherever you need us to fit in model instead of, "Hey, take this whole box. Take it or leave it."

[00:15:54] Sean: Yep. Yep. I'll make one final point as I wrap here 'cause I know that, huge, ginormous organizations require many partners. And,

[00:16:09] Jason Ford: Mm-hmm.

[00:16:09] Sean: and you can fit in a lot of areas helping to define, helping to govern, helping to implement, engineer, manage, all that good stuff. If there's something they need that you and your team can't directly I know you have a large bench of, know a guy"

[00:16:28] Jason Ford: Exactly

[00:16:29] Sean: who can actually help fill the gap while also maintaining the onshore onshore requirements as well. A good resource to have, you and your team, Jason, and for direct and also great partnerships. As I've said many times, points, ending points, different for every organization. Sometimes they need to change. Almost always the internals look different. But thankfully, you and your team, Jason, have experienced seeing a lot of those journeys and can pull different pieces and parts into new programs to help ensure success along the way. Good stuff

[00:17:15] Jason Ford: Thanks for letting me talk about what we love doing. I mean, that's really what it comes down to is if you love what you do, then, you know, it becomes a lot easier to get through the hard things

[00:17:24] Sean: Exactly. And getting through the hard things is all about defining your own path, and there's a place on steelpatriotpartners.com/findyourpath where you can answer a few questions, and the result of that will give you a chance to connect with the Steel Patriot Partners team to take you on that journey that's gonna help you get from A to Z specific for your own business.

So everybody for staying tuned for this, and there's a lot more coming, so hang out and follow along.