17 modules · 200+ tools for AI assistants · 18 walkthrough videos

The all-in-one, AI-first
operations platform.

Two ways in, one company underneath. Your team works in the screens. Anyone on the team can also open Claude or ChatGPT and work in the same company through 200+ tools, as themselves.

Start free
The project page: team and capacity, burn rate, milestones, the wiki teaser and the task snapshot
ClaudeOpelli · Northwind Studio
How is Storefront Revamp going? Give me the week in three lines.
Used tracking_project_summaryUsed list_tasks · status=in_progress,blocked

Burn is at 61 % of the month's plan with 9 days left. Two tasks are blocked on the checkout API, both Mark's. The Aurora phase-two proposal is due Friday and has no next step yet.

Put a next step on that deal: "Send revised proposal", Friday, mine.
Used update_deal · Aurora Retail · Phase two

Done. It is on the account timeline and on your Friday.

And ping Nina that the checkout tasks are hers to unblock.
Used comment_task · STORE-118, STORE-121

Commented on both and mentioned Nina; she gets the DM from the Opelli Bot.

Reply…

Sessions

The same week, from both sides.

Each session is one of the walkthroughs, told twice: on the screens the team uses, and in the chat client somebody opened beside them. Every tool name is real.

01 · Monday

From the sync note to the board.

OpelliMonday catch-upAurora replyAugust invoicesLoyalty launch pageWho is out in October
ClaudeOpelli · Northwind Studio
What happened on Storefront Revamp since Friday?
Used generate_report · last 3 days · STORE

Eleven tasks moved, two shipped. Nina published the checkout copy page. 14 hours tracked. Nothing from Aurora yet.

Open Friday's sync note and turn the decisions into tasks in the running sprint, assigned as agreed.
Used get_wiki_page · Weekly sync 2026-09-04Used create_task × 4

Four tasks: STORE-131 to STORE-134, linked to the note. Two are Mira's, one Nina's, one yours, all in sprint 12.

The payment one is the blocker. Make it P0 and mark it blocked by STORE-118.
Used update_task · STORE-133 · priority P0, blocked_by STORE-118

Done. Mira got the P0 message; the board shows the blocked chip.

Reply…
02 · Tuesday

A reply from Aurora Retail.

OpelliMonday catch-upAurora replyAugust invoicesLoyalty launch pageWho is out in October
ChatGPTOpelli · Northwind Studio
Anything waiting in the mail queue from Aurora?
Used list_mail_queue

One message, forwarded this morning: "Re: Phase two scope", from Charles at Aurora Retail, with a reply from their CFO quoted underneath.

File it on Aurora and read it.
Used file_mail · Aurora RetailUsed read_entry_with_agent

Summary: they accept the phase-two scope and want the loyalty page live before their October campaign. Next step proposed: send the revised proposal by Friday, which replaces the step you set yesterday. People: Charles (known), and a new name, Lucy Marsh, "our marketing lead".

Accept the next step, move the deal to Proposal, and look Lucy up.
Used update_deal · stage Proposal, next step acceptedUsed lookup_person · Lucy Marsh, Aurora Retail

Deal moved. Lucy Marsh: one strong match on Aurora's own team page, marketing lead since 2024, with the source linked. Shall I add her as a contact with the buying role "champion"?

Yes.
Used create_contact

Added, with where each field came from recorded on the contact.

Reply…
03 · Thursday

The launch page, before October.

OpelliMonday catch-upAurora replyAugust invoicesLoyalty launch pageWho is out in October
ClaudeOpelli · Northwind Studio
Draft a launch page for Aurora Loyalty from the project's wiki. Headline about earning on every purchase, a sign-up box, three benefit cards.
Used get_wiki_page · Aurora Loyalty · BriefUsed create_siteUsed write_site_files · index.html, styles.css

Staged as version 1, unpublished. Preview link attached. The copy comes from the brief's "What members get" section.

Make the sign-up a real form that files a lead on Aurora's account, and put it above the cards.
Used create_form · Aurora Loyalty sign-up · lead formUsed open_formUsed write_site_files · index.html · edit

Version 2 staged. Submissions file a Lead-stage deal on Aurora Retail, matched by the sender's domain.

Publish it on loyalty.aurora.example.
Used publish_site · version 2

Live. The domain needs one DNS record on their side; the built-in address works now. I'll be able to tell you visits and sign-ups from tomorrow.

Reply…
04 · Month end

Approved hours become the invoice.

OpelliMonday catch-upAurora replyAugust invoicesLoyalty launch pageWho is out in October
ClaudeOpelli · Northwind Studio
Which August statements are still waiting on me?
Used list_approvals · August · pending

Two: Nina on Storefront Revamp (68 h) and Adam on Mobile Companion App (41 h). Everything else is approved.

Show me Nina's entries over 6 hours first.
Used list_time_entries · Nina Roth · August · STORE

Three: 7.5 h on 12 Aug (checkout API), 6.5 h on 19 Aug, 8 h on 27 Aug (release). All billable, all on tasks.

Fine, approve both. Then draft the August invoice for Aurora from approved hours on Storefront, in Czech, with the QR code.
Used api_request · POST /api/tracking/approvals/… · approve × 2Used api_request · POST /api/finance/invoices · from approved hours

Both months are locked. Draft invoice created: 4 lines at the August rates, Czech document, QR payment code, due in 14 days. It is a draft; issuing it allocates the number, and I will only do that when you say so.

Issue and send it, with the PDF.
Used api_request · issue, send

Issued as 2026-091 and emailed to Aurora's billing address with the PDF and ISDOC inside. The send history shows it accepted.

Reply…
05 · Any day

What it will not do.

OpelliMonday catch-upAurora replyAugust invoicesLoyalty launch pageWho is out in October
ChatGPTOpelli · Northwind Studio · guest key
Who from Northwind is out in October, and what are they paid?
Used list_time_off · Octoberapi_request · GET /api/people/…/rates · refused

Lucie is out 13 to 17 October and Adam on the 31st. Pay is outside what this key can read: this connection was made from a guest account, and cost rates are a separate grant that guests never hold.

Then just move the Storefront milestone a week.
Used update_initiative · Storefront Revamp · Launch · +7 days

Moved to 24 October. It is on the roadmap and in the activity log under your name.

Reply…

One permission model for people and their assistants. Every action, a person's or an assistant's, lands in the audit log. Every model call is on the record.

Connect

One connector. Two chapters. Five minutes.

Add Opelli as a custom connector in Claude or ChatGPT, sign in, choose which modules the connection may touch. Any other MCP client takes the config Opelli prints for you.

Claude

Desktop and claude.ai, one connector that follows the account. Settings → Connectors → Add custom connector, then the consent screen lists the tools.

The Claude chapter →

ChatGPT

Developer mode, Create, paste the address, choose OAuth, sign in. Actions that change something confirm each time.

The ChatGPT chapter →

Any MCP client

A copy-paste config with a personal key, scoped to the modules you choose. It runs on your own computer, so it works against a private Opelli too.

The config file →

The whole platform

17 modules, one page.

Every module with its screens, its walkthrough and a session beside it, from Projects to Signing, plus the permission model, the security posture and the AI layer under all of them.

Explore the platform →

3 seats€0a month, forever
Every seat afterone rateevery module, the MCP server included · the price

See it on your own operations.

A short call on your projects and your month, with the assistant you already use connected to a copy of your company.