// services

Fixed-scope packages. Senior thinking. No handoff.

Four ways to work together. Each package is a productized deliverable with a clear outcome, timeline, and price floor. If none of these fits, grab a 30-minute call and we'll scope something that does.

01 1-2 weeks

Architecture Review

For teams who need a second set of senior eyes before writing a single line of code.

// outcome

A written architecture decision record (ADR) with platform recommendations, risk register, and a prioritized sequencing plan you can take to your engineering team or a build partner.

// for who

Founders, CTOs, or Heads of Marketing about to commission a new platform, replatform, or multi-region rollout.

// deliverables

  • Stack evaluation across 3-5 candidate platforms
  • Architecture decision record with trade-offs documented
  • Data model and integration sketch (CMS, forms, payments, email)
  • Risk register with mitigation paths
  • 90-minute walkthrough call + Q&A

// process

  1. 01 Discovery call (60 min)
  2. 02 Async review of current systems
  3. 03 Decision document drafted
  4. 04 Walkthrough + revision
most requested
02 2-3 weeks

CMS & MarTech Audit

The audit I ran on LumApps - 3,489 pages, 5 languages, 36 CMS collections - productized.

// outcome

A full inventory of your web + marketing stack, gap analysis, and a prioritized punch list of fixes ranked by revenue impact. Built from real crawl data, not a checklist template.

// for who

Marketing ops leaders who inherited a system they didn't build - or teams drowning in MarTech tools with no source of truth.

// deliverables

  • Full Playwright crawl (up to 2,500 pages)
  • MarTech stack inventory (analytics, forms, tracking, email, CRM)
  • CMS schema audit (collections, fields, relationships)
  • Core Web Vitals + INP benchmark per template
  • Prioritized fix list with effort/impact scoring
  • Executive summary + technical appendix

// process

  1. 01 Kickoff + access handoff
  2. 02 Automated crawl + manual audit
  3. 03 Findings synthesis
  4. 04 Delivery call + handoff
03 3-4 weeks

Migration Strategy

For replatforms where getting the cutover wrong kills traffic, revenue, or trust.

// outcome

A weighted scoring model that tiers your existing content into migrate / review / redirect, a full 301 redirect map, a target-platform schema design, and a build-ready spec your engineering team can execute against.

// for who

Teams moving off WordPress, Webflow, custom stacks, or between CMS platforms with SEO equity at stake.

// deliverables

  • Everything in the CMS & MarTech Audit
  • Page-level scoring model (GSC + analytics weighted)
  • Tiered content plan: migrate / review / redirect
  • Full 301 redirect map (canonical + legacy)
  • Target-platform schema design
  • Phased cutover timeline with rollback plan
  • Build-ready technical spec

// process

  1. 01 Audit (Package 02)
  2. 02 Scoring model calibration
  3. 03 Schema + redirect design
  4. 04 Cutover plan + handoff
04 4-12 weeks

Full Systems Build

Architecture through shipped product. One accountable owner.

// outcome

A production system: designed, built, deployed, documented. CMS wired, integrations live, content seeded, team trained. No handoff friction because there's no handoff.

// for who

Founders or teams who want one person accountable for the whole system - not a designer, then a dev, then an SEO, then a QA, then a handoff.

// deliverables

  • Everything in packages 01-03 as needed
  • Design system + component library
  • CMS schema + Studio configuration
  • Integrations (Stripe, Resend, analytics, CRM)
  • Deployment pipeline + hosting setup
  • Content seeding + editor training
  • Operations guide for ongoing management

// process

  1. 01 Architecture Review (Package 01)
  2. 02 Fixed-scope SOW
  3. 03 Build in 1-2 week sprints
  4. 04 Launch + handoff

// faq

Common questions

Do I need to pick one package, or can we combine?

Most engagements start with an Architecture Review and expand from there. Package 02 and 03 are discount-bundled when booked together. Package 04 is always preceded by 01 - I don't build what hasn't been designed.

Why fixed-scope instead of hourly?

Hourly incentivizes me to drag things out. Fixed-scope incentivizes me to ship. You get a clear deliverable, a clear price, and a clear timeline. If scope changes, we write a change order - transparently.

What tech stacks do you work in?

Astro, Next.js, Sanity, Webflow Enterprise, WordPress, Cloudflare, Vercel, Hostinger, Stripe, Resend, Pardot, HubSpot, GTM, GA4, Playwright. I'll recommend the right stack for your use case - not the one I like most.

Do you work with agencies or only direct?

Both. Agencies bring me in for architecture, migration, or technical SEO engagements their in-house team doesn't cover. White-labeled reports available.

What if I just need a quick call to figure out what I need?

Book a 30-minute discovery call on the contact page. No charge, no pitch - I'll tell you what I think the right next step is, even if it's not hiring me.

Not sure which package fits?

Book a 30-minute discovery call. No charge, no pitch. I'll tell you what the right next step is, even if it's not hiring me.

Book a discovery call