Businesses that sell monthly services, software, maintenance or agency work often learn a client is leaving from a short email a few weeks before expiry. That is too late. Most clients decide months earlier, from an accumulated sense of what they have been getting from you.
This guide sets out a system an SME can run: a renewal calendar with named account owners, what to review with the client, a quarterly meeting with a one-page report, early-warning signals, a client health score, how to handle a price increase, and the contract terms to check before renewal.
The core answer
Whether a client renews is decided by what happens during the term, not by the renewal quote sent before expiry. A system that works has four parts: a renewal calendar counting back 90/60/30 days from the contract's non-renewal notice date (not the expiry date) with a clear account owner; a performance review with the client every quarter on a one-page report in the client's own terms; watching for early-warning signals; and delivery records kept every month.
On the legal side, open the contract and check the auto-renewal clause and notice window, price adjustment, service credits, termination for convenience, written scope changes and return of data on exit. If the contract is a standard form you drafted, a term that is very one-sided may be enforceable only as far as it is fair (Unfair Contract Terms Act B.E. 2540, section 4), so contract wording cannot replace the client relationship.
1. The 90/60/30 renewal calendar and who owns each account
Start with one contract register. For every client record the start date, the expiry date, the last day either side can give notice of non-renewal or termination, the monthly fee, the account owner and the client's decision-maker. Then count back from the notice date. If the contract renews itself or requires 60 days' notice, starting the conversation 30 days before expiry is already past the point where the client can decide.
| Time before the notice date | What must be done | Owner |
|---|---|---|
| 120 days | Health check, review warning signals, list contract terms to change at renewal | Account owner |
| 90 days | Hold the performance review (QBR), ask about next year's needs and who approves the budget | Account owner + senior manager |
| 60 days | Send the renewal proposal stating scope, SLA, price and changes in writing | Account owner |
| 30 days | Chase approval, answer procurement questions, prepare a response if the client asks for a discount | Senior manager |
| Before the notice date | Get written confirmation of renew or not, and the new terms | Account owner |
The account owner should be the one person the client knows who has authority to offer terms, not the accounts team that only appears when the invoice goes out. Name a backup who sees the same account data, so the relationship survives leave, resignation or a move.
2. What to review with the client before renewal
Review five things, each backed by evidence the client can check.
| Topic | Question | Evidence |
|---|---|---|
| Agreed scope vs delivered | Was everything in the contract and statement of work (SOW) done? Was extra work done that was never written down? | Contract, SOW, change notes, acceptance notes |
| SLA and KPI results | Response time, fix time, availability, monthly performance against target | Monthly reports, tickets, system logs |
| Incidents and fixes | What happened, when it was fixed, how it will not recur, any service credit | Incident reports, root-cause notes |
| Value delivered, in the client's terms | What does the client think it got: sales, time saved, cost cut, risk avoided | The client's own numbers, not our internal ones |
| Upcoming needs | What is changing in the client's business, more, less or different service | Interviews with users and decision-makers |
The fourth item is where people slip. A provider reports "99.9% availability" while the client cares whether the sales team now issues quotes faster. Translate results into the client's language, and if you have no client-side number, ask the client what they measure.
3. The quarterly business review (QBR) and a one-page report
A QBR is not a one-sided results presentation. The aim is for the client's decision-maker to see the value, raise problems, and know what next year looks like.
Sample agenda (45 to 60 minutes)
- Review the goals agreed last time (5 min)
- Quarter results against SLA/KPI and agreed scope (10 min)
- Significant incidents, causes and fixes (10 min)
- Value the client received, in the client's own measures (10 min)
- What the client wants changed, satisfaction, risks the client sees (10 min)
- Next quarter's plan, extra work, renewal timeline (10 min)
- Summary of actions, owners and dates, sent in writing within 2 working days
One-page report (template)
| Heading | Content |
|---|---|
| Client / period / author | Name, quarter, account owner |
| One-sentence summary | The quarter in one line |
| Agreed scope vs delivered | Done / extra / outstanding |
| SLA/KPI | Actual vs target with status colour |
| Incidents and fixes | Item, time, cause, prevention |
| Value to the client | The client's own measures |
| Decisions needed | Approve extra work, change scope |
| Next quarter plan | Main work and due dates |
| Contract dates | Expiry date and last day for non-renewal notice |
Send the report as a file you can keep, and ask the client's representative to reply by email, at least to confirm receipt. These reports become the delivery evidence in section 7.
4. Early-warning signals that a client may not renew
| Signal | Possible meaning | What to do |
|---|---|---|
| Usage falling steadily | Client sees little benefit or is using something else | Call the main user, find the cause, do not wait for the next report |
| The client's champion leaves or changes department | Nobody defends our budget | Introduce yourself to the replacement within two weeks |
| Payments unusually late | Budget questioned, or cash-flow trouble | Check before proposing renewal and review the late-payment terms |
| Ticket spike or a change in tone | Accumulated dissatisfaction | Hold a problem-solving meeting, separate from any sales pitch |
| Procurement asks for more quotes or comparisons | Looking at other providers | Ask directly which criteria we have not met |
| Request to cut scope or move to per-project work | Budget cut | Offer a smaller package that keeps the contract alive |
| Emails unanswered, meetings repeatedly cancelled | Our work has lost priority | Approach through an executive at the same level |
Do not draw conclusions from one signal, but when two or more appear in the same cycle, a senior manager should review the account immediately.
5. A client health score
Score each client monthly with no more than six indicators whose data you can actually get. The table below is a hypothetical example; adjust the weights to your business.
| Indicator | Weight | 2 points | 1 point | 0 points |
|---|---|---|---|---|
| Usage vs 3 months ago | 25% | Up or flat | Down 1 to 20% | Down more than 20% |
| SLA/KPI results | 25% | Met every month | Missed some months | Missed repeatedly |
| Tickets and satisfaction | 20% | Normal | Slightly up | Spiking or complaints |
| Payment | 15% | On time | Late up to 15 days | Over 15 days late or unpaid |
| Relationship with decision-maker | 15% | Meet at least quarterly | In contact, no meeting | No direct channel |
Total score = sum of (points ÷ 2 × weight), giving 0 to 100. Hypothetical example, client A: usage flat (2), SLA missed some months (1), tickets normal (2), payment 10 days late (1), meets quarterly (2). Score = 25 + 12.5 + 20 + 7.5 + 15 = 80.
| Score | Status | Action |
|---|---|---|
| 75 and above | Green | Renewal should be easy; propose extra services |
| 50 to 74 | Yellow | Senior manager reviews; set a recovery plan within 30 days |
| Below 50 | Red | Problem-solving meeting at once; prepare special terms or a plan for losing the client |
These thresholds are for illustration, not a standard. Compare them with your own clients who did and did not renew, and recalibrate once a year.
6. Raising the price at renewal without losing the client
- Check the contract first. A contract in force does not let one side raise the price unilaterally unless a clause allows it. A lawful increase therefore happens at renewal, through a proposal the client accepts, or through a price-adjustment clause already written in. See the guide on raw-material cost increases and price adjustment.
- Give written notice before the non-renewal window so the client can assess and has a real choice, not in the final week.
- Tie it to value. Present it with past results and what is added next year, not only your cost reasons.
- Offer options, such as the current package at the new price, a reduced scope at the current price, or a multi-year contract that locks the price.
- Write the adjustment formula into the new contract, for example an agreed index or an annual cap, so you do not renegotiate from scratch every cycle.
- Watch standard-form terms. A clause letting the provider raise prices at its discretion with no way out for the client may be reviewed under the Unfair Contract Terms Act B.E. 2540, section 4. See SaaS and subscription contracts.
7. The contract angle: what to open before renewal day
| Topic | What to check | Watch out for |
|---|---|---|
| Auto-renewal and notice window | Does it renew itself, how many days' notice, by what method, to whom | Late notice may bind you for another term; keep proof of sending |
| Price-adjustment clause | When it applies, the cap, notice required | Without one, no mid-term change |
| SLA and service credits | Thresholds, measurement, credit cap, sole remedy or not | A credit that is too high may be reduced under section 383; see MSA and SLA contracts |
| Termination for convenience | Which side may end it, how much notice, any compensation | Termination under a clause is by declaring intention to the other side (section 386); follow the wording exactly |
| Scope changes in writing | Must extra work be covered by a signed amendment or an agreed email confirmation? | Extra work done orally is hard to charge for or is disputed as within the original scope |
| Data return and transition on exit | Format, number of days, help with migration, when data is deleted | Digital-service clients often ask about this; see software development contracts |
| Evidence of delivery | Reports, acceptance notes, confirmation emails, meeting notes | File by client and month |
Unpaid fees. If a client is behind on payment near renewal, handle it separately from the renewal. See unpaid invoices, and if a client will not sign acceptance so you cannot invoice, see customer not signing acceptance.
Remember that no general statute sets a renewal notice period. What fixes the rights is the contract wording, so before every countdown open the latest contract with all amendments rather than relying on the team's memory.
8. Common internal mistakes
- Contacting the client only at invoice time. The client hears from you only about money, never about results.
- Not recording scope changes in writing. The team takes on extra work orally, and at renewal the client assumes it was included in the old price.
- Starting the renewal talk after the notice date, or not knowing what date the contract sets.
- Reporting only internal numbers, such as tickets closed, without saying what the client got.
- Relying on one person. The relationship sits with a single account owner.
- Raising the price in the final week with no reason or options.
- Not keeping evidence. Reports, acceptance notes and confirmation emails are scattered across personal inboxes.
- Hiding incidents. Clients usually know already; reporting it yourself with a fix plan earns more trust.
9. Checklist for a pre-renewal review system
- Build a client contract register with the non-renewal notice date for each client
- Set reminders at 120/90/60/30 days, counting back from the notice date
- Name an account owner and a backup for every client
- Set a quarterly review cycle and send a written summary after each meeting
- Use the one-page report template, written in the client's terms
- Score client health monthly and define who acts when a client is yellow or red
- Check the contract for auto-renewal, price adjustment, service credits, termination, scope changes and data return
- Require scope changes in writing before extra work starts
- Keep monthly delivery evidence by client
- Send the renewal proposal before the notice date, with reasons for any price change
Further reading
- MSA and SLA for monthly service contracts — service levels, credits and termination
- SaaS pricing models and subscription contracts — renewing and repricing subscriptions
- Raw-material cost increases and price adjustment — price-adjustment clauses that work
- Software development contracts and source code — delivery and handing work back
- Unpaid invoices from business customers — when a client pays late
- Monthly management meeting agenda and reports — bring client health into the internal agenda
Clients renew because they see the value delivered all year, so count back from the notice date, review results every quarter with evidence, and let the contract and delivery records back up what was agreed.
We help review and draft monthly service contracts, auto-renewal clauses, price-adjustment terms, SLAs, written scope amendments and data-return clauses, and offer retainer support for businesses with many client contracts. For an initial consultation, call +66 92 254 2045 or send us the details. See also contracts and documents and legal retainer.
This guide is published by Suwanvara Law Firm — a Khon Kaen law firm established in 1986. General information only, not legal advice on a specific matter.
