Write an About Page That AI Engines Trust

Act as an entity-SEO specialist. Write my About page so AI answer engines recognize my business as a real, citable entity, and produce matching Organization + Person JSON-LD.

Entity facts:
- Legal name [LEGAL NAME] · brand name [BRAND or SAME]
- Founded [YYYY] in [CITY, COUNTRY] · current HQ [CITY, STATE, COUNTRY]
- Website [https://YOUR-DOMAIN.COM] · logo image URL [https://YOUR-DOMAIN.COM/logo.png]
- Street address [FULL ADDRESS or NONE] · phone [NUMBER or NONE] · email [ADDRESS or NONE]
- Company profile links (LinkedIn, social, directories): [FULL URLS or NONE]
- What we do (customer language): [DESCRIPTION] · who we serve: [DESCRIPTION]
- Founder #1: name, title, year joined, credentials, LinkedIn URL, optional Wikipedia URL: [DETAILS]
- Founder #2 (if applicable): [SAME FIELDS]
- Key team to name: [LIST]
- Areas of expertise (3-5 specific): [LIST]
- Press / podcast / publication mentions (full URLs): [LIST or NONE]
- Awards / certifications with year: [LIST or NONE]
- Years in business [N] · customers served [NUMBER or BLANK] · specific outcome/stat [PROOF]
- Brand voice: [warm-expert / no-nonsense / playful / premium / technical / friendly-everyday]

Pattern A — founder-led services business: leads with founder story and credentials (1-2 named humans are the trust signal).
Pattern B — team / methodology business: leads with methodology and dated track record.
Pick A or B from which carries more weight in my facts.

Output:
1. Pattern choice + one-sentence rationale
2. About page in markdown — H1: what we do + for whom (≤12 words, not "About Us") · answer-first paragraph (≤60 words: what / where / when) · founders section (full name, title, year joined, credentials, one specific accomplishment, LinkedIn + Wikipedia) · what we're known for (3-5 expertise areas with supporting sentences) · track record (dated, specific) · press/mentions (publication + linked URL) · how to reach us (NAP matching the schema). Every claim dated, named, or numbered; none of "passionate about", "trusted partner", "world-class".
3. Single <script type="application/ld+json"> @graph — Organization (name, alternateName, url, logo, foundingDate, founder array, address, contactPoint, sameAs, knowsAbout) + Person per founder (name, jobTitle, worksFor, sameAs, alumniOf), cross-referenced by @id. JSON-valid; omit instead of null.
4. Verification — Rich Results Test URL, Wikidata strategy (which entities to push), and any incomplete field that weakens the signal

Success means every name, date, and URL in the page and schema is one I supplied, and the NAP on the page matches the schema character for character.

Match the tone I specified above exactly; where I gave none, write plainly and warmly, the way a good operator talks to a customer — no corporate filler, no hedging phrases.

Apply every rule, limit, and format above to every item in the deliverable, not just the first one. Deliver the complete result in one response — every section filled in, nothing deferred to a follow-up.

If a required input is missing, ask for it once before starting; otherwise proceed and label any assumption you made.

Notes: R40 refresh; tuned to vendor prompting guidance