Does the enquiry form actually deliver?
Not whether it shows a success message — whether a message reaches a human inbox. We have found forms that returned a validation error to every visitor while the owner assumed business was simply quiet.
Service · Website support
Website support for sites somebody else built — starting with what is quietly broken.
99 Francs® takes on live websites with no handover and no documentation. We audit what is actually happening, fix it with a written way back, and move the content your team changes weekly into fields they control.
Every finding comes with evidence you can check yourself — a timing, a DNS record, a delivery test — not an adjective.
Direct answer
Website support is not a plugin-update subscription. It is somebody taking responsibility for whether the site still does its job.
Updates, backups and uptime checks are the easy part, and most care plans stop there. The failures that actually cost money are silent: a form that rejects every submission, emails held in the recipient's quarantine, a page nobody can edit without a developer. Support means finding those and proving they are fixed.
First audit
Six questions we answer before touching anything.
Each one is answered with a measurement, not an opinion — so you can check the finding yourself and see the same number after the fix.
Do the emails arrive, or land in quarantine?
We check the sending path and the receiving side: SPF, DKIM, DMARC and MX records as they actually resolve, the Return-Path, and whether the recipient's mail service is holding messages.
What is slow, and which part of it?
A slow submit is split into its stages and each one is timed, so the fix targets the real bottleneck instead of the first plausible guess.
What weighs more than it should?
Oversized hero images, uncompressed uploads and render-blocking scripts are measured before and after, with the originals kept.
What breaks the next time someone edits?
Inline styles in page builders, duplicate element IDs, two plugins doing the same job, an old developer's account still active. These are logged even when they are not today's problem.
Can the team change anything without us?
If updating a date or a phone number requires a developer, that is a support cost you pay forever. We move it into the admin instead.
What you get
A round of support, not a recurring invoice for plugin updates.
Support is scoped as work with an end and a written record, so you always know what changed and what it cost.
A first audit with findings, not adjectives
We go through the live site and report what is actually broken, with evidence: request timings, delivery test results, DNS record state, page weight. Every finding is something you can verify yourself.
Fixes, recorded with a way back
Every change to code, settings or content is written down as before-and-after with revert steps, so nothing is a mystery in six months and nothing is irreversible.
Content moved into fields you control
Anything that changes weekly — dates, contacts, prices, hero media — becomes an admin field instead of a line of code, so keeping the site current never waits on a developer.
Answer-engine readiness
Schema, direct answers, metadata, internal links and a Markdown alternate are part of support, not a separate project, so search engines and AI assistants can read the site correctly.
Best fit
Use this when the site is live, something is off, and nobody currently owns it.
The site works, but nobody is sure it works
Nothing looks broken, enquiries are just thin. This is the most common way a website fails: silently, with no error anyone sees.
The team that built it is gone
You inherited a site with no documentation, no handover and possibly no access. We start by mapping what is there and recording it before changing anything.
Every small change needs a developer
If a new date, a new price or a new photo is a support ticket, the content model is wrong. That is a fixable problem, not a fact of life.
You want a diagnosis before a rebuild
Sometimes the honest answer is that the site is fine and three things need fixing. Sometimes it is that a rebuild costs less than another year of patching. We say which.
Process
How we work on a site we did not build.
Inheriting a live site means the first risk is your own changes. So the order is always: record, measure, fix, verify, hand back control.
Record the current state first
Before a single change, we capture what exists: settings, theme files, plugin list, form configuration, DNS. This is what makes every later change reversible.
Test the money path end to end
Submit the form as a visitor. Follow the message to the inbox. Time each stage. Most support work starts here because most silent failures live here.
Fix, then verify by reloading
A green success notice proves nothing. Every change is confirmed by reloading the page and re-reading the stored value, and theme files by requesting the file itself.
Hand back control
Whatever changes often moves into admin fields, and you get a written log of what was changed, why, and how to undo it.
WordPress support
The most common case: an inherited WordPress site with a page builder, a contact form plugin, an SMTP plugin and nobody who remembers how they interact.
WordPress supportWhen fixing is not worth it
If the platform itself is the cost, we say so and price the move instead — WordPress to Webflow, or Webflow to Next.js and Payload.
Explore migrationNew build instead
When the site needs replacing rather than repairing, the same team designs and builds it in Webflow, Framer or React/Next.js.
Explore web developmentOngoing design and build
For teams that need continuous work rather than one round of fixes, the design subscription covers design, front-end and iteration at a flat monthly rate.
Explore subscriptionRelated work
Sites we took over, measured and handed back working.
Support work is hard to show in a portfolio, because the result is usually an absence of failure. These two projects have numbers attached.
Website support · WordPress
Trivelle Gardens property support
Support round on a live WordPress site for a Hobsonville townhouse development. Found an enquiry form that was silently rejecting every submission, diagnosed why the emails were quarantined, and moved agents, viewing dates and hero media into fields the client edits himself.
Redesign · Web Development
VetaDerm veterinary
Full website redesign for a Swedish veterinary dermatology clinic (Kungsbacka & Lund), rebuilt in Webflow with GSAP motion and an editable CMS. Delivered for a Norwegian client.
Terms
We tell you how many hours it takes, start today, and invoice when you are happy.
Nothing about a broken site should start with a deposit. You get the audit findings with an hour estimate against each one, we agree the total before anything begins, and the work runs at our risk until you have seen it working.
Estimated in hours
Each finding is quoted with the hours it takes. You approve the scope and the number before we start, so nothing runs on an open meter.
Started immediately
A live site quietly losing enquiries is not a scheduling problem. Urgent findings get fixed first, not after a purchase order clears.
Paid on completion
No deposit and no upfront payment. The agreed work gets done, you check it, and only then does an invoice appear.
No deposit · Hours agreed before we start · You pay when it is done
Website support FAQ
Answers for teams comparing care plans, freelancers and taking a site back in-house.
Website support is ongoing responsibility for a live site: checking that it still does its job, fixing what is broken, keeping it secure and current, and making sure the team can update content without a developer. It is broader than maintenance, which usually means updates, backups and uptime monitoring only.
Yes — that is most of this work. We take on live sites built by another team, including ones with no documentation or handover. The first step is recording the current state, so every change we make afterwards can be reversed.
Care-plan providers advertise flat monthly fees from roughly $30 to $500 a month for updates, backups and monitoring. We do not sell a care plan. The audit gives each finding an estimate in hours, you approve the scope and the total before anything starts, and you pay once the work is done — under the same outcome-based terms as the rest of our work, with no upfront payment.
There are two common causes and they need different fixes. Either the form is not sending at all — an anti-spam or validation component silently rejects the submission — or it sends and the recipient's mail service quarantines it, usually because the sending domain has no SPF, DKIM or DMARC records. The only way to tell is to submit as a visitor and follow the message, which is where our audit starts.
Yes. Content that changes often — dates, contacts, prices, hero images, banners — gets moved into admin fields with clear labels and help text, so a non-technical person can update it safely and the block hides itself when there is nothing to show.
Yes. If another year of patching costs more than a rebuild or a platform move, we say so and price both options rather than quietly billing for repairs.