5 Real Things Students Built in Xero Coding (And What They Charge For Them)
Not hype. Not demos. Real products built by real people in 4 weeks — plus the exact numbers on what they charge clients for them.
The Credibility Gap
Every "learn to code with AI" course promises the same thing: you'll build real projects and the skills will pay off.
Most of them mean it. Almost none of them can show you what the payoff actually looks like in concrete terms.
This page is the exception.
What follows are five real builds from Xero Coding students — not polished demos staged for a landing page, but working tools that actual clients pay for today. Specific numbers. Specific problems. Specific people.
If you've ever wondered whether vibe coding produces things people actually pay for, or if it's just a skill you demonstrate but never monetize: this is your answer.
Marcus B. — Management Consultant → Client CRM ($2,500/client)
Background: Marcus came into the August cohort as a senior management consultant. Zero coding background. His problem: he was manually tracking client follow-ups in a spreadsheet, losing threads, and occasionally missing check-ins entirely.
What he built in 4 weeks:
A client CRM with three specific features that solved his actual problem:
- Contact database synced to Google Contacts
- Automatic follow-up reminders based on last contact date
- A dashboard that flagged any client he hadn't emailed in 14 days
The tech stack: Next.js, Firebase Auth, Firestore, Resend for email notifications. Deployed on Vercel. Total lines of Claude Code prompts to ship it: somewhere between 30 and 40, spread across 4 weeks of iteration.
What he charges:
Marcus showed the tool to two other consultants at his firm. Both wanted it for themselves. He's now charging $2,500/client as a one-time setup fee plus white-labeling the dashboard for their client roster. He's closed three clients since graduation.
What it actually proves:
You don't have to build for strangers. Marcus solved his own problem, and the fact that it solved his problem credibly is the only testimonial his next client needs.
Sara K. — Marketing Manager → Freelance Dashboard Projects ($2,400/project)
Background: Sara had done basic HTML and CSS years ago — enough to know what a div was, not enough to ship anything. She came in wanting to build internal tools for her marketing team.
What she built in 4 weeks:
A marketing performance dashboard pulling from Google Analytics, Facebook Ads, and Mailchimp via their respective APIs. The dashboard showed all three channels in one view, with a weekly trend line and a "cost per lead" calculation that had been living in a spreadsheet.
The build was messier than Marcus's. Sara hit three separate CORS errors, a Google OAuth scope issue, and one complete rebuild when the component architecture got too tangled. Each time: described the problem to Claude Code, got the fix, moved on.
What she charges:
Sara pitched the dashboard to two external marketing clients she had relationships with from her agency days. Both said yes. She charges $2,400 as a flat project fee to build a custom version for each client's specific data sources.
The part that surprised her:
"I thought I'd have to explain what vibe coding was. Nobody cared. They cared that it pulled their numbers automatically and looked good. They didn't ask how I built it."
Clients buy outcomes. The technology is your problem, not theirs.
Jordan S. — Freelance Designer → Recurring SaaS Revenue ($200/month)
Background: Jordan is a freelance designer who'd never shipped code. He came in explicitly because he wanted to own the product layer — not just the design layer — of the tools he built for clients.
What he built in 4 weeks:
An internal project tracker for freelancers. Features: project status board, automated invoice reminders (Resend), time tracking per project, a client-facing portal where clients could check project status without emailing him.
Jordan's build took the longest to stabilize because the client-facing portal required Firebase security rules that were tricky to get right. The rule: clients can only see their own project status, not other clients' data. This took two full sessions to nail, plus one rule rewrite after he accidentally let all authenticated users read all projects.
What he charges:
Jordan's approach was different from Marcus and Sara. Instead of building for clients, he turned the tool into a product. He deployed it as a SaaS at a subdomain, charges $200/month, and has signed up four freelancers from a Slack community he's been in for years.
$800/month recurring revenue from a tool he built in week 4 of a bootcamp. He's iterated on it every month since.
The key move: Jordan didn't try to build for everyone. He built for freelance designers specifically — a niche he understood deeply — and priced it low enough that the "should I pay for this" decision took about 30 seconds.
Aisha W. — Healthcare Consultant → Recurring Client Revenue ($3,000/month)
Background: Aisha worked in healthcare consulting, helping clinics with operations. She saw the same broken intake processes at clinic after clinic and had always assumed "someone would build something for that." In the cohort, she decided she'd be that someone.
What she built in 4 weeks:
A client intake automation system:
- A customizable intake form (Aisha's clients are clinics, so the form collects patient info, insurance details, and appointment reason)
- Form responses saved to Firestore, one collection per clinic
- Automated confirmation email to the patient via Resend the moment they submit
- A weekly digest email to the clinic admin showing all new intakes, pending reviews, and completed intakes for the week
Aisha built the base system in weeks 1-2. Weeks 3-4 were all iteration: making the form fields configurable, adding the digest email, fixing a date-formatting bug in the digest that showed the wrong week.
What she charges:
Aisha landed her first clinic client in week 3 of the bootcamp — before she even graduated. She pitched it as a "pilot program" at no cost for the first month. The clinic renewed at $1,500/month after 30 days. She's now running three clinics at $1,000-$1,500/month each: $3,000/month recurring.
The move that made it work:
Free month first. Not free forever — free for 30 days with a clear renewal conversation at the end. Clinics with budget constraints almost always say yes to a free pilot, and after 30 days of the tool working, the renewal is rarely a negotiation.
Ryan T. — Operations Manager → Project Client ($3,000/project)
Background: Ryan managed operations for a mid-size distribution company. He'd watched the reporting team spend every Monday manually compiling the same Excel report from four different systems. His goal coming in: automate that specific process.
What he built in 4 weeks:
A reporting automation bot:
- Connects to two internal data sources via REST APIs (he worked with the IT team to get read-only API credentials)
- Pulls the same data fields the manual Excel report requires
- Formats them into a structured report on a schedule (every Monday at 6AM)
- Delivers the report via Slack message to the operations channel and email to the three people who needed it
Ryan's build was the most technically narrow of the five. It does one thing — produces one report, on schedule, automatically. That one thing was saving three people three hours every Monday.
What he charges:
His company hired him to build the same automation for two other report types at $3,000/project. He's also quoted the same system to a former colleague at a different company who has the same problem.
What this one proves:
You don't need a product. You don't need a SaaS. You don't need recurring revenue to justify the skill. One automation, one company, one problem — and the first conversation is with the people who already trust you, not cold leads.
What All Five of These Have in Common
Five different people, five different backgrounds, five different products. But look at the pattern:
They all built for a problem they already understood. Marcus knew consulting. Sara knew marketing. Aisha knew healthcare operations. Jordan knew freelance workflows. Ryan knew his Monday morning report. None of them invented a problem — they automated one they already lived with.
They all started narrower than they planned. Every cohort student comes in with a bigger idea than what they ship in week 4. That's not failure — that's the right constraint. The narrow version is the one that works. The bigger vision is what they're building now.
None of them waited until they felt "ready." Sara's dashboard had a CORS error when she showed it to her first client. Jordan's project tracker was missing half the features he wanted. Aisha's intake form was missing the weekly digest when the first clinic agreed to try it. Working beats polished. Always.
They all had the same toolkit: Claude Code, Firebase, Vercel. A $0/month stack that scales to real users. The tools are not the bottleneck — they never were.
The question isn't whether vibe coding produces real results. These five people are the answer to that question.
The question is whether you'll ship something, or keep researching the right time to start.
---
Xero Coding is a 4-week cohort, max 30 students. You leave with something built, not just knowledge you haven't applied. The next cohort starts soon.
Use EARLYBIRD20 at [/bootcamp](/bootcamp) for 20% off while seats remain.
Not ready to commit? Book 30 minutes at [Book a free call](https://calendly.com/drew-xerocoding/30min) — no pitch, just a real conversation about your idea and whether the cohort is the right environment to build it in.