Take the small project when it is designed as a first phase with its own clear value, and refuse it when it is your full engagement at a discount. A small piece that stands on its own gets you in the door and prices the work straight. A shrunken version of everything teaches a client what your work costs.
Design a small offer that delivers real value on its own, rather than discounting the engagement you wanted.
A first yes makes the next yes substantially more likely, but only if the first piece was worth buying.
Write down one contained piece of your work that would be useful on its own.
You are the expert in helping your clients buy.
Leah Neaderthal, Smart Gets Paid
A small first project works when it produces something valuable on its own and the client would be glad they bought it even if nothing followed. I teach this as an ETSY offer, short for Easy To Say Yes, and it exists to move a client from considering you to working with you without waiting for a full engagement to clear.
The situations where it earns its place:
What makes it work is that it is clear on value. People do not want to buy a first phase, because a first phase sounds like a down payment on an unknown. They will happily buy an assessment that tells them what to do next, which can be exactly the same work described straight.
A small project does tend to turn into bigger work, and the effect is well documented outside consulting. Freedman and Fraser tested it directly: 52.8% of people who had agreed to a small request later agreed to a much larger one, compared with 22.2% of people asked only the large request. Agreeing once changes what the next answer is likely to be.
Inside an organization, three things compound that:
The condition attached to all of this is that the small piece has to go well and has to be visibly worth its price. A cheap engagement delivered thinly proves the opposite of what you wanted to prove.
A small project is a bad idea when it is the engagement you wanted with the price cut and the scope untouched. That version teaches a client what your work costs, and the number you accept first is the number you negotiate from forever.
| Good version | Bad version |
|---|---|
| A contained piece with its own outcome | Your full engagement, discounted |
| Priced on the value it delivers | Priced to be cheap enough to approve |
| A clear next step defined before you start | A hope that more work appears |
| Scoped tightly, delivered fully | Scoped loosely, expands for free |
Two other situations where the answer is no. When the client is unconvinced the problem is real, a smaller number does not fix a belief, and the belief is the thing to work on first. And when the small project would consume the capacity you need for work that pays properly, getting in the door costs more than it returns.
Price a small first project on the value of what it delivers, exactly as you would price anything else, and let it be small because the scope is small. The temptation is to price it low enough to be waved through, and that is the move that costs you later.
What holds:
Consulting contracts in this market run anywhere from $2,500 to $250,000, so a small first piece is a normal thing to sell rather than a compromise. The question is whether it was designed or improvised.
I like small first projects, and I want to be precise about which kind.
The kind I like is an offer you built on purpose: a contained piece of work, clear on value, that a client can say yes to without a committee. It gets you inside the organization, where you learn more in three weeks than six sales calls would have told you, and it gives your contact something to point at when she argues for the bigger engagement.
The kind that hurts you is the one that happens by accident, at the end of a long process, when somebody says the number is too high and you hear yourself offering to do a smaller version for less. That is not strategy. That is negotiating against yourself, and the client now knows your price moves under pressure.
The difference is whether you designed it or reached for it.
So before you agree to anything smaller, ask yourself one question: would I be glad to have done this piece of work if nothing else ever came of it? If yes, take it. If the only reason it makes sense is what might follow, you are not selling a first phase, you are buying a lottery ticket with your capacity.
A discount request is a scope conversation in disguise, so answer it that way: ask what would need to come out for the number to work. That keeps price and value connected and gives the client a real choice. Cutting the number while keeping the scope tells them the first figure was negotiable, which changes every conversation after this one.
Naming the likely next step in the proposal helps, and pricing it fully usually does not. A sentence describing what typically follows sets the expectation without asking anybody to approve two things at once. Approvers get nervous when a small ask arrives with a large one attached, and the small ask is the one you want signed.
Too small is any piece that cannot produce an outcome worth describing. If you cannot name what the client will have at the end that they do not have now, the scope has been cut past the point of value. A tiny engagement that delivers something real is fine; a tiny engagement that delivers a fragment damages the relationship you were trying to start.
Plenty of small projects end where they started, which is why the piece has to be worth doing on its own terms. Treat every one as a complete engagement, deliver it fully, and ask about next steps while you still have their attention. A well-delivered small project that ends is a reference and a relationship, which is not nothing.