{/* Available lenses tray */}
Pick lenses · stack up to three
{LENS_LIBRARY.map((l) => (
))}
{/* Industry picker */}
Pick the industry context
{INDUSTRIES.map((i) => (
))}
{/* Scenario picker */}
Pick the problem
{SCENARIOS.map((s) => (
))}
{/* Claude-style consult panel */}
CLAUDE · LENS CONNECTOR
INDUSTRY: {ind.label.toUpperCase()}
ATTACHMENT: {sc.label}
{activeLenses.length === 0 ? (
Pick at least one lens above.
) : activeLenses.map((r, i) => (
{r.role.toUpperCase()} LENS
“{r.tagline}”
… {r.name}
{getTake(r.id, scenario, industry)}
))}
{LENS_LIBRARY.length} LENSES · {INDUSTRIES.length} INDUSTRIES · {active.length} STACKED
YOUR LIBRARY GROWS AS YOU CAPTURE
TRY IT … STACK LENSES, INDUSTRY, OR PROBLEM ABOVE · COMPOSITE · NAMES AND NUMBERS ABSTRACTED
{/* HERO */}
Lens.
{/* Headline with fixed-width slot for the rotating role to prevent line bleed */}
See any business problem through your{' '}
{role}
{"’"}s lens.
Connect Lens inside Claude. Drop in the spreadsheet, the deal memo, the customer thread … then consult any role on your senior team.
{/* DEFINITION — simple, eye-catching, five-year-old can read it */}
What Lens is
Your best people, on demand.
We capture how your senior team thinks. Then anyone on your team can ask them a question in Claude … and get an answer in their voice.
{/* INTERACTIVE STACK */}
How it{"’"}s used
Stack the lenses you need. Run them on any problem.
Lens captures the tribal knowledge of your senior team {"\u2014\u2009"}role by role, voice by voice. Stack any combination. Run them against the spreadsheet, the memo, the LOI. Add new lenses for new roles, new industries, new operators as you grow.
{/* WHAT YOU'RE ACTUALLY BUYING — spec sheet (Variant A) */}
{/* FAQ removed from here — moved to the very end of the page */}
{/* FINAL CTA — workshopped headline */}
Tribal knowledge, captured.
Stop losing your senior team{"’"}s judgment to inboxes, calls, and memory.
Lens captures it once, in their voice, and makes it consultable for everyone who needs it next.
{/* FAQ hidden 2026-05-01 per Christien — keep component available for future restore */}
);
}
// ---------- FAQ ----------
// Final 12-question set from the 2026-05-01 hand-off package.
const FAQ_ITEMS = [
{
q: 'Where does Lens live?',
a: 'Inside Claude. Lens is a Custom Connector you add once on the team account. After that, every captured operator shows up in the same chat your team already uses. No separate login.',
},
{
q: 'Has anyone used a lens to make a real decision yet?',
a: 'Yes. Real uses to date include rewriting a board memo in the captured CFO\u2019s voice, redlining an LOI through the captured GC, and structuring a churn diagnosis through the captured Head of Ops.',
},
{
q: 'How does capture work without burning the operator\u2019s time?',
a: 'About 2 to 3 hours of operator time, spread over two weeks. Most of it is forwarding existing memos and recordings of recurring meetings already on the calendar. A Telegram capture line handles ad-hoc notes between sessions. We don\u2019t run interviews. Most operators stop being asked the same question 6 times a quarter by week two.',
},
{
q: 'What happens to my data, who can read it?',
a: 'Each client has their own data. Each captured operator is maintained as its own file inside that client\u2019s space. Nothing crosses between clients. Nothing crosses between captured operators.',
},
{
q: 'How is this different from a custom GPT or a Claude project?',
a: 'A custom GPT or project gives you a system prompt and a few uploaded files. Lens captures judgment over time across memos, calls, and decisions, with inline citations back to source. The operator\u2019s voice is derived from a structured corpus, not a paragraph of instructions. And it compounds: every new memo, redline, or recording refines it.',
},
{
q: 'What happens when the operator leaves?',
a: 'The lens stays. That is the point. Captured judgment is a company asset, not a personal one. When your retiring CFO walks out the door, her reasoning on the last six quarterly reforecasts is still consultable next Tuesday. The next person in the role inherits a captured predecessor, not a blank seat.',
},
{
q: 'Who can use a lens, and how does access work?',
a: 'Any seat on your team Claude account that you grant. You can stack lenses (CFO + GC + Head of Ops) in a single chat, attach a document, and consult them together. Access is per-seat and revocable. Soft cap of 3 lenses per query, see failure modes.',
},
{
q: 'What does it cost?',
a: 'Three components. An install fee (one-time, covers hand-run capture and setup). A monthly retainer (covers up to 10 lenses, freshness tuning, support). A per-lens fee for additional captured operators beyond the 10 in the retainer. Pricing is per-lens, not per-seat. We are calibrating during operator preview, so exact numbers are negotiated as part of the pilot conversation.',
},
{
q: 'Who builds the lens?',
a: 'The Lens team builds it directly alongside you. We run intake with the source operator (one 60 to 90 minute capture session), review the first batch of structured records with you, and tune voice over the first two weeks. Existing memos, recurring meeting recordings, and a Telegram capture line for off-hours notes are folded in throughout. Self-serve build is not on the 2026 roadmap. The judgment about what to capture and how to tune voice is the work, and that work is human-led today.',
},
{
q: 'What if my industry is unusual?',
a: 'Lens does not assume a vertical. The captures come from your operator and your documents, so industry context is whatever you bring. Healthcare and B2B services are well-represented in the live tenants. Other verticals are doable but unproven at scale.',
},
{
q: 'What are the failure modes?',
a: 'Three real ones. First, sparse capture: if the operator has no written memos or recurring meetings, the voice stays generic. Second, voice drift: if the operator\u2019s thinking changes faster than the capture cadence, the lens lags reality. Third, over-stacking: combining 5+ lenses in a single query produces consensus mush. We address these with capture-density checks, freshness decay, and a soft cap of 3 lenses per stack.',
},
{
q: 'When is Lens the wrong answer?',
a: 'Three cases. First, if your senior operators don\u2019t already write memos or run recurring meetings, there\u2019s nothing to capture. Lens captures what\u2019s already being expressed, it doesn\u2019t manufacture judgment. Second, if your team isn\u2019t on Claude, this isn\u2019t the moment for you. We deliver inside Claude, not as a standalone product. Third, if you need a single answer to a generic question (best-practices, industry norms), a frontier model already does that for free. Lens is for "what would our CFO say about this specifically."',
},
];
function FAQItem({ item, color }) {
const c = color || LENS_DEFAULT;
return (