User guide
PULSE is built around one loop. You audit a site, PULSE learns the market and audience from it, you create and approve content, and you publish and measure. Then the follow-up cycle feeds what you learned back into the next round.
This guide follows that loop in four stages. The stages are how these docs are organized. The app’s own navigation groups the same screens into five categories, shown in the table below.
Where each screen lives
| Navigation category | Screens |
|---|---|
| Overview | Overview (dashboard), Marketing Console, Site Audit, Insights, Impact Analytics, Content Gaps |
| Audience | Influencers, Customer 360, Persona Profile, Intelligence Console, Leads, Follow-up |
| Content | Campaigns, Creatives, Approval, Schedule, Courses |
| Studio | Content Strategy, Strategy Roadmap, Whitepapers, Podcasts, Shorts, Presentations, Infographics, Reports |
| System | Integrations, AI Team, Settings, Billing |
Your avatar opens Account. Administrators also see Admin. The old
/metrics and /analytics addresses redirect to Insights.
How the stages connect
One Site Audit seeds most of the other screens. When the diagnosis finishes, PULSE copies its findings forward, with no extra model calls:
| From the diagnosis | To |
|---|---|
| Channel prescription suggestions | Draft content on Approval, then Schedule once approved |
| Prescriptions and audience segments | A draft campaign on Campaigns |
| The 4-week plan | A 30-day cycle on Follow-up, with check-ins |
| Audience segments | Profiles on Customer 360 |
| Competitive and positioning analysis | A market summary for the Radar |
| The niche | Market research and up to five new leads, run in the background |
You can also start a stage on its own. Content, creatives, outreach, courses,
Customer 360 profiles, and lead prospecting all accept an optional
diagnostic_id that grounds the output in a diagnosis. They run without one.
Languages
The app ships English, Spanish, French, and Portuguese catalogs. Pick the interface language in Settings. Generated content has its own language, set on each generation request.