Should You Charge Per Project or Per Month?
Back to Library
Pricing & Monetisation 11 min read Jan 2026

Should You Charge Per Project or Per Month?

Matt Haycox

Matt Haycox

Entrepreneur, Investor, Mentor

Share 11 min

Picking the wrong pricing model doesnโ€™t just hurt revenue, it breaks delivery, cashflow and your headspace. Get it right and youโ€™ll sell faster, deliver cleaner and sleep better at month end. If you want the wider context on building a proper pricing system, read Pricing Strategy for Your Businesses: The Complete Playbook.

In this article, weโ€™re going to discuss how to:

  • Choose the right model based on how work actually gets delivered
  • Stress-test cashflow, margin and risk before you commit
  • Validate project vs monthly pricing in 7 to 14 days without a big rebrand

Project Vs Monthly Pricing: A Practical Definition You Can Use

Project pricing is when the client buys a defined outcome with clear boundaries: scope, timeline, deliverables and acceptance. Monthly pricing is when the client buys ongoing capacity, access or continuous improvement, usually with a rolling renewal and a cadence of outputs.

The practical difference is this: project pricing sells โ€˜doneโ€™, monthly pricing sells โ€˜staying doneโ€™.

A quick sense-check before you go any further:

  • Projects suit work that can be specified up front, signed off, then closed.
  • Monthly suits work that needs iteration, monitoring or ongoing decision-making.
  • If youโ€™re constantly revisiting priorities, youโ€™re already in monthly land, you just might not be charging like it.
  • If the client needs a predictable budget more than they need an exact deliverable list, monthly will often convert better.

Start With Delivery Reality, Not What Sounds Good On A Sales Call

Founders often choose pricing based on what theyโ€™ve seen others do, or what feels easier to sell. Start instead with the delivery mechanics, because thatโ€™s where profit and sanity live.

Three Questions That Decide 80% Of The Answer

Ask these and answer them honestly:

  • Can you define โ€˜doneโ€™ in writing? If not, monthly is safer.
  • Does the work depend on external approvals? If yes, projects get delayed and margins leak.
  • Will priorities change mid-flight? If yes, projects become a fight, monthly becomes a plan.

Hereโ€™s the founder truth: if your team is having weekly prioritisation conversations, youโ€™re providing a service that behaves like a subscription, even if you invoice like a builder.

What Data To Gather In A Few Hours (Internal First, Then Public)

You donโ€™t need a finance team to make a smart decision, you need a small set of numbers you trust. Block 2 hours, pull this from your own ops, then sanity-check against the market.

Internal Signals To Pull Today

Use your last 5 to 10 engagements, even if theyโ€™re messy:

  • Actual delivery hours vs estimated hours: average and worst case.
  • Cycle time: weeks from kickoff to sign-off, plus how long it sat waiting on the client.
  • Change volume: number of scope changes, โ€˜quick tweaksโ€™, additional stakeholders added.
  • Gross margin by engagement: revenue minus delivery cost, as a %.
  • Cash timing: when you got paid vs when you paid staff or freelancers.

Completion check: you should be able to say, โ€˜When we sell X, it usually takes Y hours over Z weeks and we get paid like thisโ€™. If you canโ€™t, youโ€™re guessing and your pricing will show it.

Public Signals To Check In 60 Minutes

Youโ€™re not copying competitors, youโ€™re checking the โ€˜range of believableโ€™:

  • How offers are packaged: project โ€˜packagesโ€™ vs monthly retainers, whatโ€™s included, whatโ€™s excluded.
  • Price bands: look at 5 comparable firms and note minimum, typical and premium.
  • Risk transfer language: who carries uncertainty, them or the client.

If everyone in your space sells monthly and youโ€™re selling one-off projects, you may still win, but youโ€™ll need a sharper reason and a cleaner scope boundary.

Cashflow And Risk: The Real Reason Most Founders Switch To Monthly

Cashflow is oxygen. Project work can be profitable but still starve you, because payment doesnโ€™t match delivery effort. Monthly pricing smooths revenue, but it can hide unprofitable delivery if you donโ€™t manage utilisation.

A Simple Cashflow Stress Test

Run this quick calc on one typical client:

  • Project model: ยฃ12k fee, 60% upfront, 40% on completion, delivery takes 10 weeks.
  • Monthly model: ยฃ4k per month, 3-month minimum, same delivery effort spread over 10 weeks.

Now overlay your cost. Say delivery cost is ยฃ3k per month in team time and contractors.

  • Project: you might receive ยฃ7.2k in week 1, then nothing until week 10, while costs hit every month.
  • Monthly: you receive ยฃ4k at the start of each month, which tracks closer to costs.

On paper both can make money, but one keeps you liquid. Thatโ€™s why founders doing project vs monthly pricing often end up preferring monthly once theyโ€™ve been burned by one late sign-off.

Risk Allocation In One Sentence

Projects push delivery risk onto you, monthly pushes prioritisation responsibility onto the client. Choose the risk you can manage.

A One-Sentence Offer Template You Can Fill In Today

If you canโ€™t explain your pricing model in one sentence, you donโ€™t have a pricing model, you have a hope.

Template: โ€˜We help [specific customer] achieve [measurable outcome] in [timeframe], using [method], for ยฃ[price] as a [project / monthly partnership], with [one clear boundary].โ€™

That final boundary matters. For projects itโ€™s usually โ€˜scope and sign-offโ€™, for monthly itโ€™s usually โ€˜capacity and turnaround timesโ€™.

Unit Economics That Hold Up At Small Scale (10 Clients, Not 1,000)

Most pricing advice assumes scale. Founders need unit economics that work when youโ€™ve got 2 to 5 people delivering and every bad client is a big percentage of your week.

For Project Pricing, Protect The Overrun

Projects go wrong in the same place: underestimated labour and unpriced uncertainty. Your unit economics should include an explicit buffer, not a โ€˜weโ€™ll work harderโ€™ assumption.

Use this rule of thumb as a starting point:

  • Base delivery cost: your realistic hours x fully loaded hourly cost.
  • Risk buffer: add 15% to 30% for revisions, client delays and internal context switching.
  • Target gross margin: aim for 50%+ if itโ€™s bespoke and people-heavy, 60%+ if itโ€™s productised.

Completion check: if the project runs 20% long, you should still be profitable. If not, your price is fiction.

For Monthly Pricing, Define Capacity Like A Product

Retainers fail when โ€˜ongoingโ€™ becomes โ€˜unlimitedโ€™. Sell a unit the client can understand and your team can deliver.

Examples of monthly units that work:

  • Time unit: โ€˜Up to 12 hours per month, 48-hour response, unused hours donโ€™t roll overโ€™.
  • Output unit: โ€˜4 landing pages per month, includes copy and build, 2 revision roundsโ€™.
  • Outcome unit: โ€˜Weekly paid media optimisation, monthly reporting, target CPA band agreed in advanceโ€™.

The goal is the same as project pricing: predictable delivery, predictable margin.

A Validation Path You Can Run In 7 To 14 Days

You donโ€™t need to pick one model forever. You need a fast test that tells you which one sells easier and delivers cleaner for your offer.

Test 1: Quote Both Options To The Same Lead

For the next 5 sales conversations, present two priced routes:

  • Project: fixed scope, fixed timeline, fixed fee.
  • Monthly: 3-month minimum, defined capacity, clear priorities process.

Ask one question after presenting: โ€˜Which one feels lower risk for you?โ€™ Track the answer. That tells you what the buyer actually values: certainty of output, or certainty of ongoing support.

Test 2: A โ€˜Bridge Retainerโ€™ After A Project

If you already sell projects, add a lightweight month-to-month follow-on for 60 days:

  • Positioning: โ€˜Stabilisation and optimisation after deliveryโ€™.
  • Price: 20% to 40% of the project fee per month, depending on involvement.
  • Guardrail: clear list of whatโ€™s included, plus what triggers a new project.

This is a cheap test that often turns one-off work into a revenue floor.

Test 3: Pre-Sell A Monthly Slot With A Start Date

Monthly is easier to sell when itโ€™s scarce. Offer โ€˜2 client slots starting on 1 Februaryโ€™, then close one before building any new packaging. Youโ€™re testing demand, not your Canva skills.

Operational Guardrails That Protect Margin And Time

Your pricing model is only half the system. The rest is how you stop delivery from eating your week. These guardrails are what make either model sustainable.

Guardrails For Projects

Keep it tight and written:

  • Definition of done: acceptance criteria and who signs off.
  • Change control: what counts as a change, how itโ€™s priced, how quickly you respond.
  • Client responsibilities: access, approvals, content, feedback timelines.
  • Payment triggers: milestone-based, not โ€˜when everyone feels happyโ€™.

If youโ€™re doing project vs monthly pricing and you keep getting dragged into โ€˜just one moreโ€™ requests, your change control isnโ€™t strong enough, or you should be selling monthly.

Guardrails For Monthly

Retainers need a delivery operating system:

  • Weekly prioritisation: 20-minute call or async list, one client owner on their side.
  • Work intake: a single channel, no WhatsApp chaos.
  • Definition of โ€˜urgentโ€™: what qualifies and what it costs.
  • Quarterly reset: revisit goals, scope fit and pricing.

Completion check: if the client canโ€™t tell you what they want to achieve next month, you will drift into low-value busywork. Thatโ€™s how retainers become resentful.

Mini Cases: Three Realistic Scenarios And What Iโ€™d Do

These arenโ€™t perfect, theyโ€™re the sort of situations founders face on a Tuesday.

Case 1: Shopify CRO For A UK DTC Brand

They want a conversion lift, but they canโ€™t commit to a fixed list of tests because inventory and promotions change weekly. Iโ€™d sell monthly: a defined number of experiments and a fortnightly decision call. Project pricing only works here if you limit it to a single funnel audit with a fixed output.

Case 2: Finance Ops Clean-Up For A 12-Person Agency

The โ€˜messโ€™ is finite: reconcile accounts, fix invoicing, implement a reporting cadence. Iโ€™d sell a project with milestone payments and a tight definition of done. Then offer a small monthly โ€˜keep it tidyโ€™ retainer for 2 hours per month.

Case 3: B2B LinkedIn Content For A Founder-Led Consultancy

Content is ongoing and results compound, but the founderโ€™s time is the bottleneck. Monthly works if you set a clear unit: 8 posts, 2 long-form pieces, one monthly planning call, with drafts due 5 days before publish. A project will end up being an endless edit loop unless youโ€™re brutally strict.

Risks, Hedges And When To Switch Models

Both models have traps. The trick is spotting the early warning signs and having a hedge ready.

Common Project Risks

Risk: Scope creep disguised as โ€˜collaborationโ€™.
Hedge: Price change requests as a menu: โ€˜Option A: ยฃ750 for the add-on, Option B: move it into Phase 2โ€™.

Risk: Client delays blow your timeline and block new work.
Hedge: Add a โ€˜pause clauseโ€™: if feedback is late by 10 business days, timeline resets and you can re-slot the work.

Risk: You win deals on low price then try to make it up in volume.
Hedge: A minimum fee based on your break-even hours, not the clientโ€™s budget.

Common Monthly Risks

Risk: โ€˜Unlimitedโ€™ expectations and a slow creep in time spent.
Hedge: Publish your service standard: response times, meeting cadence and what counts as a new project.

Risk: Retainer becomes a polite churn because results are vague.
Hedge: Tie work to leading indicators: response rate, qualified calls booked, deployment frequency, not just โ€˜activityโ€™.

Risk: You discount to win the retainer then canโ€™t raise prices.
Hedge: Build an annual price review into the agreement, linked to scope and outcomes.

When Itโ€™s Time To Switch

Switch from projects to monthly when 2 things are true: clients keep asking for โ€˜one more thingโ€™ after delivery, and you can see repeatable ongoing value. Switch from monthly to projects when delivery has become a predictable, bounded system and clients just want it implemented once.

Do And Donโ€™t Checklist For Choosing The Model

  • Do price the risk, not just the work, because uncertainty is what destroys margin.
  • Do make cash timing part of the decision, not an afterthought.
  • Do write down the boundary in plain English and put it in the proposal.
  • Donโ€™t sell monthly without a capacity unit, โ€˜ongoingโ€™ is not a unit.
  • Donโ€™t sell projects when success depends on weekly prioritisation and fast feedback.
  • Donโ€™t pick a model based on what your competitor does, pick it based on how your work behaves.

Download The Offer Packaging Blueprint And Decide Faster

If you want a quick way to turn your service into a clean project package, a clean monthly retainer, or both, download the Offer Packaging Blueprint: Turn One Service Into a High-Value Product and use it to map your deliverables, boundaries and pricing units in under an hour.

Key Takeaways

  • Choose project or monthly based on delivery reality: if you canโ€™t define โ€˜doneโ€™, you need a monthly unit and a prioritisation cadence.
  • Validate with small tests in 7 to 14 days and make sure your unit economics still work if delivery runs 20% long.
  • Protect margin with guardrails: change control for projects, capacity and intake rules for monthly, plus clear cash timing either way.

FAQ For Project Vs Monthly Pricing

Which is more profitable, project or monthly pricing?

Either can be profitable, but monthly is usually more predictable while projects can deliver higher margin when scope is tight. The winner is the model where you can control risk and avoid unpaid extra work.

How do I price a monthly retainer without selling โ€˜unlimitedโ€™?

Sell a clear unit: hours, outputs, or a defined operating cadence with limits and response times. Put the boundary in the proposal so expectations are set before the first invoice.

What if a client insists on a project price but the work is ongoing?

Offer a project โ€˜Phase 1โ€™ that creates the plan or implements the first slice, then give a priced monthly option for iteration. Youโ€™re meeting their desire for certainty while protecting yourself from endless change.

Should I offer both options on my website?

Yes, if you can explain the difference cleanly and the buyer can self-select based on risk and preferences. Keep it simple: one project package and one monthly package beats five confusing variants.

What contract terms matter most for project pricing?

Acceptance criteria, change control, client responsibilities and payment triggers. If those arenโ€™t explicit, youโ€™re effectively doing a retainer without getting retainer cashflow.

How long should a minimum monthly term be?

For most operator-led services, 3 months is a sensible minimum to get traction and avoid churn after onboarding. If results take longer to show, use 6 months but keep a clear quarterly review point.

When should I raise prices on a monthly client?

When scope has grown, utilisation is consistently high, or outcomes are strong and provable. Give notice, tie the increase to whatโ€™s changing and offer a downgrade path so it feels fair.

Can I move existing project clients onto monthly pricing?

Yes, but do it around a natural milestone: after delivery, after a quarter, or when the next set of priorities appears. Position it as โ€˜continuity and optimisationโ€™ with a clear unit, not as a price hike for the same work.

Want More Like This?

JOIN GROWTH HQ

Get direct mentorship from Matt, access recorded courses and training, and join a network of operators who are actually building — not just talking about it.

Learn More