Get in touch
Most conversations start with one workflow: intake, contract review, compliance operations, research, drafting or AI governance. I also take advisory questions on AI governance, regulated digital markets and legal operations, and I am glad to hear about speaking, board seats and AI-governance roles.
serdar@lexsas.comThis is technology and process consultancy, not legal representation. LEXSAS is not a law firm, gives no legal advice, and nothing here creates an attorney-client relationship.
If you are writing about a workflow, five lines are enough
- The matter type
- What kind of work it is, in your own words: incoming requests, NDAs, notice-and-takedown, research memos.
- The volume
- How many of them a week or a month, roughly, and where they arrive from. A rough figure is enough; “around forty a month” does the job.
- The systems
- What the work touches today: mailbox, document system, contract system, matter system, UYAP, UETS, a spreadsheet, whatever it is. List all of them; even one matters.
- The reviewer
- Who would sign, by role. A name or a role is fine, and if that is genuinely unclear at this stage, say so, because it is often the most useful thing you can tell me. Before anything is built the approving lawyer or role is settled and written down; a workflow is not built with that field open.
- The timing
- When you need something running, and what is driving that date.
What not to send
- No confidential detail, no client identities, no personal data, no documents.
- Nothing under a duty of confidence and nothing privileged. A description of the problem, its type and its volume is enough to scope it.
- No long needs analysis or specification: we write that together, and writing it now means writing it twice.
If documents are needed later, we agree that separately and in writing, and I ask for no document before a non-disclosure agreement is signed.
What happens next
A call of about an hour
The workflow, the team, the systems, the reviewer. No charge, no obligation.
A written scope
Stages, mandate, record format, the one measure, the dates and the price.
A supervised pilot
A baseline first, nothing unattended, and a pass or fail on a date fixed at the start. Everything it produces stays with you, in an exportable form.
I read it and reply within two business days. If a workflow is the right answer, the next step is a call of about an hour that ends with one workflow chosen, the controls it needs named, and an agreed way to tell whether it worked. The written scope sets the fee, agreed in writing before work begins; there is no per-user licence list. If a workflow is not the right answer, I will say that instead, and say what I think is.
If you would rather read first: the operating standard is the method in full, security and data handling covers what this site collects and where a workflow runs, the eight workflows have a page each, and there is a starting point for in-house legal teams and one for law firms.
- linkedin.com/in/asimserdaryilmaz
- Location
- Istanbul, Türkiye (UTC+3). Work runs remotely; scoping calls and pilot reviews can be held in person in Istanbul.
- Languages
- Turkish and English.
What happens to your email: this site sets no cookies, runs no analytics and loads nothing from a third party, its fonts included. If you write, the address is used to reply and for nothing else. Who is responsible for it, how long it is kept and your rights are in section 1 of security and data.