Skip to content
Startups Series: Jackie Space, BMNT Partners episode artwork

Oct 12, 2016 31 min

Startups Series: Jackie Space, BMNT Partners

from CNAS Podcasts Hosted by Center for a New American Security

Jackie Space, Partner at BMNT Partners, explores DOD’s current focus on Silicon Valley and national security startups and offers advice to entrepreneurs in the domain.

Episode details come from the podcast's RSS feed.

Embed this episode

Ready to play

Startups Series: Jackie Space, BMNT Partners

0:00 31:29
of matches

Transcript Auto-generated, may contain errors

Welcome to the Center for New American Securities National Security Startups Podcast Series, hosted by Senior Fellow and Director of the Technology and National Security Program, Ben Fitzgerald. Hi, everyone. Welcome back to the CUNAS National Security Startups Podcast. We are here today with Jackie Space from BMT Partners.

Welcome, Jackie. Thank you. So Jackie has fantastic perspective that she can provide here. She is, in addition to being a partner at BMT, she's also the founder or co-founder at BMT Capital.

She's a former officer with the United States Air Force and is also a visiting fellow at National Defense University's Center for Technology and National Security Policy and is also on the board of Sylvonics Biomedical Startup. I don't see how you have any spare time at all in addition to doing all those things, Jackie, but thank you for taking the time to do this. Yeah, no, thank you for having me. So let's just get straight into things.

Could you just tell us a little bit about BMT, who you guys are, that kind of thing? Sure. So we are a three-year old company based in Silicon Valley. We started by people who were the founders who all had extensive military backgrounds who wanted to continue service to their country.

And now we've grown to about 25 people and we have a pretty interesting group of folks that work for us that come from really diverse backgrounds that all have an interest in national security, but also I think have just a diversity and interesting perspective to bring to the problems that we're working on. And so we're here to basically solve national security problems at Silicon Valley speed. So I think I have to ask then, understanding that that general problem, what's the specific problem that BMT was founded to solve? Sure.

So we saw a problem on both sides of government and private industry and wanting to work together, but really unable to sort of align the priorities and timing and even the language and how they communicated with each other. And so on the one side and just drawing from my background in defense acquisitions, I saw a lot of tech and programs that were being developed and funded that were not necessarily had an application or a problem that they were solving and weren't useful to potentially the users that needed to use it. At the same time, with the rise of all the innovation that's coming out of the private industry, we saw a really interesting and good tech that was on the private side that they wanted to be able to sell the government or saw a solution that could be applied to and couldn't align the cycles in terms of how they could work together. And so I saw a lot from the government side just as frenzy of just wanting to fund tech for the sake of funding tech and not really again, thinking through the whole strategy of who's picking it up, who's using it, what's the transition pathway, all this sort of pre-requirement stuff that needed to occur that wasn't happening.

And so that's where BMT was created to basically align the problems that were emerging in the battlefield to the emerging innovation and sort of maximize efficiency and availability of the just enormous resources and talent that this country has to solving national security problems. So that's quite compelling. I have to ask a particular question and as a defense note, I know the answer, but what does BMT actually stand for? No, I get this question a lot and yes, it's not just a random acronym.

It stands for Begin Morning, Nautical Twilight. And basically the term is an old military strategist term used for military planning. I think it dates back to the French Indian War and it describes a time when the sun is below the horizon and incidents I think are 12 degrees. And yet you can still start to make out the shadows and light on the ground.

And the term was used for the time when it was sort of the greatest threat to opposing sides, but also the best time to attack. And so we thought it was sort of apropos to what we were seeing on this tech landscape of a lot of great promise, but also a lot of vulnerabilities in the international security system. I like it. So given that problem and the group of folks that you've brought together, how are you going about fulfilling the mission that you've set for yourselves?

Yeah, we can't solve a valley because we felt it was a good place to start to find talented people and business methods that we could apply back to our knowledge of how the government works in terms of, you know, with technology and on the battlefield side. And honestly, after I'm looking around the valley for the first year and trying to figure out our way around, we initially started by consulting with startups who wanted to work with government. And while that helped us to learn a lot about the start of culture and what their pain points were and how the valley operated, we still weren't fundamentally addressing the problem of how to align the two sectors. And so we quickly realized that there needed to be this better framework and methodology for how that engagement worked.

Part of this was coming out of the fact that we could show the government, people on the government side some of the best and most amazing technology, but it didn't matter if it wasn't aligned to the government bicycles, it wasn't aligned to the requirements process, if there wasn't that sort of pre-planning work that had to be done in order to ingest something like that to solve the problem. So we adjusted out of that business model and we combined what Peter Nool had developed when he was at the Army's rapid equating force. And we knew that that model worked in the government in terms of being able to take the solutionary teams directly out into the field and sourcing problems directly from the battlefield. And so he had proven that model out over three years.

He had built this ecosystem of people not just from Silicon Valley, but from all over the United States and people that were working on these amazing life-saving solutions. And he also was able to do it in a way that he was executing, I think, a billion and a half dollars on a $300 million budget, meaning that he was bringing all kinds of mission partners to the type of work. So we took that model of problem sourcing and then at the same time, being in the valley, we ran into Steve Blank and the work he was doing when the lean startup movement and teaching the startup at Stanford. And we found that his model actually worked quite well with what Pete had been doing in the Army in the sense that with the startup, you have to go through this.

There is no business plan and there's a whole bunch of unknowns set in front of you. And so lean startup really teaches you or really teaches startup founders how to basically take a set of unknowns and turn them into knowns through very early hypothesis testing and a lot of customer validation and basically getting out of the building to go validate your set of assumptions. And so basically we combined the two models and came up with hacking for defense, which is a way that we basically source problems from the government. We build a network of people and entities around the problem and then we really started selecting the problems that we call the mission model canvas which is adapted from lean startup business model canvas.

And we start finding the stakeholders and users of the system and understanding their value proposition. And so all of this is really pre-requirements work. So we have a really good set of validated assumptions around a particular solution to hand back, and the government works with this on this hand back when they start writing those requirements. And by the time they're able to release and verify an RP, they're in line with industry in their line with what their users want.

So that's a fascinating set of offerings. I'd be interested if you could talk a little bit about how your business model works. It sounds from what you've talked through that you have clients on the government side and also clients on the private sector side. It's just interesting how that works in terms of from two perspectives.

One, how that makes the solution set, you just talk about work, and then also how you run BM&T to be able to cover those different clients. Well, yeah, I mean, from a business model perspective, I mean, we truly look at ourselves as problem-solving organization, the heart of the better, through H4D, it's enabled us from a business model perspective to have a sort of systematic way that we engage. And so through that, we're able to plan strategically how those engagements work. We have a very sort of defined set of steps that we go through with our clients on the government side that helps us to work with our industry partners so that they know what's coming, they know when they're invited to the table.

One of the problems that we found working with industry and getting them to the table is that a lot of it was just miscommunication. They wouldn't understand the strategy of what the government side was doing or the timeline or the intent of the engagement. And so we spend a lot of time doing that translation. And I think we're different in a business model than other companies in that we aren't selling solutions that we've developed in-house.

So we know that we're not the smartest people in the room. I'm definitely not. So we like to, I mean, part of the model enables us to basically access some of the best and brightest talent in the world to come look at these problems. And so through that, we really are just looking for the best solutions.

And it's a validation behind that that we're interested in. So that's really how we operate. We're not selling prototypes or products. Yeah, it's interesting.

So you're a startup that helps startups and you have a model for helping people build models and systems to build solutions. It's a little meta. It's totally not. It's very 2016.

I like it. Given the space that you operate in, which is developing and there's a lot of miscommunication and all those sorts of challenges in there, just be interested in the core challenges you guys face growing the business and also scaling your impact, given the objectives, seems to really be about impact as much as business size. Yeah, it's really challenging. I think when you're doing something different, especially as a young business, it's a challenging prospect.

I mean, one is sort of selling that this works. And the way that we've got about doing that is we really focused on getting tactical wins. So not necessarily coming in at the enterprise level yet and saying, hey, we're going to change our organization and your organization is coming to be innovative. What we focused on is more hard problems that people at say, we work with a lot of different agencies, but hard problems that basically can get a win in the next year or so, and the smaller group of people and growing that out.

So as we, now after three years, I can say we've got some really good wins behind us and satisfied clients that this model works. And so now we're looking at more of a strategic level of expanding into more of enterprise level type organizations. And not just in the government, we're getting a lot of interest from other ways that this could be used. So for instance, we've been approached for city planning type activities, so hacking for urban resiliency.

Or we just did a space study with Christopher's Emperor at CTNSP, looking at how government looks at emerging commercial space. And so, you know, and we've been approached by the corporations and how they do innovative transformation. So we're starting to look at that scaling and what that means to us. But starting company is hard.

I think now the level that we're at going from 25 people to 50 people is almost just as challenging, I think. I'd be interested in your take on the common challenges or recurring themes you see in terms of issues between startups and DOD just being able to collaborate in your business. Sure. So I think from a the term startup has a lot of meaning behind it.

There's so many different levels of startups and we've worked with startups from concept through their fundraising. And we've worked with companies that are much more mature and get their skills in Silicon Valley. So not necessarily startup, but they still have something to offer to a solution. And so as far as, so the question is advice on collaboration or advice on just for companies that we're seeing.

And just the challenges that sort of come up. So you mentioned earlier, which I thought was a great point, just communication. And then buying cycles, all those kinds of things. So the challenges between both entities.

Yeah, actually. What are the barriers? Oh, yeah. I mean, it really is.

It really comes down to communication. It was what I'm seeing. A lot of the debate about how to do this right is centered on acquisition reform. And I wholeheartedly agree that we do need reform.

But I'm also not holding my breath for it. Right. You could be holding your breath for 30 years. We've been waiting at least that long.

Yeah. So we really had to, in order to make this work, we had to figure out what's working what can we do today with the resources we have available today. And a lot of it comes down to just the way that the engagement occurs. So I think from the military and the television side, they've never been asked to become venture capital capitalist.

Right. And it's sort of unfair to say, okay, now you have to act like one. And without any, it's not part of the main jaw jar, potentially. And it's just not the culture that they grew up in.

And so what I find really fascinating in the sense is that the two communities actually are not that far apart in the sense that a venture capital firm might look at 2000 companies and fund eight. And the government, when they're in tech scaling, has a lower track record or the same. They're pretty much on par with the amount of stuff that they look at in terms of what they end up funding. But I think the difference in why the government sort of gets this sometimes bad reputation about that is because it's the way that they do it.

So instead of, I think in a VC firm, they know their space really well at investing in. They spend a lot of time meeting with companies and founders and entrepreneurs and really learning about what's in the space. And then when they do take meetings, it is hard to raise money and it's hard to get into capital money. But at least there's a feedback mechanism in place.

And at least when you walk into a VC firm, what their strategy is, what their portfolio is like, what their targets are. They have all that out there. And I think that's something that on the government side, we can improve in terms of instead of showing up to a meeting and just saying, okay, showing what you got back to the private company, actually explaining why you're there, what's your strategy, what's your problem you're dealing with, what's your funding timeline? Just basic questions like that, having a more a back and forth dialogue.

I remember when I first started working with Dr. Manlia Sharvat, who's a CEO of Sivonics. And I met her when she was at concept stage and we went through a million-a-half dollar race together. I was one of her first investors and then we're going through another race.

But when she first started, I mean it was just her. And she has this amazing technology that IP that's come out of Stanford that is basically a cognitive assessment tool in digital health. And we're getting a lot of traction in the firm and health industry. But there was interest from the government side.

And so they were asking her to come and show up to conferences and come and talk about it. So I said, great, I want to go with you. Let's go see what this is about. And they kept calling her and wanting to show up at these things.

And finally when I asked the guy, I said, well, why are you talking to her? And what's your strategy? And he said, oh, well, we want to go palm for this. We put in a palm cycle, which is like the next three to five years, for this type of technology.

And I'm like, she is not at the level right now where she can be dealing with something like that. And just for our readers who haven't had to suffer through the budgeting cycle, what is the palm cycle? So it's a program objective, a random? Yes, it's a putting on the spot.

But I used to actually contribute to writing those when I was in the near-course. And it's a multi-year funding cycle. So she would potentially not be even close to funding for three years. And then if it came through, she would have multiple years of funding, but she may not be in business for years.

Right. And it's great. Yes, the great potential. But that's where I think the term startup gets almost overused or isn't defined accurately, because there's a big difference between a startup and a startup that maybe has gone through one race or seller races.

Because those startups can actually handle some of that type of government engagement. But the very early ones, it's almost impossible at that point to really go spend time if you want to have a business in the next year working with government. Yeah, it makes a lot of sense. So then the flip side to that question in terms of the challenges you see is what's the advice that you provide to the startups you work with?

Obviously, there's not just one thing that you say. But in terms of, again, general themes, what are the core pieces of advice that you would give to someone listening to this podcast, for example, if they were running a startup focus on national security? I think anybody who's starting to know is that it's very hard soul searching work. It's not for the faint of heart.

And that's why a lot of startups fail. I mean, it's very difficult to grow a business that your customers have the strategy. And also at the same time operate a company that can grow to scale. And when you're doing it, you don't have everything as a known.

You really don't have true direction. You don't have a structure behind you that can support something you do. So I think that the best piece of advice for me that I'm learning and that I have seen work well for the CEOs and people I've worked with is having trusted advisors around you that have gone through an aspect of what you're dealing with. And you know that their advice is good.

But they also will tell you things that are honest and it can be really hard at the ego. And so you have to be able to deal with that. And it's hard. And the good ones, good advisors won't talk to you when you first start.

Because you have to get yourself established a little bit and prove that you're serious and really keep showing up every day and working through it. And then slowly, I think you'll start to talk people around you that you can trust to do that. But it's very challenging. Especially for the single founders.

It's a lonely experience. Yeah. And also, I think I'm sure this is true in loss of domains, but I think very true in the national security space. Once you have that business that is starting to be successful, every bad advisor in the city wants to come out and get on retainer to offer you advice.

So tell them the difference between a good advisor and someone who's just going to take your money can be challenging. Some of our, I think some of the best people we've worked with from advisor perspectives are ones that you can tell truly believe in what we're doing. And they're not looking for money. They really just have this belief in wanting to help us.

And you see, that's the one thing I really do appreciate about Silicon Valley is that because of the culture of startups and the fact that it's very hard and the failures that occur can be very big and painful. That there is this sort of camaraderie wanting to help each other out in some way. Because I mean, it's a, it's a, it's a, it's a, it can be a tough lonely business. In that sort of broader Silicon Valley context, I'd be interested in your thoughts on Deity's current Silicon Valley and startup focus noting the, the points you made validly about what do we mean by startup.

Has the Deity got its goals right? Is it headed in the right direction? Whether that's from the secretary's perspective, from a DIUX perspective, just in general would be very interesting of course. So DIUX is a client of ours.

I am a believer in what they're doing. I think, you know, just like any government program that starts, it takes time. I've never seen a government program stand up quickly. I don't think Ecutel did.

They didn't have their budget in place for a while. In terms of what they're doing right, what I really appreciate about the model is, is that government and military is looking at how do we work better with private industry right before it was, well, we've got E-Q-Tel and E-Q-Tel does is investing, you know, for emerging startups. And that's great. And there's definitely, I think they serve a great role for that.

But there are a lot of companies and a lot of tech and innovation that's happening outside of the E-Q-Tel model that doesn't fit in that model. And so then we go back to talking about, well, how do we develop those relationships, the strategy, the things that are needed in order for us to do this right, we need something in place that is on the ground and enables that conversation. And so I think the term, whoever came up with the term matchmaker did a big disservice. I don't think that was the right term.

I think that now from what I'm seeing, I know Raj Shah was on here talking about what they're doing. I think they've really got it right in terms of how they're framing things right now. And particularly, I mean, I mean, I'll plug for ourselves, but on the problem sourcing side is where we're working with day-of-ex as a problem sourcing and translation. But the other thing that I think is encouraging is the fact that, you know, Raj and his team, you know, they all have extensive private industry experience.

And so they have a lot of relationships in place. They understand the pain points and how to frame this in a way that it makes sense. And so do you think that on the Silicon Valley side of things, on the startup side of things, that there's been a reasonable response? Do you think the valley is getting its head together and starting to understand some of the opportunities associated with collaborating with the data?

Yeah, you know, that's an interesting point. I mean, I've heard, you know, obviously grumblings from both communities, DC and Silicon Valley. And but the one area, and I would say is not even for day-of-ex, but what we've seen a lot, and I think it's really encouraging. And I think day-of-ex is going to benefit from is that in the valley, there is this appetite to work on world-changing things, right?

And so, you know, there's this sort of fatigue with, you know, working on the next one-hour delivery app versus, oh, hey, you know, there's soldiers in the field who, you know, you could say the lives, you know, with this thing or, you know, there's major implications of a nuclear security perspective. Just the problem is that we've brought into the valley. We've gotten this amazing response from people excited to work on that stuff. For instance, like we just had an H4D sprint where we were working with an agency and we brought in designers from San Francisco and digital designers, right, to be able to help them put their models together.

And, you know, they were actually staying later than the government people because they thought it was really cool the stuff that they were working on, you know, versus it was either that or like the next Angry Birds 7. So I feel like, you know, there is an appetite there. And yeah, I mean, do companies get annoyed when, you know, or people get annoyed when they feel like nothing's happening? Yeah, but I also know a lot of companies that have welcomed engagement because they are welcoming the discussion and the type of stuff that's coming to the valley.

So I think the valley is a lot to gain by having some of the problems that DC looks at in this center. Yeah, absolutely. So, so in closing, I'm just interested. Where do you see this relationship going over the next few years?

And feel free to give both an optimistic and a pessimistic response unless you have, you naturally go one way. Well, I think naturally, I'm going to be an idealist just because, you know, I've put my company on this. You need to be. So one of the things I think is really encouraging is just the amount of dialogue that's occurring over this, which creates a lot of, I think, interesting discussion as well as transparency.

And you see both sides, so it's not just a Silicon Valley thing. I mean, we're seeing a lot of interest and it's not just a playing on thing. I mean, we're seeing people from all over government offices that are wanting to work on this type of engagement and not just with Silicon Valley, but with, you know, all the other innovation centers in the United States. And so for me, I think this is proving a model out.

And if we can do it in the valley where, you know, we've got some of the, you know, the brightest people and some of the most fastest emerging tech, I think we can do that in any of the other places as well, where you've got just the right people and just this interesting tech. So, I mean, I really hope that this is something that will continue. I think one of the things that, you know, through all this debate is hopefully that there's more of an understanding between what drives Washington DC and what drives Silicon Valley. I think that two communities don't talk as well as they should.

And there's not enough people that can go back and forth. And so, so we're really, you know, I think as we grow those types of people that are looking at national security as something that's interesting to work on, that dialogue will continue. You know, one of the most encouraging things that we've seen also is hacking for a fence now in the university system. The fact that you've got students, so we started this at Stanford.

And I was on the original teaching team there with Steve Lang and Peter Nolan and Joe Feltier. But it was really amazing to see that the level of passion and dedication that went into the work that these students were doing. And, you know, I kind of was skeptical about, like, well, you know, we first started like, how, you know, are these students really going to want to do this? Are they going to want to work on these types of problems?

How much time is they going to put into this? And we found the opposite response. I mean, they found that working on real world problems that they can actually have a real impact was very encouraging. And when you think about that, there's now a whole other ecosystem of people that would have never worked on or thought about national security stuff.

That's really exciting to me. I think from my from idealism perspective, I think it's going to continue to get better. Well, it's always nice in this line of what to be able to end on a positive note that tends not to be the case. So thank you for bringing that optimistic outlook to whole thing and for sharing your expertise with our listeners.

One more thing actually, I'm talking about hacking for defense in the university side. I don't mean to do one more plug, but as far as from the government side, the National Defense University's Center for Technology, National Security Policy, Christopher Zember, and his group out of there at the MD5, National Security Technology Accelerator, they've been huge promoters of hacking for defense in our original sponsors for that. And we see a lot of what they're doing in DC and the people that they're engaging with that do sort of understand how it works in Silicon Valley and vice versa. So anyway, going back to the discussion about how is this going to be in the next four years, we just think that it's going to continue to get better.

No, I agree. I think that there are lots of folks inside government increasingly who get it and it's reassuring to see places like CTNSP at NDU sort of bridging that gap, especially at the working level in very practical ways. It's fantastic. I worked with Christopher back when he was a director at the information else's centers and he grew what they were doing there to be a very practical and useful mechanism for contracts.

And so when I was working a lot of the rapid technology stuff, I mean, they were such a resource. So he really gets that engagement from a tactical analyst's strategic level. So he's one of our original partners and it's just it is great to find people like that in DC who are working to better than engagement. That's right.

People in the Pentagon and the Broad Departments actually care about this stuff. They do. Yeah. And there isn't a way to execute.

So again, another positive point. Yeah. Thanks again for joining us. Yeah, absolutely.

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 31 minutes long.

When was this CNAS Podcasts episode published?

This episode was published on October 12, 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.