Leegality
A design system built from two years of old work, new work and my own.
Leegality builds eSign and document-workflow software for Indian banks and lenders. Its communication has to make RBI regulation readable. As design lead, I gathered the designs that already existed and the new ones the team was making, sorted out what worked and what didn’t, and designed what was missing. Over two years that became a shared visual system: what we made fed the system, and the system shaped what we made next.
- 55M+eSigns
- 33M+documents
- 3 months → 3 weeksturnaround
+ Leegality in numberseSigns and documents: reported 2025 figures
Good pieces, no rules
Leegality already had a logo, a palette and three fonts. What it didn’t have was any guidance on how to use them together.
So everyone made it up as they went. Every team picked its own colours, and nothing quite looked like the same company.
#5A1FCCPurple 2
#7530E2Purple 3
#903FF9
#DD4E4EPeach 2
#F26966Peach 3
#FF837C
#D88212Gold 2
#EF991BGold 3
#FFAD26
#06003B
#F3F3F3
#FFFFFF
Plus Jakarta SansHeadings
RobotoBody copy
InterProduct UI
+ What I started withA logo, a palette, three fonts
+ Before · 2021–2023Posts and thumbnails · no shared language
Every element has a job
The same decisions kept coming back, so I turned them into rules the team could apply without asking me.
How I used AI to find these patterns- Purple identifies, gold supports, peach flags what’s wrong.
- Green and red only carry status, never decoration.
- Plus Jakarta Sans structures, Roboto explains, Ink Free annotates.
- One block per kind of content: requirement, explanation, question, mistake → fix.
- One template for every screen walkthrough.
- Illustrations borrow from the palette, never copy it.
On white
On navy
On purple
On light purple+ Logo in useEach wordmark version on the background it was made for
+ From nine colours to six rolesValues from the Figma system
#FFFFFF#E9E0FC#FFF5E6#08023D#7E41F4#F2F2F2#FCB149#FCE8E6#FF8B81#E5F5E9#22C55E#EF4444+ Colour usageSized by how often each colour is used
+ Plus Jakarta SansRegular to Bold
+ RobotoLight to Medium
+ Ink FreeCallouts only
Make regulation readable.
Clear information helps borrowers make an informed decision.
01 02 03
+ Type hierarchyHeading : body · 24 : 12
Check
Cross
WhatsApp
Vernacular
Legal stamp
SignatureKFS shall be in the prescribed format.
Clause 4 · Provide a KFS to all prospective borrowers.
Questions to ask your vendor
- Do you support vernacular agreements?
- Can you capture vernacular eSign consent?
Same blocks, every page
Build a block once and use it everywhere. Readers learn the pattern and skim faster.
Entire flow is in English.
Support the borrower’s language.
+ Reusable elementsSame blocks, every page
- 1
Fictional lenders like Bharat Bank stand in for real customers.
- 2
Annotations pinned to the element the regulation is about.
- 3
One primary action per screen, always in the same place.
- 4
Numbered steps with A/B branches when two screens are alternatives.
- 5
Short captions beside each screen, with the key feature named in purple, like “OTP-less Quick Sign”.
+ Template anatomyHover a point to explore · five parts of the template
+ Same template, two journeysFinal playbook · pages 38–39
- 1
The characters. Lenders, branch agents and borrowers, drawn simply with expressive gestures.
- 2
The colour scheme. Never the exact brand tones, always from the palette: muted for KFS, brighter for accessibility.
- 3
The device. Phones show the exact screen the borrower sees, in their own language.
- 4
The icons. One flat family in the brand colours, with red only for what breaks.
- 5
The scene. Real places, from a branch counter with a Hindi sign to a village courtyard.
+ Illustration styleHover a point to explore · KFS and accessibility playbooks
Make regulation readable
The language took shape in the KFS playbook: 53 pages explaining the RBI’s Key Fact Statement rules to lenders. We tested whole directions on the same page, and the final put each legal clause on a white card so the rule always stays readable.
Readable also meant navigable. In a swimlane, each party gets a lane and every step gets a number, so a compliance team can follow who does what, and when.
When the old process and the new one share a visual language, the difference between them becomes the story.
Direction 1
Direction 2
Final+ One page, three directionsOriginal working PDFs · June–August 2025
+ Cover explorationsThe requirements became the outlined tiles
+ The KFS playbookPages 4–5 of 53 · drag or use the arrows
+ Architecture of a KFS flowFour lanes · numbered steps
Physical · 30–35 min
Digital · 15–20 min+ Before and after, in one languageGold-loan playbook
+ Accessibility playbookEight gaps that break eSign journeys
Extending the language across the brand
Playbooks, product identities, customer stories, social, events and merch. Each format drew on the same decisions.
Customer stories are where the system flexes. Federal Bank and SBFC Finance bring their own colours and logos into Leegality’s layouts. The structure, type and callouts stay ours, so every story still reads as Leegality.
ConsentIn and SignStation each got a distinct mark, endorsed “by Leegality”.
ConsentIn
SignStation+ Product identityTwo new products, one family
+ SBFC Finance · in handBack and front cover · mockup
+ SBFC FinanceTheir logo, our layouts
+ SocialLinkedIn carousel · problem, product, offer
+ StoriesWebinars, playbooks, ads and events · one system
+ CultureHiring posts · Diwali 2024 box and stickers (mockups from the print files)
Changing how the work moved
Layouts were only half of the slowdown. Design needs surfaced after copy was final, and feedback came in long, open rounds.
I started briefing the copy team before writing began. Pages were assembled from existing patterns, and feedback moved through clearer rounds. Together, these changes brought playbook design after content approval from about three months to three weeks.
Playbook design, after content approval
Purple marks what changed. Reuse alone didn’t produce the speed-up: earlier briefing and clearer feedback mattered just as much.
+ Three months to three weeksDesign turnaround after content approval
+ Three playbooks, one system138 pages built from the same blocks, type and colour roles