Website maintenance for the site you already have

Give routine upkeep a clear scope

A useful website care plan makes responsibilities clear: what gets checked, what gets updated, where backups live, and which edits are included. The scope should reflect how your site works. A store with orders and payment integrations needs different checks from a small information site.

Maintenance can cover software updates, backup configuration, recovery checks, access reviews, and testing important visitor actions. Security work can include removing unused plugins and reviewing account permissions. No maintenance arrangement makes a site immune to problems; the practical aim is to reduce avoidable risk and have a recovery route.

• Agree on update frequency and checks for forms, checkout, and other important features.
• Define backup coverage, storage, retention, and how restoration will be tested.
• Separate routine upkeep from larger repairs, redesigns, and new features.

The small jobs that keep a site useful

Website updates often start with ordinary requests: change opening hours, replace a staff photo, or remove an expired promotion. Check the details too: image sizing, mobile layout, and link destinations.

We also take fix-it jobs on websites we didn’t build. Send the symptom and where it happens. A broken contact form might need a focused repair; a recurring plugin conflict may need investigation before anyone can sensibly estimate the fix.

• Replace text and images, publish supplied content, or adjust navigation.
• Repair a form, investigate missing notifications, or correct a mobile layout.
• Check redirects after a page moves and fix broken internal links.
• Investigate slow pages, failed integrations, or errors after an update.

Start with access, priorities, and a baseline

In your first email, include the site address, platform if known, current problems, and any deadline. Tell us who manages hosting, domain registration, and the code. Mention your existing developer or agency, along with any changes already underway. Screenshots and steps to reproduce an error are more useful than passwords in an email.

The first scope can cover a review of the setup: available backups, pending updates, custom code, and the pages or transactions that matter most. If the unknowns are substantial, paid discovery can establish the work before a larger quote.

Agree on access, the change list, checks, and a release window before work starts. Where the setup supports it, changes can be checked on a separate test copy first. The handoff should record what changed, what was checked, and any remaining work, whether the job ends there or moves into ongoing maintenance.

Care that fits your platform

WordPress maintenance can include core, theme, and plugin updates, database and file backups, and checks around custom functionality. WooCommerce work also needs attention to the purchase path. Updating software is only part of the job; checking that the site still does its job matters too.

For Shopify, Webflow, Squarespace, and Wix, scope the work around the settings, content, themes, and integrations available through the platform. Confirm what the provider handles and what remains your responsibility. Backup and recovery options need to be checked against the actual setup.

For custom sites and web apps, we work with Next.js, React, and TypeScript. Maintenance can involve dependencies, build errors, API integrations, and deployment configuration. Access to the repository, hosting, and relevant service accounts helps establish what can be changed and tested.

Choose an arrangement that matches the workload

Hourly work suits a short list of edits or fixes. A fixed-price project suits a defined cleanup or repair. A website support retainer suits recurring work where you want agreed priorities and an ongoing contact. Pricing is quote-only: we scope the work and provide a fixed quote or an hourly estimate.

This suits owners, marketers, and agencies who need practical help with an existing site. We can take a sub-project alongside another studio, white-label or credited. We take on a small number of projects at a time, so you work directly with the people doing the work.

A maintenance scope is a poor fit for an undefined rebuild. Separate that work into discovery or a project. If you need round-the-clock incident coverage or strict response commitments, raise those requirements before choosing an arrangement; a monthly retainer alone does not define them.

Our own products are the proof we can show

We design, build, and maintain our own products end to end, including nine apps live on the App Store and this hand-built website. Rain, Moonflower, and Broski are among those owned products. They are our work, not client case studies.

hehe.software itself includes a WebGL hero, video, and structured data. Your maintenance scope starts with your site: its platform, custom code, dependencies, and outstanding issues.