Five Up DesignsProcess & terms
How a Five Up Essential build actually happens
The same standardized pipeline runs for every build — that consistency is what keeps the price at $249 and the timeline predictable. Nothing is charged until you choose to publish.
Qualification
You tell us about your business through the qualification form and we confirm Five Up Essential is a fit — no payment collected here or at any step until you decide to publish.
Domain & access
We connect your existing domain, or help you register one, and set up the access we need to build.
Content intake
One structured intake cycle — you supply your logo, copy, contact details, and images in one organized pass.
Template assignment
We assign the approved template that matches your business type and page needs.
Build
We configure the template with your brand, content, and pages — a free working draft, not a mockup.
QA
We check the build for broken links, layout issues, and mobile behavior before anyone outside the team sees it.
Client review
You review the free draft and request changes for as long as you need — no charge and no clock running on this part.
Publish
When you're happy with the site and ready to go live, you complete the one-time $249 payment through the site itself. That's the only payment in this entire process, and it happens on your timeline, not before.
Launch
The site goes live on your domain, hosted on Cloudflare's global network with SSL in place — hosting itself is never a separate fee.
Post-launch check
A short check-in after launch to confirm everything is working as expected in the real world.
Managed-care activation
Your included update year begins, and you're set up to submit standard update requests going forward.
30-day check-in
About 30 days after launch, we check in on how things are going and remind you the care plan is there ($49/year, no commitment) whenever you want it.
One important timeline note
The production clock starts once you've supplied all required content, assets, and access — this keeps timelines fair to everyone. A build can't move through content intake, template assignment, or QA faster than the content it depends on arrives.