E3 Leasing
A lease deal from first lead to purchase order, with everyone able to see where it stands and who it is waiting on.
Deal management platform · May 2025 - Oct 2026
What each deal moves: equipment, from a supplier to a lessee.
- 7
- Stages from lead to purchase order
- 6
- Staff roles on one pipeline
- 47
- API routes
An internal web app for an equipment-leasing company in the UAE. Sales, Credit, the general manager, the managing director, Finance and administrators move each deal through lead, inquiry, credit scoring, two-level approval, contract, activation and purchase order.
The problem
Deals were followed through spreadsheets and email chasing. Nobody could see at a glance where a deal stood or whose approval it was waiting for.
The approach
One pipeline holds every deal and its figures. The approval rules are enforced in the database itself, and the final approval creates the contract automatically.
A deal's path
- 01Lead
- 02Inquiry
- 03Credit score
- 04Approval
- 05Contract
- 06Activation
- 07Purchase order
What I did
- Translated stakeholder requirements into contract, supplier and lessee workflows, reducing manual work by 50%.
- Implemented onboarding and approvals, accelerating contract cycles by 60% and reducing data errors by 30%.
- Built the app end to end, from the data model and approval functions to generated contracts and the test suite.
- Also built the company's marketing site, in React, Vite and GSAP.
What it does
- Leads to inquiries
- A lead becomes an inquiry in one action, carrying its lessee and supplier with it. Both are checked for duplicates.
- Deal financials
- Cost, advance, tenure, rate, instalment, fees, VAT and margin, calculated in one place and covered by tests.
- Credit scoring
- A score calculator for each lessee, with the history of every score kept.
- Two-level approval
- Credit approves first, then the general manager, with escalation to the managing director. A rejection returns to Sales to edit and resubmit, and approvers can act from an emailed link.
- Contracts
- Generated as Word and PDF with the supplier's and lessee's logos, then tracked from draft through signature and activation to close.
- Purchase orders
- Raised against an active contract, approved, produced as PDF and emailed to Finance.
- Records and audit
- Document storage, a deal sheet in Excel, proposal PDFs, notifications, inventory, user invites and an audit log.
How it is built
- Application
- Next.js 16 with the App Router, React 19 and TypeScript, with TanStack Query and Zustand: 26 pages and 47 API routes, deployed on Vercel.
- Data and rules
- Supabase provides Postgres, sign-in and file storage. Row-level security guards every table, and the approval workflow lives in Postgres functions, so a deal cannot skip a level whatever the client sends. Each person has a system role and an approval role.
- Documents and tests
- Contracts, proposals and deal sheets are built with docxtemplater, pdf-lib and exceljs, and email goes through Resend. 22 Playwright spec files cover the flows, the calculations among them.
- Next.js 16
- React 19
- TypeScript
- Supabase
- PostgreSQL
- Playwright