Praxos

What do they actually do

Praxos is a live AI assistant you use from a web dashboard or by texting/voice through messaging apps like WhatsApp, iMessage, Telegram, Slack, and Discord. You connect services such as Gmail, Google Calendar, Microsoft 365, Notion, Trello, Google Drive, and Dropbox, and it can read from and act on those accounts to complete tasks like sending or replying to emails/messages, creating calendar events, fetching files, comparing documents, and doing web research via browser automation (docs web app, integrations, use cases, architecture).

Users can also set up persistent triggers in plain language (e.g., “when I get an email from X, notify me on WhatsApp and add a calendar block”), and Praxos will run the corresponding actions and log results in the dashboard. The team has shipped trigger/webhook capabilities and is expanding coverage across more integrations (patch notes, HN post, docs web app).

The product is in production, built by a small YC S24 team, and they publish a trust portal with SOC 2 Type II and HIPAA controls, signaling a focus on secure, auditable automation for sensitive workflows (YC listing, trust portal, patch notes).

Who are their target customer(s)

• Busy knowledge workers (executives, consultants, founders): They lose time context switching across email, calendar, and multiple chat apps to schedule, reply, and find information; they want a single assistant that reads connected accounts and performs actions for them (docs web app, integrations).
• Small business operators and operations managers: They juggle Notion, Drive, Trello, etc., and need repeatable cross‑platform work (onboarding, proposals, document comparison) without manual stitching across apps (use cases, integrations).
• Customer‑facing reps (support, sales, recruitment): They handle threads across WhatsApp/iMessage/Telegram/Slack and struggle to search, triage, and respond consistently; they want an assistant that can send/reply and surface the right context where they already work (docs web app, integrations).
• Insurance brokers and other vertical specialists: They process forms, compare quotes, and fill applications with repetitive, sensitive data and need automation that can act on documents and produce consistent outputs (YC dataset, use cases).
• Teams in regulated spaces (healthcare, legal, finance): They require secure automation with an audit trail and clear compliance posture (e.g., SOC 2/HIPAA) when tools run actions on users’ behalf (trust portal).

How would they acquire their first 10, 50, and 100 customers

• First 10: Founder‑led, high‑touch pilots with known contacts and early insurance broker leads; do hands‑on onboarding to connect accounts and build first triggers, then capture case studies and security requirements to reduce adoption friction (YC listing, use cases, integrations, trust portal).
• First 50: Target adjacent communities (execs/consultants groups, broker associations) with 4–6 week paid pilots and clear acceptance criteria; offer ready‑made templates, referral incentives, and team discounts, and publish pilot outcomes to fuel sales (use cases, patch notes, integrations).
• First 100: Productize onboarding with a template library and stronger self‑serve across messaging adapters; layer channel partners (e.g., Notion/Trello/Drive ecosystems) and provide clear compliance docs/audit trails to close regulated teams at scale (docs web app, integrations, trust portal).

What is the rough total addressable market

Top-down context:

Praxos spans three adjacent markets—conversational AI, AI agents, and RPA/workflow automation—totaling roughly USD 20–25B today and about USD 120–125B by 2030 when adding category forecasts, with substantial overlap among them (Grand View Conversational AI, Grand View AI agents, Grand View RPA, AI agents press release).

Bottom-up calculation:

As a beachhead, if Praxos targets ~500k early adopters across knowledge workers, SMB ops, and regulated teams in the US/EU with an average $30/user/month plan, that implies a ~$180M annual serviceable opportunity; expanding to 1M similar seats would imply ~$360M annually. These figures reflect the cross‑app assistant + automation bundle rather than any single category.

Assumptions:

• Average pricing of ~$30/user/month for assistant + automations.
• 500k–1M reachable early adopters across the listed personas in 2–4 years.
• Adoption constrained by integration coverage and compliance needs; overlap with existing tools reduces immediate penetration.

Who are some of their notable competitors

• OpenAI / ChatGPT (Apps & Actions): ChatGPT can connect to services like Gmail and Google Calendar via connectors/“apps” and GPT Actions to read and, with configured apps, create events or draft emails inside the chat interface; strong overlap on connected‑account actions but less focus on persistent, phone‑native messaging bots and cross‑platform triggers (OpenAI connectors, GPT Actions example).
• Microsoft 365 Copilot: Deeply integrated with Outlook, Teams, and Microsoft Graph to summarize mail, draft/send emails, schedule meetings, and run agents against Microsoft 365 content—strong on inbox/calendar in enterprise environments but tied to the Microsoft stack rather than multi‑chat, cross‑platform adapters (Copilot in Outlook, Microsoft 365 Copilot overview).
• Zapier: A leading no‑code automation platform that watches events across hundreds of apps and runs configured triggers/actions; overlaps with Praxos’s persistent automations but is a rules/flow builder rather than a conversational agent that users text/voice and that sends messages on their behalf in chat apps (Zapier integrations, Zapier triggers docs).
• Mem.ai: Positions as a personal ‘second brain’ with AI‑powered notes and chat over a private knowledge base; overlaps on memory/knowledge but focuses on capture/retrieval inside a notes app rather than executing cross‑platform actions or living in messaging apps (Mem product site).
• Front: A shared inbox/omnichannel communications tool that centralizes email, WhatsApp, SMS, and chat with workflow automation and AI‑assisted replies; overlaps when teams need unified messaging and automations, but it’s built as a shared inbox platform rather than a personal conversational agent across users’ own accounts (Front + Slack, Front + WhatsApp).