FYC LABS
Phase 1 Build Proposal / 9.8.2026
For Spencer and the Discover Echo team

Publish on
Tuesday.
Without asking.

The front end moves off WordPress onto Next.js and Paigebuilder, so your team edits the site instead of filing tickets.

Phase 1 Build 3 Weeks / $7,500
The Situation

The site was
rebuilt in 2018.
It shows.

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.

The Investment
$7,500 Fixed price, billed 50/50.

One number, agreed up front. We carry the overrun risk. Half at signature, half at launch.

57 Hours of design + dev

Design and dev hours bundled, and that number is the scope spread total. Project management, design review, and QA break out there line by line.

Kickoff: TBD Ship: 3 weeks from kickoff
What We're Building

The front end,
rebuilt in 3 weeks.

01

Design foundation

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.

02

Home and contact

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.

03

Instrument pages

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.

04

Paigebuilder setup

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.

05

Hosting and deploy

The site lands on Google Cloud with a staging environment, a repo you own, and a deploy you can trigger yourself. Uptime and error alerts are wired before launch.

06

Tracking that survives

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.

The Difference

Two ways to run
a website.

The current setup

Every idea is a ticket.

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."

After the rebuild

Every idea is a prompt.

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."

WordPress, 2018 Next.js and Paigebuilder, 2026
From Discover Echo

"I can't do anything on this side because we're limited by the blocks that we've built."

Spencer Timme
Marketing, Discover Echo
The Timeline

3 weeks,
setup and build overlap.

KickoffLaunch, end of week 3
Design Foundation
W1
Environment + CMS
W1-2
Page Build
W2-3
Tracking + URLs
W3
QA + Cross Browser
W3
Launch + Handoff
W3

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. It also means a late change to the design foundation costs more than an early one.

The Scope / Part 01 of 02

User-facing interfaces.

Open any line for what's included
Interface Component Design Dev
  • Type, color, and spacing pulled from your live site
  • Header, footer, and navigation rebuilt as reusable components
  • Mobile breakpoints matched to what your visitors see today
  • Component set documented so future pages inherit it automatically
  • Every homepage region editable by prompt, including the hero
  • Instrument lineup pulls from the same content the product pages use
  • Existing analytics tags fire on the new page unchanged
  • Renders on phone and tablet at your current breakpoints
  • One template serves all 3 instruments, so changes land everywhere
  • Specs, imagery, and copy move into editable regions
  • Current URLs and page metadata preserved exactly as they are
  • Quote builder links keep pointing at quote.discover-echo.com, untouched
  • Submissions keep going to the same place they go today
  • Validation and a confirmation the visitor actually sees
  • Spam protection so the inbox stays usable
  • Built from the same component set, no new design work
Part 01 Subtotal 7h 20h
The Scope / Part 02 of 02

Backend, deploy, and project overhead.

Interface Component Design Dev
  • Content model built to match how your pages are actually structured
  • Prompt editing works from the chat panel or Claude on desktop
  • Staging preview before anything reaches the live site
  • Walkthrough session so your team can publish without you
  • Cloud environment provisioned with staging and production separated
  • Repository created in your name with deploy access for your team
  • One click deploy from Paigebuilder, with a tested rollback path
  • Uptime and error alerts wired before launch, not after
  • Full URL inventory and redirect map built before cutover
  • Tag and cookie behavior verified with Jill across both domains
  • Paid search landing pages tested against the new site pre launch
  • Page metadata carried over so rankings hold through the move
Part 02 Subtotal 0h 15h
+ Project Management 15% of total 6h
+ Design Review Floor, 10% of design 2h
+ QA + Testing 20% of dev 7h
Project Total 9h 48h
FYC LABS
Picking It Back Up

Ready when you are, Spencer.

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 $7,500 fixed, billed half at signature and half at launch. Blog and library migration stay outside this one until we've scoped them properly, so say the word on this piece and we'll get you on the build schedule.

Contact

Brian Hammond
VP of Sales, FYC Labs

Reach Me

bhammond@fyclabs.com
fyclabs.com

Proposal valid 14 days 9.8.2026
01 / 10