FAQ for builds, fixes, scope, pricing, ownership, and support.

Both. FunkPd builds new business-critical WordPress sites and systems, fixes broken or fragile existing sites, stabilizes risky setups, and diagnoses the right path when the answer is not obvious.

Choose rescue when the current site can be saved and the failure is active. Choose rebuild when the base is too fragile to keep patching. Choose new build when there is no safe owned base yet or the business needs a clean system from day one.

Yes, if the work can be scoped and proven. Nolan starts by finding what exists, what is broken, who owns the accounts, what risk matters, and whether rescue, rebuild, stabilization, or a new build is the safer path.

Yes, when the scope is direct and the decision path is clear. Published work includes industrial, commercial, WooCommerce, catalog, workflow, and multi-site WordPress projects. Nolan still needs direct access to the right people and systems.

Yes, when the site or system matters enough to scope properly. FunkPd is not the cheapest path for a simple brochure site, but small companies can be a fit when ownership, lead flow, stability, or clean handoff matters.

Fast cheap builders can work for simple cases. FunkPd is for companies that need ownership, control, proof, WordPress flexibility, and a system that will not collapse when the business depends on it.

Nolan handles diagnosis, scope, build, fixes, and handoff directly. There is no sales layer, project manager, or outsource chain between the buyer and the person doing the work.

The agreed checks happen before the job closes. Depending on scope, that can include staging review, form tests, checkout tests, redirects, backups, speed checks, tracking checks, screenshots, changelog, access notes, and handoff notes.

Urgent work is reserved for real business risk: site down, checkout broken, forms dead, malware visible, launch blocked, or revenue affected. If capacity exists, urgent rescue can jump the queue. Routine edits stay in the normal queue.

Start with the site URL, goal, risk, deadline, and access status. If the path is unclear, the first paid step can be a diagnostic or blueprint before build, rescue, or stabilization work starts.

Send the site URL, failure, risk, access status, and deadline. Broken, hacked, crashed, unstable, checkout-blocking, or revenue-blocking sites route to Website Rescue. Sites not worth patching route to WordPress Rebuilds. Fragile but salvageable sites route to Stabilization.

These are current CAD ranges. Website Rescue is $3,500-$8,500. Essentials Rebuild is $4,500-$9,500. Growth Rebuild is $9,500-$18,000. Stabilization Fix is $1,250-$2,500. Stabilization Sprint is $3,500-$7,500. Systems work is scoped separately. Final scope and price are written before work starts.

Stabilization is the category for making a fragile site safe. Website Rescue is the flagship urgent paid product for failed builds, hacks, outages, unstable releases, and revenue-blocking failures. Smaller crash fixes can route to Stabilize Site or hourly support when that is safer.

No. Stable low-risk sites should pay ad hoc through Web Maintenance. No monthly plan means no reserved capacity or guaranteed response window. Site Ops Coverage only fits when slow response would cost more than the plan.

Cheap patching can hide the real failure. If the site has bad ownership, brittle plugins, no staging, weak backups, or broken checkout risk, the safer move is to stabilize or rebuild the base instead of adding another quick fix.

No. It means support is matched to risk. Stable sites use ad hoc support. Sites where delay would cost more than coverage can use Site Ops Coverage with reserved capacity and defined response expectations.

Site Ops Coverage is monthly monitoring, checks, priority response, proof notes, and improvement work for justified risk. If nothing breaks, the site still gets better through cleanup, speed work, content edits, SEO fixes, tracking checks, documentation, backlog reduction, or risk reduction. It is not unlimited support and it is not 24/7 by default.

Emergency routing is for real outages: site down, checkout broken, forms dead, visible malware, DNS or email failure, or a launch-critical page broken. Cosmetic edits, new features, and routine backlog items are not emergencies.

The FunkPd Proof Pack depends on scope. It may include before and after screenshots, Lighthouse or WebPageTest results, crawl results, form tests, backup checks, changelog, plugin notes, redirect checks, tracking checks, DNS or email checks, accessibility checks, launch checklist, and handoff notes.

Cutover normally waits on the agreed proof list: key page checks, form tests, redirects, backups, access notes, tracking checks, and visible review of the fix list. The exact proof depends on scope.

FunkPd is intentionally small. Nolan only accepts scope that can be finished properly. Urgent work can jump the queue when there is real outage risk, but reserved response windows belong to Site Ops Coverage.

You should own domains, hosting, analytics, backups, licenses, accounts, and credentials. FunkPd can work inside client-owned systems or hand systems over cleanly. No lock-in, no hostage accounts, no mystery stack.

Yes, for post-launch or out-of-scope work. Standard support is $175/hr CAD. WooCommerce and complex support is $225/hr CAD. Urgent or after-hours work is $325-$450/hr CAD with a 2-hour minimum when capacity exists.

Brand therapy, vague moodboards, committee-led redesign loops, social media calendars, ad management, endless revisions, no decision maker, and no clear business problem are not a fit.

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