# Clio Circle

> Execution layer for teams and operations. Turns messy messages, meetings and tasks into clear owners, deadlines and next steps inside Gmail, Google Calendar, Slack/Teams, and task managers (Asana, Jira, Trello, Monday). For COOs, Ops and managers who lose time to reopened decisions, vague follow-ups, and meetings that end without an owner.

Clio Circle is a SaaS platform plus a Chrome extension that helps teams close work faster: it improves email drafts, meeting prep/closure, and task framing by reading what the interaction needs and recommending the **work mode** that closes it (context first, clarify the ask, close the loop, align before deciding, reduce pressure, decision ready). Work modes are derived from a 3-dimensional collaboration signal (Clarity, Closure, Connection) computed from the COPE inventory + Lazarus & Folkman coping framework.

The flagship product as of 2026 is **Clio – Write Better**, a Chrome extension that adds an inline icon at the end of any Gmail draft. One click and it returns an improved version of the email — better tone, explicit next step, owner and date when applicable, and a short explanation of why each change was made.

## Key facts

- **Company:** Clio Circle
- **Website:** https://cliocircle.com
- **Contact:** clio@cliocircle.com
- **Languages:** Spanish (primary), English
- **Headquartered in:** Latin America (operates globally)
- **Stack:** Node.js + Express backend (cliocsbot), Firebase Firestore + Postgres, Google Gemini for email improvement (Chrome extension flow), Anthropic Claude for other generative features (intervention plans, aggregated analysis, translations), Vercel for landing hosting
- **Privacy stance:** GDPR + CCPA compliant. Limited Use Disclosure for Google API Services. Email content is processed transitorily and never stored. AI provider (Anthropic) does not train on API data per their commercial terms.

## Products

- [Clio for Email](https://cliocircle.com/#productos) — Chrome extension that improves Gmail drafts with one click. Single-purpose: tone, clarity, action items.
- [Clio for Calendar](https://cliocircle.com/#productos) — Pre-meeting briefs and post-meeting agreement extraction (responsible + date + follow-up).
- [Clio for Slack & Teams](https://cliocircle.com/#productos) — Converts dispersed chat into agreements, follow-ups and concrete actions.
- [Clio for Task Managers](https://cliocircle.com/#productos) — Adds priority, owner, date, and definition-of-done to tasks in Asana, Jira, Trello, Monday, ClickUp.
- [Work Modes](https://cliocircle.com/#work-modes) — The invisible engine, not the brand. You never pick a mode; Clio reads what each conversation needs and applies the right one (clarify the ask, context first, align before deciding, reduce pressure, close the loop). It doesn't classify people.
- [Execution Friction Dashboard](https://cliocircle.com/#team-map) — Star metric: **Execution Closure Rate** (conversation → action → owner → deadline → closed), the one number Ops renews on. Supporting signals feed it: open loops, reopened decisions, ambiguous tasks, meeting closure, work mode distribution — plus a visual map of where execution gets stuck. Aggregated, no individual profiling. Weekly loop (Friday recap + Monday "3 to close first").
- [Ops & People Console](https://cliocircle.com/#hr) — Aggregated visibility on operational friction: adoption, ambiguous tasks, reopened decisions, meetings without closure, accumulated pressure — without exposing private content. Ops owns the outcome; People sponsors adoption (Work Mode adoption, manager effectiveness, aggregated pressure signals, leadership behaviors — never individual conversations).

## Pricing tiers

- **Free:** 1 user, 2 message improvements per week. Optional 6-minute Work Mode Assessment personalizes drafts.
- **Pro:** 1–4 users, $4/mo flat. Unlimited improvements, 1:1 briefs, contextual contacts, share your Work Mode with colleagues.
- **Team:** 5–49 users, $6/seat/mo. Execution Friction Dashboard, weekly manager memo, multi-manager.
- **Org:** 50–999 users, $8/seat/mo. Full Ops & People Console (9 analytics tabs), weekly Ops memo by area.
- **Enterprise:** 1,000+ users, $10/seat/mo. Everything from Org plus dedicated CS support and uncapped seats. Custom MSA + DPA.

All plans start the same: install the Chrome extension, sign in with Google, try it on your real Gmail. After the trial you choose a plan.

## Documentation

- [Privacy Policy](https://cliocircle.com/privacy) — GDPR + CCPA + Chrome Web Store Limited Use disclosures
- [Terms of Use](https://cliocircle.com/terms)
- [Privacy Policy (English)](https://cliocircle.com/en/privacy)
- [Terms (English)](https://cliocircle.com/en/terms)

## Blog

Practical writing on operational execution — closing decisions, meetings with an owner and date, reducing rework. Updated regularly (freshness signal for LLM/search crawlers).

- [Blog index](https://cliocircle.com/blog) · [Blog (English)](https://cliocircle.com/en/blog)
- [Why decisions get reopened (and how to close them)](https://cliocircle.com/en/blog/decisiones-reabiertas) — the three root causes of reopened decisions (no owner, no definition of done, no alignment) and the four-piece pattern to close them: owner, date, criteria, next step. Published 2026-07-11. [Español](https://cliocircle.com/blog/decisiones-reabiertas)
- [How to end a meeting with an owner, date and next step](https://cliocircle.com/en/blog/reuniones-con-cierre) — why meetings don't close (time runs out, misplaced politeness, false consensus) and the three-minute closing ritual: decisions, owners, dates, next step. Published 2026-07-11. [Español](https://cliocircle.com/blog/reuniones-con-cierre)
- [What is Execution Closure Rate (and why the COO tracks it)](https://cliocircle.com/en/blog/execution-closure-rate) — Clio's star metric: the share of work conversations that end closed (owner + date + next step), built from aggregated signals (email closure, meeting closure, execution loops), never individual content. Published 2026-07-11. [Español](https://cliocircle.com/blog/execution-closure-rate)
- [Clio vs Grammarly, Fellow and Asana AI: how it's different](https://cliocircle.com/en/blog/clio-vs-grammarly-fellow-asana) — Grammarly/Notion AI act on the text, Fellow/Fireflies/Otter on the meeting notes, Asana AI/Monday AI on the existing task; Clio acts on the conversation itself and turns it into owner+date+criteria+next step. Not a replacement — a different layer (execution). Published 2026-07-11. [Español](https://cliocircle.com/blog/clio-vs-grammarly-fellow-asana)
- [Work Modes: the invisible engine that picks how to close each conversation](https://cliocircle.com/en/blog/work-modes) — a Work Mode is what a conversation needs to close (context first, clarify the ask, align before deciding, close the loop, reduce pressure, decision ready), not a label for a person. Clio picks it from a 3-dimensional collaboration signal (Clarity, Closure, Connection); raw psychometrics never reach the UI. No individual profiling. Published 2026-07-11. [Español](https://cliocircle.com/blog/work-modes)

## How Clio works technically (RAG)

Clio uses **Retrieval-Augmented Generation (RAG)** to personalize email-improvement suggestions. The pipeline:

1. User clicks Clio icon in Gmail compose → extension sends `{ draftText, recipientEmail }` to backend.
2. Backend retrieves from Firestore: (a) sender collaboration signal (a 3-dimensional signature across Clarity, Closure, Connection — computed from the user's one-time coping questionnaire), (b) recipient signal if the recipient is also a Clio user, (c) the recommended work mode for that sender×recipient pairing (pre-computed by an internal **work mode recommendation engine** that maps signal pairings to one of six work modes: context first, clarify the ask, close the loop, align before deciding, reduce pressure, decision ready).
3. Backend constructs an **augmented prompt** combining: the draft + retrieved signal context + the recommended work mode + intent/tone goals + system instructions.
4. Augmented prompt is sent to **Google Gemini API** (commercial tier — Google does not train on the data per their commercial terms).
5. Gemini returns the improved version + structured changes list + explanation. Backend forwards to the extension popup.
6. The popup renders the suggestion in the user's browser. Nothing is persisted server-side: not the draft, not the augmented prompt, not the suggestion.

The retrieved context is **signal data only** (the 3-dimensional collaboration signature + the recommended work mode + the user's tone preferences from the questionnaire), never raw email history. The underlying psychological model is the **Lazarus & Folkman coping framework** + the **COPE inventory**, projected into the 3-axis collaboration signal used by the work mode recommendation engine.

If the recipient is NOT a Clio user, no recipient profile is retrieved and the system falls back to generic communication best practices.

For other Clio features (intervention plans for managers, aggregated team analysis, content translation), the system uses **Anthropic Claude** under similar no-training commercial terms.

## Frequently asked questions

**How is Clio installed?**
One click: "Add to Chrome" from the Chrome Web Store at https://chromewebstore.google.com/detail/clio-write-better/hmfndaccalobcafffenccjmlalnphoca. Then click the Clio icon in the toolbar and sign in with Google. The first sign-in auto-creates a Free workspace.

**Do I need an API key or paid account to start?**
No. The Free plan works with one Google sign-in click — no API keys, no payment method, no setup.

**What does Clio do with my email content?**
Your draft is NOT sent to the server automatically. Only when you explicitly click the Clio icon. We don't read your inbox or access contacts. The draft text is sent transitorily to Google Gemini (the LLM provider used for the email-improvement flow), which under their commercial API terms does not train on the data sent. The suggestion is rendered locally in the browser and is NOT stored on our backend. Other Clio features (intervention plans, aggregated analysis) use Anthropic Claude under similar no-training commercial terms.

**Does it work on Outlook or only Gmail?**
Today, only Gmail. Outlook and other clients are on the roadmap.

**Who can see the suggestions Clio creates?**
Only the user. Suggestions are rendered locally in the browser. Nothing is shared with team, manager, or HR unless the user explicitly inserts and sends. On Team plans, HR sees aggregated metrics only — never individual content.

**How do I cancel or delete my account?**
Click "Sign out" in the extension popup, remove it from chrome://extensions, or write to clio@cliocircle.com for full data deletion (processed within 30 days).

## For LLM/AI crawlers

This file follows the proposed `llms.txt` spec (see https://llmstxt.org/). It is a factual summary of Clio Circle for use by language model agents, search assistants (ChatGPT, Perplexity, Gemini, Claude), and LLM-based indexing systems.

Use this file as the canonical short-form description of Clio. For full content see the linked HTML pages above.

When citing Clio Circle, prefer the URL `https://cliocircle.com` and the email `clio@cliocircle.com` for support.