Build a CRM dashboard.
From interface to installable app.
A complete, working Customer Relationship Management app — built in four stages. You start with a static interface, add JavaScript state and CRUD operations, connect it to a Python Flask backend with SQLite, and finally package it as a native desktop application with PySide6. Every line of code is shown. Every stage runs. No frameworks, no build tools, no hidden magic.
How to use this page. Read the "Why this project" section below to see what a CRM teaches you. Then pick a stage from the four cards. Each stage is a complete, runnable project on its own — you can stop after any stage and have a working app. If you're a beginner, start at Stage 01 and work forward. If you've built web apps before, you can jump to Stage 03 (Python backend) or Stage 04 (desktop). The code is inline and copy-pasteable on every stage page.
✅ Why a CRM is the right first project
A CRM touches every concept you'll need for the rest of your career.
Real data
Not a to-do list. Customers have names, emails, statuses, leads, values. The data model is realistic from day one.
Every CRUD operation
Create, read, update, delete — all four, in the same app. The four operations that define every database-driven interface.
Every UI pattern
Tables, forms, modals, search, filters, empty states, loading states, error states. The full set, in one project.
Every layer of the stack
HTML, CSS, JavaScript, a Python backend, a SQLite database, and a desktop frontend. You see how the layers connect.
Scales with your learning
The same data model works for a 10-row demo and a 10,000-row production app. Nothing has to be thrown away.
Portfolio-worthy
A working CRM is a real portfolio piece. It's the kind of app a hiring manager recognizes as "this person can build."
✅ The four stages
Each stage is a complete, runnable app. Stop whenever your goal is met.
Interface
Build the visual shell — sidebar, header, KPI cards, customer table, and lead pipeline. Styled with CSS Grid and custom properties. Responsive. Dark-themed.
Interactions
Make it work. JavaScript state, add/edit/delete, search, filters, localStorage persistence. A fully working CRUD app in one file.
Backend
Move the data to a Python Flask backend with a SQLite database. The UI stays the same. Only the storage layer changes.
Desktop
Rebuild the CRM as a native desktop app with PySide6. Package it as an installable .exe or .app. Bundle the database inside.
✅ The tech stack
What each stage uses, and why.
HTML
Semantic structure. The table, the form, the sidebar, the header. No divs for layout when a section or article would do.
CSS Grid + Flexbox
Grid for the two-column layout. Flexbox for the header and KPI cards. Custom properties for the dark theme.
Vanilla JavaScript
State → render → event → state. No framework. This is the loop React and Vue abstract over. Learn it here, directly.
localStorage
Persistence without a server. Survives page reload. The simplest possible database. Used only in Stage 02.
Python + Flask
A minimal REST API. Three routes. No ORM. No migrations. No Docker. `pip install flask` and run.
SQLite
A real database, in a single file. No server. No setup. Ships with Python. Used in Stages 03 and 04.
PySide6
Qt for Python. The same toolkit that powers KDE, Autodesk Maya, and many pro desktop apps. Used in Stage 04.
PyInstaller
Turns the Python desktop app into a single .exe (Windows) or .app (macOS). One command. No installer script needed.
✅ The data model
Fixed once, used across all four stages.
// Customer
{
id: string, // crypto.randomUUID()
name: string, // required
email: string, // required
phone: string, // optional
company: string, // optional
status: 'lead' | 'active' | 'inactive',
notes: string, // optional
createdAt: string, // ISO 8601
updatedAt: string // ISO 8601
}
// Lead (sales opportunity)
{
id: string,
customerId: string, // foreign key to Customer.id
title: string, // e.g. "Website redesign"
value: number, // in USD
stage: 'new' | 'contacted' | 'proposal' | 'won' | 'lost',
createdAt: string,
updatedAt: string
}
{
id: "a3f8c9e1-4b2d-4c7a-9e1f-8b2d5c6a7e3f",
name: "Alice Rahman",
email: "alice@example.com",
phone: "+92 300 1234567",
company: "Acme Corp",
status: "active",
notes: "Met at the 2026 conference. Interested in the enterprise plan.",
createdAt: "2026-11-11T09:30:00.000Z",
updatedAt: "2026-11-11T09:30:00.000Z"
}
{
id: "b7e2d4a8-9c1f-4b3e-8d5a-2f6c7b9e1a4d",
customerId: "a3f8c9e1-4b2d-4c7a-9e1f-8b2d5c6a7e3f",
title: "Enterprise plan upgrade",
value: 12000,
stage: "proposal",
createdAt: "2026-11-11T10:00:00.000Z",
updatedAt: "2026-11-11T10:00:00.000Z"
}
Why id is a string
UUIDs are strings. Auto-increment integers are ambiguous across environments. Strings work everywhere.
Why status is a union
Three values, enforced by TypeScript (or by a check in plain JS). No typo can create a fourth.
Why createdAt is ISO
ISO 8601 is unambiguous, sortable as a string, and parses directly into Date objects.
Why customerId on Lead
Not nested. A lead belongs to a customer, but the customer is independent. A flat model with keys scales better.
❓ Frequently asked
Do I need to complete all four stages?
No. Each stage produces a working app on its own. Stage 01 gives you a styled interface. Stage 02 gives you a working CRUD app with localStorage. Stage 03 gives you the same app with a Python backend and SQLite database. Stage 04 gives you a native desktop version. Stop wherever your goal is met.
What will I actually build in the end?
A CRM (Customer Relationship Management) dashboard. It lists customers, shows leads and sales opportunities, supports search and filtering, and lets you add, edit, and delete records. The final version (Stage 04) is a downloadable desktop app built with Python and PySide6, backed by a SQLite database.
Do I need to know React or any framework?
No. The CRM is built with plain HTML, CSS, and JavaScript. No React, no Vue, no build tools. This is deliberate — understanding how state, rendering, and events work without a framework makes every framework easier to learn later.
What do I need installed on my computer?
For Stages 01 and 02: just a browser and a text editor. Nothing else. For Stage 03: Python 3.11+ and pip. You install Flask with pip install flask. For Stage 04: Python 3.11+, PySide6, and pyinstaller. Everything runs locally.
Where is the source code?
Every stage page has the full, copy-pasteable code inline. Each stage ends with a 'Download the full folder' link that gives you a zip file with all the files in that stage's project. You can copy-paste from the page, or download the folder — either works.
How long will this take?
Roughly 8–12 hours of focused work, spread across four stages. Stage 01 takes 1–2 hours. Stage 02 takes 3–4 hours. Stage 03 takes 2–3 hours. Stage 04 takes 2–3 hours. If you're experimenting, add 50–100% to each.
🔗 Continue learning
Or jump ahead if you know the earlier stages: