Counsel, Shaped to the Situation
The shape of the work follows the shape of the problem: what you’re building, how you do business, or what you’re developing.
The engagement takes the shape of the work.
Our services are built around your specific requirement. The formats below are the ones we use most often.
Product Counsel
Counsel that sits with the product, not downstream of it.
The legal question usually arrives inside a build decision. So we start by learning the product: what it does, how it is put together, and where it can fail.
We learn the product first
Observability, autonomy stacks, control systems. None of it is intuitive, and advice from someone who has not followed the explanation arrives generic. We do the reading, and we ask until we can describe it back to you.
- Architecture & data-flow walkthroughs
- Technical diligence support
- Feature & release review
Answered while they are still decisions
Questions raised at design stage have options behind them. The same questions raised at signing have only concessions. Open-source obligations, data flows and third-party dependencies are cheaper to settle before they are load-bearing.
- Open-source licence management
- Data privacy & DPDP by design
- Third-party & integration review
The paper that ships with it
Drafted so the commercial model and the product agree with each other. Where the same questions recur, your team gets a position it can apply without waiting on legal.
- Pilot & enterprise agreements
- Licensing & developer terms
- Negotiation playbooks & fallbacks
Commercial Counsel
Decisions taken with the risk and the liability already priced in.
The contract is the last step. Ahead of it sit the structure of the business, the rules it works inside, and who carries which risk. We take those first.
How the business is put together
Who contracts with whom, on whose paper, and what each side answers for. Those choices are usually made before anyone calls a lawyer, and they set the exposure for everything that follows.
- Commercial model & structuring
- Risk & liability allocation
- Standard positions & contract turnaround
Working inside a regulated perimeter
In financial services the first question is whether an activity needs a licence at all, and who may lawfully carry it on. Banks and institutions then pass their own obligations down to you.
- Fintech & adviser structuring
- Regulatory perimeter advice
- White-label & partner arrangements
Risk that passes all the way through
You buy on one set of terms and sell on another. Where the two do not meet, the difference is yours to carry.
- Reseller, channel & distribution
- Supply, manufacturing & vendor terms
- Back-to-back risk review
Project Counsel
Worked backwards from the date it goes live.
We map the sequence at the outset: counterparties, consents, funding. Then we build the timetable and hold it, so the workstreams converge rather than drift.
The vehicle and the people in it
Most project disputes are not about the asset. They are about who agreed to fund what, and who decides. That gets settled at formation, or it gets settled later and at more cost.
- Joint ventures & SPVs
- Shareholder & governance arrangements
- Project investment & funding
The documents the project runs on
Each document allocates a risk that another one assumes has already been allocated elsewhere. We read them together rather than in turn.
- EPC & construction
- Offtake & power purchase
- O&M and equipment supply
Sequenced to the date
Approvals and conditions precedent arrive in an order that is not negotiable. We hold the checklist, and keep the data room in a state where diligence is a formality.
- Timetable & conditions precedent
- Regulatory approvals & consents
- Data room & closing management
If You're Not Sure
Describe the situation rather than the service. We'll tell you which format fits and whether it should run as a retainer or a defined engagement. Or that none of them does, and who would serve you better.
Start a Conversation