Overview
Start with PyColors in the right order. Validate your SaaS surface, understand the system, and move toward a production-ready business foundation.
Build your SaaS in the right orderLink to section
PyColors helps you move from idea to credible SaaS product without spending your best time on the wrong layer too early.
The goal is simple:
- validate the product surface
- build with consistent UI foundations
- use patterns for real product behavior
- wire auth, billing, backend, and delivery when the business layer becomes the blocker
- launch with more confidence
This section gives you the fastest path through the docs.
Core idea
Start with the surface. Validate the product. Upgrade when infrastructure becomes the bottleneck.
Choose your pathLink to section
Start with Starter Free
Choose this path when you need a credible product surface before backend complexity.
- real SaaS screens
- dashboard and navigation
- auth, billing, admin, and settings surfaces
- mocked data and UI states
- fast demo and MVP validation
Move to Starter Pro
Choose this path when your product needs real users, real payments, protected access, and backend foundations.
- real authentication
- Stripe Checkout and billing portal
- webhook-driven subscription state
- Prisma-ready backend foundation
- secure delivery after purchase
What you should do firstLink to section
Understand the product pathLink to section
PyColors is not just a UI library.
It is a path from product validation to SaaS launch:
- Design System gives visual consistency
- UI gives reusable primitives
- Guides explain how to compose real interfaces
- Patterns solve repeated product flows
- Starter Free validates the surface
- Starter Pro wires the business layer
Run the starter locallyLink to section
Start with the product surface.
Run the app locally, click through the main routes, and understand what is mocked before changing too much.
Explore the UI foundationsLink to section
Review the primitives that power the product:
- Button
- Input
- Card
- Badge
- Alert
- Dialog
- Table
These components keep the product interface consistent as it grows.
Learn the patternsLink to section
Patterns show how primitives become real product flows:
- data tables
- overlays
- async actions
- empty, loading, and error states
This is where UI becomes product behavior.
Upgrade when wiring slows you downLink to section
When the question changes from “what should this product feel like?” to “how do I launch this with real users and payments?”, Starter Pro becomes the faster path.
Fastest path by goalLink to section
Validate an idea
Start with Starter Free, adapt the product copy, rename the core entity, and show the app to users.
Build a serious baseline
Use UI, Guides, and Patterns to create consistent product flows before custom logic takes over.
Launch and monetize
Move to Starter Pro when auth, billing, backend, protected routes, and delivery become the bottleneck.
Time to first resultLink to section
| Milestone | Target |
|---|---|
| Run the project locally | 10 minutes |
| Understand the main routes | 30 minutes |
| Adapt the product surface | 1–2 hours |
| Ship a first demo | Same day |
| Wire production foundations | When validation is clear |
| Launch with real auth and billing | Starter Pro path |
Time-to-value matters
The faster a builder sees a credible product surface, the faster they understand the value of PyColors.
Recommended reading orderLink to section
Set up the project locally and validate that everything runs.
Explore the app, main surfaces, and first product flows.
Understand where routes, components, features, and product foundations live.
Add your first product feature without breaking the architecture.
Free vs Pro decisionLink to section
| Question | Best path |
|---|---|
| I need to validate the product surface | Starter Free |
| I need a credible UI demo | Starter Free |
| I need real accounts and sessions | Starter Pro |
| I need Stripe Checkout and billing portal | Starter Pro |
| I need subscription state to control access | Starter Pro |
| I need secure delivery after purchase | Starter Pro |
| I need to reduce launch risk | Starter Pro |
Upgrade when wiring becomes the bottleneck
Starter Free validates your product. Starter Pro wires your business.
Revenue-focused mental modelLink to section
PyColors is designed around a simple business principle:
Spend less time rebuilding repeated infrastructure. Spend more time on product, positioning, distribution, and customers.
That matters if your goal is to build a serious SaaS business.
The documentation should help every visitor understand:
- what PyColors solves
- where to start
- when Free is enough
- when Pro becomes the faster path
- why buying the foundation can be higher leverage than rebuilding it
What to avoidLink to section
Prefer
- running the project before refactoring
- understanding the Free → Pro path
- validating product UX before deep backend work
- using patterns for repeated product flows
- upgrading when auth and billing slow launch
Avoid
- rewriting everything before understanding the baseline
- starting with billing before validating the product
- mixing UI primitives with business logic
- treating Starter Free as a complete backend
- waiting too long to deploy and test the product surface
Next stepsLink to section
Validate a credible SaaS surface with mocked product flows.
Launch with real auth, billing, backend foundations, protected routes, and delivery.
Explore the primitives that power real SaaS interfaces.
Move from primitives to product-level flows such as tables, overlays, and async actions.
Build fast. Validate early. Upgrade when ready.
PyColors is built to help you reduce the distance between idea, product, launch, and revenue.