External presence

Introduction

The corporate website, privacy policy and customer contact channels are part of the operating model. They do not have to live on the final product platform, but the company needs to understand who owns them, who can publish changes and what public commitments are being made.

Key considerations

• Corporate website hosting.
• Website platform ownership, billing and publishing access.
• Website DNS change responsibilities.
• Responsibility split where an external supplier manages the site.
• Public privacy contact.
• Public security contact.
• Public support or general enquiry contact.
• Website contact form handling.
• Cookie and analytics position.
• Privacy policy ownership and update process.
• Status page later in maturity.

External presence should not become an orphaned marketing asset. It is part of customer trust, privacy communication, incident response and commercial credibility.

How this evolves as the company grows

• At company setup, the corporate website, public contacts and privacy routes need clear ownership even if hosted externally.

• Before Pilot, public wording should match the real product, support route, cookie position and privacy posture.

• At Production, the external presence becomes part of customer assurance and incident communication.

• As the company scales, external presence should be managed like a controlled asset with owners, review dates and change evidence.

What an agent should look for

• Who owns public content and hosting?

• Do privacy and support contacts match operations?

• Are public claims reviewed?

What good looks like

The company can explain the decision, show the evidence behind it and identify the next point where the control needs to mature.