A technical case study of a UAE legal firm's transition from offline-first to fully digital operations.
Tasheel Legal Consultancy is a UAE-based legal firm with over fifteen practice areas — civil, commercial, family, labour, property, maritime, aviation, and more. When we started working with them, the firm had a strong reputation, a loyal client base, and was operating almost entirely through offline channels in a market that had decisively moved to digital-first expectations.
This is a technical walkthrough of how we architected the solution, what trade-offs we made, and what we'd do differently if we built it again.
The four problems we had to solve
A standard agency response to "we need to digitize our law firm" is to deliver a website refresh. We've seen that pattern fail enough times to know it doesn't address the underlying issues.
We started with a workflow audit. Four problems surfaced:
First, no access outside office hours. Every client inquiry — a cheque bounce case, a travel ban check, a divorce consultation — required a phone call or office visit. The firm was effectively invisible to overseas clients in different time zones, and unresponsive to anyone trying to engage outside a narrow window.
Second, zero case visibility for clients. Once a matter was opened, clients had no way to check progress without calling the office. This generated a constant volume of follow-up communication that consumed lawyer time and left clients feeling uninformed.
Third, physical document dependency. Power of Attorney, contract reviews, and legal opinions all required clients to physically submit documents. For expatriates in other emirates or principals overseas, this was often prohibitive.
Fourth, a weak digital presence that misrepresented the firm's actual capability. Prospects searching for UAE legal help online encountered a website that didn't reflect the firm's true depth.
The architectural decision: two layers, decoupled
We could have built one large monolithic system. We didn't. We built two layers that work in concert but are independently maintainable.
Layer one is the public-facing site, tasheellegal.com. Its job is acquisition: turn searchers into inquiries, build organic authority through content, and present the firm credibly to first-time visitors. We structured it around practice areas and client intent — every major service has a dedicated page that answers the questions clients actually search for. Service triggers (Book a Consultation, Get Power of Attorney Online, Check Travel Ban, Legal Contract Review) are embedded directly on the homepage so a client with an urgent problem can take action immediately. A legal blog publishing in-depth guides compounds over time, driving organic traffic.
Layer two is the Tasheel Legal Portal — an authenticated client experience platform that lives at a separate subdomain. Its job is delivery and retention: give every client with an active matter a real-time dashboard of their case, digitize the document-intensive workflows, and run 24/7 regardless of office hours.
The decision to keep these separate matters. A common mistake is to build the authenticated portal as a logged-in version of the public site. That conflates two very different concerns — marketing and operations — into one codebase. When the marketing team wants to A/B test a landing page, they shouldn't have to coordinate with operations. When operations needs to ship a new workflow into the portal, marketing shouldn't be a blocker. Decoupling pays for itself within months.
Solving the access problem
The portal operates 24/7. A client in Mumbai at midnight with a UAE travel ban issue can initiate the check immediately. A corporate client in London reviewing a UAE contract can submit it for legal opinion without a single phone call. The firm's operational hours stopped defining its reach.
The technical work here is unglamorous but important. Time zones get handled at the data layer, not the UI layer — every timestamp stored in UTC, rendered in the user's local time. Document uploads run through a chunked upload pipeline that handles intermittent connectivity gracefully, because the assumption is mobile users on variable connections, not desktop users on fibre. Notification delivery routes through email, SMS, and WhatsApp depending on the client's stated preference — set once during onboarding.
Solving the case visibility problem
Every client with an active matter gets a personal case dashboard. Status updates, upcoming deadlines, next steps, and matter history live in a single view. The volume of "what's happening with my case?" calls drops because clients already know.
The implementation detail that mattered most here: lawyers update case status as part of their existing workflow, not as a separate data entry task. When a lawyer files a document with a court, the case status updates automatically. When they schedule a hearing, the client sees the date the moment it's entered. The system that surfaces information to the client and the system that lawyers use to do their work are the same system. Anything else fails because the second-system tax is too high — lawyers won't double-enter, ever.
Solving the document workflow problem
Three document-intensive services got the heaviest treatment.
The Online Power of Attorney workflow lets overseas clients initiate, submit, and manage their POA entirely without visiting the UAE. We modeled the full state machine — initiated, documents received, reviewed, draft prepared, client approved, executed — and built the interface around the states, not the documents. A client at any point sees exactly where their POA stands and what's needed next.
The contract review workflow uses structured uploads with metadata capture upfront. Clients describe their need, attach their documents, and select urgency. The intake routes to the right lawyer based on practice area and capacity. Review status is visible end-to-end.
Travel ban verification — one of the firm's highest-volume requests — was fully self-service. Clients initiate the check themselves through a structured form. The system handles the verification logic. Results return to the client without manual processing.
What we'd do differently
If we were rebuilding this today, we'd invest more upfront in observability — structured logging across both layers, dashboards for operational metrics like portal session length, workflow completion rates, and abandonment points. We built basic analytics. We'd build them more seriously now.
We'd also expose more of the firm's domain content to AI retrieval. The legal blog we built has compounded value as SEO. A modern build would also surface it as a retrieval-augmented knowledge base for the firm's internal lawyers — letting any team member query "what's our position on this specific area of recent law" and get answers backed by the firm's own previous work.
The architecture decisions we made hold up. The decoupling, the workflow-first design, the time-zone handling, the unified system for lawyers and clients. These were right at the time and they're still right.
What this kind of engagement actually delivers
A firm that runs as a 24/7 digital practice rather than an office-bound one. Lawyers freed from coordination work to do legal work. A client base that extends beyond physical proximity to the office. A brand that finally matches the calibre of the work the firm has been doing all along.
This is what Tier 3 work looks like in practice. It's not a website. It's not a portal. It's the operational architecture of a service business that's decided to compete at a different level than it has been.