How to Brief a 72-Hour WordPress Build

A 72-hour build does not fail because WordPress is slow. It fails because the brief is a vibe and the feedback is a trickle.

This is how to brief us, or anyone working on a hard clock. The pipeline itself is in How we build custom sites in 72 hours and process.

Send this before kickoff

• What you sell, in one paragraph. Not a manifesto. The sentence a stranger would repeat.
• The pages you actually need. Count them. Core is up to 10. Complete is up to 20. Extra pages are quoted flat before you pay. See pricing.
• Two sites you respect, and why. “Make it pop” is not a note.
• Logo, colors if you have them, and the real photos. Stock is a last resort.
• Who answers in 48 hours. One name. A committee is how 72 hours becomes six weeks.

Do not send this

• A 40-comment Figma file of a homepage you already rejected.
• Six equally ranked “priorities.”
• Copy you plan to rewrite after launch. Launch copy is the brief.

The 48-hour feedback rule

You get one complete preview. You send one consolidated round. We apply it. Then it ships. Open-ended notes after that are extra revision rounds at $49 each, listed on pricing.

If the offer is still being invented, wait. DIY is fine for an idea. A real business with countable pages can start on contact. 50% reserves the slot. Brief in 30 minutes.

If you are still choosing a package, the cost calculator maps pages and a store to Starter, Core, or Complete.