About
Ambition is not the same thing as being able to describe the product.
A generation of lawyers wants to practise in technology. The ambition is serious. The preparation often is not. They can discuss the Nigeria Data Protection Act, the shape of consideration, and the manners of a well-drafted indemnity. Then a product manager says the session token is in Redis, a webhook did not arrive, or user acceptance testing was deemed accepted, and the room goes quiet.
The quiet has a cost. Policies are pasted from a jurisdiction the product does not live in. Service levels are numbers with no hours attached. Liability for a payments API is left in the gap between the company the user sees and the company that actually moves the money. Acceptance clauses are so soft that a system can be called unfinished for as long as it is convenient, or finished before anyone has tested it.
Tech & Counsel is a modular curriculum written for that gap. It is technical literacy for lawyers, not a software engineering course wearing a gown. The historical teaching notes for this path were developed as Tech Law Academy. The product you are in is Tech & Counsel: the same foundational sequence, taught as education.
The approach
You start with the stack and the way software is planned, branched, reviewed, and handed over. You then map data the way a product team actually holds it, and only then draft. Later modules take licensing, open-source risk, assignment of code, privacy by design, Nigerian regulators you will actually meet, and the first night of a breach.
What changes if you finish the reading
- Draft a privacy notice that could be checked against the data dictionary, not against a template.
- Explain cookies, pixels, and SDKs well enough to argue about a banner with the person who will implement it.
- Ask a sharper question when an API, a webhook, or a hosting region is doing the work the contract pretends the client does.
- Read an acceptance-testing dispute as a record of criteria, time, and sign-off, rather than as a mood.
What we are not
Not a law firm. Not a pupillage. Not a live advice service. Not an official certification. Nothing on this site is a precedent, and nothing here creates a solicitor–client relationship. Exercises use teaching scenarios. They are not instructions for a file you are holding.
Tech & Counsel provides education only. Nothing on this site is legal advice, and nothing here creates a solicitor–client relationship.
People
Three seats. Photographs to follow.
Names and biographies below are placeholders kept in one content file so they can be replaced without a redesign. The image filenames stay the same when the real portraits arrive.
Founder
Founder
Placeholder biography. Replace this copy in lib/content/site.ts, or drop a photograph in at the same filename. The founder’s seat is the person who decided lawyers should learn the stack before they learn another template.
Curriculum
Curriculum
Placeholder biography. This seat shapes the modules: tech literacy first, then privacy drafting, contracts, and product advisory. Written for lawyers, not for engineers who already live in the repository.
Product
Product
Placeholder biography. This seat keeps the path usable: reading order, progress, and a lesson page that behaves like a textbook rather than a file dump.