You and your AI

Stop re-explaining
your business
to your AI.

The light CRM alternative for shops — client tracking built for you and your AI

For shops and ateliers: every order, call and follow-up lands on one timeline your assistant can actually read. Ask « Catch me up since Friday » — it answers from what happened, not guesses.

Try for freeSee how it works →
The Historis dashboard: a three-column board — needs attention, new and recent — of events linked to the right people and tagged, several added by your AI via MCP.The Historis dashboard: a three-column board — needs attention, new and recent — of events linked to the right people and tagged, several added by your AI via MCP.
◆ Ask your AI

« Catch me up since Friday. »

Underneath, one MCP tool call — get_daily_brief — computes what's overdue, due today and coming up. The agent phrases it; the buckets are deterministic.

claude.ai · connected to Historis
You · Mon 09:02

Catch me up since Friday. What happened, what do I need to know, what needs handling?

◆ get_daily_brief(horizon_days: 7)→ overdue 1 · due_today 2 · upcoming 3
◆ Claude

Since Friday: 14 events landed. Here's what matters —

To know · 3
Payment received — invoice 2026-118 (logged Friday)
12 orders logged over the weekend, two flagged urgent
Mrs Durand confirmed Thursday's delivery
To handle · 2
Sophie Kahn's quote — 1,000 cards, due today
Support ticket #88 — callback promised before noon
Overdue · 1
Acme quote — no reply for 17 daysrule: quote pending > 14d
MCP log · live
09:03:11WRITEclaude.ai · create_event(« Follow-up Acme — quote »)◆ via MCP · reversible
09:02:19READclaude.ai · get_person_context(« Acme Corp »)9 events · 2024-03 → 2026-06
09:02:14READclaude.ai · get_daily_brief(horizon_days: 7)overdue 1 · due_today 2 · upcoming 3
08:57:40READchatgpt · search_events(« invoice 2026-118 »)2 events matched
every call logged · attributable · reversible
Five sources, one timeline

Capture from everywhere.

You don't change your tools. Type a note or let an agent write today — email, collectors and webhooks are next. Every event converges into the same timeline, dated and sourced.

MANUAL
A line typed in 10 seconds.
EMAILSOON
Forward a thread — it will land as a dated event, linked to the right person.
◆ MCP AGENT
Claude or ChatGPT writes via MCP. Attributable, logged, reversible — always.
AUTO-COLLECTSOON
Scheduled collectors will bring recurring events in. No hands needed.
WEBHOOKSOON
Your stack will push events the moment they happen.
One timeline · all sources
09:42 · MANUAL
Call Mrs Durand — screen quote
typed in 10 seconds
11:15 · EMAIL
Shipping confirmation #1042
forwarded from Gmail · soon
◆ 14:08 · MCP AGENT
Follow-up note on the Acme quote
claude.ai · via MCP
17:30 · WEBHOOK
Payment received — invoice 2026-118
webhook → historis · soon
23:00 · AUTO-COLLECT
Nightly import: 12 orders
collector · soon
A contact's page in Historis: their whole history on one timeline — events, tags and an AI summary added via MCP.A contact's page in Historis: their whole history on one timeline — events, tags and an AI summary added via MCP.
DeterministicEvery event has an identifiable source and an exact date — never an AI guessing behind your back. A webhook is deterministic. A guess is not.
Three pillars

What your inbox can't do.

Right now it lives in a spreadsheet you forget, in your head, or in an AI that makes things up. Historis is the one timeline you can both trust.

01 / CAPTURE

One event, one line.

Typed in 10 seconds or written by an agent you validate — every event lands with an identifiable source and an exact date.

sourced · dated · deterministic
02 / RELATIONS

The threads weave themselves.

Each event links to one or more people. Mrs Durand's full history surfaces in one click: March quote, April support call, May order.

1 person · N events
03 / FOLLOW-UPS

Rules, not guesses.

« Quote open for 14 days », « Support ticket not closed ». You define the rules, Historis counts the days. Deterministic, predictable, fixable. Zero AI false-positives.

SQL-like · transparent
◆ MCP & Bring Your Own AI

Your Historis becomes a source for your AI.

Historis ships no AI. It exposes your data via MCP — the open protocol adopted by Claude, ChatGPT, Cursor. Your assistant reads from home. You see every request.

No AI included. You bring your own.

You already have Claude Pro, ChatGPT Plus, or a local LLM — use them. When Claude queries Historis, it's Claude calling, not Historis talking.

◆Organization-wide permissions — you control what agents read & write.
◆Zero tokens billed by Historis. You pay your AI at its source.
MCP · V1claudechatgptcursor
MCP tools · v1
READget_daily_briefoverdue · due today · upcoming · stale
READsearch_eventsfull-text over the whole timeline
READget_person_contextone person, full history
READget_organization_contexttags, people, recent activity
WRITEcreate_eventopen event · logged · reversible
WRITEbulk_create_eventsidempotent batch ingest
WRITEmanage_rulesdeterministic follow-up rules
12 tools · documentation→
Pricing

Simple. Transparent. Cancel anytime.

One price for Historis. Your AI, you pay it at your provider. Zero tokens billed by us.

Free
$0/month

For a freelancer or small team getting started. Free forever.

  • 1 workspace · up to 5 users
  • 1 team · 250 active events
  • 25 contacts · 20 tags
  • MCP · read + write
Get started
RECOMMENDED
Pro
$10/ user / month

For a small team tired of dropping threads.

  • 5 teams · up to 25 users
  • Unlimited events & people
  • API tokens · JSON export
  • Priority support
Try
Business
$17/ user / month

For organizations that need security, audit, and admin controls.

  • Everything in Pro + unlimited teams & users
  • Per-agent access controls
  • Require 2FA for all members
  • SSO (SAML/OIDC)Soon
  • Audit log & advanced rolesSoon
Try
FAQ

Questions, answered.

Is Historis a CRM?

Not the heavy kind. Historis is the light, event-based alternative: no pipelines or custom fields to maintain — you log what happened (orders, calls, follow-ups) on one timeline your AI can read. It is the part of a CRM you actually use.

Does Historis include an AI?

No, by design. You bring your own — Claude, ChatGPT or Cursor — and connect it over MCP. Historis is the memory; your assistant does the talking, and you never pay us for tokens.

How does my AI remember my business?

Everything you capture lands on one shared timeline, linked to the right people. Your assistant reads it on demand — ask « Catch me up since Friday » and it answers from what happened, not guesses.

Which assistants work with Historis?

Any MCP client — Claude, ChatGPT and Cursor today. You connect once, set what it may read and write, and every action stays logged and reversible.

What is an MCP CRM?→Why an event-based CRM→Read the Notes→
Who's behind Historis

Built by the person who answers for it.

Historis asks you to trust it with your client history. Here is who you are trusting it to — and what that holds us to.

I'm Sven Le Cann. I built Historis for my own small business: client history lived in notebooks, inboxes and my head, and every follow-up depended on memory. Historis is the record I needed — the one I use every day.

It stays deliberately simple to answer for: a French product, run by a sole proprietor under French law, funded by subscriptions only.

Sven Le CannFounder · Historis
Commitments · on record
Made in FranceOperated by a sole proprietor based in France, under French law.
Hosted in the EUDatabase and backups run in Frankfurt (Supabase); the API runs in the EU (Railway).
Never soldYour data is never sold, rented or shared for commercial purposes.
No AI trainingNo AI model is ever trained on your data. Historis runs no server-side AI.
In full:Security→Privacy→contact@historis.app

Try Historis. Give yourself a memory.

Free to start, no card. No data leaves without your consent.

Get startedSee the app in detail→