FAQs. Clear answers. No noise.

Use the Start page to choose your modules (Protect, Pulse, Propel) and complete onboarding. You’ll enter billing details on the secure checkout screen, then we take it from there.

You’ll complete a short onboarding checklist (site access + goals). Then we run a baseline pass, stabilize the essentials, and move you into an “operated” state: monitoring, updates, backups, and proactive improvements based on the modules you selected.

Not usually. If you already know what you want, you can start immediately. If you’re unsure about scope, complex constraints, or timing, you can book a call and we’ll point you to the right module mix.

Most teams start with Protect + Pulse so hosting and operations are managed as one system. Add Propel when you want one-time improvements (new pages, integrations, fixes, performance work).

Protect is ongoing WordPress operations: updates, monitoring, security hygiene, backups, incident response, and keeping your site stable. It’s designed to reduce surprises and keep your site quietly reliable.

Yes — Protect covers routine maintenance and update workflows so your site stays current and stable. We prioritize safe rollout, backups, and validation. If an update requires deeper refactoring, we’ll recommend a Propel block to handle it cleanly.

Anything that puts your site’s availability, security, or core business function at risk (e.g., downtime, critical errors, suspected compromise). Protect is built around catching issues early and responding quickly when something breaks.

Yes — those sites benefit the most from stable operations. The right mix depends on your plugin ecosystem and traffic. If you’re running a high‑risk stack, we may recommend pairing Protect with Pulse for tighter control over the hosting environment.

Pulse is managed hosting tuned for WordPress: performance, reliability, and the infrastructure layer that lets operations run smoothly. Think of it as the foundation that keeps everything fast and dependable.

Often, yes. Protect can operate on many hosts. That said, Protect + Pulse together is the smoothest experience because we can standardize performance, backups, and monitoring end‑to‑end.

Yes — when you choose Pulse, migration is typically part of getting you into a stable, operated state. We aim for low risk and minimal disruption, and we’ll align timing around your business needs.

Pulse focuses on WordPress hosting and reliability. For email, we generally recommend a dedicated provider (Google Workspace, Microsoft 365, etc.) for best deliverability and support.

It’s a streamlined package that combines Protect (operations) and Pulse (hosting) into one managed system. Annual pricing is shown as a simple anchor. Monthly options are available as well; final pricing and plan details are confirmed at checkout.

Yes. You can choose monthly or annual during onboarding. Annual is ideal when you want the most predictable engagement; monthly is great when you want flexibility.

Yes — plan terms and cancellation details are shown during checkout. If you ever need to pause or change modules, reach out and we’ll help you land in a stable spot first.

Plan-specific billing and refund terms are provided at checkout. If something feels off, talk to us — we’ll prioritize a fair, professional resolution.

Propel is one‑time improvement work: fixes, enhancements, new pages, integrations, performance work, and design/dev iteration. It’s ideal when you want progress without hiring a full-time team.

• 1 hour: quick diagnosis, small fix, “can you just…” tasks.
• 5 hours: small upgrade batch (forms, small sections, cleanup pass).
• 10 hours: focused sprint (new landing page, performance round, integrations).
• 20 hours: meaningful iteration (multi-page build, redesign slices, deeper refactors).

If you’re unsure, start with 5 hours — it’s enough to make real progress without overcommitting.

You can purchase Propel as a one-time engagement. Protect is recommended when you want ongoing stability so improvements don’t regress over time.

It depends on scope and queue. Small tasks can move quickly; larger work is scheduled and delivered in clean, reviewable milestones. If timing is critical, book a call and we’ll align on priorities.

Typically: WordPress admin access, hosting panel/SSH (if relevant), domain/DNS access (when needed), and any key third‑party tools (CDN, email provider, analytics). We request the minimum required and keep access organized.

Protect emphasizes secure defaults, routine patching, monitoring, backups, and fast response when something looks off. If your environment needs extra controls (compliance, staging rules, access constraints), we’ll tailor the workflow.

We use secure, modern credential handling practices. Exact tooling can vary by engagement; if you have a preferred system (1Password, Bitwarden, etc.), we’ll align to it.

After onboarding, you’ll have a straightforward way to send requests and track progress. Protect handles operational support; Propel covers scoped improvements and builds.

Response expectations depend on your plan and the nature of the request. Emergencies are prioritized. Normal requests are triaged and scheduled for safe execution. You’ll see relevant details during onboarding.

Yes when it makes sense. Staging helps reduce risk for updates and improvements — especially on complex sites. For smaller sites, we may use lighter validation flows depending on the change.

Yes — backups are part of keeping WordPress boring (in a good way). The exact approach depends on your host and modules selected; Pulse + Protect is the most cohesive setup.

Yes. A stable, fast site often comes from fewer moving parts. If we see risky, redundant, or brittle plugins, we’ll recommend a safer alternative or a Propel task to refactor the dependency.