Rescue, rebuild, or stabilize the WordPress system.

Pick the path by site state: broken now, not worth patching, or fragile but salvageable. Systems work comes after the base holds.

Rescue firstBroken sites need containment before rebuild talk.
Rebuild when neededReplacement only makes sense when patching costs more risk.
Stabilize before growthAdd systems only after the base can hold them.

SERVICE_PATH_ROUTER()

STATE_TO_SCOPE

RESCUE // Broken or unsafe now

Use this when the site is actively costing money, trust, leads, or staff time. Contain the failure first.

$2,000-$5,000 for full rescue after triage.

Website Rescue ->

REBUILD // Not worth patching

Use this when the old site is too slow, fragile, bloated, or poorly owned to keep repairing.

Essentials: $2,500-$6,000. Detailed Growth: $6,000-$12,000.

WordPress Rebuilds ->

STABILIZE // Fragile but salvageable

Use this when the site runs, but updates, hosting, speed, security, forms, or plugins keep creating risk.

$750-$1,500 for common stabilization fixes; larger cases are scoped.

Stabilization ->

EXTEND // Stable enough to expand

Use this for WooCommerce, catalogs, CRM automation, integrations, and custom workflows after the base is stable.

$7,500-$45,000+ by stage for serious systems work.

Growth Systems ->

AUDIT // Needs diagnosis

Use this when the right path is unclear. Get a written diagnostic plan before rescue, rebuild, SEO, or systems work.

$250-$500.

Website Audit ->

SUPPORT // Needs small support

Use this for ad hoc edits, updates, breakage, and small fixes on stable low-risk sites.

$150/hr standard support; $175/hr ecommerce support.

Web Maintenance ->

01 // Rescue

BROKEN_SITE_RECOVERY

Website Rescue is for hacked, down, failed, unstable, or unsafe WordPress sites. Triage comes first, then a fixed repair scope.

02 // Rebuild

WORDPRESS_REBUILDS

Rebuilds replace sites that are no longer worth patching. The goal is a clean base, fewer moving parts, visible proof, and ownership handoff.

03 // Stabilize

WORDPRESS_STABILIZATION

Stabilization removes the fragility: slow pages, bad hosting, broken updates, risky plugins, security gaps, unreliable forms, and unclear access.

04 // Extend

SYSTEMS_AFTER_STABILITY

Extend only after the site is stable enough to carry more business logic. Systems work covers WooCommerce, catalogs, CRM automation, and custom workflows.

05 // Fit_Check

FIT_FILTER

Fit

Serious operators, broken systems, fragile WordPress or Elementor sites, WooCommerce risk, bad handoffs, slow pages, unstable hosting, broken forms, messy SEO or tracking, brittle integrations.

Not fit

Brand therapy, vague moodboards, committee redesign loops, social media calendars, ad management, endless revisions, no decision maker, or no clear business problem.

Monthly support rule

Most small sites do not need monthly plans. Site Ops only makes sense when traffic, revenue, complexity, staff edits, security risk, or downtime risk justify reserved capacity.

Proof, Handoff, Ownership

PROOF_BACKED_HANDOFF

You get evidence, not vague assurance. The proof changes by scope, but the rule is the same: show what changed, why it changed, and how it was tested.

The handoff should make the site easier to own, not more dependent on FunkPd.

Get fixed scope

Send the site URL, problem, urgency, access status, current host or platform, known failures, and desired path.

Operator Identity

Built and fixed by one person.

You work with Nolan Phelps directly. He does the diagnosis, scope, build, fixes, and handoff himself.

No sales layer. No project manager. No outsource chain.

Since 2017WinnipegWordPress rescue
Nolan Phelps

Nolan Phelps

FunkPd