Warren
Client testimonial
Engineering services by Hamza Khan
I help legal-tech teams and legal organizations build AI systems, connect everyday workflows, assess application security, and build or improve software.
No legal advice. A person approves every consequential step.
Built with
The tools behind the work, with what each one does in plain words.
intake-agent · change set
+ POST /intake
+ matter permissions
+ action audit log
Spec agreed
Acceptance criteria signed off
Build
API, data model and permissions
Checks
Tests pass before release
Release
Shipped with handover notes
01 / Services
Agentic AI, cybersecurity and product engineering, delivered end to end by one engineer.
Agentic AI
AI agents that research, draft and act across your tools, with human approval before anything runs.
Cybersecurity
Authorized testing that finds weaknesses in your web, API and AI systems before clients rely on them.
Engineering
Design, build and scale software, from new features to the platform your team already runs.
02 / Proof
Clients in their own words, and the platforms we built together.
Client videos do not yet have reviewed captions.
03 / Day-to-day operations
It answers clients, updates cases and routes everyday work through your approved tools, and hands anything important to the right person.
What it handles
01Client calls
“What’s happening with my case?”
02Identify the matter
Caller verified and matched to their case
03Check status with approved tools
Reads stage, next date and open requests
04Answer and update
Shares permitted basics; records new details
05Escalate when needed
Connects the case attorney or case manager
06Logged
Call summary and actions saved to the matter
Connect your own legal research tools, such as LexisNexis, Harvey or Legora. Your attorneys still give the advice.
04 / Built for sensitive work
Approved sources go in, reviewable work comes out, and each release is security-tested before your team relies on it.
Every workflow follows three rules
Built into the systems your firm already uses. What connects depends on access, APIs and agreed scope.
Also case management, phone and SMS, e-signature and court notices.
Before launch I plant attacks, fix what they find and retest, mapped to the OWASP Top 10 lists.
I've helped client teams through ISO 27001, SOC 2 and HIPAA audits by building the access controls, audit logs, encryption and evidence their auditors examined.
Auditors issue the reports and certificates; I build what they examine.
No legal advice: your attorneys make every legal decision. I'm not your auditor and don't guarantee compliance. Product names and logos are trademarks of their owners. Shown to identify integrations; no endorsement implied.

05 / Who you work with
I connect legal operations and firm knowledge with AI workflows, application security and full-stack product engineering.
I can own a defined workstream or work alongside your existing team, from understanding the process through implementation, verification and handover.
6+ years
Engineering experience3+ years
In legal technologyEnd-to-end
Delivery ownershipHow an engagement runs
Map the workflow, the system owner and what a useful outcome means.
Agree the work, access, deliverables and acceptance criteria.
Implement or test, keeping findings and decisions visible.
Review the delivered behavior, document limits and agree next steps.
06 / Next step
30-minute intro call · or email hkhantanoli@gmail.com(opens in new tab)
Questions
Law firms, legal-tech founders and in-house legal teams are my main focus. I also work with AI and B2B software teams whose applications handle sensitive information.
No. I build and test software. Your attorneys make every legal decision, and the workflows I build route legal questions to them.
Often the starting point is an existing system. I first assess its available APIs, access permissions, data quality and workflow constraints, then define what can be connected or extended.
Yes. An assessment can stand on its own with documented findings and remediation guidance. Implementation and retesting can be scoped separately or included in an agreed engagement.
Yes. A first review of one agreed workflow is free, sized to your application and the question. You receive a brief record of what was reviewed and suggested next steps. Larger or complex workflows are scoped as a paid assessment; smaller ones can start with a short trial. It is not a comprehensive penetration test, and active testing needs agreed authorization.
Yes. Most firms start with one recurring task that has a clear owner and usable inputs. We agree the scope, review points and acceptance checks, then build.