Is there a minimum engagement size?

The floor exists because of overhead rather than greed. Any engagement involves understanding the situation, agreeing what will happen, doing the work, and handing it over. That structure costs roughly the same whether the work itself takes two hours or twenty, which means a very small project spends most of its budget on the process around it rather than on the outcome.

For genuinely small things, the better answer is usually advice. Twenty minutes explaining how to do something, or which tool to use, or why the thing you were about to buy will not help, frequently resolves what somebody arrived intending to pay for. That conversation is worth having and it is not an engagement.

Consider bundling small items rather than pursuing them individually, which is the arrangement that makes them viable. Five small tasks addressed together share the overhead and become a sensible project, where each one alone would not. If you have a list of minor things, that list is the engagement rather than the first item on it.

Be wary of the small project that is actually a large question wearing a small request. A business asking for a page to be added frequently has an underlying issue about what the site says and who it is for, and doing the small thing well means addressing the large thing first. Recognising that early is what prevents a defined piece of work from expanding.

There is a version of small work that is straightforwardly worth doing, which is anything with a clear boundary and an obvious outcome. A specific technical fix, a defined page, a tracking setup, or a review of something you already have. Those scope cleanly, deliver quickly, and are a reasonable way for both parties to test whether the working relationship functions.

Starting small is frequently the sensible route for a larger relationship, and it is worth saying so rather than treating it as a compromise. A defined piece of work with a clear outcome tells both parties whether the arrangement works, at a cost that does not matter if the answer is no.

Ask directly rather than assuming something is too small to raise. The cost of the question is a message, and the answer is either that it is worth doing, that it should be bundled with other things, or that you can do it yourself in an afternoon. All three are useful.

Then be honest with yourself about whether the small thing is the actual problem. Businesses frequently pursue a minor fix because it is easier to define than the larger issue, and the larger issue is what is actually costing them.

Consider whether several small things share a cause, since a list of minor annoyances frequently points at one underlying problem. Fixing that resolves the list, where addressing each item individually treats symptoms and the list regenerates.

Group small work into a defined session rather than treating each item as a request, since an afternoon addressing eight things is efficient in a way that eight separate conversations across two months is not. That format suits ongoing minor needs considerably better than a series of tiny projects.

Be direct about the budget you have rather than asking what something costs in the abstract, since that lets the scope be shaped to fit rather than quoted and then negotiated. Most work can be reduced sensibly if the constraint is known at the start.