Unequal tiles encode priority: a bigger tile is a more important metric, so the hierarchy reads before you have read a single label.
What we build
Web App
A working tool — sign-in, data, dashboard — not just pages.
A website tells people about your business; a web app RUNS part of it. Bookings, orders, customers, staff — screens with real state behind them.
Describe the tool and the builder generates a working app screen: navigation, tables, forms and actions. Full SaaS scaffolds add authentication, a database with row-level security, and payment rails as real source code.
Optional — a logo, a photo of your place, or a screenshot of a site you like. Drag them here. Nothing is stored after the build.
What a build includes
- A working app screen: sidebar, stat cards, tables, working modals
- Full-stack scaffold on request: Supabase auth, Postgres with RLS, Razorpay/Stripe webhooks
- Source code you own — hand it to any developer without lock-in
- Refine by chatting: add a column, a filter, a new screen
How to use it
- Name the job the tool does: 'track my workshop's orders', 'let staff manage bookings'
- List the columns and actions you need — who uses it and what they must see
- Build, then refine the screens in plain English
- For the full application with accounts and payments, see Full SaaS on /pricing
What this type has to get right
- The most important number sits top-left — eye-tracking shows an F-shaped scan: across the top, then down the left edge
- One number per tile, with its unit and change inline; every chart shares one colour scale
- Cards reflow at smaller widths instead of shrinking, so density survives the phone
Where it usually goes wrong: Every tile the same size and weight — nothing is ranked, so the user reads all of it to find one thing.
Designs that suit a web app
Every one of these is a real design language, and every card below is that language's own page shrunk down — not a picture of it. Open one to see it full size, or name it in your prompt and the build comes out in it.
Dark chrome recedes and lets charts and code carry the colour — the reason editors and analytics tools have used it for decades.
A strict grid and one type family in a few weights are what make forty numbers comparable instead of decorative.
On a dashboard every non-data pixel competes with the data. Restraint here is function, not fashion.
Right for a floating command palette or overlay — but never the data layer itself, where translucency destroys contrast.