What if the person who can solve your problem is already in front of you, but the way you're looking for an answer makes them hard to recognize? We can do that with technology. We ask about a scanner's specifications before we can explain what the information needs to help us decide. We can do it with people, too, mistaking an easy conversation for a clear picture of what someone can actually contribute.
On The Matthew Byrd Podcast, I talked with Jason San Souci about two parts of his work that brought that question into focus. Through The Drone Strategist, he helps operators understand how enterprise deals are structured. Through Neurodiversity Works, which he built with his wife, he helps neurodiverse students prepare for opportunities in this industry. The connection is a ceiling. In both settings, someone can have the ability to do the work and still struggle to get past the process in front of them.
Start with the decision
Jason's explanation of the drone business was direct: “They make money for solving problems. Helping people make decisions.” That distinction sounds simple until you look at what we lead with when we're trying to win work. We can talk at length about the equipment, the accuracy, or the hours we've spent learning to capture data. Those things matter, but the person buying the service still needs to understand what the result will help them do.
I've seen that same challenge in laser scanning. During our conversation, I talked about people buying a scanner because they see a growing industry, then struggling to understand the value of the data to different businesses. If we don't understand that value, it's hard to explain our price. We end up comparing hours with someone who may be solving a completely different problem. Starting with the customer's decision gives us a better way to figure out what information is needed and how much work makes sense.
Learn how enterprise buyers buy
Jason used building inspections as an example. A customer may need information before a warranty expires, which gives the inspection a purpose beyond producing another model. Understanding that purpose changes the questions we ask about timing and what the customer needs to receive. He also described the less visible parts of enterprise work, including risk and data handling. A one-page decision brief, in his approach, needs to make sense to the person supporting the project and the people reviewing or approving it.
Assess the work more clearly
The hiring discussion brought a different kind of process into view. Jason described technically capable students reaching an unstructured interview built around small talk and then struggling to show what they could do. His point wasn't to reduce expectations. As he put it, “Keep the bar where it is. Raise the bar.” The question was whether the interview gave the candidate a useful way to demonstrate the ability the role actually required.
I asked him about that because I've been someone who talks about hiring the person rather than hiring a technical resume. I wanted to understand where that judgment could miss something. Jason suggested starting with a conversation about individual needs, with examples such as sending questions in writing ahead of time. What I appreciated about that part of our discussion was the practical place it gave us to begin. We can look at an interview question and ask what it tells us about the actual job.
Reconnect with people you know
That requires learning how a customer works before assuming that a stronger technical pitch will answer every concern. Jason described operators who had already done a one-off project for a potential enterprise customer without recognizing the larger opportunity. We don't always need to begin with an unfamiliar company. Sometimes we need to ask a better question of someone we already know. What happens after the assignment we've completed, and is there another decision coming up that our work could help them make?
Keep showing up with purpose
We also talked about relationships, and Jason's visit gave us a real example. We'd met and communicated before an opening in the podcast schedule created the chance to record together. That opportunity had some history behind it. I shared how messages can go unanswered because I get busy, rather than because I don't want to hear from the person. Jason's advice was to keep making the interaction useful, rather than treating every follow-up as another pitch.
There's a responsibility on both sides of that conversation. If we're trying to be understood, we can show our work in a format that fits us, whether that's writing, photos, or video. If we're making the decision, we can think about whether we're asking the right questions. Neither a polished message nor a comfortable interview gives us the whole picture. Taking a little more care with the process can help us see work and people we would otherwise overlook.
That's the question I keep coming back to in this conversation: what are we making easier to see, and what are we accidentally making harder? Jason's examples give us somewhere specific to look, from the first proposal to the next interview. Catch the full conversation on YouTube, Apple Podcasts, or Spotify: How to Turn $500 Drone Jobs Into Six-Figure Deals | Jason San Souci. You'll also hear about his path through remote sensing, his commercial drone work, and his advice on continuing when a career takes an unexpected turn.