One employee named Nostic for teams of 5–50. Lives in Slack, connects Google Workspace, and handles the operational grind — inbox, scheduling, briefs, follow-ups, and company knowledge — so your people stay on clients and judgment.
One coworker across support, sales, marketing, projects, and ops — not a role shop.
Answers the team in Slack from your knowledge; drafts customer replies; escalates refunds, legal, and angry cases.
Meeting and account briefs; follow-up drafts; stale-deal nudges when CRM is connected.
Campaign and newsletter drafts in your tone; content-calendar reminders.
Tasks, morning/weekly status, overdue nudges.
Ingest, search, and summarise Drive/docs; calendar and contacts once Google is connected.
Asks before customer-facing email or anything that binds the company.
Proactive in Slack. Human gates before anything that binds the company.
Posts a brief in Slack: calendar, open tasks, anything stale.
Answers questions, drafts replies, updates tasks from what the team says.
Queues sends and external calendar invites for human approval.
Slack is required to start. Google Workspace unlocks inbox and scheduling after launch — Gmail, Calendar, Drive, Contacts, and Sheets. OAuth only; no API keys to paste.
More connectors after beta.
Slack
Primary channel — required to start. Answers, briefs, and team Q&A live here.
Google Workspace
Gmail, Calendar, Drive, Contacts, Sheets — unlocks inbox and scheduling after launch.
Company-specific memory, enforceable permissions, and a complete audit trail — not another black-box chatbot.
Approval gates
High-impact writes — email send, external invites — wait for a human.
Company memory
Facts, preferences, decisions, and commitments compound week over week.
Audit trail
Actions are attributed and reviewable. Tenant data is not used to train public foundation models.
Straight answers for security, rollout, and how Nostic behaves in your org.
Nostic is a persistent coworker: one employee with company memory, initiative across Slack and Google Workspace, and approval gates for high-impact actions — not one-off prompts in a thread.
You define approval gates and escalation paths. Every step is logged; sensitive actions require human confirmation. Built for oversight, not black-box autonomy.
Outputs are grounded in your connected sources and surfaced as drafts your people can review. We never promise infallibility — we prioritize traceability and correction loops.
A curated tool allowlist plus OAuth scopes for Slack and Google Workspace. Least privilege by default; high-impact writes stay behind approvals.
Yes. Private beta is one org at a time: connect Slack first, start Nostic, then add Google Workspace when you are ready.
Your tenant data is not used to train third-party foundation models. Contractual terms cover usage, retention, and subprocessors — your security team can map this to your policy.
Private beta for small teams that need an ops force-multiplier — not another chatbot.