Skip to content
Odysı
See if we fit
Case Study Our own software

How Odysi Studio runs on Claude.

Odysi Suite is the CRM, project tool and call recorder we built to run Odysi Studio: Odysi CRM, Odysi Projects and Odysi Scribe. The software holds the record. Our own Claude does the reading, logging and drafting through an MCP connector, with each person's permissions and the team's written rules.

Product Odysi Suite: Odysi CRM, Odysi Projects, Odysi Scribe
Built with Claude Code with Claude Opus, Claude Design
Status Live since September 2026, in beta
Stack TypeScript · PostgreSQL · MCP · Claude
Read
The problem

The work lived in too many places.

Until September 2026, Odysi Studio's pipeline was spread across Pipedrive, Notion, email threads and memory. Calls and client work sat in other tools again, so no single place said where a deal stood, what was agreed on a call or what a client was waiting for.

Claude could already read our email, Google Drive and calendar. What it lacked was a structured place to write what it found, under our rules and with each person's access.

FIG. I · Where the work lived
PipelinePipedrive
NotesNotion
ContextEmail threads
Next stepsMemory
→One record that our Claude reads and writes
The question we started from

What would a CRM look like if the Claude we already work in did the work in it, instead of an assistant built into the software?

Why we moved away from Lovable

We needed the reverse of built-in AI.

Our first CRM, our website and some internal tools were built on Lovable. Setup was quick: the systems were connected for us and things mostly worked without much involvement. Building with Claude asks more of you.

But Lovable builds software with AI inside it. We wanted the opposite: the Claude we already work in, with its connectors to Gmail, Google Drive and Google Calendar and its browser, doing the work in our own software.

That meant writing an MCP server: a set of operations any connected Claude can discover and run without access to the code. Once it existed, anyone on the team could connect from their own Claude session and start reading, adding and changing records, for example updating a deal from a Gmail thread.

The first CRM we built on Lovable was a different product. We rethought it from the start in Claude Code, around the connector rather than around a screen.

We wrote separately about moving our website off Lovable: Claude Design instead of Lovable.

What we built

Three apps on one account, and one set of written rules.

Odysi Suite holds and shows the data. The person's own Claude, or ChatGPT, does the work through the connectors.

01

Odysi CRM

Companies, people and deals, with the history of every value. Claude logs emails, writes notes, moves stages and creates tasks through 165 operations. Every change shows who made it: “Thomas ◆ via Claude” when his AI did.

02

Odysi Scribe

The Odysi Recorder for Mac and Windows records a call on any call app. Scribe then works in three steps: AssemblyAI transcribes, Gemini names the speakers, and Claude Sonnet, through the Anthropic API, files the call on its meeting and deal and gives it a title.

03

Odysi Projects

A workspace per client project: tasks, messages, documents, approvals and results. Claude proposes and drafts through 161 operations; anything the client will read waits until a person publishes it.

04

The Playbook

The team's written rules, in a clear hierarchy: team documents, with each person's own rules on top. Every conversation and every scheduled run reads it first, from any session, and corrections are turned into new rules.

No built-in AI agent. Odysi CRM and Odysi Projects make no generative AI calls of their own, apart from suggestions in CSV import and duplicate checks. Odysi Scribe is the exception, for transcription. Everything else is triggered by a person, in their own Claude session or in a scheduled task.

How it works

Claude works in Odysi Suite through MCP.

Each person connects their own Claude once, with OAuth 2.1 and PKCE. Every call then runs with that person's permissions, each workspace has its own connector address, and the Playbook is read before anything else.

A weekday at Odysi Studio

Scheduled and on request
Morning check · scheduled
A scheduled Claude task reads Gmail since the last run and logs the emails that matter on the right deals and people.
Pipeline
It moves deal stages, writes the deal log and creates follow-up tasks with dates.
Drafts, never sent
It writes replies and follow-ups as Gmail drafts. A person reads and sends every one.
Calls · Odysi Scribe
Calls are recorded with the Odysi Recorder, transcribed with named speakers and filed on the meeting and deal.
After the call
Claude reads the transcript and writes the note on the deal, turns next steps into tasks or proposed tasks on the client's project, and drafts the proposal or follow-up.
Client work
In Odysi Projects, Claude reads client email and WhatsApp and proposes tasks, drafts updates and gathers results. People accept, publish and confirm.
Five tools, many operations

Each connector exposes five fixed tools. One lists the operations, two run them (read or write). New abilities reach open conversations and scheduled tasks without reconnecting, Claude's context stays small, and every write is explicit.

The person's own permissions

OAuth 2.1 with PKCE, one connector address per workspace, and every call made as the member who connected. Changes are labelled “via Claude” in Activity and on the record.

Rules read first

The Playbook is written once and read by every session: the whole team works from the same rules, in as many separate conversations as they like.

References, not re-reading

Claude stores emails, file links and calls in the record. The next task fetches exactly what it needs instead of reading whole Gmail threads again, so there is less context and the answers are more accurate.

Built with Claude

Odysi Suite was built with Claude Code running Claude Opus, with Claude Design for the interface, Claude chat and Artifacts for specs, and Cowork scheduled tasks to run the studio on it while it was being built.

Work started on 19 September 2026 and Odysi Studio was using it every day within two weeks. By 18 November 2026: about 2,600 commits, about 320,000 lines of code, about 770 test files and about 200 database tables in PostgreSQL (Supabase), hosted on Railway.

What Claude still gets wrong

Claude sometimes did not follow specific written rules, such as writing rules. Corrections given in a conversation were not always stored as rules unless someone asked, and it is easy to forget to ask.

We refined the instructions that turn corrections and feedback into Playbook rules until this worked reliably. The trade-offs remain: scheduled tasks need a paid Claude plan, and setup takes more effort than an all-in-one builder.

How people stay in charge

Claude prepares. A person decides.

Claude does the reading, logging and drafting. The steps that reach other people, or that a client relies on, stay with a person.

Review steps
01 Emails are drafts: Claude never sends
02 Client messages wait until a person publishes them
03 Results are confirmed by a person, never through the connector
04 Every change is labelled, with the history of every value
Where it stands

Odysi Studio runs on it every day.

Live since September 2026
Claude now does most of the pipeline admin.

Logging, updating and drafting happen in Claude, through the connector. We read, decide and send. Figures from Odysi Studio's own workspace, 18 November 2026.

✓1,022 deals, 2,609 people and 1,911 companies
✓About 1,530 emails logged in four weeks
✓43 calls transcribed with Odysi Scribe in three weeks
✓Weekly pipeline review and client results from the same record
In beta for other businesses
Open to other teams, with honest trade-offs.

Odysi CRM is in beta and other businesses can start on the Free plan. Odysi Projects is available on request.

□Scheduled tasks and Cowork need a paid Claude plan
□Connecting Claude and writing the Playbook take some setup
□Plans and credits are on the pricing page
What it shows

What we take from building and running it.

01

A company can run its sales, calls and client work through Claude, with the software as the record.

02

MCP works best with stable tools, the person's own permissions and written rules that every session reads first.

03

Claude Code with Claude Opus took the suite from first commit to daily use in two weeks.

About Odysi Studio

A small studio. We find where AI is worth it, build those few things and leave you able to run them.

Odysi Suite is how we run our own work. We build the same kind of system for clients: their Claude, working in software built around their data and rules.

Start on the Free plan

Want your team to work like this?

For developers The Odysi Suite for developers: REST, MCP, OAuth and webhooks Read the guide →