Skip to main content
Back

DIGILAWYER · BIGOH TECH • 2024 – now · 4 min read

Three products, one designer, twelve weeks.

No design function to three live products

View live page(opens the live design system in a new tab)
DigiLawyer

As the founding product designer at DigiLawyer, a legal platform with no design function, I had three products due at once. As the sole design owner, with engineering through QA, I took the B2B dashboard, B2C website and shared application to launch in 12 weeks. All three launched, and MAU then rose 22% month over month.

Figma link

DGSign (DigiLawyer) · view only

View in Figma(opens in a new tab)

OVERVIEW

3

Products in 12 weeks

Dashboard, website and shared application, concept to launch.

+22%

MAU, month over month

Month over month from a 20.8K baseline, after the PDP, PLP and search rebuild.

−40%

Design-to-dev handoff

Design to development, through the component library and guidelines.

14

Projects on the system

The design system that came out of it.

THE SITUATION

A legal platform with no design function behind it.

  • BigOh Tech took on DigiLawyer, a consumer legal platform for India.
  • No design owner, no shared language, three products to stand up at once.
  • Real legal work: notices, agreements and e-stamps across 20+ states.

The core challenge:

Launch a B2B dashboard, a B2C website and the application both depend on, in twelve weeks, with one designer.

Where DigiLawyer started
Where DigiLawyer started
DigiLawyer on a phone: “India's Legal platform for Citizens”

THE USERS

Two sides of the same product.

  • Legal teams
    Work their cases in the B2B dashboard.
  • People who need legal help
    Find and buy DigiLawyer's services on the B2C website.
  • Both, underneath
    The shared application carries what both sides depend on.
DigiLawyer on a phone: “India's Legal platform for Lawyers”
DigiLawyer on a phone: “India's Legal platform for Citizens”
A man with a coffee mug beside DigiLawyer on a phone: “India's Legal platform for Judges”

PAIN POINTS

No design function, and three products due at once.

  • No owner
    Nobody accountable for how DigiLawyer looked or worked.
  • No shared language
    Nothing tied the surfaces together, so each would have been designed on its own.
  • Three surfaces at once
    A dashboard for legal teams, a consumer website, and the application under both.
  • Friction nobody had measured
    After launch, the product detail, listing and search pages were where people stalled.

WHY IT HAPPENED

The constraint was breadth, not depth.

  • Three surfaces, one designer, one launch date.
  • None of them could feel like a different product.
Heat maps and funnels, PDP / PLP / search
Heat maps and funnels, PDP / PLP / search

DESIGN GOALS

Design goals

  • One system across three surfaces
  • Neither side borrowed
  • Launch in twelve weeks
  • Decide from data

SOLUTION

What shipped

  • B2B dashboard
    For the legal teams working cases.
  • B2C service website
    Where people find and buy DigiLawyer's services.
  • Shared application
    The layer both sides depend on.
  • Rebuilt PDP, PLP and search
    Redesigned against heat-map and funnel analysis.
  • The design system
    Built alongside the product; now running 14 projects.How the system was built ↗
The B2B dashboard · Illustration
The B2B dashboard · Illustration
The DigiLawyer website on a laptop: “Features of Digi Lawyer India”
DigiLawyer's sign-up screen on a laptop: “Create a free account”

PROCESS

From discovery to handoff

  1. 01 · MOBILE

    The website on phones: hero, features, pricing, newsletter

    The website on phones: hero, features, pricing, newsletter
    The website on phones: hero, features, pricing, newsletter

  2. 02 · GRID

    The website on a 12-column grid: 120px margins, 24px gutters

    The website on a 12-column grid: 120px margins, 24px gutters
    The website on a 12-column grid: 120px margins, 24px gutters

  3. 03 · PRODUCT

    The product's components in use: status, model picker

    The product's components in use: status, model picker
    The product's components in use: status, model picker

  4. 04 · PROTOTYPE

    Walkthrough

    Walkthrough
    Walkthrough

DECISIONS & TRADE-OFFS

Key decisions and trade-offs

  • Surface by surface, decisions shared
    I worked one surface at a time but kept the decisions shared: one information architecture, one interaction language, one set of patterns.
  • Data before redesign
    Later work went only into parts that showed measurable friction. Heat-map and funnel analysis first, then the PDP, PLP and search rebuild against what it showed.
  • Handoff as a system
    A component library and structured interaction guidelines, with engineering alongside through implementation and QA.
  • Colour on the website, not the dashboard
    The AI chat dashboard stayed minimal, like Claude and ChatGPT. The same system looked flat on the website, so the website got colour.Trade-off: Two surfaces, two temperatures: visitors must be drawn in; dashboard users already know their goal.

OUTCOMES

Launched in three months, then grown

I remained sole design owner of the product area for over two years.

A DigiLawyer billboard: “India's Legal platform for citizen like you”

REFLECTION

What it taught me

Breadth is a design problem of its own. Three products in twelve weeks only worked because the decisions were made once and shared, not remade for every surface.

  • Measure the friction, then fix it
    The rebuild that moved MAU started from heat maps and funnels, not from what we assumed was wrong.

SELECTED WORK

Morecasestudies

All work