A lot of the time, “no scope” isn’t a mistake. It’s how they figure out whether you’re any good before they commit to anything.
A fractional asked me recently:
“I had a meeting that felt kind of off.
Good chat, but no clear next step.
They didn’t ask for a proposal.
Did I miss something?”
Usually: no.
Sometimes the lack of scope is the whole point.
Because there’s a specific kind of meeting that happens right before a real engagement, where the team knows something is stuck, but they can’t name the work yet.
They’re not shopping for execution.
They’re trying to see if you can help them figure out what the work even is.
And they do that by watching what you do when things aren’t clean.
The meeting that feels “off”
These meetings have a familiar vibe:
Nice people. Interesting problem. Plenty of context.
But no one says, “Here’s the project.”
No one asks for a proposal.
No one says, “Can you send pricing?”
Instead you hear lines like:
“Let’s start with a chat.”
“Maybe there’s a way to work together to get this over the line.”
“We’re at a point where we need to step back.”
That’s not casual language.
It’s careful language.
They’re telling you they don’t know what the work is yet, and they’re watching whether you can handle that without turning it into a pitch.
What they’re actually testing
When a team asks for a proposal, they’re buying output.
They have a rough scope in their head, even if it’s incomplete.
When they don’t ask for one, they’re often evaluating something else:
Can this person listen, find the real tension, and stay useful without rushing to a plan?
They’re also screening for a common failure mode:
Smart conversation sitting on top of weak execution is a real smell.
Meaning: plenty of opinions, great vibes, no traction.
So they watch whether you can stay concrete without forcing certainty.
This is upstream work.
Not “do this thing.”
More like:
What’s actually going on here?
Why does progress feel slower?
Which decision are we avoiding?
What are we trading off without admitting it?
Why it feels harder than normal consulting
At this stage, nothing is on fire.
The product usually works.
Users aren’t furious. Metrics aren’t collapsing.
But progress is slower in a way nobody can explain.
So the problems stop showing up as bugs and start showing up as tradeoffs:
Navigation vs guidance
Freedom vs focus
Principles vs patches
Speed now vs speed later
Here’s what that looks like in real life:
You suggest simplifying onboarding. It reduces confusion, but now support load goes up because you removed the “advanced” paths power users relied on.
You tighten the flow. New users move faster, but retention drops because the product starts feeling rigid.
You change one thing and something else shifts.
That’s why the conversation feels layered.
Every topic bleeds into the next, because the system is connected.
If you’re actually contributing, you feel the mental load of tracking the whole system, not just one task.
That feeling isn’t a red flag.
It’s information about the kind of work this might become.
The mistake people make
Most people leave these meetings and think:
“No next step. Guess there’s no project.”
Or they panic and try to force it into a normal sales motion:
They send a proposal.
They push for scope.
They ask for timeline and budget.
They try to “close.”
But that moves too early.