How Admix.software shipped a full dashboard in under a week
Admin dashboards are one of those things that look simple until you actually build one. Then you're three weeks in, drowning in data table edge cases, arguing with chart libraries, and wondering why role-based access control has seventeen different approaches and none of them feel right.
Admix.software skipped all of that. They shipped a full admin panel—user management, analytics, role-based access, the whole thing—in under a week. Here's exactly how.
The backstory
The team behind Admix had been selling ad management services manually. Spreadsheets, email threads, and a lot of copy-pasting between tools. They knew they needed a proper dashboard for their clients, but every agency they talked to quoted $15k minimum and a 6-to-8 week timeline. For a bootstrapped team, that was a non-starter.
One of the co-founders reached out to me after reading about how adworthy.ai was built with skills. His question was simple: "Can this work for a dashboard-heavy app? We need tables, charts, user management, and it has to look professional."
I told him to grab two skills: the SaaS Builder skill for the full-stack architecture and the shadcn Dashboard skill for the UI layer. $58 total.
Day 1: Foundation
They started Monday morning. Dropped both skills into the project, opened Claude Code, and described the app: an ad management platform where clients log in, see campaign performance data, manage their ad creatives, and handle billing.
By end of day one, they had auth working, the database schema defined, and a basic dashboard layout with a sidebar, header, and content area. The shadcn Dashboard skill was handling the UI composition. Proper use of shadcn/ui components, not the hacked-together version you get when an AI agent guesses at component APIs.
The SaaS Builder skill set up the backend. API routes, database queries with Drizzle, server actions for mutations. Clean separation between server and client code. The kind of architecture that doesn't fall apart when you add features later.
Day 2: User management and data tables
This is where most dashboard projects start to slow down. Data tables with sorting, filtering, pagination, and inline actions are deceptively complicated. The shadcn Dashboard skill includes patterns for all of this because every dashboard needs tables and getting them wrong means rebuilding them later.
By Tuesday evening, Admix had a user management panel where admins could invite team members, assign roles (admin, manager, viewer), disable accounts, and see login activity. The data tables supported server-side pagination, column sorting, and bulk actions. All built on top of TanStack Table with shadcn/ui styling.
Role-based access was the piece the co-founder was most worried about. Different users seeing different things based on their role. The SaaS Builder skill handles this with middleware-level checks and component-level guards. The agent set up the permission system once and it propagated across every route and UI element.
Day 3: Analytics and charts
Wednesday was for the analytics layer. Campaign performance charts, revenue tracking, user activity graphs. The shadcn Dashboard skill includes patterns for Recharts integration with shadcn/ui cards, so the charts actually match the rest of the UI instead of looking like they were dropped in from a different app.
They built a dashboard home screen with key metrics (total revenue, active campaigns, client count, conversion rates), trend charts for the last 30/60/90 days, and a recent activity feed. The data was real—pulled from their existing spreadsheet data that they imported into the database.
By Wednesday night, the core product was working. A client could log in, see their campaign performance, manage their team, and view analytics. An admin could see everything across all clients.
Days 4-5: Polish and deployment
Thursday and Friday were about the details. Loading states, empty states, error handling, mobile responsiveness, and deployment. The SaaS Builder skill includes Vercel deployment patterns, so getting it live was a single command.
They added a few touches that made it feel finished: a command palette for quick navigation (the shadcn Dashboard skill includes the cmdk pattern), toast notifications for actions, and a dark mode toggle. These feel like nice-to-haves but they're the difference between "it works" and "it feels like a real product."
By Friday afternoon, admix.software was live. Their first three clients were using it that same day.
What the co-founder told me
I asked him for an honest take after two weeks of clients using it. Here's roughly what he said:
"The dashboard feels like something a 5-person team built over two months. Our clients keep asking who our developer is. We spent $58 on skills and about $40 on Claude Code API usage. The agency quotes we got were $15k to $25k. I don't understand why anyone would pay that for a standard dashboard."
He also mentioned something I found interesting: the code quality was high enough that when they later hired a part-time developer to add a few custom features, the developer said the codebase was "surprisingly clean" and easy to work with. That's the skill doing its job. It doesn't just generate code that works. It generates code that a real developer can maintain.
The breakdown
| Factor | Agency quote | Actual (with skills) |
|---|---|---|
| Cost | $15k - $25k | ~$98 (skills + API usage) |
| Timeline | 6 - 8 weeks | 5 days |
| Features | Auth, dashboard, analytics | Auth, dashboard, analytics, RBAC, data tables, dark mode |
| Maintenance | Ongoing retainer | Self-maintained |
Why dashboards are a sweet spot for skills
Admin dashboards follow predictable patterns. Auth, tables, charts, forms, role management, settings pages. Every dashboard needs these things and they all work roughly the same way. That's exactly the kind of build where skills outperform everything else—the patterns are well-established and the skill encodes them from real shipped products.
If you're building any kind of admin panel, internal tool, or client-facing dashboard, the SaaS Builder skill plus the shadcn Dashboard skill is the combo. Same two files behind Admix. Same patterns. Same results.
Frequently Asked Questions
What skills were used to build Admix.software?
Two skills. The SaaS Builder skill handled the full-stack architecture—auth, database, API routes, billing, and deployment. The shadcn Dashboard skill handled the UI layer—data tables, charts, layout patterns, component composition, and theming.
How long did it actually take to build?
Under a week. Monday through Friday. The core dashboard with user management and analytics was functional by day 3. Days 4 and 5 were polish, edge cases, mobile responsiveness, and deployment. Clients were using it by Friday afternoon.
Can I build a similar admin dashboard with these skills?
Yes. The two skills together cover auth, user management, role-based access control, data tables with sorting and pagination, analytics charts, settings pages, and deployment. Any admin panel or internal tool follows these same patterns. You describe your specific data and features, and the agent builds it using the skill's architecture.
Do I need to know shadcn/ui to use the dashboard skill?
No. The skill teaches your AI agent how to use shadcn/ui components correctly—proper composition, theming, responsive layouts, data table patterns, and chart integration. You describe what you want in plain English. The agent handles the technical implementation.