Work
Inventory dashboard — a Studio demonstration
A fictional wholesale company needs stock visibility across two warehouses. Used as the Studio’s reference build: prompt → plan → generated app → sandbox preview.
Illustrative example — not a client engagementNext.js · TypeScript · Convex · Tailwind CSS
- Context
- This is the demonstration project that ships inside AlgoSweden Studio. It exists so the product can be evaluated honestly without real client material — and so this site never needs an invented "customer".
- Problem
- A fictional wholesaler tracks stock in spreadsheets across two warehouses; counts drift, reorder points are guesses, and nobody trusts the numbers on Mondays.
- Constraints
- The company is fictional; the constraints are not. The build runs through the real demo pipeline: templates come from the Studio’s allowlist, the sandbox enforces hard CPU, memory and time limits, and no external services or credentials are available — everything must work in a cold, disposable environment.
- Role
- Generated end-to-end by Studio agents (planner → architect → builder → reviewer); the same pipeline any customer project runs through.
- Architecture
- Single Next.js application with a Convex data layer: articles, locations, stock movements, reorder rules; server-enforced workspace scoping; sandbox-built preview.
- Key decisions
- Three calls shaped the build. Seed data is generated in code rather than imported from anywhere — the demo must boot in a fresh sandbox with zero credentials. One Next.js application instead of a service split — at this size, inspectability beats architecture theatre. And a checkpoint lands after the reviewer step, so every generated change can be inspected and rolled back before it reaches the preview.
- Outcome
- No business metrics are claimed — it is a demonstration. What it proves: the pipeline produces a working, inspectable, exportable application with honest failure states.
- Evidence
- Reproducible on the Studio Starter plan: the demo project is one click from the dashboard.
- Confidentiality
- None. This is a public demonstration: the prompt, the plan, the generated code and the preview are all open for inspection. Nothing is anonymised, because nothing here is client material.