Direct Answer

My big proposals kept scaring nonprofit clients into "let me think about it." So I stopped leading with big. Now I offer a small paid first step, a plan, an audit, a pilot, before I ever pitch the larger engagement. It lowers the client's risk, builds trust, and the bigger yes tends to follow on its own. Tight budgets say yes to small far faster than they say yes to huge.

Every video in my "30 Hacks From Dahlia" series ends with the same line: I help small teams do big things. This hack is the one I learned the hard way, by watching that promise almost fail on delivery. For a stretch, my proposals were big by default, full strategy, full build, full price, all bundled into one ask. And the response I kept hearing back, especially from nonprofit clients with the tightest budgets and the most cautious approval chains, was some version of "let me think about it."

That phrase is a tell. It rarely means no. It means the ask was bigger than the amount of trust that existed between us at that moment. Nobody wants to be the person who approved a large, unproven spend on someone they just met. So the proposal sits. It gets "revisited next quarter." It quietly dies in a board packet. Not because the work wasn't needed, but because I'd asked for a yes that was too heavy for a first conversation to carry.

Why tight budgets say yes to small

Nonprofits and small teams don't have slush funds for a leap of faith. Every dollar usually has to be justified to a board, a grant restriction, or a founder watching cashflow line by line. A large proposal asks them to make a large decision on limited evidence: my reputation, a sales conversation, and a document. A small proposal asks for something much easier to approve: a modest, bounded expense that solves one real problem and produces one real deliverable. Committees can say yes to that in a single meeting. They can't always say yes to a five-figure commitment in the same room.

This is the part I underestimated for years. I assumed the barrier was price. It's not, not entirely. The barrier is risk, and price is just the number attached to it. Shrink the risk, and a client with a genuinely tight budget will move faster than one with money to spare, because the small yes doesn't require them to bet on someone they don't know well yet.

What makes a good small first step

Not every small offer works. A good small first step has a clear, standalone deliverable, something the client can actually use even if they never hire you for anything else. A plan. An audit. A pilot of one specific piece of the bigger idea. It has to be scoped tightly enough that you can deliver it fast, and it has to be priced at a real, if modest, number.

That last part matters more than it sounds like it should. It is not a free sample. A free first step tells a client the work isn't worth paying for, and it tells you the same thing about your own time. A small paid step is different: it's a genuine, if scaled-down, piece of professional work, delivered at a price that respects both the client's caution and your own hours.

What belongs in a small first step

A single, named deliverable. A plan, an audit, or a pilot, not a vague "discovery phase" with no defined output.
A tight, honest timeline. Small steps earn trust partly by proving you can deliver quickly, not just well.
A real, modest price. Low enough to approve without a lengthy sign-off, high enough to respect the work involved.
Standalone value. The client should walk away with something usable, even if the bigger project never happens.

How the small step builds trust before the bigger ask

Trust doesn't get built by a proposal document. It gets built by watching someone actually do the work. A small first step lets a hesitant client see how I run a project before they've committed to a large one: how I communicate, how I hit a deadline, whether the deliverable is genuinely useful or just padded to look thorough. By the time that small engagement is done, they're not evaluating a pitch anymore. They're evaluating a track record, one they watched happen in real time.

That shift changes the entire tone of the next conversation. A client deciding whether to trust a stranger with a big budget is a slow, anxious decision. A client deciding whether to expand on work they already saw delivered well is a much faster one. The small step doesn't just lower the dollar risk. It replaces a leap of faith with an actual data point.

Why free consultations often backfire

💡
The seriousness signal

A free consultation filters for nothing. Anyone will take a free hour, including people who were never going to hire anyone. A small paid step filters for real intent on both sides: the client has to decide the problem is worth even a modest investment, and I have to actually deliver something worth what they paid. That mutual seriousness is what a free call can't manufacture.

I used to offer free consultations because it felt like the lower-friction option. It is lower friction, which is exactly the problem. Friction is doing useful work at that stage: it's separating the people with a real problem and a real budget line from the people who are just curious. A small paid step keeps that filter in place while still being far easier to say yes to than the full engagement.

Shrink the first ask, not the value of the work.

Letting the small step make the case for the bigger one

The natural path from small to big isn't a separate sales pitch tacked onto the end of the small engagement. It's built into the deliverable itself. If the small step is a real audit, it should surface the actual gaps, risks, or opportunities in the client's own systems and numbers, not in a slide I wrote to sound persuasive. If it's a real plan, it should map out a sequence of phases where the next one is the obvious next investment, because the plan itself made the case, not me.

By the time a well-done small step is finished, the client is often the one asking what a fuller engagement would look like. That's a completely different conversation than the one where I'm trying to convince someone to trust me with something large before they've seen a single piece of my work. The small step did the convincing. I just have to answer the question honestly when it comes.

Pricing the small step

There's no universal number here, and I'm not going to pretend there is. What matters is the principle: price the small step low enough that a tight budget can approve it without months of back and forth, but high enough that it respects the actual hours the work takes. The goal isn't to make it cheap. It's to make it small, a bounded, well-defined piece of work priced fairly for that scope, not a discount on the bigger project disguised as a freebie.

Undercharging for the small step causes the same problem as giving it away for free: it signals the work isn't worth much, and it makes the eventual jump to full-project pricing feel jarring instead of natural. Price it as its own real thing, and the step to the bigger engagement feels like an expansion of value already proven, not a bait-and-switch.

One hack, out of thirty

This is hack 28 in a series I started because I kept noticing the same small, unglamorous adjustments make the biggest difference in how a small team actually operates. Selling the small first step isn't a trick. It's an honest acknowledgment that trust is built in stages, and asking for it all at once is usually asking for more than the moment can hold. Shrink the first ask, let the work speak, and the bigger yes tends to arrive on its own.

Key takeaways

"Let me think about it" is a signal. It usually means the ask outsized the trust in the room, not that the work isn't needed.
Tight budgets move faster on small asks. A bounded, modest expense is easier to approve than a large leap of faith.
Paid beats free. A small paid step filters for real intent; a free consultation filters for nothing.
Let the deliverable make the case. A real audit or plan should surface the reasons for the bigger project on its own.
Price the step, not a discount. Modest and low-risk, but fair for the actual work involved.

Frequently Asked Questions

A good small first step has a clear, standalone deliverable: a plan, an audit, or a pilot the client can actually use, even if they never hire you for anything else. It should be scoped tightly enough to deliver fast and priced modestly enough to feel low-risk, but it should never be free. The moment it's free, it stops signaling seriousness and starts reading as a sample.

A free consultation filters for nothing. Anyone will take a free hour. A small paid step filters for real intent on both sides: the client has to decide the problem is worth a real, if modest, investment, and you have to actually deliver something worth that payment. That mutual seriousness is what a free call can't create.

Price it low enough that a tight budget can approve it without a lengthy sign-off process, but high enough that it respects the actual hours it takes you to do it well. The goal isn't to make it cheap, it's to make it small: a bounded, well-defined piece of work at a fair price for that scope, not a discount on the bigger engagement.

The small step should do the selling for you. If the deliverable is a real audit or plan, it naturally surfaces the gaps, risks, or opportunities that justify the larger project, in the client's own data and language, not in a separate sales pitch. By the time it's delivered, the client is usually the one asking what a fuller engagement would look like.

Dahlia Imanbay, AI Strategist and Fractional CMO

Dahlia Imanbay

AI Strategist, Fractional CMO, and Full-Stack Developer with 16+ years of experience building AI systems for healthcare, SaaS, and mission-driven brands. Writes from production experience, not theory.

Explore the series

Browse all 30 hacks

The full "30 Hacks From Dahlia" series, one small, practical shift at a time.