Claude has become a real part of my workflow lately — not just for writing code, but for the parts of freelancing that used to eat up hours: designing service covers, drafting case studies, structuring portfolio content, even thinking through pricing and positioning.
What I like is that it doesn't default to generic output. When I gave it my resume and actual project details, it used them — real project names, real tech stack, real context — instead of filler copy I'd have to rewrite anyway.
As a student building a freelance career in Flutter, .NET, React, and Python, having a thinking partner that helps turn raw work into something presentable (without losing the substance) has been genuinely useful.
Crenaly: a booking SaaS I designed and built end-to-end for appointment-based businesses in France: salons, barbers, beauty and wellness.
The core idea: when a client cancels, the freed slot is automatically offered to clients who asked for an earlier time. The first to accept gets it, their appointment moves in place, and the slot they leave is offered next. No double booking, no manual work.
Around it, a full product:
→ Branded booking page for each business, embeddable on their own site
→ Mobile-first booking flow, no account needed
→ Agenda, client management, team roles & permissions
→ Verified reviews, analytics, Stripe billing
Automatically offering a cancelled slot to the next client is such a practical feature for salons and barbers. Designing and building Crenaly end to end must have made those flows much tighter.