Business
Business

Create Your Own Position Out Of Thin Air

Business

Create Your Own Position Out Of Thin Air

A man looks at someone else's business the way a plumber looks at a house.
developing·concept·1 source··Jun 16, 2026

The Plumber Who Saw the Leaks: Reading a Brand for Holes Nobody Else Noticed

A man looks at someone else's business the way a plumber looks at a house. Most visitors see a nice kitchen. The plumber hears the drip behind the wall, spots the slow drain, clocks the pipe that's one winter from bursting. Jack Moses did this to a famous podcaster's brand. He wasn't asked to. There was no job opening. He just looked — and where everyone else saw a successful creator, he saw a list of leaks: no Twitter posting, no email capture, no cross-posting of podcast clips, no LinkedIn. Then he did the thing that turns a diagnosis into a paycheck. He walked up to the house and said, "I can fix all of that," and got hired into a role that did not exist five minutes earlier.1

That's the move. You don't apply for a position. You manufacture one out of a gap that only a wide enough skill set lets you see.

What This Actually Is

Creating a position out of thin air means spotting an unmet need inside someone else's operation, naming it, and proposing yourself as the person who fills it — before anyone has decided the need is worth a hire. The need was always there. What was missing was someone with enough range to see it as an opportunity rather than as noise.2

The engine underneath it is breadth. A specialist who only does one thing sees the world through that one thing's keyhole. A generalist who has stacked several skills sees the whole machine, including the parts that are missing. Moses is explicit that this is downstream of having a broad skill set: "Freelancer B because he has a broader skill set, he can spot opportunities that freelancer A can't."3 The position you invent is the visible output of perception nobody else has.

How the Eye Gets Wide Enough to See the Gap

Vision scales with what you've done with your hands. When Moses was only a ghostwriter — "I needed to be told what to do and I just wrote for people's social media accounts" — he couldn't see opportunities, because his eye was trained on a single task.4 As he built his own products and brand and stacked more skills, his field of view widened. Suddenly he could look at a podcaster's whole funnel and see the missing email capture, the absent cross-posting, the unused LinkedIn — because he now understood all of those systems from the inside.5

There are two mechanisms braided together here. The first is plain competence: you can only spot a broken funnel if you know what a working funnel looks like. The second is what Moses calls the internal game — "raising your consciousness and seeing things that you can't previously see."6 Strip the metaphysical framing and a defensible operator claim remains: your perception is bounded by your experience, and widening the experience widens the perception. The skills are the lenses. Add a lens and a whole category of opportunity that was invisible snaps into focus.

The delivery mechanism is the network. Moses didn't have a contact line to the podcaster. He routed his proposal "through a connection" up a chain of command until it reached the man, who liked it and hired him.7 Seeing the gap is necessary but not sufficient — the proposal still has to travel. Perception plus a path equals a job that didn't exist.

What This Hands the Rest of the Vault

This page supplies the vault's clearest worked example of skill-stacking converting into raw opportunity. Other pages argue that range is valuable; this one shows range producing a specific outcome — a hire — through a specific mechanism: seeing holes a narrow operator can't see. It gives the abstract "each skill doubles your odds" claim a concrete causal story.

It also reframes job-getting itself. Most of the vault's career thinking assumes you respond to demand that already exists. This concept says the sharpest operators generate demand by making a latent need legible to the person who has it. That's a different posture, and it threads into the vault's positioning and personal-monopoly material as a tactical sibling.

Analytical Case Study: The Aubrey Marcus Job That Wasn't a Job

Watch the sequence, because the order of operations is the lesson.

Moses starts by choosing the target on alignment, not on whether they're hiring: "Who do I want to work with? I want to work with somebody who is aligned with my values and on a similar path to myself."8 He lands on Aubrey Marcus, a big spiritual podcaster. He does not check for an open role. He audits the brand: "He wasn't posting on Twitter. He didn't have a good email capture. He didn't have a good email marketing strategy. He wasn't cross-posting his podcast clips anywhere. He wasn't utilizing Twitter threads... He wasn't on LinkedIn."9

Notice that every hole is a skill Moses already owns. The audit is only possible because his arsenal is wide enough to recognize each absence. A pure copywriter would have seen "a successful podcaster" and moved on. Moses sees a punch list.

Then the proposal: "I saw all these holes and I said, 'I can plug in and do this for them.' And so there wasn't even a job position open, but through a connection that I had... I proposed this idea through a chain of command and it reached him and he really liked it and I got hired."10 No application. No waiting for a posting. He named the gap, named himself as the fix, and used a relationship to deliver the message.

The coda is the honest part: about a month in, he realized he didn't want the job at all — he wanted to do his own thing. But he keeps the lesson: "I believe I went through that to learn the skill of you can create your own position out of thin air if you have enough skills and you can see things sufficiently."11 The job was disposable. The capability was the prize.

Implementation Workflow: Auditing a Brand Like a Building Inspector

You're scrolling someone's profile. Not a stranger — someone whose work you actually respect, someone building in a direction you'd be proud to be near. Stop treating it as a fan. Start treating it as an inspector with a clipboard.

You open their Twitter and there's nothing for three weeks. Note it. You go to their site and look for the email signup — it's buried below the fold, or it isn't there. Note it. You watch a podcast clip and check whether it's been cut into shorts anywhere. It hasn't. Note it. Each absence lands in your gut as a small click of recognition: I could do that. I could do that. I could do that. The list writes itself, and it's a list of things you already know how to build.

Now you stop and ask who you know. Not a cold DM into the void — a real connection, one human between you and them, or two. You write the proposal as a plan, not a pitch for employment: here are the leaks, here's what fixing them looks like, here's me offering to do it. You hand it to your connection and let it travel up the chain. Then you wait, knowing the worst case is silence and the best case is a position that existed nowhere until your eye conjured it.

The Invisible-Gap Failure (Diagnostic Signs)

You waited for the posting. You refreshed the careers page instead of auditing the brand — which means you've outsourced your opportunity to whether someone else has already named the need. The whole edge is naming it first.

You see a polished brand and assume it's complete. The drip is behind the wall. If you only see the nice kitchen, your skill set is too narrow to spot the plumbing, and the fix is more range, not more confidence.

You spotted the gap but had no path to the person. The proposal died in your drafts because you never built the connection that carries it. Perception without a relay is a private hunch.

You named yourself the fix for a hole you can't actually patch. This collapses on contact — you get the role and can't deliver, and the reputation cost outlasts the gig.

Evidence / Tensions / Open Questions

The core claim is credible operator experience: a wide skill set lets you perceive opportunities a specialist misses.12 It's a single first-person anecdote, though — 🚩 SINGLE SOURCE — and survivorship is doing quiet work. Moses tells the story where the gap-spotting led to a hire; the proposals that went nowhere don't make the highlight reel.

A genuine tension sits at the center: Moses took the manufactured job and quit it inside a month.13 Read one way, that confirms the lesson was the capability, not the role. Read another way, it's a caution — manufacturing a position you don't actually want burns a relationship and a month for a skill you could have practiced on a target you'd stay with. The transcript leaves this unresolved, and it should stay unresolved here.

The "raising your consciousness" framing of expanded perception is [POPULAR SOURCE] and overstates a real thing. The defensible version — experience widens what you can notice — needs no metaphysics. Open question: is gap-spotting trainable directly, or only as a byproduct of stacking skills across years?

Author Tensions & Convergences

Moses and Justin Welsh (and the Perell positioning canon) converge on a shared premise: the market does not come pre-sliced with your name on a slot. Where Perell argues you must create, not find, a niche, Moses runs the same logic one level down — into employment itself. Perell says don't look for an empty niche; invent one. Moses says don't look for an empty job; invent one. The structural move is identical: refuse the posture of a searcher, adopt the posture of a maker.

The split shows up in who supplies the gap. Perell's creator manufactures a niche out of their own combination of obsessions — the gap is internal, defined by the unrepeatable intersection of what only you care about. Moses's operator finds the gap inside someone else's operation — the hole is external, sitting in another person's funnel, waiting to be named. One invents demand from the self; the other harvests latent demand from a target. That difference is the whole reason this page lives in business rather than creative-practice: it's about reading an operation, not expressing a self.

Hormozi would press on the survivorship. His volume-negates-luck stance reframes Moses's one clean Aubrey Marcus story as a single successful draw, and would ask how many audits produced no hire before this one landed. Moses tells it as perception; Hormozi would tell it as reps. The honest synthesis is both: you need the eye and enough attempts that the eye gets a chance to pay off. What the disagreement exposes is that "I saw the gap" and "I sent enough proposals that one connected" are two different explanations for the same outcome, and the transcript only gives us the flattering one.

Cross-Domain Handshakes

Here's the plain version first: spotting a gap nobody else can see is the same trick whether you're reading a business, a market, or your own creative voice — the wider your range, the more invisible openings light up.

  • Each Skill Doubles Your Odds of Success — This is the parent mechanism, and the handshake is causal rather than thematic. That page argues breadth raises your value and your odds; this page shows the channel through which it does — perception. Stack a skill and you don't just become more useful in the abstract; you literally see opportunities that were invisible before, because each skill is a lens trained on a different kind of gap. The Aubrey Marcus audit is impossible for a one-skill freelancer not because they lack confidence but because they lack the lenses. The insight that surfaces only when you read the two together: skill-stacking's real payoff isn't capability, it's vision — the capabilities are almost a side effect of the wider field of view they grant.

  • Perell — Create Not Find a Niche — Both refuse the searcher's posture and adopt the maker's. Perell builds a niche where none existed; Moses builds a job where none existed. Putting them side by side reveals a single underlying law operating at two scales: positions of all kinds — market slots, employment, identity — are not found objects but manufactured ones, and the constraint on manufacturing them is perception, not permission. Reading Perell alone, you'd think niche-creation is a content strategy. Reading Moses alongside it, you see it's a general-purpose operating stance: the world doesn't hand you a labeled slot, so you carve one, and the carving tool is a wide enough eye to see where a slot should be. Neither framing, on its own, shows you that "create a niche" and "create a job" are the same gesture pointed at different targets — that only appears when the two pages sit together.

  • Luck Surface Area — The connection here is the delivery problem. Moses's audit is worthless without the connection that carries his proposal up the chain. Luck surface area explains why he had a connection to use: years of action and friendship had built the relay before he needed it. Spotting the gap is the action-luck and opportunity-luck quadrants firing at once; the network is what converts a private observation into a hire. What the pairing makes plain is that gap-spotting and luck-building are not two skills but one loop — the network feeds you the targets to audit, and the audit gives the network something concrete to relay.

The Live Edge

The Sharpest Implication: If positions are manufactured rather than found, then "there are no jobs in my field" is a confession about your perception, not a fact about the market. Every operation you respect has leaks. The reason you can't see them isn't that they're hidden — it's that your skill set hasn't given you the lenses yet. Unemployment, on this reading, is partly a vision problem dressed up as an economic one.

Generative Questions:

  • How many gap-audits should an operator run before concluding the eye isn't trained yet versus concluding the proposals aren't traveling? Where's the line between a perception failure and a network failure?
  • If manufactured positions are disposable to the manufacturer (Moses quit in a month), what does that do to the other party — and is gap-spotting ethical when you already suspect you won't stay?
  • Could the entire skill be compressed into a single repeatable audit checklist, or does it die the moment it's proceduralized, because the whole point is seeing what a checklist would miss?

Connected Concepts

Footnotes

domainBusiness
developing
sources1
complexity
createdJun 16, 2026
inbound links1