Building a 3D print shop SaaS across 20 parallel agent workspaces
A heavy day driving one SaaS to a working v1 through many parallel agent workspaces: inventory, orders, queue, dashboard, plus animated docs and an AWS migration study.
A very busy day. Almost everything pointed at one product: a SaaS to manage a 3D printing workshop. I ran it across many parallel agent workspaces at once, each picking up a different task off the same backlog.
3d-print-saas-management-system
This was the core of the day. I split the backlog into independent tasks and let separate workspaces work them in parallel, then merged the results. By the end the app had a real shape: Supabase auth and an app shell, basic registrations, filaments and per-location stock with quick adjust, real-time inventory with low-stock alerts, quotes and orders with payments and pending balances, a production status flow (waiting, printing, done), a reorderable demand queue, a user CRUD, and an audit log view. The day closed with a visual dashboard tying it together (low stock, queue, production, payments).
A few decisions worth keeping: forms standardized on React Hook Form plus Zod, with that rule written into the agent and skill docs so future tasks follow it. Client pickers moved to react-select with inline search and create, since "either search or register" was bad UX. I also drove the running app in Chrome through MCP, clicking through it like a real user to validate against the PRD and specs, which surfaced real gaps (a broken /estoque nav link, missing stock location on a form).
I also gave the project a front door: a public landing at the root, a redirect to the dashboard when logged in, and animated module docs at /docs built with Remotion and Framer Motion, including a rendered video walkthrough from signup through stock, order, and dashboard.
itop.com.br
Spent time on an infra question instead of code. The VPS with Dokploy has been flaky, so I weighed moving this project to AWS, partly to get the hands-on AWS experience the market keeps asking for. Walked through Elastic Beanstalk, ECS with Fargate, and an SST plus ECS plus Fargate setup, and which managed database fits. No migration yet, just a clearer map of the options.
Tooling
Small quality-of-life win: wired up a terminal command to open the Zed editor in the current directory, the same way I launch Cursor with cursor ..
Running one backlog through twenty workspaces in a day is a strange new rhythm: less typing, more orchestrating and reviewing.