Revenue relies on clear promises and fair limits. We write T&Cs and SaaS terms that match how you actually sell, so customers sign and support isn’t fixing gaps later.
When to use this
- You’re shipping a SaaS or service and need terms that cover trials, renewals, support and data without scaring early customers.
- A marketplace, reseller or enterprise prospect wants your T&Cs, a DPA, and a sensible SLA before they’ll move.
- You’re moving from one-off projects to subscriptions and need pricing, scope and termination to reflect that shift.
- Liability, uptime, or data issues tripped a deal and you want paper that prevents a repeat.
What’s included
Core terms – scope of service, order form structure, pricing and taxes, start dates, auto-renewal and upgrades/downgrades.
Service levels (where relevant) – targets, maintenance windows, credits that are fair at your stage.
Data & privacy – controller/processor positions, DPA with UK GDPR wording, security commitments you can meet.
IP & licensing – what’s licensed, what’s retained, open-source flags, and customer responsibilities.
Acceptable use – practical boundaries, suspension rules that you can enforce.
Liability & risk – caps and exclusions that reflect real exposure, not wishful thinking.
Implementation pack – editable Word + PDF, order form template, and a short sales-enablement note.
How we deliver
Discovery. We look at how you sell today: plans, trials, support, data flows, and the awkward bits sales keeps meeting.
Scope & fixed fee. You’ll know what we’re drafting and what’s out of scope before we start.
Draft & adjust. First drafts land quickly; we tune for tone and the markets you’re selling into.
Enable. Final docs plus negotiation notes your team can use on the next call.
Pricing (fixed fees; bespoke available)
SaaS Terms + DPA (startup stage) – from £950 (ex VAT)
Standalone Business T&Cs (services/supply) – from £650 (ex VAT)
Add an SLA – from £300 (ex VAT)
Edge cases (complex DPAs, reseller/marketplace programmes, heavy enterprise schedules) are fine—we’ll scope a bespoke bundle against our standard rates (£275) and convert it to a single fixed fee you approve.
Timeline
Discovery and scope this week. First draft typically inside a few working days once inputs arrive. Enterprise addenda may add a loop; we keep momentum and track open points so nothing drifts.
Inputs we’ll need
- Pricing model, plan names, trial rules, and how renewals work.
- Support hours, channels, and any promised response/restore times.
- Data map in simple terms: what you collect, processors used, where it lives.
- Any customer paper you must mirror (procurement asks, infosec minimums).
- Recent red-lines or blockers from sales-what keeps coming up?
FAQs
Can we keep terms short without losing protection?
Yes. Early-stage customers sign clear, focused terms. We keep boilerplate lean, put real obligations where they matter, and save the long form for enterprise if you need it.
Do we need a DPA if we’re a controller and the customer is too?
Usually, yes—at least to set roles, security, sub-processors and international transfers. We’ll map who does what and draft a DPA your infosec answers can support.
Our liability cap-how high should it be?
It depends on price point, risk, and what’s insurable. We’ll set a default cap that fits your model, with sensible carve-outs and an optional higher cap for enterprise buyers.
Understanding Terms of Business
Sales hates paper that sounds like it came from another company. If your terms of business don’t match how you actually sell, someone on your team ends up translating them on every call—what “trial” means, when renewals trigger, who answers at 7.30am when something creaks. We sit with the facts first: the order form you use today, how invoices go out, what support really looks like on a bad week, and the few red lines you won’t cross. Then we write terms and conditions of business that sound like you, not a stranger.
There’s no “standard” that fits every product. A pay-monthly SaaS with self-serve upgrades needs different levers to a fixed-price services engagement. So scope gets a home; changes get a route; refunds and pauses are written down in the same plain English you use with customers. Uptime promises have numbers you can live with. Credits aren’t theatre. If procurement pushes their long form across the table, we mark the bits you can accept and the ones that quietly move too much risk your way.
Liability belongs in daylight. We’ll set a cap that maps to deal size and real exposure, not a wish. Exclusions that buyers expect; nothing buried. IP and licensing spelled out so nobody argues three months after go-live. Data handled in the same breath: if you process customer data, the DPA says who does what, where it sits, who your processors are, and how transfers work. If both sides are controllers, the line is drawn now, not during diligence.
A small example. A client was losing time on auto-renewal spats and vague “service levels”. We rewrote a page and a half: clearer notice windows, measurable support targets, credits that didn’t break margin. The deal that had stalled for two weeks signed the next day. The next one didn’t stall at all.
Good terms of business make closing feel ordinary. That’s the point.
