// Use Cases — sector-specific landing pages targeted at Head of Sales, AMs, // CROs, and CEOs in each industry. AEO/GEO-friendly: each sector gets its own // persona/pain/signals/weekly-loop framing so AI engines surface them for // sector-specific buyer queries ("AI for manufacturing sales", "B2B catering // account management", etc.). // // Routes: // #/use-cases → UseCasesHub (directory + "more coming" tile) // #/use-cases/manufacturing → UseCase slug='manufacturing' // #/use-cases/catering → UseCase slug='catering' const { useState: useStateUC } = React; const USE_CASES = { manufacturing: { slug: 'manufacturing', name: 'Manufacturing', short: 'Manufacturing & industrial distribution', tagline: 'For industrial distributors, parts suppliers, and equipment manufacturers', cardSummary: 'Long sales cycles, channel-partner complexity, RFQs scattered across email and CRM, and reorder rhythms that vary by account.', heroDek: "Long sales cycles, complex spec discussions, channel partners drifting in and out of activity, and a book of recurring accounts where the meaning lives in the details. Nautilida runs the weekly rhythm so the team — leadership, AMs, channel managers — walks into Monday already knowing where to act.", audience: [ {role:'Head of Sales', context:'Industrial distributors managing 100–1,000 active reorder accounts.'}, {role:'Account Managers',context:'Covering 20–80 accounts each, balancing recurring orders with one-off RFQs.'}, {role:'CROs', context:'B2B parts, equipment, and raw-material suppliers running multi-channel revenue.'}, {role:'CEOs', context:'Small and mid-market manufacturers selling through reps and channel partners.'}, ], pain: [ "Long sales cycles with multiple buyer-side stakeholders — engineering, procurement, plant ops — and no system that holds the full thread.", "Reorder rhythms vary by account: some monthly, some quarterly, some only when stock runs low. No easy way to see which ones are slipping until a quarter is already missed.", "RFQs and quote revisions scattered across email, CRM, and spec sheets, with no memory tying them to historical decisions on the same account.", "Channel partners and distributors that go quiet for weeks and nobody notices until pipeline is gone.", "AM rotations wipe months of compounded context — what the buyer cared about, the price commitments, the spec everyone agreed on.", ], signals: [ 'Reorder frequency and basket-change patterns at the account level', 'Quote-to-order conversion windows and revision counts', 'Spec discussion drift — when a spec keeps changing, that is the signal', 'Channel partner activation cadence', 'Engagement decay on key buyer contacts (procurement, engineering, plant managers)', 'New buyer surfaces — procurement contacts changing means the relationship is in transition', 'Service contract renewal windows', 'Industry-specific seasonal patterns (capex cycles, fiscal-year budget windows)', ], loop: { mon: "Top reorder accounts at slip risk. Top RFQs likely to close. The one channel-partner pattern that changed since Friday. The AM team gets their priorities by 9am.", mid: "Every AM walks into account calls with the last three touches, open RFQ threads, the spec still being debated, and the buyer-side question left unanswered.", fri: "What moved across the book this week. Which RFQs progressed. Which channel partners came back. The plan for next Monday is already drafted.", }, faqs: [ {q:"Our reorder cycles vary wildly by account. Can Nauti handle that?", a:"Yes — Nauti reads each account's individual reorder pattern over months, not a one-size-fits-all rule. Monthly, quarterly, or stock-driven, the pattern is what matters and the pattern is what compounds in memory."}, {q:"We sell through distributors and direct at the same time. Does that confuse it?", a:"No. Nauti's account memory holds both shapes side by side — a direct account and a channel-partnered account look different in the data, and the brief reflects that. Each AM and channel manager gets a view scoped to their book."}, {q:"Our deals involve engineering and procurement. Does Nauti understand spec discussions?", a:"It reads them like any other buyer signal. A spec that keeps changing is a signal. A spec that gets locked is a signal. Engineering going quiet is a signal. The brief surfaces which ones matter this week and why."}, {q:"Our CRM hygiene isn't great. Will Nauti still work?", a:"Yes — Nauti reads email and chat alongside CRM and fills gaps. If the CRM is sparse but the inbox is rich, the inbox carries the memory. Improving CRM hygiene over time is a side-effect, not a precondition."}, {q:"Who on our team uses it day-to-day?", a:"Head of Sales gets the Monday brief and Friday recap. Each AM gets their own priority list and pre-call prep. The CRO gets the portfolio-level recap. Channel managers get partner-specific patterns. Same loop, different lens."}, ], }, catering: { slug: 'catering', name: 'B2B Catering', short: 'B2B catering & corporate hospitality', tagline: 'For B2B catering firms, corporate event companies, and hospitality providers', cardSummary: 'Office reorders, one-off events, and hybrid bookings in the same memory. Skip signals, day-of-week shifts, and destination classification when tags are missing.', heroDek: "Office catering, corporate events, hospitality contracts — different shapes, same memory. Nautilida runs the weekly rhythm so the team walks into Monday already knowing which accounts are slipping, which events should have rebooked but haven't, and which patterns just changed.", audience: [ {role:'Head of Sales', context:'B2B catering firms managing 50–500 active accounts across offices and events.'}, {role:'Account Managers',context:'Balancing recurring office catering with one-off corporate events and hybrid bookings.'}, {role:'CROs', context:'Corporate hospitality and food-service companies running multi-shape revenue.'}, {role:'CEOs', context:'Catering firms operating across offices, events, and seasonal contracts.'}, ], pain: [ "Office accounts, one-off events, and hybrid bookings — three different signal shapes, often inside the same CRM with the same fields.", "Reorder windows for office catering that drift quietly — a weekly office that goes silent for two weeks isn't always flagged in time.", "Event re-booking patterns lost across reps — last year's repeating event might not get rebooked this year if nobody is tracking it.", "Destination classification (office / event / other) often unknown without HubSpot tags, and tags get missed in the rush.", "Seasonal spikes (holiday, summer, fiscal year-end) overlap with steady reorder accounts and confuse the leadership view.", "AM rotations lose months of buyer-relationship context that lived in one person's head.", ], signals: [ "Skip signals — accounts that ordered on a rhythm and missed the last window", "Changed order sizes (head-count shifts as offices reopen, contract, or expand)", "Day-of-week shifts — a Tuesday office that drifts to Wednesday means something", "Destination classification (office / event / other) — HubSpot tag first, order content fallback", "Event re-booking patterns — last year's repeating events that haven't rebooked this year", "Seasonal pattern overlay — separates seasonal spikes from real account shifts", "New buyer surfaces — when the admin contact inside an office account changes, the relationship has moved", ], loop: { mon: "Three office accounts skipped their reorder window. Two events from last year haven't rebooked. The Wednesday-office pattern shifted. The AM team gets their priorities.", mid: "Every AM walks into account conversations with last orders, the rebooking due-window, the head-count trend, and the destination history.", fri: "What moved across the book. Which offices came back. Which events booked. What patterns broke. Monday's plan is already written.", }, faqs: [ {q:"We have a mix of recurring office accounts and one-off events. Can Nauti handle both?", a:"Yes — that mix is the use case. Nauti separates the two signal shapes (recurring rhythm vs event re-booking) inside the same account memory, so the office side and the event side stay legible without forcing them into the same template."}, {q:"Our HubSpot tags for office vs event are inconsistent. Will Nauti work?", a:"Yes. Nauti reads the order content as a fallback — head count, time of day, recurring vs one-off shape — and infers the destination type when tags are missing. Tag hygiene improves over time but is not a precondition."}, {q:"Our season is wildly cyclical (holiday spike, summer slump). Does Nauti get confused?", a:"No. Pattern recognition runs on the account level over months, so seasonal effects are separated from account-specific shifts. The Monday brief tells you which accounts are slipping in absolute terms, not against a flat baseline."}, {q:"Who on the team gets value from it?", a:"Head of Sales gets the Monday brief and Friday recap. AMs get account-level priorities and pre-call prep. The CRO can ask Nauti portfolio-level questions any time — top accounts, events that didn't rebook, growth shifts. The CEO can ask \"which accounts grew this quarter\" without anyone assembling a spreadsheet."}, {q:"We've got AMs who rotate accounts. Does that break the memory?", a:"No — that is the whole point. Account memory travels with the account, not the rep. The new AM walks into the relationship with months of context already there: last orders, rebooking due-windows, the contact who actually decides, the patterns that matter."}, ], }, }; function UseCasesHub(){ const goHome = (e)=>{ e.preventDefault(); window.location.hash = ''; }; const goWaitlist = (e)=>{ e.preventDefault(); window.location.hash = '#/waitlist'; }; const goContact = (e)=>{ e.preventDefault(); window.location.hash = '#/contact'; }; const order = ['manufacturing', 'catering']; const cards = order.map(slug => USE_CASES[slug]).filter(Boolean); return (
{/* Top strip */}
← BACK TO SITE
{/* Hero */}
[ use cases · sector deep-dives ]

USE CASES. by sector.

How an AI team lead shows up in real revenue books. Each page is written for the people running the team — Head of Sales, AMs, CROs, CEOs — in that specific sector. Pain, signals, the weekly loop in their terms.

{/* Cards grid */}
SECTORS // {String(cards.length).padStart(2,'0')} LIVE · MORE COMING FOR HOS · AM · CRO · CEO
{cards.map((c)=>( ))}
{/* Outro CTA */}

DON'T SEE YOUR{' '} sector?

Tell us what your book of accounts looks like. If the shape is recurring revenue or repeated relationships, the loop probably fits — and we'll write the page next.

Tell us about your sector → Join the waitlist
); } function UseCaseHubCard({uc}){ const [hover, setHover] = useStateUC(false); const onClick = ()=>{ window.location.hash = '#/use-cases/' + uc.slug; }; return (
setHover(true)} onMouseLeave={()=>setHover(false)} style={{ background: hover ? 'var(--bone-3)' : 'var(--bone)', border:'1.5px solid var(--ink)',borderRadius:14, padding:'24px 24px 22px', boxShadow: hover ? '8px 8px 0 var(--violet)' : '6px 6px 0 var(--ink)', transform: hover ? 'translate(-2px,-2px)' : 'none', transition:'transform .25s cubic-bezier(.2,.7,.2,1), box-shadow .25s ease, background .2s ease', display:'flex',flexDirection:'column',gap:14, cursor:'pointer', }}>
{uc.name.toUpperCase()} USE CASE · LIVE

{uc.short}.

{uc.cardSummary}

· for HoS · AM · CRO · CEO READ →
); } function UseCaseComingCard(){ const goContact = (e)=>{ e.preventDefault(); window.location.hash = '#/contact'; }; return (
// MORE TO COME USE CASE · DRAFTING

More sectors, soon.

Logistics. Pharma distribution. Industrial services. SaaS post-sale. The shape repeats — recurring relationships, cross-stack memory, weekly rhythm. New use cases land here as we write them.

· tell us what fits next WRITE IN →
); } function UseCase({slug}){ const data = USE_CASES[slug]; const goHome = (e)=>{ e.preventDefault(); window.location.hash = ''; }; const goHub = (e)=>{ e.preventDefault(); window.location.hash = '#/use-cases'; }; const goWaitlist = (e)=>{ e.preventDefault(); window.location.hash = '#/waitlist'; }; const goContact = (e)=>{ e.preventDefault(); window.location.hash = '#/contact'; }; if (!data) return null; return (
{/* Top strip */}
← USE CASES ← BACK TO SITE
{/* Hero */}
[ use case · {data.short.toLowerCase()} ]

Nautilida for {data.name.toLowerCase()}.

{data.tagline}. {data.heroDek}

WRITTEN FOR ◉ HEAD OF SALES · AM · CRO · CEO
{/* Who this is for */}
WHO THIS IS FOR {data.audience.length} ROLES
{data.audience.map((a, i)=>(
{a.role} {a.context}
))}
{/* The problem */}

The problem in {data.name.toLowerCase()}.

What the team is actually fighting in this sector — the things that don't show up in a pipeline chart.

    {data.pain.map((p, i)=>(
  • {p}
    • ))}
{/* Signals Nauti reads */}

The signals Nauti reads here.

Sector-specific signals, read across CRM, email, and chat — and synthesized into the weekly brief. The signals are what compound week over week.

{data.signals.map((s, i)=>(
{s}
))}
{/* The weekly loop in [sector] terms */}

The weekly loop in {data.name.toLowerCase()} terms.

What Monday, mid-week, and Friday actually look like in this sector. Same loop, written in your language.

{/* FAQ */}

Frequently asked.

{/* Outro CTA */}

SEE IT ON YOUR{' '} own book.

Connect HubSpot and Teams. The first Monday brief, written for {data.name.toLowerCase()}, lands at 7:00 AM.

Join the waitlist → Talk to a human
); } function LoopCard({label, tone, body}){ const accent = tone === 'lime' ? 'var(--lime)' : tone === 'violet' ? 'var(--violet)' : 'var(--ink)'; const bg = tone === 'violet' ? 'var(--ink)' : 'var(--bone-3)'; const fg = tone === 'violet' ? 'var(--bone)' : 'var(--ink)'; const fgSoft = tone === 'violet' ? 'rgba(250,248,241,.85)' : 'var(--ink-soft)'; return (
◉ {label}

{body}

); } function FAQUC({items}){ const [open, setOpen] = useStateUC(-1); return (
{items.map((it,i)=>{ const isOpen = open === i; return ( ); })}
); } Object.assign(window, {UseCase, UseCasesHub, USE_CASES});