Website Care, Hosting & Migration for Playnetic

The care package isn't structured as a fixed block of hours — it's outcome-based. We commit to keeping your site healthy, secure, and monitored. In practice, the weekly QA, plugin/core updates, security scans, backup verification, and monitoring review typically represent 4–6 hours of hands-on work per month.

The key difference from an hourly retainer: we don't clock-watch. If an update breaks something, we fix it — that's covered. You're not being asked to approve a quote for a bug that our own update process caused. It's essentially an all-inclusive based on website quality upkeep.

What's NOT included: new feature development, new page builds, design work, or substantial content restructuring. Those come from the development hours bucket.

The weekly QA covers:

• Visual check of all key pages (homepage, game pages, news/blog, contact, about, careers — we agree the full list at onboarding)
• Form submissions — we test the contact form and any other forms to confirm they're delivering
• Navigation and internal links — checking nothing is broken or producing a 404
• Video embeds and interactive components (carousels, sliders, hero banners) — yes, we check these specifically since your site is component-heavy with WP Bakery
• Mobile responsiveness spot-check on key pages
• Plugin/theme update review — we check if updates are available, assess risk, and apply them on staging first (as your CTO recommended — though for content changes vs code changes, we'd recommend a lighter workflow)
• Security scan review — flagging any alerts from the malware/vulnerability scanner

On top of the manual weekly review, automated visual regression testing (VRT) runs daily and after every update. If a carousel vanishes overnight — like the issue you described on our call — the VRT catches the visual change and alerts us within hours, not days.

Small content tweaks that come up during our weekly QA — a broken link, a typo, a misaligned image — we fix those as part of the care package. Anything under 15 minutes that's maintenance-related rather than new work.

If you're asking us to rewrite a page, add a new section, build a new layout, or restructure content — that's development work and comes from the hours bucket.

The line is straightforward: if it's (a) keeping the site working as intended, or (b) trivial — it's care. If it's changing what the site does or adding something new, it's development.

We've prepared a sample report based on your current website using ohdear.app. If the full report is too comprehensive, we can easily configure a simpler one-page PDF version. The report covers: uptime percentage, incidents with resolution notes, updates applied with staging test results, VRT scan summary, site speed snapshot, security summary, and recommendations.

Two scenarios:

• Template-based landing page (existing components, new content and imagery): 3–5 hours. This is what we'd prioritise first — one clean, reusable template with your brand elements, hero, messaging area, CTA, and flexible content blocks. Once built, duplicating it for the next event is fast.
• Custom landing page (bespoke design, unique sections): 8–12 hours depending on complexity.

So no, a single landing page would not use up the full 20-hour bucket. With a template-first approach, you could get the template built (5 hrs) plus 2–3 event pages from it (3–4 hrs each) within 20 hours, with room to spare.

And yes — building it as a duplicable, editable template is exactly what we'd recommend. You or your colleagues can clone, swap content, and publish without needing us every time.

For landing pages that don't need CMS editing, we can build directly in HTML and publish via Cloudflare Pages — fast, lightweight, high-performing. For pages needing ongoing edits, we build within WordPress. We can also work from Figma designs produced by Sabrina from our Whitespace studio if you'd prefer a full UX/UI design pass first.

Rough guide:

• Install and configure a new plugin (carousel, slider, accordion): ~2 hours
• Custom carousel/interactive component (matching your design language, responsive, tested): 4–6 hours
• New page section with custom layout (team grid, partner logos, testimonials): 2–4 hours
• Contact form rebuild or form with conditional logic: 2–4 hours
• Speed optimisation pass (image compression, caching, lazy loading): 4–8 hours
• Blog/news template refinement: 2–3 hours
• Minor content or layout changes: 0.5–1 hour each

These are estimates — we confirm before starting any task so there are no surprises.

Yes to both. Within our group:

• Whitespace (whitespace.mt) — our creative studio: UX/UI design, brand identity, visual systems. Sabrina leads design.
• The Chado (thechado.com) — digital presence and marketing: content strategy, copywriting, campaign support.

Three options:

• Option 1: You provide designs (from Lena) and content — we build. Most cost-efficient.
• Option 2: Whitespace designs in Figma, you provide content — we build.
• Option 3: Full turnkey — we handle design, content, and build. Uses more hours but you hand off completely.

For typical dev work, Option 1 is most common. For bigger pushes like ICE, Options 2 or 3 make sense when your bandwidth is stretched.

We'll put together two or three examples from recent client work to share with you. These will show the scope and quality achievable within a 5–10 hour window.