> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Your AI teams > The six teams behind the two outcomes: what each lead does, the specialists reporting to them, and where in the product you work with each team. Work in Vortex IQ is organised into six teams. Each team has a **lead** who plans the work, briefs the specialists and reports back to you, and **specialists** who do the individual jobs. You never pick a team: you pick an outcome, and the teams behind it do the work. **Why leads have names and specialists have roles.** You will see your leads every week, so they have names. The specialists behind them are easier to recognise by what they do. Lead names are editable per store, so you can call your health lead whatever your team already calls that job. ## The teams behind each outcome **Pulse** finds and explains, **CodeCraft** fixes, **Bridge** keeps the way back. **Beacon** wins visibility, **Muse** improves the journey, **Compass** stops wasted spend. ## Pulse, store health Watches your store around the clock. Runs your scans and re-checks, keeps your reports current, and raises the alarm on anything that could cost you revenue, usually before you notice. Pulse never applies a change itself: it finds the problem, explains it and hands it on. | Specialist | What it does | | ----------------- | -------------------------------------------------------------------- | | Crawl Specialist | Walks every page type on a schedule | | Findings Analyst | Turns raw issues into ranked fixes | | Evidence Verifier | Re-checks every finding before you see it | | Report Writer | KPI packs, fix lists with the revenue at stake, and review documents | | Risk Monitor | Daily at-risk and revenue-leak checks | ## CodeCraft, store development Your development team on tap. Takes a ticket such as "checkout button broken on iPhone", briefs the specialists, and hands back a reviewed, tested change with before and after screenshots and a way to undo it. Honest enough to close a ticket with "nothing needs changing". CodeCraft works for every team, not only Pulse. | Specialist | What it does | | ------------------ | ------------------------------------------- | | Solution Architect | Designs the fix before anyone writes code | | Conflict Analyst | Checks your other apps will not break | | UI/UX Designer | Anything touching layout | | Developer | Writes the code | | DevOps | Runs the build on your staging copy | | QA Tester | Tests, with before and after screenshots | | Auto-Fix | Repairs failing builds without a round trip | | Security Reviewer | Checks every change | | Release Manager | Opens the change for your review | ## Bridge, staging and migration Safe copies and safe moves. Keeps a staging twin of your store for rehearsing changes, migrates catalogues between stores and platforms with verified counts, and runs the change tracking that makes every other team's one-click rollback real. | Specialist | What it does | | ------------------------ | -------------------------------------------------- | | Staging Operator | Fresh store copies on demand | | Anonymisation Specialist | Customer data never reaches staging | | Migration Mapper | BigCommerce, Shopify and Adobe Commerce, mapped | | Verification Counter | Before and after counts on every move | | Rollback Keeper | Every change tracked live, so undo is always ready | ## Beacon, SEO and AI visibility Gets you found on Google, in image search, and inside AI shopping answers such as ChatGPT and Perplexity. Runs your metadata at catalogue scale and keeps your store readable to the machines that send you customers. | Specialist | What it does | | ------------------------ | ------------------------------------------------- | | Keyword Analyst | What your customers actually search for | | Metadata Writer | Titles and descriptions, on brand, at scale | | Schema Specialist | Rich results: prices, ratings and FAQs in Google | | Content Drafter | Blog drafts and guides that you approve | | AI Visibility Specialist | Visibility files and feeds for AI shopping agents | | QA Sampler | Spot-checks every bulk run before it applies | ## Muse, store experience Owns the words and moments your customers actually touch: checkout, error messages, sale pages and emails. Audits your interface, then tests copy and layout variants to find what converts. | Specialist | What it does | | --------------------- | ----------------------------------------- | | UX Auditor | Walks your store like a picky customer | | Copy Specialist | The small wording that stops abandonment | | A/B Analyst | Runs variants and declares honest winners | | Accessibility Checker | Compliance built into every change | ## Compass, ads performance Points your advertising spend where it converts. Audits your ad accounts, finds the waste, and fixes the feed and landing page mismatches that quietly burn budget. | Specialist | What it does | | --------------- | ---------------------------------------------- | | Spend Auditor | Ranks waste by what it costs you a month | | Feed Specialist | Keeps shopping prices matching your site | | Keyword Analyst | Negative keywords built from real search terms | | Landing Aligner | Makes the page match what the ad promised | ## Where you work with each team Teams are how the work is organised, so you will meet them through the part of the product that does that work. Use this to find the right screen. | Team | Where you work with it | Documentation | | --------- | ----------------------------------------------- | ------------------------------------ | | Pulse | Store Audit and your findings | [Store Audit](/actions/store-audit) | | CodeCraft | Findings you approve, and the work that follows | [Kanban Board](/actions/kanban) | | Bridge | Staging copies, backups and restore points | [Vortex Apps](/vortex-apps/overview) | | Beacon | The SEO and GEO engine | [SEO and GEO](/actions/seo-geo) | | Muse | Experience findings from your audits | [Store Audit](/actions/store-audit) | | Compass | Advertising findings and feed alignment | [KPI cards](/nerve-centre/kpi-cards) | What each team can detect and change depends on the connectors you have added, the permissions you granted, your plan and the workflow. ## The rules every team follows Human approval is the default for anything written to a live store. Bounded automation runs only where you explicitly enable it. An evidence check tries to disprove each finding before it reaches you. Anything uncertain is dropped rather than shown. Teams reason about your store. The platform performs the reads and writes, within the permissions you granted. A finding ends as an applied change, a pull request, or guided steps. Never a silent failure. ## Where to go next The setup path for finding and fixing what is costing you sales. The setup path for capturing demand you are missing.