I Built a BPS Website: Build, Push, Sleep

Issam Hamed — Tue, 14 Jul 2026 17:42:09 +0000

What is a BPS website?

BPS stands for Build, Push, Sleep. It's a simple framework I use for shipping side projects:

Build it fast with AI assistance
Push it to free hosting
Sleep while it runs itself

No servers to babysit. No monthly bills. No accounts to manage. The site just exists, serves users, and quietly earns.

My latest BPS project is DocForge, a free invoice, receipt, and quote generator. Here's how the philosophy shaped every decision.

Rule 1: Zero running costs

If a project costs money every month, it needs to earn money every month. That's pressure. BPS removes it.

DocForge runs entirely on free tiers:

Next.js on Vercel (free hobby tier)
Client-side PDF generation so there's no backend doing heavy work
No database for users because there are no accounts

The PDF part is the key trick. Every document is generated in the visitor's browser. Nothing is uploaded, nothing is stored, nothing is processed server-side. That's not just a privacy feature (though it is one), it's what makes free hosting viable. The server ships static-ish pages and the user's machine does the work.

Rule 2: Zero maintenance by design

Every feature I didn't build is a feature that can't break:

No signup means no auth bugs, no password resets, no email deliverability issues
No stored documents means no storage costs, no GDPR headaches, no data breaches
No backend jobs means nothing to monitor at 3am

The entire product is a form, a live preview, and a download button. That surface area is small enough that once it works, it keeps working.

Rule 3: Traffic that compounds while you sleep

A BPS site can't rely on you promoting it forever. It needs traffic that grows on its own, which means SEO.
DocForge is structured as a programmatic SEO play:

Tools by document type: invoice, receipt, quote, purchase order, pay stub, credit note, delivery note, letterhead
Invoices by profession: photographer, contractor, tutor, web developer, and more, each with tailored defaults and copy
Invoices by country: US sales tax, UK VAT, Canada GST/HST, India GST, and so on, with correct labels and currency

Each page targets a real long-tail search like "photographer invoice generator" or "VAT invoice UK". The important part: every page is a genuinely different, working tool with unique guidance. That's what keeps it on the right side of Google's thin content rules. Doorway pages get penalized. Useful variants don't.

Rule 4: Monetize without ruining the product

The tools are 100% free and fully functional. Revenue comes from two passive sources:

A single discreet ad placement
Affiliate links to accounting software, for users who outgrow simple documents

No paywalls, no locked features, no "free trial" bait. The free product IS the marketing.

The build itself

Stack: Next.js, TypeScript, Tailwind, shadcn/ui, deployed on Vercel.

I built it AI-assisted, working in fast iterations. The repo even has a worklog and screenshots of each iteration if you want to see the process: github.com/issamovitch/thedocforge

Total infrastructure cost so far: $0 plus the domain.

Why this works for solo builders

Most side projects die from maintenance fatigue, not lack of ideas. You ship something, it needs attention, life happens, it rots.

BPS flips that. Design for zero upkeep from day one, and the project survives your attention span. The worst case is a free site that helps people make invoices. The best case is a small asset that grows in the background while you build the next one.

Try it: thedocforge.com

Questions about the stack or the SEO structure? Ask below.

I Built a Freelance Rate Calculator With AI, Shipped It, and Walked Away

Issam Hamed — Mon, 13 Jul 2026 20:12:02 +0000

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.

DEV Community: Issam Hamed