HQ Paphos, Cyprus · worldwide
99 Francs® takes on live WordPress sites built by another team: forms that quietly reject every submission, emails that never reach an inbox, page builders that overwrite content, and text that should have been an admin field years ago.
We diagnose against evidence — a delivery test, a DNS lookup, a stage-by-stage timing — and record every change with a way back.
A form that returns an error to every visitor, a domain with no SPF record, a page builder overwriting the content someone just edited. None of these announce themselves, and none are found by a plugin-update subscription. They are found by submitting the form as a visitor and following what happens next.
The numbers below are measured, from real projects — not illustrative figures. Where a case study exists, it is linked so you can check them.
Usually one of two things. Either the form never sends — an anti-spam or timing validation rejects the submission before the mail step — or it sends and the recipient quarantines it. On one site we found the first case: every single submission was being rejected, visitors saw a validation error and the agents saw nothing at all.
Almost always DNS rather than WordPress. We check what actually resolves for the sending domain — SPF, DKIM, DMARC, MX — instead of assuming. On the same site the domain had no SPF record, no DMARC and no MX at all, while the mail provider was already setting a correct Return-Path.
We split the request and time each stage. In one measured case WordPress, the form plugin and validation took about 345 ms, while the transactional email API took roughly 880 ms on its own. The site was not the slow part, so the fix was interface feedback, not optimisation.
Page builders like WPBakery and Elementor store their own copy of the content and can overwrite edits made elsewhere. The fix is knowing which layer owns which content, and moving the volatile parts out of the builder entirely.
Usually an unoptimised hero image. One homepage hero went from 6.6 MB to 1.66 MB with a like-for-like quality check, and the original stayed in the media library.
Dates, contacts and prices sitting in a template are a permanent support cost. They belong in admin fields with help text, where a non-technical person can change them safely.
WordPress support that survives the next theme update and does not depend on us still being around.
Contact Form 7, Gravity Forms, Fluent Forms or WPForms — we test as a visitor, follow the message to the inbox, and fix whichever half is broken: the send, or the delivery.
ACF field groups plus shortcodes in a child theme, so agents, dates, prices, banners and hero media are editable, labelled and safe to change.
Two SMTP plugins fighting, a page builder overwriting content edits, a caching layer serving a stale template, an anti-spam component rejecting real users.
Every code, settings and content change recorded before-and-after with revert steps, so the next person — including us in six months — is never guessing.
No documentation, no change log, sometimes no admin access. We start by mapping and recording what exists, then work in reversible steps.
We audit what their setup actually does before removing anything, including accounts and access that should have been revoked at handover.
Brochure sites, property developments, clinics, local services. Sites where the enquiry form is the entire commercial function and has to work every time.
Support is scoped as a round of work with an end and a written record. If you also want ongoing cover afterwards, that is a separate, explicit conversation.
On an inherited WordPress site the biggest risk is your own first change. So nothing gets touched before the current state is recorded and the enquiry path is measured.
Theme and child theme, plugin list, form configuration, mail setup, caching layer, DNS. Captured as before-and-after with revert steps.
Submit as a visitor, watch the request, follow the message to the inbox, time each stage. Most silent WordPress failures are found in this one pass.
Code goes into the child theme and custom field groups, so a theme update never wipes the work and every change survives the next upgrade.
A green admin notice proves nothing. Values are confirmed by reloading and re-reading, theme files by requesting the file itself, and the client gets the log.
The same approach applied to Webflow, Framer, Shopify and custom builds: record, measure, fix, verify, hand back control.
Website supportIf the plugin stack is the recurring cost rather than the symptom, moving off it can be cheaper than another year of patching.
WordPress to WebflowA townhouse development in Auckland: dead enquiry form found in a routine check, quarantine diagnosed against actual DNS, delay measured stage by stage.
Read the case studyWhen the site needs replacing rather than repairing, the same team designs and builds it in Webflow, Framer or React/Next.js.
Explore web developmentTrivelle Gardens, a townhouse development in Hobsonville, Auckland: the enquiry form was rejecting every submission, and it was found in a routine check rather than reported as a fault.
Website support · WordPress
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
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.
We tell you how many hours it takes, start today, and invoice when you are happy.
A WordPress site quietly losing enquiries should not wait on a purchase order. You get the findings with an hour estimate against each one, you approve the total before we start, and no money changes hands until it works.
Every fix — the form, the DNS, the plugin conflict — is quoted with the hours it takes. You approve the scope and the number before we start; nothing runs on an open meter.
If the enquiry form is dead, that gets fixed first. We do not schedule a discovery call for something a delivery test answers in ten minutes.
No deposit and no upfront payment. The agreed work gets done, you check it, and only then does an invoice appear.
Yes. We build ACF field groups and shortcodes in the child theme so dates, contacts, prices and hero media become labelled admin fields. Blocks can sort and expire their own content — past dates drop off and the block hides itself when nothing is left. There is a worked example in the Trivelle Gardens case study, including the admin screens.
Care-plan providers advertise flat fees from roughly $30 to $500 a month for updates, backups and monitoring. We do not sell a care plan. Each fix is estimated 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.