Last month I shipped RateForge, a free freelance rate calculator that generates AI-powered, shareable client reports. Total build time: a weekend. Ongoing maintenance: zero. Here's the full story, what worked, and what I'd do differently.
The problem
Every freelancer I know has typed "how much should I charge as a freelancer" into Google at 2am. The answers are always vague blog posts: "it depends on your experience!" Thanks.
What freelancers actually want is a number. Better yet, a number they can show a client to justify their rate.
So RateForge does two things:
- Calculates your hourly and project rate based on your skills, experience, location, and desired income
- Generates a clean, AI-written rate report you can share with clients via a link
That second part is the differentiator. A calculator gives you a number. A shareable report gives you leverage in a negotiation.
The stack (spoiler: it's boring on purpose)
Frontend: Next.js, deployed free on Vercel
AI reports: LLM API call that turns the calculator inputs into a professional one-page summary
Database: none for the calculator itself. Reports are saved to a database so each one gets a permanent shareable link the client can open anytime
Cost to run: effectively $0 at current traffic
I build all my sites this way. I call the model Build, Push, Sleep: build it with AI assistance in days, push to production, then leave it alone to earn passively through ads and affiliates. No feature roadmap. No sprint planning. If it needs babysitting, I built it wrong.
How AI changed the math
Two years ago this would have taken me a month. Here's roughly how the weekend broke down:
Saturday morning: scoped the rate formula. Base rate from role and experience, adjusted for location cost-of-living, overhead, non-billable time, and target income
Saturday afternoon: AI pair-programmed the entire calculator UI. I mostly reviewed and tweaked
Sunday: built the report generator, wrote the prompt that turns raw inputs into a client-friendly document, polished, shipped
The rate formula was the only part that needed real thought. Freelancers systematically underprice because they forget that a 40-hour week is maybe 25 billable hours, and that they pay their own taxes, insurance, and tools. The calculator bakes all of that in so users don't have to.
What I learned
- The shareable artifact is the growth loop. Every report a freelancer sends to a client is a tiny distribution channel. I didn't have to build "viral features." The core use case is the marketing.
- Free tools rank. Utility pages with a clear job ("calculate X") earn links and rank on long-tail searches without ongoing content work. Perfect fit for a zero-maintenance model.
- Constraints make you ship. Giving myself one weekend forced ruthless scope cuts. No accounts, no saved history, no dashboard. Just the tool. Nobody has asked for the features I cut.
The honest downsides
- Zero maintenance means zero iteration. If a competitor ships a better version, I won't be racing them
- AdSense on a low-traffic tool pays in coffee money at first. This is a portfolio game: many small sites, compounding over years
- "Sleep" only works if the build quality is solid up front. Cutting corners on day one means the site quietly breaks on day 90
Try it
If you freelance, run your numbers through RateForge. It takes about a minute, and the report is free. You might discover you've been underpricing by 30 percent. Most people are.
Questions about the build, the formula, or the Build, Push, Sleep approach? Ask in the comments. I read everything, even if the site never gets another commit.
Top comments (0)