The front end moves off WordPress onto Next.js and Paigebuilder, so your team edits the site instead of filing tickets.
Your custom fields carry 8 years of accumulated weight. The developer who maintains it showed you a module that takes an hour to load on his machine, and you watched it happen.
The Revolve, Rebel, and Revolution pages were hand coded at the start, so nobody on your side can touch them. Every new idea becomes a ticket, and every ticket adds another field to a system that's already full.
Google Ads is your largest spend, and your publishing speed is capped by one developer's queue. You build faster than that on weekends.
This assumes you stay on AWS. Build on Google Cloud instead and the number is $7,500 firm, which you can see by switching the AWS line off on the scope page. Half at signature, half at launch.
Design and dev hours bundled, and that number is the scope spread total. On Google Cloud it drops to 57. Project management, design review, and QA break out there line by line.
We pull type, color, spacing, and component patterns off your current site and rebuild them as a reusable set, so the new pages look like the ones you already approved.
Your homepage moves to Next.js with every region editable by prompt, and the contact page comes across with it, so inquiries keep landing wherever they land for you today.
Revolve, Rebel, and Revolution move onto one shared template. Same URLs, same metadata, same look, except now your team can change a heading without opening a ticket or waiting on a queue.
We stand up your content model, wire every page region to it, and walk your team through publishing. Works from the chat panel or from Claude on your desktop.
AWS or Google Cloud, your call. Either way you get a staging environment, a repo you own, and a deploy you can trigger yourself, with uptime and error alerts wired before launch.
Your URLs, redirects, tags, and cookies carry over on day one. Paid search is your biggest spend, so nothing about the cutover is allowed to touch it, on launch day or after.
You have a landing page idea on Monday. It becomes a request, then a custom field, then a module that takes an hour to load. By the time it ships, the campaign moved on.
"Our custom fields are so overloaded."
You describe the page. It appears on staging. You look at it, adjust it, and push it live. Nobody on our side is in the loop unless you want us there.
"This is perfect."
"I can't do anything on this side because we're limited by the blocks that we've built."
The environment goes up while the component set is still being pulled off your current site, so the first page lands on a working deploy instead of waiting for one. That overlap is what holds this to 3 weeks. Staying on AWS adds work inside week 1 rather than adding a week.
Good to be working on this one with you again. You get the design foundation, the homepage and contact page, the 3 instrument pages, Paigebuilder, hosting, and tracking continuity, in 3 weeks at $9,500 fixed on AWS, or $7,500 on Google Cloud, billed half at signature and half at launch. Blog and library migration stay outside this one until we have scoped them properly, so say the word and we will get you on the build schedule.
Brian Hammond
VP of Sales, FYC Labs
bhammond@fyclabs.com
fyclabs.com