Owner growth · Service economics

Should Your Service Business Set a Minimum Project Size?

The short answer: Set a minimum project size when the fixed cost of qualifying, scoping, onboarding and governing small jobs prevents them from creating buyer value or contribution. Base the floor on delivery economics and capacity, publish useful context, keep an exception or lighter route, and test whether it improves suitable enquiries—not simply whether it rejects more people.

Editorial illustration of project scopes passing through a copper minimum-size threshold into a stable delivery-capacity structure, with smaller requests routed to a lighter service path
Coherent projects cross the operating threshold while smaller needs retain a useful route · Original illustration by ThomPerformance

A small project can consume nearly all the fixed effort of a large one

The prospect still needs a response, fit call, proposal, onboarding, access, governance and invoicing. Yet a narrow project may not solve the real problem or recover that fixed effort. Accessible pricing can become a weak outcome and an unprofitable queue.

The opposite mistake is an unexplained floor chosen for prestige. It may reject a valuable buyer, hide a weak offer or force a customer into more scope than they need. A minimum project size should protect a coherent result and operating capacity—not signal exclusivity.

My verdict is direct: set a minimum only when the business can show why work below it is structurally difficult to deliver well, then give smaller needs an honest next route. The threshold can be a fee, duration, deliverable set or required business outcome. It is not always a public price.

This differs from whether to raise prices, publish prices online or bundle services. This guide asks where the standard engagement should begin.

The Minimum Project Size & Capacity Gate

Use six checks before introducing a floor. If leadership cannot answer them with its own evidence, hold the policy and reconcile recent work first.

Australian Government guidance says pricing should support business goals, cover costs, reflect value and consider capacity. That is useful direction, not a universal fee. A floor is strongest when it protects both sides: enough expertise for delivery and enough scope to solve something useful.

Reconcile contribution instead of guessing from revenue

Start with fixed commercial and setup work. Add direct delivery and governance, then compare contribution with capacity and customer value. SBA break-even guidance separates fixed costs, selling price and variable costs; a project decision also needs buyer fit and opportunity cost.

Illustrative example — not client proof or a benchmark
Project cohortIllustrative patternOwner interpretation
Small custom projects$3,000 average fee; $1,050 fixed pursuit and setup; $1,500 delivery cost$450 remains before allocated overhead, rework and opportunity cost
Standard diagnostic$2,000 average fee; $350 fixed effort; $750 delivery costA defined scope creates a useful smaller route with less coordination
Core projects$9,000 average fee; $1,200 fixed effort; $4,200 delivery cost$3,600 remains before allocated overhead and tax

Every number is synthetic. The example does not recommend a fee, margin or threshold. Replace it with business-owned cohort evidence and use consistent treatment of owner time, salaries, contractors, tools, overhead, tax and rework.

Do not use fee alone. A standardised project may be healthier than a larger bespoke engagement with senior discovery, fragmented approvals and repeated changes. Measure the operating pattern behind the price.

The Enquiry-to-Delivered-Contribution Loop

The gate defines the policy. This six-stage loop tests whether it improves the whole customer and delivery system.

Marketing should attract suitable opportunities while preserving a path for buyers who are too early or too small today. Connect decision pages and conversion tracking to CRM and finance so sources can be reconciled with accepted projects and contribution.

If the minimum is public, state prices and mandatory fees accurately. The ACCC warns against misleading displays and drip pricing. Confirm local rules; clear context builds trust.

Choose the operating model from the evidence

What leadership seesVerdictBest next moveAvoid
Small jobs lose money and fragment deliverySet a clear floorPublish a starting scope and qualify before proposal workNegotiating every enquiry individually
Small needs repeat with low variationStandardiseCreate a fixed-scope package or paid diagnosticDelivering a bespoke project at package economics
Early buyers often expand laterBuild a progression routeDefine the evidence that moves a buyer into the core engagementAssuming every small request has future value
Good-fit buyers reject the thresholdRepair value communicationExplain outcome, dependencies, proof and alternativesUsing exclusivity language to defend weak clarity
Capacity is temporarily underusedUse bounded exceptionsSet an owner, quota, learning goal and end dateResetting the permanent floor through quiet discounts
Core projects create value and contributionScale selectivelyPromote the proven segment and scope within capacityBuying more demand before delivery can absorb it

If low-value customers are already inside the business, use the guide to review unprofitable relationships. If the constraint is scarce specialist time, first decide how to grow when the team is at capacity.

Run a 60-day minimum-project-size test

Days 1–20

Reconcile recent work

Group projects by source, scope, fee, pursuit effort, setup, delivery, rework, contribution, outcome and expansion.

Days 21–40

Design the routes

Set one provisional floor, one coherent smaller option and explicit exception ownership. Update buyer-facing context.

Days 41–60

Observe and decide

Compare suitable enquiries, proposal effort, wins, delivery load and early contribution with the prior cohort.

Keep the floor when suitable opportunity quality and delivered contribution improve without damaging customer value. Package repeated smaller needs. Repair communication when suitable buyers misunderstand the threshold. Remove it when the evidence shows arbitrary rejection rather than operating protection.

Sixty days may reveal enquiry and sales effects before every project finishes. Keep the cohort open through the normal delivery and payment cycle, and do not present early pipeline as realised profit.

ThomPerformance's growth services connect demand, qualification, landing pages, measurement and practical AI to commercial decisions. Review the case studies, evidence standards and operator-led approach.

Frequently asked questions

What is a minimum project size?

It is the smallest engagement a service business normally accepts under its standard delivery model, expressed as scope, duration, fee or outcome. A sound minimum reflects the fixed work required to qualify, scope, onboard, govern and deliver—not a number copied from another firm.

How should a service business calculate its minimum project size?

Add fixed pursuit and setup effort to the delivery and governance required for a coherent outcome. Then test contribution against overhead, scarce capacity and customer value. It is a business-owned decision model, not a universal margin formula.

Should the minimum project fee appear on the website?

Publish a starting fee, range or scope threshold when it helps buyers self-qualify, but explain what is included. If projects vary materially, explain the factors and offer a diagnostic instead of presenting a false fixed price.

Will a minimum project size reduce leads?

It may reduce raw enquiries. Judge the change by suitable opportunities, sales effort, delivery contribution and customer outcomes. If valuable early-stage buyers disappear, add a paid diagnostic, standard package, partner referral or lighter route.

Can the business make exceptions to its minimum?

Yes, under an explicit rule. Strategic learning, a credible expansion path, spare capacity or low complexity may justify one. Record the reason, owner and expected value so exceptions do not become the normal model.

Protect the minimum scope that makes good work possible

A minimum project size is useful when it protects a coherent buyer outcome, defensible contribution and the capacity to serve well. Build it from real delivery evidence, communicate it plainly, preserve a useful smaller route and review the projects that mature. The goal is not fewer customers. It is better-fit work the business can complete profitably and responsibly.

Sources and evidence notes

Evidence boundary: The gate, loop, decision matrix and sample figures are ThomPerformance practitioner tools. They are not legal, accounting or pricing advice, client performance, a margin recommendation or an industry benchmark. Confirm cost allocation, tax, contract and price-display requirements with qualified advisers in the relevant market.

Free operating template

Stop reviewing paid ads with screenshots and green arrows.

Use the same weekly review structure I use to connect spend with qualified leads, opportunities, pipeline and decisions.

  • Commercial scorecard
  • Creative test log
  • Decision ownership
Discuss your project