> ## Documentation Index
> Fetch the complete documentation index at: https://docs.superun.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Demo first, Build later

> Don't wire login/DB before rules settle — finish Demo, then Build in slices.

Jumping into Build (login, DB, permissions, admin) as soon as UI looks “good enough” often causes the most rework: one rule change can touch UI, data, and logic at once.

### Save credits: Demo first, then Build

1. After look-and-feel is settled, finish a **Demo** with test data — don’t rush Build.
2. Walk the core flow as a real user: entry, jumps, fields, required inputs, login necessity, result pages.
3. Enter Build only when structure, content, and product rules are mostly fixed.
4. Build in slices — ship the core path first, then add the next piece.

### Example

For booking: finish “submit booking” first; then login, cancel, notify, and admin.

### Note

Don’t linger forever in Demo polishing trivial details either — once the core task works, move on.

## Related docs

[Ideation and creation](/superun/tips-tricks/ideation-and-creation)

## Original WeChat post

[Original WeChat post](https://mp.weixin.qq.com/s/Hr6Jmrp0p95a7OwongL2vw)