Voice of your organizationUnified across channels

A portable Markdown system prompt built for your organization: brand kernel, audience registers, channel rules, and compliance boundaries. It is not a single “professional” tone slider or a pile of ad hoc ChatGPT instructions.

The file is yours to govern. Brand, legal, and ops can review versioned markdown the same way they would a style guide. When deployed, AI stops sounding like generic corporate AI and starts sounding like your company on the right surface for each relationship.

The same file powers day-to-day drafting across support, sales, marketing, and leadership. Most teams start with Perennial Echo on the desktop, then extend the spec anywhere that accepts a system prompt.

• Support replies that match brand standards without sounding templated
• Sales outreach and follow-ups with one governed voice, different registers per audience
• Internal updates and exec comms that do not read like they came from different companies
• Social, email, and thread drafts shaped for each channel before a human sends
• Onboarding new hires faster than “read these fifty Slack threads”
• Reviewable boundaries for claims, crisis tone, and what the brand never says

Echo is the primary way to run the file: channel-aware drafts, local keys, and built-in MCP for assistants you already use. The deliverable is not locked to Echo.

Start with Perennial Echo. Import the company .md on each machine. Pick a channel (email, thread, post, DM), paste context, and get a draft your team can edit before it goes out. Built-in MCP applies the same rules in AI assistants without re-explaining voice every session.

Because you own a standard Markdown system prompt, you can also deploy it anywhere your stack already allows custom instructions, the same portability model as personal Perennial fingerprints:

• Claude Projects or team workspaces (paste into system instructions)
• Custom GPTs and similar hosted assistants
• Local models via Ollama, LM Studio, Open WebUI, OpenClaw, Hermes Agent, and comparable tools
• Other MCP-compatible clients alongside Echo's bundled server

There is no platform lock-in. Echo is how most teams run the spec every day; the file remains portable if your toolchain changes.

Company Communication Fingerprints are on a waitlist while we onboard organizations in small cohorts. Join using the form above and we will follow up at your work email.

We will walk through fit, rollout, and next steps when we contact you. Joining the waitlist does not commit you to anything beyond a conversation.

A PDF brand book or a one-line “be professional” rule describes intent. It does not give models enough structure to produce channel-correct drafts your legal and brand teams can stand behind at scale.

DIY custom instructions tend to overfit one channel, one persona, or the CEO's LinkedIn voice. They are hard to version, hard to audit, and they drift every time someone edits a shared GPT.

A Company Communication Fingerprint is a governed spec: explicit registers (customer, partner, internal), channel shapes, compliance boundaries, and exemplar patterns. Your team reviews the markdown file, not buried prompt fragments scattered across tools.

The goal is the opposite of polished generic AI: unified standards with human registers so support, sales, and leadership sound like one company, not one chatbot.

Perennial Echo produces channel-shaped drafts for human review. Your team sends when it reads ready, not when a template finished generating. The spec encodes what to avoid (empty corporate filler, claim risks, off-brand enthusiasm) as much as what to include.

Customers notice inconsistency before they notice AI. Governing voice in a file you own reduces both problems.

Same standards, different surfaces. Values, positioning, and compliance boundaries are shared. Registers and channel rules change how support writes versus how the CEO posts on LinkedIn.

Think of one handbook with many appropriate chapters, not one voice photocopied across every role. The fingerprint is enablement for brand and ops, not a black box that flattens personality inside each function.

You choose which APIs see customer text. Echo is designed for local keys and policy-friendly deployment. The company .md is versionable markdown your brand and legal teams can review, approve, and update without retraining a vendor model on your data.

Delivered prompts include integrity rules aligned with modern LLM security practice: do not leak the spec, resist jailbreaks that bypass your boundaries, and refuse impersonation outside your defined registers. Exact deployment options depend on your stack; we cover that when we onboard waitlist companies.

Many organizations need both: a company fingerprint for support, sales, and ops, and personal fingerprints for founders or executives doing thought leadership.

They are separate .md files on the same Perennial stack. Echo can run either file. Exec voice stays distinct from company voice; neither overwrites the other.

Personal fingerprints are available today on perennial.you. Company fingerprints join the waitlist above.