They Didn't Ask for a Proposal
No scope usually means they’re testing how you think, not what you can deliver.
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.
And it sends the wrong signal.
It treats the meeting like it was about output, when it was actually about judgment.
What to do instead
The goal here is simple:
Stay useful, without spending real energy too early.
Keep things moving, without turning it into a pitch.
1) Don’t send a proposal
A proposal creates pressure to define work before anyone has clarity.
It also frames you as execution help, when they’re still figuring out the problem.
If they want a proposal, they’ll ask.
If they didn’t ask, don’t volunteer it.
2) Send a short reflection
Not a “following up!” email.
A reflection.
Something brief that proves you heard what matters, without pretending you have the answer already.
You’re trying to do three things:
Mirror back the real tension
Show you’re not rushing to fix it
Offer a small next step that creates clarity
Here’s a template you can copy and paste:
Subject: Quick reflection
Thanks again for the conversation. The tension I heard was [tension 1] and [tension 2]. It sounds like things are mostly working, but progress has slowed because the tradeoffs are getting tighter.
No suggestions from me yet. I mainly wanted to mirror back what I heard and see if that matches your read.
If it does, a simple next step could be one working session focused on one decision: [example decision].
3) Watch the response, not the speed
People obsess over response time.
That’s not the signal.
The content is the signal.
Good signs look like:
They correct you with specifics
They add detail you didn’t have
They ask you to react to a real situation
They propose another conversation without asking for deliverables
Weak signs look like:
“Thanks!” with nothing behind it
“Let’s reconnect sometime” with no substance
Immediate pricing requests with no context
Endless vagueness that never sharpens
4) If they re-engage, narrow the job fast
Avoid open ended advisory.
Offer something small and contained so you can test working chemistry in reality:
One decision
One flow
One working session
One short problem framing doc
This protects you from drifting into abstract debate.
5) If it stays vague, walk
If they keep talking in circles, or every concrete issue gets explained away with principles, you’ll end up doing a different job:
Translating reality into language they can tolerate.
That’s exhausting, and it usually doesn’t lead anywhere.
So give yourself permission to stop.
Follow up once.
If nothing sharpens, move on.
A quick read you can use right after the meeting
If there’s no scope, send a reflection. Don’t send a proposal.
If they say “let’s just chat,” assume they’re evaluating how you think. Don’t pitch.
If they go quiet for a week, don’t spiral. Wait and watch the substance when they reply.
If they re-engage without deliverables, suggest one contained session on one decision.
If it’s polite praise with no specifics, don’t chase.
One nuance people miss
Being evaluated doesn’t mean you should want the job.
Sometimes you read the room correctly and still decide it’s not a fit.
Chemistry matters.
And high level work still needs traction, not just respect.
The takeaway
If they didn’t ask for a proposal, you probably didn’t miss anything.
They might be deciding whether you’re someone they can think with before they commit to anything.
So don’t rush to sell.
Show you understood what’s hard.
Offer one small next step.
And if it never becomes concrete, let it go.
Thanks for reading,
Gev
Happy Sunday, Gev!
This is a great topic to explore with Blair Enns' Four Conversation. I used to confuse speed with value and alignment during the sales process which would result in doing more work then I needed to land a client. I'm learning to slwo down and go through the steps to ensure the alignment and fit first.
Shared this with our Slack crew.
Hey Gev! Qq: if they don't get back to you in 2 weeks, do you recommend a follow-up email to check in or would that make the potential client feel pressured?