Skip to main content

Marketing-site reference — benaios.com (offer/narrative)

reference · pm · updated 2026-06-28 · source

Captured 2026-06-10 (#296). José: "this is like what I want" — reference for message, offer and narrative for the tuempresa.digital / TED OS marketing page. NOT a visual design reference — the aesthetic comes from our own brand (knowledge/brand.md, Paper artboards), not from this site. Screenshots: references/benaios/ — benaios-00-fullpage-1440.png (everything) + benaios-01-hero … benaios-09-footer (per section, 1440px).

What they sell (in one line)​

"AI Operating System installed in 14 days, owned by your team" — productized installation of a Second Brain + 2 proof automations, with full handoff to the client.

Why it's the reference​

  • Productized offer with a fixed timeframe: "14 days" in the hero, the CTA and the timeline. No open scope.
  • Ownership as the differentiator: "Owned by your team on day one of handoff" — anti agency dependency.
  • A single repeated CTA: "START THE 14-DAY INSTALL" (nav, hero, close). Zero services menu.
  • Explicit anti-funnel: "Straight to a real call. No funnel. No email gauntlet."
  • A named role on the client side: "The Operator" — whoever runs the system after the handoff (≈ our internal builder/operator from the builder-network model).

Page structure (5 sections + close)​

#SectionMessage
Hero"Become an AI-first company with your Second Brain OS""Your team has ChatGPT. Your company has nothing." → we install the shared infrastructure
01 PROBLEM · The Gap"Your team has AI. Your company has scattered context."Knowledge scattered across Slack/Drive/CRM/people's heads; Day 14 → Year 1 timeline showing how institutional intelligence compounds vs. staying flat
02 SYSTEM · What gets installed"The anatomy of your AI Operating System"2 deliverables: (1) Second Brain — a shared, queryable context layer that connects to the existing stack without replacing anything; (2) Two proof automations — one proving the Brain works, the other that the pattern repeats ("Why two")
03 TIMELINE · The 14 days"Three phases. Two weeks. One handoff."Days 1–4 Discovery (real screen-shares, not docs) → Days 5–10 Brain Setup → Days 11–14 Proof + Handoff. Each phase with an explicit OUTPUT
04 OPERATOR"Who runs the Brain after we leave."Not a new hire: someone on the team, a few hours/week. 4 functions: maintains the Brain, ships new automations, onboards, internal point of contact
Close"Install your Second Brain.""One call to scope it. One handoff to run it." + CTA

Copy patterns to replicate (mechanics, not text)​

  • Individual vs. institutional contrast: "Your team has X. Your company has nothing/scattered context."
  • Concrete numbers everywhere: 14 days, 2 automations, 3 phases, 4 Operator functions.
  • "Why two" — they justify the deliverable's scope (one proof + one repeatable pattern).
  • Compounding timeline (Day 14 / Month 1 / Month 3 / Month 6 / Year 1) to sell the long term.
  • Each timeline phase closes with "OUTPUT: …" — the delivery contract visible on the page.
  • "We watch how the business actually runs, not how the docs say it runs."

Mapping to TED OS (note, not decision)​

  • Their "installed Second Brain OS" ≈ TED OS delivered to a B2B client (MVP ~90 days, first paying client).
  • Their "Operator" ≈ our builder / internal client operator (builder-network).
  • Their anti-funnel + deal clarity = the same spirit as the "deal clarity" in the builder model.
  • Pricing: the page does NOT show prices — everything goes to a call. Our pricing is still undefined; this doc fixes nothing about it.