I Had No Experience. I Won Anyway. Here's the Actual Reason.
I walked into a technical meeting with a government engineering team and I had no engineering background whatsoever.
They asked technical questions. I answered zero of them directly. I left with the project moving forward.
This is not a story about faking expertise. It’s a story about understanding which expertise actually matters in any given room — and making sure you show up with that one.
The expertise trap
There is a common belief that you need deep expertise in your field before you can operate credibly in it. That gaps in your technical knowledge are weaknesses that will be discovered and used against you. That authority requires knowing everything.
This belief causes two problems.
First, it keeps people out of markets they could successfully enter, because they’re waiting to develop expertise that can only be developed by being in the market.
Second, it causes people who do enter to spend enormous energy performing expertise they don’t have — which is both exhausting and transparent to anyone who actually has it.
What authority actually requires
In the meeting with the government engineers, the real questions being evaluated were not technical. They were: Can this company deliver? Will the timeline hold? Is the financial structure sound?
These were questions I could answer with complete confidence, because they were in my domain. I understood contracts. I understood project management at the business level. I understood the risk structure of government procurement.
When a technical question arose — fire suppression specifications, structural load calculations — I didn’t attempt an answer. I said: “My engineer will align with you on the specifics.” Then I redirected to the level of conversation that mattered: can we deliver, on time, within the financial structure we’ve agreed.
This is not evasion. It’s accurate process. Technical details get resolved in the technical stage. Strategic meetings resolve strategic questions. Knowing which level of conversation you’re in — and operating at exactly that level — is a skill that most people never develop.
The minimum viable expertise
When I entered the government construction market, I had knowledge of procurement processes from previous work, a technical director with real construction experience, understanding of contracts and financial risk, and the ability to manage relationships at the decision-making level.
I did not have engineering knowledge, construction site experience, technical certification, or years in the industry.
The expertise I had was exactly sufficient to operate at the level I needed to operate. The expertise I didn’t have was covered by people whose job it was to have it.
How to identify your actual domain
Ask yourself: in the work you’re trying to do, what decisions actually require your direct knowledge? What can be delegated to people whose domain it is?
Most people dramatically overestimate the range of expertise they personally need to operate. They’re trying to cover the whole field when they only need to own one corner of it — deeply, confidently, without apology.
Find your corner. Own it completely. Let the engineers handle the engineering.
Vinicius Araujo entered a market he didn’t fully understand and built it to over $3M in contracts. His book, No Eggs, No Chicken, No Pan, is about how.