August 11th, 2026

A while back, I got on a call with a founder I’d been talking with for months. Let’s call him Marcus.

​
​

Marcus had a clear vision. He’d clearly been sitting with it for a while – he knew the shape of what he wanted, he had language for it, and he’d done real thinking on his own before we ever spoke.

​
​

Early in the call, he stated a number of hours he thought we’d need together.

​
​

I asked what those hours would build – what would exist at the end that doesn’t exist now.

​
​

“That’s what I need you to help me figure out,” he said.

​
​

Fair enough – that’s often exactly the work. But here’s where it got stuck: he’d already arrived at the number of hours before any of that figuring-out had happened. The number wasn’t the output of a scoping process. It was a placeholder that had stepped in and started acting like an answer.

​
​

So every time I tried to open up the real question – what are we actually building, what does done look like – there was nowhere for it to land. In his mind, that part was already settled. At X hours. Before the scope existed to justify it.

​
​

That’s the pattern I want to highlight for you today, because I don’t think it’s limited to hiring conversations.

​
​

Sometimes the number arrives before the process that’s supposed to produce it.

​
​

A budget gets set before the project is defined. A timeline gets promised before anyone has mapped the actual steps. A headcount gets decided before the role is scoped. The number feels like progress – it’s concrete, it’s decisive, it’s something to hold onto. But if it didn’t come from the scoping work, it can’t be tested against the scoping work. It just sits there, blocking the conversation that was supposed to happen first.

​
​

The Scope Test

Take a number you’re currently holding – a budget, a timeline, a headcount, an hours estimate – and ask:

​
​

• Where did this number actually come from? A calculation, a gut feeling, or something you saw someone else do?
• If the scoping process happened after this number, would it likely land on the same number?
• What would you need to see or learn to feel comfortable changing it?
• Are you protecting this number because it’s right, or because it’s already decided?

​
​

If a number you’re holding didn’t survive that test, that’s not a failure – it’s useful information. It usually means the scoping work still needs to happen, and the number needs to step aside long enough to let it.

​

If you’re sitting with a number like that right now – one that feels settled but hasn’t actually been tested – I’d love to hear about it. Book an intro call here – no pitch, just a conversation about what’s behind that.
​

​

Talk soon,
Moriah

​

P.S. This is the first of three patterns I keep seeing at the exact moment ambition meets execution. Next up: what happens when the concept is agreed on, but signing the contract still stalls.