Skip to content
Startups Series: Neill Sciarrone, BAE systems episode artwork

Oct 20, 2016 28 min

Startups Series: Neill Sciarrone, BAE systems

from CNAS Podcasts Hosted by Center for a New American Security

Neill Sciarrone, Senior Director of Strategy and Planning at BAE Systems, discusses how the defense industry can adapt to better collaborate with, and generate value from, startups.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Startups Series: Neill Sciarrone, BAE systems

0:00 28:26
of matches

Transcript Auto-generated, may contain errors

Welcome to the Center for New American Security's National Security Startups podcast series, hosted by Senior Fellow and Director of the Technology and National Security Program, Ben Fitzgerald. Welcome, everyone, to another installment of the CNAS National Security Startups podcast. We are joined today by Neil Sharoni. Welcome, Neil.

Hello. Neil is the Senior Director for Strategy and Planning at BAE Systems. Prior to her time at BAE, she was Special Assistant to the President for Homeland Security and a Senior Director for Cyber and Information Sharing at the White House. And before that, she had the significant opportunity of helping stand up the department of Homeland Security, working on the critical infrastructure, cyber, and intelligence components of that new organization.

So, Neil, with all of that fantastic background and varied experiences, it's great to have you here. I'd like to start just by looking at your current work at BAE. Right. So, you are the Senior Director for Strategy and Planning.

Can you explain to us what that is, what you do, and how you do it? Sure. Basically, what it means is that I develop and evaluate our business strategy. So, focus on the ways in which we grow as a business, both organically, meaning internal investment, and what we refer to as inorganic.

Most people refer to that as just margins and acquisitions. So, how do I make sure that we continue to grow as a business and meet our customers' needs? And I spend a lot of my time actually focused on emerging technology. So, as part of that work, I assume that you're constantly trying to identify those different ways in which BAE can grow.

How do you go about making decisions on which of those methods, whether you want to pursue organic or inorganic growth? Right. So, there's no easy answer to that. If there was, I likely wouldn't have a job.

Right, right. It's always important to find hard problems and have those be part of one's employment. Right. But really, it's around looking at our capabilities and looking at the broader market around us, right, and kind of understanding what is it that we do really well, what is it that our customers need, what are the new problems that we face, that our customers face, and how do we make sure that we're approaching these problems in a way that returns shareholder value?

Yes. Because, at the end of the day, that's a key component of any business. Absolutely. And so, when we're looking at capabilities, one of the first questions I always ask is, you know, how core is this to who we are and what we've done?

So, for example, electronic warfare, that's our heritage. And so, in that realm, it's usually an investment that's internal. It's something where we know we can sustain our advantage, and it's core to who we are and what we do. There are other activities where, say, we're going after a specific program, and we need a specific capability to fit that.

And that's where we look at different ways of achieving that capability. You know, people have a tendency to focus either on are you investing internally or are you going to buy something? Right. And to me, that means you've missed a whole part of the spectrum of how we approach this.

You know, we can do this any number of ways, from a simple purchase order, where we go to a small supplier and acquire that technology, a subcontractor relationship where we go together and on a project. Sometimes that's a little bit more of a subcontractor relationship. Sometimes it's more of a teammate relationship. You're invested in that company as well, and you have shared goals.

And then the last piece of the spectrum is really M&A. People tend to get there pretty quickly when they think about how you do investments, and I like to stop people and say there's multiple stops along that path before you get to an actual acquisition. Well, the M&A stuff sounds exciting, right? What do you do, M&A?

The reality and the ability that can create real value for many organizations often lies in between. Right. So, as you're making those decisions, what is it that you're looking for in a potential partner, whether that's as a subcontractor, a teammate, for a joint venture, or, in some cases, for acquisition? So, there's a lot of things we look for.

First, the technical capabilities, right? So, in many cases, you are looking for capabilities that are not easy for you to develop on your own or that you can't develop them quickly enough to meet a need that you have, right? So, number one, technical capabilities. Number two, we tend to look at contractual performance, right?

So, how to perform as a business. It seems pretty straightforward, and yet when you talk to folks, that's one of the last things they think of when you say, I want to know how they're performing. Quality, right? So, if you're going to partner with someone, you want to know that they have practices in place to ensure the quality of what they're providing you.

I'd be remiss if I didn't mention financial returns of shareholder value. A little bit around sharing of the company's values, right? So, is this company that we want to partner with similar to ours? Do they view the things that are important to them?

Are they the same things that are important to us? Business ethics being an example of that. Look at their existing relationships. So, who are their key customers?

What are those relationships with the customer? All those things factor in when you're trying to decide who to partner with, and they're all things I think you would normally expect. I haven't listed anything that you go, wow, that's surprising. Right, right.

Although, it's interesting to get a sense of the things that are often overlooked as well. So, in talking through this, it's helpful to use examples as much as possible. Do you have an example that you could share with us of an organization you have partnered with or required to talk through how that process works? I will, but first let me kind of show you, we have a tendency when you're looking at acquisitions to approach them for multiple purposes.

So, it tends to be that the smaller companies are where we get a lot of that niche technology, and we tend to look to the smaller companies for that type of needs. When we look at larger companies, it's not only for their technical capabilities, but also how they complement us or broaden our market. I will say this, and this might be shocking too, we tend not to acquire simply for the sake of growing revenue. Right.

So, if we do a large acquisition, it's not just to add on. It's truly our belief that together, we would function as a better company than separate, and it's that synergy that we're trying to achieve. So, when you think about it, think of, you know, sometimes we acquire for that niche technology, sometimes we acquire to be able to grow, whether in a specific customer area or a specific capability area. Yeah, and it's an important distinction, especially when for many folks outside of defense industry, whether they're in government or other realms, the general starting assumption is that, like, revenue and profit are the only things that are important.

And obviously, they are important, but if that's all one is thinking about, you're missing strategic opportunities. You're missing a lot of strategic opportunities. And so, with that example, I'm going to use one that was around finding an niche capability for us. And I think the best example is actually Signals Innovation Group, or SIG, as we call it.

It was a 35-person company, headquartered in Durham, North Carolina, so right there in the middle of Research Triangle area. They had been working with us for about four years on BlackWolf, which was activity-based intelligence. And so, they had this really cool capability that allowed them to track objects in video and to analyze that ISR and multi-net source data. And they had products that would allow you to look at that and fuse the data from disparate sources over time.

So, very niche technology, very niche algorithms, but key to an area in which we spend a lot of time and effort. And they were currently a sub to us working on that work. So, we knew them. We knew their capability.

We knew their employees. We knew their culture. And we knew it was a capability that we desired. And we knew it was key to expanding and moving forward with our customer.

And so, when we looked at it, we said, yeah, we actually want to own this. We want to make sure this is part of our core technology. And so, we decided to move forward with an acquisition. Knowing that it was a cultural fit, I think, helped them.

And one of the big fears you hear from small companies is we're a 35% company. We're going to get acquired by a defense firm and they're going to gobble us up. Right, right. And so, we made a real commitment as we were going through that acquisition to make sure that that didn't occur.

So, it's interesting to me as well as you laid out that you worked with them for four years. So, knowing that that wasn't just when you'd done a couple of visits. A long-term partnership. And that also hints at that spectrum that you laid out earlier that you can go up those steps one at a time, potentially.

Correct. It's very interesting. It kind of goes without saying that acquisitions are tricky for everyone involved. Just be interested in sort of how you guys made that one work.

Clearly, part of this was the pre-work in terms of working together, cultural fit, that kind of thing. But once you decided to do the acquisition, how did you step through from that moment forward? I think acquisitions are challenging no matter what industry you're in, right? I think the defense industry adds some unique aspects to it.

Just the amount of regulation and oversight that we have at times can make this a little bit trickier. For us, the integration is the key piece. And I will tell you that for me, personally, it was an area of concern. I came to BAE through an acquisition.

So I worked for a small tech startup that was acquired by BAE. And so I had lived that. I know how it can be handled. And so making sure that we do it right for us is one of the most important processes of this.

You know, this may sound weird, but the most important piece of it is really the employees. When you're buying a company, you're buying the employees. They are the intellectual property, they are the culture, and they're the reason that you find value in the company. And I know that seems pretty straightforward, but sometimes in the day-to-day kind of compliance piece of doing that integration, you lose sight of that.

Yeah, and also you aren't doing it purely for altruistic reasons. So make sure that you get them into the process early on and make sure they understand what's the rationale behind this acquisition? Why did you value them so much? Where do you see the business moving?

Painting the future for them, getting them engaged early on, and making sure that it is a true merger, right? And that you navigate that personnel piece pretty carefully. So back to SIG, how we make sure this happens. We actually assigned a BAE person whose sole purpose was to help protect SIG in that position.

So they went down, spent time with them as a company. It was someone who knew BAE's processes, procedures, et cetera. And it was their job to sort of be the gatekeeper to help determine what things needed to happen right away and what things could wait a little while. And his job was to keep our huge company from overwhelming the 35 employees that were there and their leadership.

So the leadership continued to run a business and deliver while we dealt with the back-end side of making sure that they came and incorporated into our corporate processes. So they don't have to worry about the new TPS report format? Training. I mean, you know, it's one of those things where you have to do all those things, but you don't have to do them right away.

And so making sure that you think through logically how to approach it and you do it in a way which causes the least amount of disruption. Fantastic. So you've mentioned shareholder value a couple of times in this conversation already. I assume that SIG had shareholders.

They may have been a venture-backed startup, I think. Valuations or methods of valuation between defense industry and sort of West Coast acquirers. So just be interested in how that played out in this instance. So in this instance, you know, they had in-catel packing.

And so not surprisingly, having an organization who was committed to providing this type of capability to the warfighter and intelligence community meant that they saw BAE as a good partner for the business. Obviously, as I mentioned, we had spent time with them for years. And so they knew a lot about us, just like we knew a lot about them. You know, but in general, I think shareholders are looking for a return on their investment.

And that you only get in a couple of ways. Right. Right. Either through an IPO or through a strategic sale.

Yes. We acquired our business and, you know, we offered them something that considered fair. Okay. That'll work.

So moving on from the SIG case and into your broader work, it seems like a big part of your work, in addition to assessing BAE's business strategy and continuing to evolve that, is mentoring the businesses that you're partnering with or have acquired so that they can make the most out of working with BAE. So just be interested in understanding what's involved in that mentoring. What is it that you do and what are the areas in which these startups tend to need support? I think it really depends on where the business has been.

Right. So first of all, I'd say, you know, if you approach it monolithically, you're missing a large part of how you can actually be helpful. Absolutely. Absolutely.

And so if they spend a lot of time being solely commercially focused, we spend a lot of time helping them understand why should they find the defense market interesting. Right. What are the government processes that get put into place that we can assist them with? What are the oversight and regulations they're going to have to deal with?

We help them gain a better understanding of the DOD mission. Understanding how their end customer is likely to use their product. And sometimes this is really challenging them to think differently, especially in a commercial application to a defense application. That can be kind of a large translation.

Regardless, we spend a lot of time on what I'll call their traditional items. Right. So business development, risk assessments, engineering. But what may surprise you is we spend just as much time on what I would refer to as surprising areas, like helping them with manufacturing processes and how you refine that.

Helping them understand some of the alternative manufacturing technologies that they may want to utilize. We do a lot with open source software architectures. And so working with developers on how do you utilize that environment? How do you make everything open?

Teaming with their lawyers on understanding the IP implications of that. Working with small firms on agile development and technology development and some of the things that to us are just part of our DNA that aren't necessarily part of the DNA of a small startup. I had to pause for a minute because I'm so happy that you're talking about open source software. This podcast is not about open source software.

We'll talk about other things. So you mentioned a very interesting point in there, which is something that we've been exploring for a while, which is why would a small business startup or an otherwise commercial business find the defense market interesting? I'd just be interested in your take on that and sort of how you make that case to them and what the opportunities are. So I think there's a couple of points I would go to.

First, it's a massive market. The activity market is large and it's constantly looking for innovation and new technologies. So you have a huge opportunity space. It's also relatively stable.

So although we've seen a decline in budgets from the highs, we are starting to see growth again and our cycles tend to be longer and so it allows you a bit more stability and structure. And having that predictable budget line or funding stream is key for small business. The ability to go to your investors and say, yes, this is a reoccurring revenue that I have based on my ability to move into this market. In many cases, it also gives you a different type of environment in which to test your product or your capability.

And in many cases, that's a really rugged environment. And when you think about how your product may be used, in many cases, it's the ultimate test. People joke about how you're putting it through obstacles to make sure the device or product or whatever withstands wear and tear. In many cases, we take care of the things that are really hard for a small agile startup to do, which is providing that structure that allows the compliance, that allows the regulatory processes to work and we can kind of be that interlocutor, that bridge between what they do and DOD.

So that last point is really interesting and just as a follow-up question. To what extent are you able to provide an administrative back-end support? And I'm sort of speaking a little bit from personal experience. When I was running a startup, we had to spend so much time just learning our way through DCAA audits and ITAR and those kind of things.

Is that something that you sort of have solutions where you can plug these guys in and they don't have to worry about that anymore? How does that work? In many cases, yes. It's what we do.

It's how we live. It's how we breathe. It's core to our business model. It's how we function day to day.

And so the ability to help a small business through that process or to take care of that process for them when they're our partner is part of what we do. And so it's how we provide benefit to these small agile companies. And so it's something to consider when you're looking for different types of markets to access is partnering with a large prime means they take care of many of those headaches for you. That's fantastic.

So thinking about things from the perspective of startups, the startups you advise, what general advice do you have for them if they're looking to work with a large defense business like BAE? Okay, so a couple things. One, be very specific and approach a large prime with a specific opportunity, contract or customer that you would like to target and where you believe a partner with a ship with them can help. It is much easier for me to put a small startup in touch with the right person when they come to me and say, we have this capability, we think this customer could use it in this way.

So that specificity of, I want to go after this opportunity with you means, okay, then I can put you in the right spot with the right person to talk to, and you don't get pushed around from person to person inside a large company saying, that's fantastic, but not really me, let me point you to my colleagues. So approach a large prime with something very specific and think for that opportunity. So where could your product or solution best be utilized, your capability, do your research. So know a little bit about what the prime is known for.

People tend to talk about the defense primes, again, as kind of a monolith, but we all have unique cultures and unique capabilities and things that we're known for. So make sure you're approaching us with a little bit of knowledge around what it is we care about, what we pride ourselves on doing. That will go a long way. And the last piece of advice is to get involved with some of the organizations that are typical within the defense industry.

So FCA and INSA, industry associations. And so there's numerous industry associations, whether it's service-specific associations, I just chose two that tend to be broader, but spending some time with those associations can be really helpful for small businesses. And your first piece of advice is particularly noteworthy to me in that startups tend to come to introductions with their origin story and their vision and also a great deal of flexibility. That's part of the value of a startup, right?

What are you going to do next year? We can do almost anything. Certainly, that was my experience. And it's natural to think that that's your strength.

And in many instances, it is, but it's not necessarily the best way to introduce oneself to a prime. Right. I like that a lot. So just taking a step back from that, you're in one of those great positions where you're in frequent contact with people from different worlds, DOD people, intelligence community people, defense industry, startups, venture capital.

And I'm guessing you have to do a lot of translating between those communities. So I'd just be interested in your take on what some of the biggest disconnects are or cases where people think they're talking about the same thing, but they're not. How do you see all that? What are the common challenge areas?

So I will say working with all those different communities is one of the things I love most about what I do. So think tanks, government, industry, academia, I get to talk to and interact with all of them. And what I wasn't prepared for in this role was exactly the amount of translating that you do. You tend to think whatever environment you're in that you use these very common phrases and you know exactly what they mean, so does everyone else.

And that is far from the case. I'll give you a couple of examples. So cyber means very different things to different people, as does agile development. So what DOD considers agile and what Silicon Valley and an academic consider agile are slightly different things on that same scale.

What I've been surprised with is even standard business terms can mean something slightly different. For example, addressable market. So people use addressable market all the time. One of the first things I ask back is, okay, do you mean the total market space?

Do you mean the market addressable to you today based on your capabilities? Do you mean the market that could be addressable to you if you had some additional capabilities? What specifically do you mean by that term? Or pipeline, return on investment, all these things sound straightforward, but have a slightly nuanced meaning.

And so the one thing I have learned is that you cannot be over clear when you use these terms, right? And so if you are a startup and you're in one of these meetings, ask. So when a large prime says, you know, what's your addressable market? There's nothing wrong with coming back and saying, okay, so I think you're asking X, or to me, the addressable market is X, right?

So clarify what you mean by that. It doesn't give you a disadvantage to make sure you are actually talking about the same thing. And the last thing you would want to do is make assumptions and you both leave the meeting and you're talking about absolutely different things. Yeah.

And then you numbers look crazy and people question the basis of the entire relationship. Correct. And pipeline, that's key, right? So when you talk about your pipeline, be very precise on what you mean by that, because you'll be able to do that in the future.

Yeah, exactly right. So in closing and sort of reflecting, a lot of our conversation today has been how startups should think about opportunities in defense or with defense industry. But I'd just be interested in your take on the opposite perspective. So startups are very much in passion right now.

That's the answer to all of our problems. Assuming that's actually partially true and we're going to see this kind of collaboration for a while, what should defense industry do to adapt to better collaborate with startups or to generate more value from those relationships? I think you said that almost perfect, which is making sure we acknowledge the value that working with startups bring, right? I can't stress enough internally how much spending time with a startup changes and enhances what our engineers do.

It's that innovation and that culture and agile entrepreneurship that at times you just need a fresh influx of that within your business, right? And so spending time, always a good thing. Making sure we value the startups that we work with and making sure we're partnering with them the right way. So I talked about all those different levels of partnership so that they maintain the key piece that brings the value to you.

You never want to enter into a type of partnership, whichever that is, that destroys that piece. That said, there are real challenges. And so the defense industry can be a bridge of the mission between startups and the government. But ultimately, I think the government, if they're going to wind up continuing to desire working with small businesses and bringing that innovation in, are going to have to figure out how some of those regulatory requirements and contracting requirements are adjusted.

And so I don't see this as something where government has to solve the problem or that small startups need to change or that the defense industry needs to change. I actually think this is one of those issues that it's a partnership and all three pieces need to work to change to make this work. Yeah, absolutely. And the opportunities are there.

Yes, absolutely. So that's a positive kind of feeling to wrap things up on. Neil, thanks for taking the time to talk with us and for providing that perspective and some really specific insights into how to make this collaboration work between these different types of organizations. Thank you.

Thanks so much. To hear more from the National Security Startup Series, go to startups.cnas.org or search for CNAS on iTunes or SoundCloud.

Frequently asked questions

How long is this episode of CNAS Podcasts?

This episode is 28 minutes long.

When was this CNAS Podcasts episode published?

This episode was published on October 20, 2016.

Is there a transcript available for this episode?

Yes, a full transcript is available for this episode. You can read the complete transcript on the episode page.

Can I download this CNAS Podcasts episode?

Yes. Use the download control on the episode player to save the publisher-provided media file.