All work/Case 03 of 10/Multi-product SaaS8 min read
EclaraWhitelabel
A white-label admin platform, consolidated without losing a feature.
Eclara is a white-label education platform. An academy buys it, puts its own name on it, and runs students, tests, payments and its website from one admin panel. As the sole designer, I redesigned the entire admin experience.
CoverThe redesigned dashboard: balance, products and the most frequent actions first.
The short version
Challenge
The product had grown one page at a time for years. Fourteen sidebar items sat at equal weight, some pages could only be reached through text links, and a second product (the franchise system) had been added with its own conventions.
Approach
I grouped pages by the job they serve. Pages that finish the same task became one workspace, with tabs, tables you can act on directly, and side drawers instead of new pages.
Outcome
34 pages became 6 workspaces with no features removed, and support got its own ticketing screen. The redesign is live, and it became the base for EachCanTeach.
34 → 6pages merged into workspaces
6 → 1student pages
10 → 1website settings pages
5language versions per question, visible in place
01 / Overview
One product, many academies.
A white-label product can’t be designed for one customer. The same panel serves an academy with twelve students and one with several thousand, an owner who lives in the wallet and one who only creates tests. Requirements kept arriving mid-project, each valid and each from a different kind of user, so much of the work was discussion, rework and finding a structure that worked for all of them.
BeforeAfter
DragDashboard, before and after.
02 / The problem
Pages organised by history, not by task.
I listed every screen and the job it served, and the same pattern kept appearing: one job, many pages. Registering, upgrading and finding a student took six pages. Turning on part of the academy’s website meant finding the right one of ten. The question list even needed a legend across the top to explain its own icons.
14sidebar items at equal weight
5menu items for one testing workflow
2products with different conventions
0screens for support, so queries came by phone
03 / New structure
Six workspaces instead of thirty-four pages.
One rule: if two pages exist to finish the same job, they become one screen. Lists and forms share a view, so a new record appears immediately, and secondary tasks open in side drawers so you never lose your place.
Test PackageQuestion MasterBatchTest MasterExam Master
Testing engine5 → 1
Question BankTest tableBundle wizard
CentresWalletsRequestsHistory AHistory B
Franchise workspace5 → 1
CentresStudentsWalletRequestsMessagesReports
BannersGalleryNotesTestimonialsNavigationSocialTheme+3 more
Website management8 → 1
Every switch on one boardEditor below
Wallet summaryOnline rechargeRecharge historyDebit history
Transactions4 → 1
Revenue stripRecharge deskHistories
CategoryServiceEnquiryTransaction
Your services4 → 1
Stats stripFour jobs as tabs
NoteThe number of meetings is not included, for morale reasons.
04 / Testing engine
The biggest piece of work.
The old testing module was spread across five menu items, mostly forms and tables. The new Question Bank shows the subject and topic tree with question counts, plus the questions themselves in all five languages, on the same page. Creating a test became one table where each row carries its own actions, and packaging tests for sale became a three-step wizard beside the live bundle list.
BeforeAfter
DragQuestion Bank, before and after.
Fig.Test table: manage a test without opening it.
Fig.Bundle wizard: details, contents, pricing.
05 / Before and after
The same idea, everywhere.
Each comparison applies the same decision at a different scale: fewer pages, more done in place. Drag the handle to compare.
BeforeAfter
DragStudent registration: six pages became two tabs above the student table.
BeforeAfter
DragFranchise system: one workspace, with a centre created in a two-step drawer.
BeforeAfter
DragWebsite management: ten pages of toggles became one board.
BeforeAfter
DragTransactions: four pages became one workspace.
BeforeAfter
DragProfile: who the academy is, separated from what it shows.
BeforeAfter
DragYour services: four pages became tabs above one form.
app.eclara.io/support
Fig.New: a support workspace that separates the academy’s own queries from its students’ and centres’.
06 / Results
Fewer places to look.
The redesign is live. The same features now sit in about a sixth of the pages, so each academy’s staff learns one pattern and reuses it across every module. It also became the foundation for EachCanTeach.
Decision 01
Tabs over pages
Related tasks share one screen, so switching between them is a click, not a page load.
Decision 02
Act in the table
Row actions replace “open, edit, save, go back” for tasks done dozens of times a day.
Decision 03
Drawers for creating
A centre or bundle is created beside the list it will join, so you keep your place.
Learnings
White-label design isn’t a styling problem. It’s about holding many businesses in one structure without any of them feeling like an afterthought.
Almost there+50 XP for finishing0 of 10 case studies cleared.