# Company AI intake

Work through this with your team. Record UNKNOWN instead of guessing.

## 1. Identity

Feeds into: the constitution, house rules, company facts

- REQLegal business name, exactly as it must appear
  Answer: 

- REQThe name rule: how the name always appears, and how it must never appear. Abbreviations, the comma before LLC, permitted short forms
  Answer: 

- REQThe one-liner: what you do, for whom, in one sentence
  Answer: 

- The thirty-second version, an elevator paragraph
  Answer: 

- REQWhat you do NOT do, and what you never want to be mistaken for
  Answer: 

- REQIndustry, plus regulated flags: health, legal, financial, insurance
  Answer: 

- Geography served, which becomes a hard rule if the answer is one state
  Answer: 

- Web presence: domains, socials, existing live pages
  Answer: 

## 2. People

Feeds into: governance and the org facts

- REQOwner and final approver: name, role, contact
  Answer: 

- REQThe brain operator, whoever runs the AI day to day
  Answer: 

- Additional approvers, and what each may approve
  Answer: 

- Team roster: name, role, contact, headshot
  Answer: 

- REQThe money, legal and external-send gate: who can never be bypassed
  Answer: 

## 3. Audiences

Feeds into: the target-audience files, two to four of them

- REQA label, like HOA board member, and who they actually are
  Answer: 

- What they want, and what they fear
  Answer: 

- Words they use, and words that turn them off
  Answer: 

- The single action we want from them
  Answer: 

- REQWhich one is the hero audience. Exactly one yes
  Answer: 

## 4. Voice

Feeds into: the voice files

- REQThree to five voice adjectives
  Answer: 

- REQThe default tone, picked from seven named registers
  Answer: 

- Approved signature phrases: things you actually say
  Answer: 

- REQBanned words and phrases
  Answer: 

- REQThree writing samples you love, yours or anyone’s, for reverse-engineering the voice
  Answer: 

- Mechanics: emoji policy, exclamation policy, whether humor is allowed
  Answer: 

## 5. Hard rules

Feeds into: the guardrails

- REQThis AI must NEVER… say, do, or claim
  Answer: 

- REQPricing publishing policy: public, quote-only, never published, or gated
  Answer: 

- Claims we can prove, each with its source, versus claims we must never make
  Answer: 

- Competitor mention policy
  Answer: 

- Anything low-profile or confidential the system must protect
  Answer: 

- House mechanics: date format, phone format, dash policy, capitalisation
  Answer: 

## 6. Facts

Feeds into: the facts layer, the part everything else cites

- REQServices and products: plain-English description, who it is for, price or range, timeline, which one is the flagship
  Answer: 

- REQPricing detail, and exactly what is quotable
  Answer: 

- Credentials, licenses, certifications, awards. Verifiable only
  Answer: 

- Founding story, history, key dates
  Answer: 

- Stats you can cite, each with its source
  Answer: 

- REQThe top ten questions clients ask, with your best answers
  Answer: 

- Testimonials, with written-permission status per quote
  Answer: 

- REQThe document upload manifest: decks, price lists, sample deliverables, SOPs. Preserved verbatim
  Answer: 

## 7. Market

Feeds into: competitor and SEO facts, and module triggers

- Top three to five competitors, with your one-line take on each. Verified by live search at build time
  Answer: 

- Service area detail: cities and regions, ranked
  Answer: 

- Why you win: two to four pillars
  Answer: 

- SEO ambition, and target searches if known
  Answer: 

- Where clients actually come from today
  Answer: 

## 8. Brand

Feeds into: the Brand OS, and house style

- REQBrand maturity: a full Brand OS exists, or logo and colors only, or starting from scratch
  Answer: 

- Upload manifest: logos, fonts, guideline documents, collateral you love
  Answer: 

- Known color codes
  Answer: 

- Visual direction words, and brands you admire
  Answer: 

- The visual never-list
  Answer: 

- If starting from less than a full system: the Brand OS build request is generated automatically, and audited against a five-part contract before assembly proceeds
  Answer: 

## 9. The collateral menu

Feeds into: skills, templates, and the routing table

- REQPick from the catalog: print, web, email, presentations, social, business documents, sales and ops
  Answer: 

- REQThe first three pieces you need on day one. These become the reference gold standards, built first
  Answer: 

## 10. Modules and infrastructure

Feeds into: optional modules and integrations

- Website: keep existing, rebuild inside the brain, or none
  Answer: 

- A content and SEO engine, yes or no
  Answer: 

- Partner or account kits, and the list of accounts
  Answer: 

- Team size, which selects the workflow-zone variant
  Answer: 

- Meeting and transcript filing
  Answer: 

- Accounts that exist: repository, hosting, workspace, CRM, email sender. Credentials are never collected on a form, dashboard-only, as a rule
  Answer: 

## 11. History

Feeds into: the memory layer

- Decisions already locked, which the AI must not reopen
  Answer: 

- Known unknowns, seeded straight into the questions register
  Answer: 

- In-flight work: campaigns, launches, deadlines
  Answer: