ROAST MY WEBSITE

the audit is the cheapest way into this studio and the hardest thing to sell, because it is the one product a buyer cannot inspect before paying. a website they can look at. a design system has a figma file. an audit is a promise that a stranger will tell them something useful about their own site, and every agency on the internet makes that promise.

the objection is never "$500 is too much". it is "$500 for what, exactly."

the answer is to give the thing away in a form that proves the format without doing the work. roast my website runs the same pass a paid audit opens with — read the page the way a buyer does, on a phone, cold — and returns it automatically, for $10 a pack.

the decision that shaped everything else: the moat is the knowledge base, not the model. anyone can point a model at a url. what makes a roast worth reading is the accumulated set of things that are actually wrong with small product sites, written down, versioned, and improved every time a real audit finds something the automated pass missed. the model is a renderer for that. swap it next year and the product survives.

so the funnel runs one direction, deliberately: free roast → paid audit → project. every roast ends by naming what the automated pass cannot do, which is the part i charge for.

it had to bill real money, which is a different engineering problem from looking like it bills real money.

pixelform holds no razorpay credential and neither does roast my website. both are satellites of devsforfun id, which is merchant of record: the satellite asks the hub to mint an order, the hub prices it from its own plan row and ignores whatever amount the satellite sends, and the browser gets back an order id and a public key. a client-side price cannot be tampered with because the client never states a price.

the second hard part is that the two products have to agree about money across a network boundary. a roast credit pack is worth $200 off the audit, so the audit checkout has to ask roast my website whether a code is real. the distinction that took the longest to get right is that an *invalid* code and an *unreachable* coupon service are different outcomes. collapse them and you either tell a paying customer their earned discount is fake, or you quietly charge full price during an outage. codes are consumed once, after payment, enforced by a unique constraint rather than a check-then-act.