User Journey Diagram for SaaS Workflow Swimlanes

Tech architecture infographic titled "User Journey Diagram" using HOW-IT-WORKS archetype adapted as workflow swimlanes for a tech / SaaS company. Show 5 horizontal swimlanes with labeled boxes and directional arrows: Customer, Marketing Website, Product App, Support / Success Team, Data / Billing Systems. Build an executive-deck grade user journey map with clear left-to-right progression from discovery to activation to retention. Include labeled boxes for each stage with icon + canonical English name + one-line English role description. Suggested boxes: in Customer lane: "Visitor — Person exploring the product", "Lead — Signed up for updates", "User — Logged into the app", "Subscriber — Paying customer", "Advocate — Refers other users". In Marketing Website lane: "Landing Page — Explains value proposition", "Pricing Page — Shows plans and features", "Signup Form — Captures account details", "Email Campaign — Sends onboarding messages". In Product App lane: "Authentication — Verifies identity with HTTPS login", "Onboarding Flow — Guides first-time setup", "Dashboard — Main workspace for daily tasks", "Feature Usage — Core product interaction", "In-App Prompt — Encourages upgrade or referral". In Support / Success Team lane: "Chat Support — Resolves user questions", "Customer Success — Drives adoption and retention", "Knowledge Base — Self-service help articles". In Data / Billing Systems lane: "CRM — Stores lead and account status", "Analytics — Tracks events and funnel metrics", "Billing System — Manages subscription payments", "Notification Service — Sends transactional email", "Feedback Store — Collects survey responses". Connect all boxes with arrows showing user journey and system handoffs. Arrow labels in English should be technically plausible and concise, such as: "Ad click", "Page view", "Signup POST", "201 Created", "Verification email", "HTTPS login", "200 OK + session token", "Event: first project", "Usage events", "Upgrade request", "Payment confirmation", "Support ticket", "NPS response", "Referral link". Add small illustrative metrics near selected stages in English, such as "CTR 3.2%", "Signup rate 12%", "Activation in 2 days", "Trial 14 days", "Monthly churn 4%", "Avg response 5 min", with note that values are example only. Add a numbered legend 1-7 in English walking through lifecycle: 1. Customer discovers the SaaS via marketing entry points. 2. Visitor reviews value proposition and pricing details. 3. Signup form creates account and sends verification message. 4. User logs in and completes onboarding steps. 5. Product usage generates analytics events and activation signals. 6. Billing converts active trial users into paying subscribers. 7. Support, feedback, and referrals improve retention and advocacy. Visual style: sketchnote, editorial developer-blog illustration, isometric or flat tech-diagram style, vector-clean infographic layout. Use tech blue and cyan palette with white background, dark navy outlines, cyan highlights, light blue swimlane fills, subtle hand-drawn annotations, soft shadows, crisp spacing, high readability, executive presentation mood, polished but approachable. Use generic department, browser, app, chat, payment card, database, analytics, email, and support headset icons. No real company logos, no real person names, neutral department titles. All text MUST be written in English (array). Every heading, label, caption, legend and metric name in the image must be in English — not English. Spell each English word correctly using English characters and diacritics. Numbers stay as digits, no real cloud-vendor logos (AWS / GCP / Azure) — use generic cloud icons, no watermarks No real-company logos. Use generic icons for departments / tools / vendors. Org-chart titles stay neutral (no real person names). Process timings / costs / volumes are illustrative example values.