Services

Corporate website support

Forms that actually deliver, certificates that never lapse, current news, and security sign-off. A company site has to look alive.

Timelinemonthly

What's included

  • Enquiry delivery verification
  • Certificate and domain tracking
  • Form spam protection
  • News and careers publishing
  • Updates and security patches
  • NDA and security team sign-off
  • Monthly reporting

A corporate site rarely generates revenue directly, which is precisely why it gets neglected. The damage here isn't lost orders, it's credibility: a prospect visits to check whether the company is still a going concern and finds news from two years ago, job postings for roles filled long since, and a browser warning about an insecure connection. They draw conclusions fast.

The most common and most painful failure is a contact form that has quietly stopped sending email. It looks perfectly healthy: the visitor fills in the fields, sees a thank-you message, and waits for a call. The email goes nowhere — a mailbox password changed, the host tightened its sending policy, or the recipient address moved. The company spends months assuming the website simply doesn't generate enquiries.

How we work

  1. Inventory the contact points. We collect every form, every destination address, phone numbers and legal details published on the site, and confirm all of it is current and functioning.
  2. Scheduled delivery checks. We send test enquiries on a schedule and verify the message reached the right inbox. Silence from the sales team stops being a mystery.
  3. Expiry calendar. SSL certificate, domain, licences. Renewed ahead of time — a browser blocking your site over a weekend costs far more than the certificate did.
  4. Form protection. Captcha and server-side filtering so spam doesn't bury genuine enquiries. A manager wading through a hundred junk submissions a day will eventually miss a real one.
  5. Updates and security. Patches, dependencies, closing vulnerabilities. For a corporate site a breach is a reputational event first and a technical one second.
  6. Publishing. News, vacancies, documents. Send the material and we put it live so the site doesn't read as abandoned.

What you get

A site you can show a partner without wincing, and one that doesn't turn prospects away with a security warning. Enquiries reach the people who should receive them, and that's verified rather than assumed. The news section looks maintained.

A note for larger organisations: we work under NDA, clear access with your information security team, and commit response times in an SLA — for mid-size and enterprise clients that's usually a precondition rather than an extra. If the site sits on a website builder, see Tilda website support, where the work looks somewhat different. Plans and response tiers are on the technical support page.

Timeline

Onboarding takes two or three days: inventory, monitoring and delivery checks, renewal calendar. Then month to month. Publishing requests go live within the working day; urgent corrections such as an outdated phone number or wrong company details go out the same day. Technical incident response follows your plan.

A typical scenario

Consider a manufacturing company whose site carries a request-for-quote form. The host tightens its email sending policy and messages from the site begin disappearing silently. The form still thanks each visitor for getting in touch. Six weeks pass before somebody notices by accident — and for all that time prospective customers assumed the company simply couldn't be bothered to reply. With scheduled delivery checks, that failure surfaces within the first day.

FAQ

How can we know enquiries from the site actually arrive?
Only by testing. We send scheduled test submissions and confirm the message landed in the right inbox. A form showing a thank-you page proves nothing — it will show exactly the same page when delivery is completely broken.
What does corporate website support cost?
For a brochure site the entry plan is usually enough. A multi-section portal with a customer area and integrations is quoted separately after we've looked at the project.
Do you work under NDA and with security team approval?
Routinely. We sign non-disclosure agreements, go through access approval, and work from restricted addresses where required. For corporate clients this is standard procedure rather than an exception.
Our form is drowning in spam. What can be done?
Captcha plus server-side filtering that stops bots before they reach your inbox. The trick is not overdoing it: aggressive protection also drives away genuine customers, so the settings get tuned against real traffic.
Who keeps track of the SSL certificate?
We do. It goes on the renewal calendar alongside the domain. A certificate that lapses on a Friday evening means a weekend of browser warnings across every page — considerably cheaper to prevent.
We only update news twice a year. Is support still worth it?
The technical watch matters regardless of publishing frequency: updates, certificates, working forms. Publishing is an available extra, not the core of the service.
What happens if the site gets hacked?
For a corporate site it's primarily a reputational hit — visitors see injected content or a search engine warning. We treat it as P1: clean up, close the entry point, and get the search engine flags lifted.
Other services