Eliga Consultancy Services

Eliga Consultancy Services Contact information, map and directions, contact form, opening hours, services, ratings, photos, videos and announcements from Eliga Consultancy Services, Information Technology Company, London.

Fractional Counsel for Tech and SaaS Businesses
Eliga provides embedded in-house legal support to tech startups and SaaS businesses without the cost or rigidity of a full-time hire.

03/10/2026

The phrase “legal can sort it out later” has weakened more contract negotiations than any difficult clause.

By the time the agreement reaches a lawyer, the price may be agreed, the launch date promised and the customer told that a particular feature is included. There is still room to negotiate the wording, but much less room to change the deal behind it.

That is why effective contract negotiation starts before the first redline.

What must the business deliver? Which risks can it control? What would make the deal unprofitable? Where can it offer an alternative without giving away the outcome it needs?

A contract negotiation lawyer should help answer those commercial questions, then turn the answers into terms both sides can use.

If a clause is causing a standstill, look at the promise behind it. That is often where the negotiation can move again.

Read more in the first comment. Book a consultation with Dhruve using the link in the second.

23/09/2026

Most people searching "business contract lawyer" are not looking for a law firm. They are looking for someone to tell them, quickly, whether the contract in front of them is safe to sign.

That is a narrower job than it sounds, and most legal services are not built for it. A full review can take days and cost more than the deal is worth. A quick skim from whoever is free misses the one clause that actually matters.

What that search is really asking for: someone who can look at a specific commercial contract, in the time it deserves, and say plainly what carries risk and what does not.

Book a consultation, link in comments.

16/09/2026

💭 Thought for the day

Every multi-year software discount has a hidden price. You just don't pay it until you try to leave.

The CMA is now investigating Microsoft's business software ecosystem, bundling, interoperability, Copilot, the whole stack you were told was "better together." Evidence gathering runs through September. No finding has been made yet, no new rights exist for customers today.

That's exactly why this matters now, not after a ruling changes anything.

The discount you signed up for locked in the bundle. Nobody priced what it costs to unwind it. Not the migration, not the retraining, not the year you'd spend untangling one vendor's tools from how your business actually runs.

You don't find that number when you sign the renewal. You find it the day you try to walk away, and by then it isn't a negotiation anymore.

Read the full update, link in comments.
Book a consultation, link in comments.

14/09/2026

⚠️ Your SLA is the reason nobody gets fired when your product goes down.

That sounds like the opposite of what it's for. An SLA is supposed to protect you when they fail.

And it does, on paper. 99.9% uptime, service credits, a nice table.

Here's the part nobody reads. Most SLAs cap the entire remedy at a credit worth a fraction of what the outage actually cost you. No credit, no matter how bad the week was, covers lost revenue, lost customers, or the Monday morning you spent explaining it to your board.

The vendor didn't get away with the failure. The SLA got away with defining what the failure was allowed to cost them.

Go and check what your worst outage this year actually entitled you to. Not the percentage. The number.

Read the full update, link in comments.
Book a consultation, link in comments.

01/09/2026

Your SaaS renewal terms are about to get renegotiated.

The CMA just published findings on Microsoft 365 subscription practices and flagged exactly what buyers hate: auto-renewal defaults, opaque switching costs, and renewal terms that make exit materially harder than entry.

The authority's signalling enforcement action is coming, and likely remedies include opt-in renewals instead of opt-out, transparent exit cost schedules, and portable data in standard formats.

If you're on multi-year SaaS agreements, procurement teams are already renegotiating ahead of CMA action. If you're a SaaS vendor, assume every customer is going to push back on lock-in clauses. Contract renegotiation timelines have collapsed to 60-90 days.

This isn't a horizon item anymore. It's happening now.

Read the full update: link in comments.
Book a consultation: link in comments.

10/08/2026

The same contract. Three businesses. Three different answers.

A twelve person SaaS company, three weeks from closing a raise. The two clauses that matter are change of control and the IP position, because in ninety days a buyer's diligence will price exactly those, and a clause that lets this customer walk on acquisition is worth more than the contract itself.

An agency delivering the same scope through subcontractors. Completely different two. The flow down and the indemnity, because their real exposure sits with people they do not employ and cannot supervise on the day it goes wrong.

A company whose customer is regulated. Different again. Audit rights and the breach notification clock, because their customer's obligations land on them, and the clock they have agreed to downstream is shorter than the one they can actually meet upstream.

Same paper. Same clauses on the page. The risk sits somewhere different in each business, and no amount of reading the document tells you where.

That is the distinction we keep coming back to. A review reads the contract. Counsel reads the business, then reads the contract.

If the person advising you cannot name your funding timeline, your delivery model and who your customer answers to, they are not choosing your two clauses. They are choosing the average ones.

Book a consultation link in comments.

A Data Processing Agreement is easy to treat as the document you sign because someone in procurement asked for it.But a ...
09/08/2026

A Data Processing Agreement is easy to treat as the document you sign because someone in procurement asked for it.

But a DPA is really answering a much more important question:
WHO IS RESPONSIBLE FOR WHAT WHEN PERSONAL DATA MOVES BETWEEN TWO BUSINESSES?
And that opens up some very practical questions.
→ Who is actually the Controller and who is the Processor?
→ What data are we talking about?
→ What is the Processor allowed to do with it?
→ Who else can access it?
→ Where can the data go?
→ What security has actually been promised?
→ How quickly does the other party need to tell you about a breach?
→ And when the contract ends, where does the data go?

If your DPA answers those questions with phrases like "customer data", "industry standard security" or "as required", it may be worth looking again.

We have put the anatomy of a DPA into one practical Q&A covering 14 questions worth answering before you sign.

Read the full article link in comments.
Book a consultation link in comments.

The Anatomy of a Data Processing AgreementParts 5 & 6: the final stretchSub-processing & Transfers: know who else touche...
07/08/2026

The Anatomy of a Data Processing Agreement
Parts 5 & 6: the final stretch

Sub-processing & Transfers: know who else touches the data, and where it goes. A Sub-processor added quietly overseas can breach the agreement even if the work is fine, so get transfer safeguards in writing before data leaves the country.

Breach, Audit & Termination: the section everyone skips, until they need it. "Reasonable efforts to notify" is not a deadline. Insist on a specific window for breach notification, real audit rights, and a clear data return/deletion obligation at termination.

That's the full series: 6 parts, one contract, no more guessing what's actually in your DPA.

Book a consultation link in comments

The Anatomy of a Data Processing Agreement : Part 4"Industry standard security" says nothing. A DPA should name actual m...
07/08/2026

The Anatomy of a Data Processing Agreement : Part 4

"Industry standard security" says nothing. A DPA should name actual measures: encryption, access control, staff training, backups, monitoring, incident response matched to the risk level of the data, and reviewable.

✔ Technical measures named
✔ Organisational measures named
✔ Standard matches the risk
✔ Auditable

Book a consultation link in comments.

07/08/2026

The Anatomy of a Data Processing Agreement

Part 3 : Processing Instructions
Question: does your DPA say exactly what can be done with the data, or just imply it?

A Processor should only ever act on the Controller's documented instructions — not on assumption, not on "whatever makes sense."

A good DPA should clearly define:
✔ The purpose of processing
✔ The scope of what's covered
✔ The duration it applies for
✔ What happens if an instruction falls outside all of that

Vague scope today becomes a dispute later.

Address

London

Opening Hours

Monday 9am - 5pm
Tuesday 9am - 5pm
Wednesday 9am - 5pm
Thursday 9am - 5pm
Friday 9am - 5pm

Website

, ,

Alerts

Be the first to know and let us send you an email when Eliga Consultancy Services posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Shortcuts

Share

Category