Public pages
The homepage desktop display headings and supporting copy use a larger scale consistent with the other marketing pages. Its Questions and contact section is visible after the closing call to action, with individual FAQ disclosures and a separate contact form card; the whole section is not hidden behind a closed disclosure. Submitting the homepage contact form sends an interest notification through Resend to CONTACT_LEADS_TO (default [email protected]) and uses the visitor's email as Reply-To. Configure RESEND_API_KEY and a verified-domain RESEND_FROM on the server. Until those settings work, the form shows an error and links visitors to the direct email address instead of claiming the message was sent. The home page, Product, Solutions, Integrations, Events, About and Book a Demo pages explain the platform. Product and Solutions navigation panels open on hover-capable devices, remain clickable on touch and keyboard, and do not remain open together. Product previews are labeled as examples. The About page presents the mission, story and published product milestones, then explains the platform through one automatically sequenced product story. The published principles follow that showcase. Its supplied futuristic eco-tech command-center image forms the full-bleed hero background, darkened on the left to keep the headline readable. A client-rendered Three.js workforce scene layers in front with a heavy, multi-tier Orchestrator machine, a transparent spherical chamber with structural ribs, a suspended energy core, a rotating mechanical ring assembly, and six thick orbital platforms. Every specialist link is a curved 3D cable with a visible physical socket; eight staggered packets travel outbound and back along each of the six routes continuously, with cable and endpoint light pulses. The hero presents one larger Explore AI Pods call to action and more legible workforce benefit labels without the former secondary See how it works link. The six specialists are the approved high-definition transparent PNG illustrations, positioned on the platforms with contact shadows; procedural mascot meshes and retired model renders are not used. The cinematic machinery uses perspective, physically based materials, shadows, reflections and atmospheric lighting. The scene contains no interface panels or decorative labels. This is illustrative: no workflow runs and no tool connects. Reduced-motion preferences stop the animation and off-screen scenes pause rendering. The About workflow titled Build your AI team starts at its first stage only when at least 15% of that section enters the viewport. Its timeline pauses while off-screen or in a hidden browser tab, then resumes without skipping stages; stage selection and Replay remain available. The product showcase titled See what we are building follows one fictional Northstar product-launch brief through ten beats: ten example employees, an objective, a plan, four assigned specialists, three tool-context arrivals, a draft, a human review, and a reviewed outcome. The four chapters advance automatically in about 18 seconds without tab clicks. On large desktop viewports, the story stays below the header during a bounded native scroll sequence; scrolling forward advances the workflow. Skip story links go directly below it. Mobile, short viewports, and reduced-motion mode keep normal page flow. Playback begins with the workforce only when the visual is at least 20% visible, pauses off-screen or in hidden tabs, and holds on the completed outcome. Pause, previous/next, chapter selection, and Replay remain available. Selecting a chapter or step pauses playback; reduced-motion preferences require manual progression. Notion, Google Drive, and Slack supply labeled fictional context, not live reads. The review shows an example correction to an unsupported claim. No tool is connected, no reviewer is actually contacted, and nothing is published. The hero summary reports 28 roles from the employee registry and the six specialists shown, alongside human-guided and governance principles; it does not claim unverified performance statistics. The product story uses static canonical employee artwork with HTML/CSS transitions, not a real-time 3D engine. Its ten-role example is a subset of the registry, not a change to the total role count. Mission, story, milestones, and principles come from the admin-managed About content. Unpublished milestones and principles are omitted.
The home page hero uses the supplied office-and-city background and a progressive eight-scene campaign story. It begins with the empty room, then a woman and laptop arrive, her marketing-campaign request appears, and one Workforce Orchestrator receives it. The plan takes focus, five named specialists enter one by one, their contributions are collected, and a single review-ready package remains. Future actors and output cards are not present before their scene; the duplicate intake bot and persistent connector diagram have been removed. Canonical specialist names and illustrations are unchanged. The sequence takes roughly fourteen seconds after assets are ready, starts when 30% of its viewport is visible, pauses off-screen or in hidden tabs, and holds the final package until Replay. Previous/next and direct chapter controls pause playback; the hero’s own pause control does not change the separate workflow example below it. Reduced-motion mode advances manually without entrance animation. A fixed-height mobile storyboard replaces the old long vertical composition. The expandable gallery still exposes all current registry roles. Each specialist now shows a different contribution to the fictional Morrow Focus Notebook launch: brief inputs and hypotheses, marketing copy, an original ad, a proposed seven-day calendar, and measurement definitions. Select a specialist to pause and inspect their work. The final package offers Creative, Copy, and Plan previews; Open the campaign displays a full scrollable report. Visitors can download the original ad PNG, six-page campaign PDF, and launch copy TXT. The product picture is an AI-generated concept; copy and reports are authored sample artifacts, not the output of a live agent run. No campaign results are claimed. This demonstration never runs a campaign, submits an objective, or connects tools. Three distinct character cards lead to creating a pod, exploring solutions, and learning about the product. The five-stage workflow demonstration supports play, pause, replay, and direct stage selection; it changes only the example UI and never updates an external system. Reduced-motion preferences disable automatic animation; the separate workflow example remains usable through manual stage controls. Ambient character motion and demonstration playback pause while their sections are outside the viewport, and automatic demonstration playback pauses in a hidden browser tab. The previous multi-objective simulator and full registry explorer remain available in expandable panels. Filterable employee cards and the registry count come from the current agent definitions; the catalog count comes from the public catalog, whose entries require configuration and are not installed accounts. The Everything the pod needs to work section demonstrates a customer handoff or launch brief using authored Google Drive, Notion, and Slack excerpts. Four stages show selected sources, an example access policy, source-linked context assembly, and human review. The 5.4-second sequence starts when 30% of the resulting brief panel is visible, pauses off-screen or in hidden tabs, and holds at completion. Source inspection and chapter selection pause playback; reduced motion advances manually. The examples never read connected accounts, change permissions, or send messages. Solution cards link to the six current solution routes. The autonomy selector describes illustrative operating levels, and the governance panel presents configurable concepts, not a claim that every control is active in a visitor's workspace. The closing call to action opens booking; questions and contact remain available below it.
The Product navigation opens three single-action cards: Build links to the lifecycle, Connect links to Integrations & MCP on the Product page, and Operate links to deliverables. Explore product opens the Product overview. The bullet points explain each route; they are not separate controls.
The Product hero presents a centered workforce workbench: an objective, two specialists, approved context and human review. Selecting a node pauses at that stage. Lifecycle, capability, integration, employee, activity, request, knowledge, document and deliverable controls remain local demonstrations. The button above the lifecycle selector opens the existing preview dialog. Counters and charts are fictional. Hero playback reaches review after 3.4 seconds, with manual controls and reduced-motion support; no workflow is deployed.
Demo booking behavior
The public Book a Demo page embeds a Calendly event type using the configured HTTPS event URL, which defaults to https://calendly.com/contact-theaipods/30min. NEXT_PUBLIC_CALENDLY_URL can override it. Calendly supplies availability, invitee fields, time-zone handling, confirmation, and any calendar or meeting integrations configured in that Calendly account. AI Pod does not create or confirm a reservation until Calendly reports calendly.event_scheduled. When the configured URL is invalid, the page shows a setup state. The older internal demo scheduler and its API remain in the codebase for existing direct integrations, but this public page does not submit to them.
The public Book a Demo page opens with a private walkthrough scene. Header and footer Book a demo links open the top of this page; the in-page scheduling actions move to the calendar. Finance, People and Customer work selections change the employee and sample agenda in that hero only. The primary action opens the Calendly panel below; the existing six focus cards pass their topic as Calendly UTM context. Visitors enter details and choose a time in Calendly. The From conversation to real possibilities section uses an image-free, four-stage conversation-to-plan preview: challenge, workflow, review checkpoints, and next steps. Selecting a stage changes an illustrative brief and pauses automatic progression. Playback waits until the section is visible and pauses off-screen, in hidden tabs, or for reduced-motion preferences; manual selection remains available. The Bring your use case link returns to the booking calendar. The tools strip and closing booking action remain. Illustrations do not connect accounts or execute work.
The public Events page opens with an interactive front-row session preview. Choose a product-demonstration, hands-on-workshop, or human-review question; each follows a question, a concrete example, an audience follow-up, and a takeaway. The preview advances in about nine seconds once its visual enters the viewport, pauses off-screen or in hidden tabs, and holds on the takeaway. Pause, chapter selection, and Replay remain available; reduced-motion preferences use manual chapters. It is an illustrative HTML/CSS presentation, not a live broadcast, recording, or executed workflow. Light mint, blue and white sections and the supplied From the stage conference artwork follow. Its hero actions scroll to the featured event or archive. The page includes a featured event, archive filtered by the years and event types present in the data, past-session cards, resource links, private-session booking action, and FAQ. Featured registration uses the existing event registration form. A past-session card says Watch recording only when that event has a recording URL; otherwise it opens event details as View session. The current seeded events are sample events and their past sessions do not yet have playable recordings. Minimal finance, enterprise-design and human-approval illustrations each use one distinct mascot, a simple prop and a pale background. These and the featured television scene are illustrative event artwork. The conference artwork is decorative and does not imply a video is available; the “Watch past sessions” action opens the archive. The news destination currently announces future updates rather than published articles. Event detail pages and registration management remain available. The removed upcoming catalog, live-series duplicate, speaker showcase, and topic browser are not part of this page.
Application pages
After signing in, Onboarding saves company context. Its 19 steps are grouped into six chapters: Discover, Understand, Connect, Configure, Simulate and Launch. Select a chapter to reveal its steps; switching steps keeps the current in-memory draft. Save draft or Save & exit persists changes. Each step has a contextual blueprint preview, and readiness is calculated from actual setup requirements rather than steps visited. Help me fill this step requests editable AI suggestions for eligible fields using the configured chat provider. Customize AI help supplies additional context or targets a field; Draft complete onboarding prepares suggestions across eligible sections. Review and accept fields individually, then save. Website research remains available on Company. AI does not grant permissions, invent actual headcounts or activate the company. Workspace contains the command center, Pods, Results, Decisions, Company blueprint, AI employees, Work & activity, and MCP & integrations settings.
Admin
The platform-owner admin console is separate from a company owner’s workspace and restricted to authorized administrator accounts. Its overview shows account, company, file and administrator totals. Manage owners opens Accounts; select an account to inspect its companies. The older /admin#owners link also opens Accounts.
Files opens a company directory labeled by website. Select a company to see only its uploaded files. Search beside the file totals filters company websites before selection, then filenames, categories and statuses within the selected company. Files remain stored against their company, not a shared global folder. Text indexing extracts readable content into saved chunks. The worker creates model-tagged embeddings with configured NVIDIA or Azure credentials. Live retrieval combines semantic similarity and keywords; missing or failed embeddings fall back to keywords.
Settings contains Edit About and homepage team visibility. Events remains in the sidebar with its existing editors; neither editor is an overview shortcut. Change password and Log out are below the administrator profile in the sidebar. The standalone admin Pods view has been removed; operational work remains in Workspace. Refresh failures display an inline error while retaining loaded records.