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
Stop revenue leaks
Pulse finds and explains, CodeCraft fixes, Bridge keeps the way back.
Accelerate growth
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.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.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.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.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.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.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.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
You approve production changes
Human approval is the default for anything written to a live store. Bounded automation runs only where you explicitly enable it.
Findings are verified, not guessed
An evidence check tries to disprove each finding before it reaches you. Anything uncertain is dropped rather than shown.
No team holds your credentials
Teams reason about your store. The platform performs the reads and writes, within the permissions you granted.
No dead ends
A finding ends as an applied change, a pull request, or guided steps. Never a silent failure.
Where to go next
Stop revenue leaks
The setup path for finding and fixing what is costing you sales.
Accelerate growth
The setup path for capturing demand you are missing.