Help hub & product blueprint

1. Target Market Definition

• ICP: primary SMB / lower mid-market (≈80–800) with Slack or Teams; secondary mid-market BU / region; tertiary enterprise division (bounded seats, fast isolation).
• Underserved industries: professional services, healthcare ambulatory, regional manufacturing & logistics, private education, franchise / multi-site retail.
• Personas: IT admin (tenant, federated sign-in, integrations), service desk agent (queues, SLA, comms), end user (non-technical — intake only in plain language). Plug-and-play setup + with OpenAI auto tenent setup + SSO logins + RAG+AI+Agentic

2. Core Problem Analysis

• Too complex: data model and admin trees before outcomes; tools assume CAB + CMDB maturity already exists.
• Implementation failures: time (blank tenant + workshops), cost (modules + SI + upgrades), training (taxonomy courses), adoption (portal nobody uses).
• Integration confusion: OAuth scope sprawl, duplicate tickets (email + chat), schema mapping to dozens of custom fields, unclear retry and ownership of webhooks.

3. Product Vision

• Zero-confusion ITIL tool: every screen has one obvious next action; ITIL lives in states/audit — UI uses everyday language.
• “Setup in 1 day” means tenant + branding + business hours + federated sign-in (or pilot auth) + email + Slack or Teams + deduped intake + starter catalog + SLA pack + invited agents + first resolved record + CSAT + audit trail — not full CMDB graph or custom REST mappers on day one.Plug-and-play setup + with OpenAI auto tenent setup + SSO logins + RAG+AI+Agentic
• Intentionally excluded (anti-bloat): deep CMDB federation, broad ESM (HR/legal/FS), arbitrary customer-built REST as a buyer requirement in MVP, on-prem by default.

4. Core Features (Keep It Lean)

Operational UI: use the four module cards in the section 4. Core Features (Keep It Lean) above this article (same page).

• Incident management — Something's wrong; P1–P4 + SLAs out of the box; major-incident mode optional.
• Service request management — I need something; catalog wizards (≤5 steps); single-level approval default.
• Change management (simplified) — Planned work; Standard / Normal / Emergency tracks; risk in guided questions, not free-text only.
• Asset management (lightweight) — Equipment & subscriptions; inventory + ownership first; relationships when maturity allows.

5. UX Strategy (Critical Differentiator)

• Non-technical first: two-path home (broke vs need); no nav trees for requesters.
• Jargon ban in intake: e.g. Incident → “Something's wrong”; Change → “Planned work”; CAB → “Reviewers”; Known error → “Known issue + workaround”.
• 3-click rule: submit common issue ≤3 taps from Help hub; assign + priority + customer update ≤3 from record; connect Slack/Teams ≤3 from integrations (target — PM-gated).

6. Integration Philosophy

• Plug-and-play setup + with OpenAI auto tenent setup + SSO logins + RAG+AI+AgenticOAuth-first email, Slack, Microsoft Teams; optional read-only cloud hooks (AWS/Azure/GCP) only with explicit customer consent.
• No traditional complex APIs as a buyer requirement — tier-1 paths are no-code; REST exists for enterprise automation, not day-one story.
• Universal layer — Conduit: normalize inbound events → work intent, dedupe by thread/message id, deliver outbound with visible retry logs and ownership.

7. Architecture & Tech Stack

• Cloud-native multi-tenant SaaS — region-pinned tenants, row-level isolation, immutable audit stream.
• Low-code / no-code workflow engine — versioned states, guards, notifications; simulate before publish.
• Microservices vs monolith — decision: modular monolith + async workers until scale triggers split Conduit, search pipeline, and attachment scanning.Plug-and-play setup + with OpenAI auto tenent setup + SSO logins + RAG+AI+Agentic

8. Key Differentiators

• Faster than ServiceNow: contractual day-1 go-live checklist + in-product setup meter.
• Easier than Jira Service Management: requesters never see project/schema concepts.
• More intuitive than Freshservice: 3-click KPIs + plain language + integration reliability UI (retries, logs, dedupe).

9. Monetization Strategy

• Model: freemium / pilot (capped agents + tickets), per active agent Team tier, + platform fee at Business+, Enterprise contract for SCIM / residency / dedicated.
• Accessibility vs scale: SMB self-serve + transparent AI caps; mid-market annual + security pack; enterprise governance SKUs — core four modules stay in base SKU.

10. Go-To-Market Strategy

• Positioning: Plug-and-play setup + with OpenAI auto tenent setup + SSO logins + RAG+AI+Agentic
• First niche: Slack- or Teams-native internal IT for ~150–800 employee professional services & SaaS (NA + UK).
• Channels: product-led growth (install → first ticket in minutes), Slack/Teams marketplaces, MSP partners with fixed 1-day go-live kit, honest comparison content.

11. MVP Definition

• Smallest sellable: incidents + SR + simplified change + CSV/manual assets + knowledge + email + one chat + RBAC + audit + Conduit v1.Plug-and-play setup + with OpenAI auto tenent setup + SSO logins + RAG+AI+Agentic
• 90 days: above slice with Normal change + static Standard checklist if needed; one chat connector first if sequencing.
• Defer: connector marketplace breadth, deep cloud discovery, arbitrary REST mapper UI, native mobile, full Problem module (use related-incidents pattern first).

12. Risk & Failure Points

• Failure modes: flaky integrations, AI trust incidents, SMB churn, enterprise security stalls — mitigate with logs, human-in-the-loop defaults, health scores, early SOC2 path.
• “Just another ITSM” if you ship RFP checkbox modules, expose admin depth as hero UX, or require SI for go-live.
• Anti–feature creep: public principles + RICE; quarterly subtract review; anything not improving day-1 go-live, 3-click flows, or integration reliability defaults to no.