A campus laundry service turned a $100 class project into six-figure school-year sales with 80% margins.
80% margins · $5,000 in the initial two-week project period
“We did $5,000 in revenue in a two-week period.”
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Alex Smereczniak and two partners started Wakewash as a freshman-year business project at Wake Forest. The class gave each group $100 and asked them to take an idea to market. Wakewash reported $5,000 in revenue during a two-week period, then grew into a campus laundry business doing a couple hundred thousand dollars per school year with 80% margins. The founders sold it after graduation for a mid-six-figure price. The business stayed student-run: Alex describes seven or eight generations of students buying, operating, and selling it. The university licensed use of its name, and the founders learned hiring, vendor contracts, marketing, and partnerships through the operation. These are founder-reported figures from an interview, not audited statements. The durable asset was a campus service plus a succession path that let new students take over.
Wakewash found a ready-made audience on campus: students who needed clean clothes and parents who wanted a practical service for the school year. The founders opened a booth for two weeks, and parents bought packages covering a semester or the full academic year.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: Alex Smereczniak reports the $5,000 project-period revenue, couple-hundred-thousand-dollar school-year revenue, 80% margins, and mid-six-figure sale. These are founder-reported interview claims; no independent financial records are cited. The interview provides no package pricing or cost breakdown.
For Wakewash, a campus laundry service can collect its first dollar by selling a defined package before the first pickup: a semester or school-year plan gives a family a clear outcome and gives the operator working cash for supplies and labor. Keep the first offer narrow.
Wakewash’s flywheel came from combining a recurring campus need with a new group of student operators every few years. A parent who bought a semester or annual package had a reason to recommend the service to another family.
For Wakewash, the difficult stretch is likely to arrive between a successful campus launch and proving another institution will approve the same model. Alex describes expansion conversations where students wanted to participate but university stakeholders hesitated over risk and liability.
Wakewash was a campus laundry service organized around students and the academic calendar. Families could buy a semester or school-year package, and the student founders handled the operating work, including hiring, vendor relationships, and university negotiations. The available profile does not establish a software product or detail the wash-and-fold workflow, so the useful product description is the service promise: make laundry easier for students living away from home, with a campus team responsible for delivery. A modern version should make the interface simple. A student should know what to bag, where to leave it, when it will return, and who can resolve a problem. A family should understand package coverage and payment. Lightweight tools can coordinate the work, but the defensible part is reliable campus execution and continuity across student leadership changes.
The reported model is package-led service revenue. Parents paid for laundry coverage by the semester or school year, concentrating sales around campus events and letting the team plan demand against a known academic period. Alex reports a couple hundred thousand dollars of revenue per school year and 80% margins. The interview does not break down package prices, labor costs, or margin accounting, so those figures remain founder-reported rather than a forecast. A new operator should price around expected order frequency, route labor, cleaning costs, lost-item handling, and the school calendar. Offer one simple package first, then add an option only after customers repeatedly request it. Record contribution margin by residence or route; campus-wide revenue can hide an unprofitable service area. The seasonal package structure works best when service costs stay predictable through the term.
Wakewash’s strongest operating signal is the reported 80% margin, paired with the founders’ work on hiring, vendor contracts, marketing, and university partnerships. The interview gives no technology stack or detailed cost ledger. The initial class exercise assigned each team $100, but that is not a verified total startup budget. A new version can begin with a mobile-friendly order form, a package ledger, route sheets, and a shared support inbox. Automate only after repeat orders expose a manual bottleneck. Keep garment tracking and customer communications tied to an order ID, and reconcile each completed order against payment and vendor costs. Margin discipline matters more than software sophistication here: measure labor per stop, rewash rates, refunds, supplies, and route density before investing in custom systems. Use simple tools until they fail under real service volume.
Copy Wakewash’s narrow first market, the package aligned to a school term, and the handoff system that let students inherit a real operation. Its founders also negotiated university permission for the Wakewash name, a reminder to settle campus trademarks and access before printing materials. Change the model by documenting every role and customer promise from the start. A modern operator can use a booking page, QR-coded laundry bags, pickup reminders, and a shared issue log, while keeping service available to students who do not want an app. Test packages with one residence cluster before committing to campus-wide routes. Build a transition plan that gives the next student team pricing, vendor contacts, university approvals, and a live customer roster. Seasonal demand and student turnover are advantages only if operating knowledge survives graduation.
The main risks are seasonal demand, dependence on campus access, and execution slipping when student operators graduate. A service can look profitable during move-in while underperforming during breaks or summer. The interview also shows an approval hurdle: other universities expressed concern about liability even when students were interested. Wake Forest’s name required a license, so trademark rights and residence access need written agreements. Laundry adds operational risks such as lost items, missed pickups, quality disputes, and vendor dependence. Test the full calendar, not only the initial sales window, and retain cash for off-season volume. Keep parent and student expectations clear in the package terms, including service boundaries and complaint resolution. The reported 80% margin is encouraging but cannot replace local unit-economics work. If quality or continuity fails, word of mouth can reverse quickly in a small campus community.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,452 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click