01
ADMIN
Runs the project.
- Uploads BOQs and drawings, version by version
- Invites vendors and compares quotations
- Tracks milestones and closes the project
CASE STUDY · PLANET X
Controlled access, clear workflows..
Product design for a secure B2B procurement platform — Admin, Vendor and Client portals.
See how we built it01 · THE PLATFORM
The procurement desk behind the factory floor.
Planet X runs industrial projects for factories. A client sends a requirement — a cooling tower, a conveyor retrofit, a new roof — and the Planet X team turns it into a standard BOQ, tenders it to verified vendors, ranks the bids and oversees the work until it’s signed off.
FIG 01 — Planet X dashboard, vendor view
02 · THREE ROLES
One project. Three very different people.
We split the platform into three portals. Each one shows only what that person needs to act on next — nothing more.
02
VENDOR
Wins and delivers the work.
- Onboards once through KYC
- Studies drawings inside the secure viewer
- Submits quotations and uploads proof of work
03
CLIENT
Makes three decisions.
- Approves the BOQ
- Chooses the vendor
- Signs off each milestone — only when it’s their turn
03 · LIFECYCLE
From request to closure
Every project passes the same five gates — BOQ approved, bidding closed, vendor awarded, milestones signed off, project closed. Each gate has one owner and one next action, so nobody has to ask whose turn it is.
- BOQ approved
- Bidding closed
- Vendor awarded
FIG 03 — Verified vendors, then the ranked bid list
- BOQ approved
- Bidding closed
- Vendor awarded
04 · BOQ & BIDS
Versioned, then ranked
BOQ changes are versioned and kept for audit. Bids arrive ranked by total price with one recommendation and the reason in plain words — here, Kaveri Enviro at L2: the only dairy-effluent specialist, ₹40k over the lowest.
FIG 04 — Revision history and the recommended bid
05 · SECURE VIEWER
Drawings stay in the room
Drawings open in a controlled room, not a PDF reader. Download and print are switched off, every page is watermarked to the vendor it was issued to, and access expires when the tender closes.
FIG 05 — Watermarked, view-only drawing room
06 · DESIGN SYSTEM
Colour means status. Nothing else.
A quiet, data-first interface: light surfaces, one dark button per screen for the next step, and colour kept for status alone — blue while work sits with the team, amber while it waits on the client, green once it’s awarded.
FIG 06 — Colour reserved for status
07 · COMPONENTS
Parts that do one job
We built the dashboards from a small set of parts, each answering one question — where am I, what needs me, how are we doing. Same parts, same place in every portal, so anyone who learns one role can read the others.
FIG 07 — Navigation, action queue, at a glance
08 · CLIENT PORTAL
Built for the occasional client
The client is a factory manager, not a procurement specialist. They arrive from a notification — “BOQ v2 is ready for your approval” — make one decision, and go back to the floor.
5 bids ranked — choose your vendor
5 bids ranked — choose your vendor
FIG 08 — Every visit starts from a notification
09 · CLIENT SCREENS
Every screen asks one thing
Every client screen leads with a single decision — approve, choose, sign off, review — with the evidence right beside it and the action in one button. No training, no hunting through tabs.
10 · ADMIN PORTAL
The admin starts with the queue
The admin dashboard opens on what’s waiting — vendor KYC reviews, unanswered queries, bids ready to rank, certificates to verify — oldest first. One button works the queue top to bottom; every project stays one click away.
FIG 10 — The attention queue, oldest first
11 · VENDOR PORTAL
A portal vendors actually use
Vendors run their week from one screen: what’s due, which invitations close soon, the milestone calendar, and the reviews that win them the next job — each part readable between site visits.
FIG 11 — Rating, milestones, calendar, reviews
12 · CLOSURE
Nothing closes on one signature
Closing takes two signed documents: the completion certificate, signed on site and uploaded by the vendor, and the snag list, uploaded by the client or the admin. Only when both are in and verified does the project close — and lock.
FIG 12 — Two signatures before a project locks