Frontend Horizon
← All solutions

Build & Convert

Recurring Site Care

Monthly content + experiment cycle under Web Design & Development on a site you already own. Same hands every month, no surprise invoices.

Sprint-priced. No retainer lock. The first sprint is the read — you see the system before you sign for the build.

  • Census-grounded

    ACS, CBP & LEHD pulls

  • 60+ ICP cards

    Shipped, signed off

  • Outcome-locked

    One named outcome per sprint

  • No retainer trap

    Sprints, not rent

Engagement details

Pricing factors, in plain English.

No mystery line items. These are the specific inputs that decide how the engagement is sized and what ships at the end of it.

  • 01

    Number of pages owned in the care plan

  • 02

    Monthly content velocity (1, 2, or 4 pieces)

  • 03

    Number of live experiments per month

  • 04

    Reporting cadence — weekly or monthly

  • 05

    Hosting + uptime + security included

Questions operators ask before they book Recurring Site Care.

  • Is this just a maintenance retainer?

    It’s an experiment retainer with maintenance baked in. Every month the read names the next test; the test ships; the result rolls into the next month’s read. The site keeps moving.

  • What if our in-house team handles publishing?

    We sit alongside, not on top. Most clients use the care plan to give their team a senior pair on demand — we draft, they review and ship; or we ship, they review and approve.

  • Can I pause for a quarter?

    Yes — pause without penalty when the budget needs to land elsewhere. The site stays live; we just stop the monthly cycle until you say go.

Who actually does the work

John Cravey, founder and lead strategist
John
Matt Snider, head of build
Matt
Pablo Novelo, head of design
Pablo
Danny, head of discovery and ICP synthesis
Danny
Josh Grounds, senior engineer and recurring care
Josh