Use published plans for recurring technical support. Defined builds and growth work are scoped separately so development, analytics, SEO, automation, and modernization are priced around the real deliverables and risk.
Published support plans are useful when recurring technical coverage is the need. Larger development and growth work should be scoped around deliverables, dependencies and the result that needs to be validated.
For recurring website, WordPress, WooCommerce, hosting, DNS and technical support where predictable access to help is more useful than a one-off quote.
For defined builds, redesigns, analytics implementations, SEO work, landing pages, migrations, custom development and other work with a clear deliverable.
For situations where development, SEO, conversion, analytics, advertising or infrastructure need to be prioritized together rather than quoted as unrelated tasks.
Two websites with the same number of pages can have very different technical risk, content requirements, integrations and validation needs.
Platform condition, legacy code, integrations, database work, ecommerce, account access and migration risk can materially change the scope.
New service pages, content cleanup, SEO consolidation, media preparation and structural changes require different levels of work.
Analytics, conversion tracking, forms, bookings, checkout, mobile behaviour and other critical paths need time for implementation and validation.
Deadlines, third-party approvals, hosting access, vendor coordination and unknown system issues can affect sequencing and effort.
| Feature | Starter $225 | Standard $450 | Priority $750 |
|---|---|---|---|
| Support requests/month | Up to 3 | Up to 8 | Unlimited |
| Target response | 1 business day | 4 business hours | 1–2 business hours |
| WordPress support | ✓ | ✓ | ✓ |
| WooCommerce support | Not included | ✓ | ✓ |
| Hosting & DNS | Basic | Included | Included |
| SSL & Security | Not included | Basic | Included |
| Site speed | Not included | Not included | ✓ |
| Work documentation | ✓ | ✓ | ✓ |
| Direct messaging | Not included | ✓ | ✓ |
| White-label / NDA | Not included | Not included | ✓ |
| Contract required | None | None | None |
| Cancel policy | Don't renew | Don't renew | Don't renew |
Monthly and yearly WordPress support for plugin conflicts, theme issues, dashboard problems, PHP errors, updates, and small site fixes.
Best for small WordPress sites that need occasional fixes and basic technical support.
Best for active WordPress sites that need regular maintenance, fixes, and faster response.
Best for business-critical WordPress sites that need priority coverage and deeper technical support.
Monthly and yearly WooCommerce support for checkout problems, order issues, gateways, shipping, taxes, product displays, and store performance.
Best for small stores that need checkout, product, and order support.
Best for active stores that need regular store, order, and payment support.
Best for stores where checkout, orders, payments, and store performance need priority attention.
Monthly and yearly hosting and DNS support for cPanel, DNS records, domains, SSL, email deliverability, migrations, and hosting-provider coordination.
Best for basic hosting, cPanel, domain, DNS, and email account support.
Best for businesses that need regular hosting, domain, DNS, and email deliverability support.
Best for businesses that need priority hosting help, migrations, DNS, Cloudflare, and provider coordination.
Monthly and yearly SSL and security support for SSL errors, mixed content, hardening, malware scans, headers, bot protection, and cleanup.
Best for small sites that need SSL, mixed-content, and basic WordPress hardening support.
Best for sites that need stronger security support, cleanup, headers, and bot/spam protection.
Best for higher-risk sites that need priority security response and stronger ongoing hardening.
Monthly and yearly site speed support for caching, Cloudflare, database cleanup, image optimization, Core Web Vitals, and performance tuning.
Best for basic speed cleanup and a clear performance report.
Best for active sites that need caching, CDN, database, and Core Web Vitals improvements.
Best for business-critical sites that need priority speed work and deeper performance remediation.
Support coverage and project work solve different problems. The commercial route should be clear enough that you know what is included, what can change, and what requires a separate scope.
Support plans are for recurring requests inside the selected service scope. Large builds, migrations, redesigns, or implementations may need a separate project scope.
A request is tracked around the problem being solved, not the number of messages required to investigate and complete it within scope.
Where annual pricing is shown, it covers twelve support periods. It does not turn unrelated project work into part of the support plan.
If a task exposes third-party, legacy, security, data, or integration work outside the original request, SmartersWeb should explain the change before expanding the work.
Published support blocks are different from scoped project work. These answers explain the recurring support model and how larger work is handled.
Book a free 20-minute discovery call to review the website, the type of help needed, and whether a support block or separate project makes more sense.
Choose your preferred way to reach us: