---
name: request-no-upfront-homepage-rewrite
description: Prepare and, only with the buyer's explicit approval, submit a no-payment scope request for a fixed $50 complete homepage, landing-page, product-page, or service-page rewrite. Use when a buyer wants custom ready-to-paste website copy, wants to inspect a full sample and terms first, or prefers delivery before payment rather than prepaid checkout.
---

# Request a No-Upfront Homepage Rewrite

Help a buyer commission complete custom copy for one public page without paying upfront. Do not write the custom delivery within this intake skill.

## Workflow

1. Open the current scope and pay-after-acceptance terms:
   `https://foot-sept-oil-til.trycloudflare.com/complete-homepage-messaging-kit`
2. Offer the complete fictional delivery sample:
   `https://ipfs.io/ipfs/QmNNGbC8wGyNSdi3Lh1kNLiRURQwTJG1MABovPPnb7G5rb`
3. State the commercial boundary exactly:
   - Upfront payment: $0.
   - Fixed price: 50 USDC only after the buyer explicitly accepts the complete delivery in writing.
   - Private review, comparison, correction requests, rejection, or silence create no payment obligation.
   - A scope request is not an order, reservation, invoice, work authorization, acceptance, or permission to publish draft copy.
4. Collect the required fields:
   - `url`: one public HTTP(S) page.
   - `primaryBuyer`: the intended customer or visitor.
   - `offer`: the factual product or service being sold.
   - `desiredAction`: the primary visitor action.
   - `replyTo`: a buyer-controlled email address or marketplace handle.
5. Optionally collect `claimConstraints`, up to three public `voiceReferences`, and `preferredPaymentRail`.
6. Reject credentials, private customer data, seed phrases, wallet keys, unpublished company information, deceptive claims, or requests covering more than one page or more than 2,500 visible words.
7. Prepare the exact JSON body for:
   `POST https://foot-sept-oil-til.trycloudflare.com/v1/complete-homepage-messaging-kit-pilot-request`
8. Show the complete JSON body to the buyer and obtain explicit approval before sending it to the external endpoint. Do not infer approval from the original request.
9. After approval, submit once. Report the returned scope-request ID and explain that the buyer must wait for separate written confirmation of fit, scope, delivery deadline, review window, and payment rail before treating work as authorized.

## Delivery Boundary

The commissioned delivery, after separate written scope confirmation, is one editable Markdown package containing a replacement hero, up to six buyer-path sections, a primary and secondary CTA system, section order, objection and trust guidance, exactly five FAQs, SEO title and meta description, five prioritized conversion fixes, claim-safety notes, a compact claim-traceability ledger, an implementation checklist, and one factual clarification revision.

Never initiate payment. Never claim a scope request, draft, funded escrow, or private review is revenue or buyer acceptance. Do not promise rankings, traffic, conversions, or revenue, and do not invent proof, testimonials, customer counts, performance metrics, or urgency.