Skip to main content

Knowledge > Products > WiseAI Agency

WiseAI Agency Overview

What It Is​

WiseAI Agency is not a product — it is the meta-brand that sits above the family of vertical AI care products. It is the parent/tech/trust surface where prospects, partners, and investors can see the whole platform story in one place: the engine, the verticals already live, the verticals in the queue, and the pastoral-care DNA that makes the whole thing coherent.

Think of it the way NVIDIA's brand sits above RTX, Tegra, Omniverse: one platform, many product lines, unified story.

Status​

FieldValue
Domainwiseaiagency.com (hostname rewrites to /wiseaiagency/* in churchwiseai-web)
Codebasechurchwiseai-web/ (shared, routes under src/app/wiseaiagency/)
StatusLive marketing + demo playground
Deploy branchmain → Vercel (same project as churchwiseai.com)
Sells anything directly?No — all CTAs route to the appropriate vertical brand site (ChurchWiseAI, FuneralWiseAI, etc.) or a custom-engagement contact form

Why WiseAI Agency Exists​

  1. Brand architecture. Each vertical (ChurchWiseAI, FuneralWiseAI, future VetWiseAI, etc.) has its own tone, palette, and customer. None of them should carry the weight of "here's the whole platform." WiseAI Agency does.
  2. Investor + enterprise surface. A funder evaluating the business, or a funeral-home corporate chain wanting a custom deployment, needs a single trusted URL that shows scale and thesis. That's wiseaiagency.com.
  3. Cross-vertical discoverability. A funeral director who stumbles onto WiseAI Agency through ChurchWiseAI content can find FuneralWiseAI without any awkward cross-branding on the church site.
  4. Demo playground. A single place where a prospect can try chatbot or voice across any vertical before deciding which brand matches their business.

Positioning​

  • Voice: Technical authority, pastoral origin. Not a startup voice — a craft-house voice.
  • Tagline direction: "AI care agents, one vertical at a time." (from code — subject to refinement)
  • Core claims: One engine (LiveKit + HEAR), multiple brand-tuned verticals, pastoral-care DNA, founder-operated, solo-founder + AI-agent ops model.

Vertical Family (from wiseaiagency/page.tsx)​

The home page presents four tiles describing the current state of each vertical:

VerticalDomainTaglineStatus
ChurchWiseAIchurchwiseai.com"AI care agents for churches."Live — primary commercial vertical
FuneralWiseAIfuneralwiseai.com"AI answering for funeral homes."Live marketing + demo, customers TBD
(third tile)—"Coming after funeral proves the pattern."Placeholder — next vertical gated on FuneralWiseAI validation
(fourth tile)—"Doctor, music school, real estate, and more. Parked and ready."Domain portfolio — shopwiseai.com, veterinarywiseai.com, legalwiseai.com held but not built

Pages (site map)​

RoutePurpose
/wiseaiagencyHome — meta-brand tagline, vertical family tiles, platform claims, founder story teaser
/wiseaiagency/verticalsFull verticals directory — each brand with status, description, and outbound link
/wiseaiagency/technologyThe engine story — LiveKit voice stack, multi-agent orchestration, HEAR protocol, per-vertical training
/wiseaiagency/playgroundPhase 4c Demo Playground — pick product (chatbot / voice) + vertical (funeral, vet, dental, restaurant, law, real estate); live pre-trained demos per vertical; conversion CTAs route to the brand site or a waitlist form
/wiseaiagency/aboutJohn Moelker's pastoral + engineering background, WiseAI founding story
/wiseaiagency/contactCustom-engagement inquiry form (not retail — for chains, partners, investors)

All routes are middleware-rewritten from wiseaiagency.com/*.

The Embed Program (Phase 4a)​

WiseAI Agency also hosts the brand sales chatbot infrastructure — /embed/brand is an iframe-hosted chatbot that any of the vertical sites can load via public/embed/churchwiseai-widget.js with data-brand-scope set. It talks to /api/chatbot/unified with a brand param and answers product questions about that specific vertical. Noindex. See churchwiseai-web/CLAUDE.md for the route catalog.

Technical Architecture​

WiseAI Agency shares the entire ChurchWiseAI stack:

  • Frontend: Next.js 16 routes under src/app/wiseaiagency/ in churchwiseai-web. No separate codebase.
  • Brand scoping: layout.tsx sets data-brand="wiseaiagency" so CSS variables swap to the meta-brand palette.
  • Demo playground: Reuses the same chatbot (/api/chatbot/unified) and voice (LiveKit demo numbers) infrastructure — just scoped to each vertical's demo prompts.
  • No subscriptions: WiseAI Agency never appears in premium_churches or Stripe. It is purely a marketing + demo surface.
  • Deployment: Same Vercel project (churchwiseai). Hostname rewrite in middleware.ts maps wiseaiagency.com/* → /wiseaiagency/*.

Relationship to Other Brands​

WiseAI Agency (meta-brand, wiseaiagency.com)
│
├── ChurchWiseAI        — churches          — churchwiseai.com     [LIVE]
├── FuneralWiseAI       — funeral homes     — funeralwiseai.com    [LIVE]
├── (next vertical)     — TBD              — TBD                 [PLANNED]
└── (future)            — vet, law, etc.   — *wiseai.com parked  [ROADMAP]

Separately (non-vertical ecosystem products — not under WiseAI Agency):
  ├── PewSearch           — church directory     — pewsearch.com
  ├── IllustrateTheWord   — sermon illustrations — illustratetheword.com
  ├── SermonWise AI       — sermon prep          — sermonwise.ai
  └── ShareWiseAI         — social SaaS          — sharewiseai.com

Key distinction: WiseAI Agency contains only the vertical AI-care products. PewSearch, ITW, SermonWise, and ShareWiseAI are ChurchWiseAI ecosystem products but not WiseAI Agency verticals — they solve different problems (discovery, content, prep, social) rather than being "AI answering for X vertical."