External presence

Introduction

The corporate website, privacy policy and public contact channels are part of the operating model. They create trust signals before the product is mature and need clear ownership.

Knowledge scope

This is startup-specific guidance in the public playbook. It is framed around the Day Zero -> Company Ready decision point and the practical trade-offs a small company faces while moving from idea to Production.

Why it matters

External presence is often treated as marketing, but it is also where customers find privacy, support, security and incident information. If no one owns it, public promises can drift away from reality.

How it fits the playbook

This reference supports the Day Zero -> Company Ready stage of the startup CTO playbook. It gives the public context for the decision without exposing the deeper assessment method behind the agentic operating model.

Design considerations

• Know where the website is hosted and who controls publishing access.
• Record responsibility where an external supplier manages the site.
• Keep privacy, security and support contact routes visible and maintained.
• Understand website DNS dependencies and contact-form handling.
• Make cookie, analytics and privacy positions match the real implementation.

What good looks like

The public website and contact channels are trustworthy, maintainable and aligned with the company's actual operating responsibilities.