The agent that onboards your new hires.

Build your company playbook from your existing sources. Find the gaps a new hire would find.

Works inSlackTelegramComing soonTeamsDiscordWhatsApp
# new-salesperson
Jonas

@Opmore First day. Where do I find our mid-market pricing, and how much discount can I offer?

Message #new-salesperson

Use Opmore as your coworker

A demo of the Opmore agent living in your team chat, shown in Slack or Telegram. In Slack it cycles through four channels and a direct message, each conversation playing out with a typing indicator before the agent answers. In channels, teammates tag the agent with an at-mention to bring it in; in the direct message no mention is needed, and the agent preps your morning from HubSpot, Jira and Gmail. The Telegram view shows the real deployment shape: a chat list holding the team group with its four topics, the Opmore Agent bot, and white-label client bots such as Your Onboarding AI and Sakura Assist, where the agent answers under the client's own name. Every answer names its source.

No new tools to learn

It runs where your team already works.

The problem

Every new hire costs you twice.

Once for the salary, and again for the weeks your best person spends re-teaching what was never written down.

?

The docs exist, somewhere.

The real knowledge never got written down.

So your best person re-teaches it. Every time.

How we build it

We extract it. You approve it.

No blank pages, no workshops. Your team can be asking it within the hour.

5 minutes

It starts from what exists.

The agent reads your website, your documents, your tools.

20 minutes

The interview fills the gaps.

It asks about what was never written down. You talk, it writes.

Under an hour

Your team asks it, not you.

Deployed and answering: a new hire, the team, or a client.

Everything the agent writes lands as a draft you approve, so the playbook says what you would say. And when a hire asks something the playbook cannot answer, you are asked once, and the answer lands there for good.

Wondering what it would find on your site?

See how your website scores

Free. We read your site against OPTICS, the six-pillar framework behind the playbook. What is OPTICS?

Over MCP

The same playbook, inside the tools they already use.

Your new hire's AI tools read the playbook over MCP and answer with your company's context.

onboarding.tsCursor
Connected to your Opmore playbook
Set up my dev environment the way the team does it.
Ask Cursor anything…

Opmore is an MCP server. Any tool that speaks MCP can read the playbook. Shown here: Cursor, Claude, Lovable, Strawberry.

A demo rotating through four tools that read the playbook over MCP. In Cursor a new engineer gets their dev environment set up the way the team does it. In Claude they pull the lead qualification rules before researching a market. In Lovable they fetch the branding and the task brief before building a prototype. In Strawberry they read the ICP before searching LinkedIn for matching companies. Each tool calls the playbook, chains its own tools on that context, answers, then starts its own work.

Questions

Ask ChatGPT how your company prices a deal and it improvises something plausible. Your Playbook was extracted from you: every answer the agent gives names the page it came from, and where the Playbook is empty it says so instead of guessing. It asks the person who knows, once, and saves the answer for the next hire.

One question: when did someone last find an answer in it? Notion stores the docs you already wrote. We extract what was never written down, and the agent brings the answer to the person asking, in Slack, with the source shown.

Your Playbook is yours, and we never train models on it. The app and your Playbook database run on EU infrastructure, operated from Stockholm. AI replies go through the model providers we name in our privacy policy, and they do not train on that content by default. You can ask us to export or delete your data, and the agent only acts through the specific tools you connect.

It does chained work across your tools. One message turns into a sequence: it reads the relevant Playbook section, opens the Jira ticket, drafts the Gmail intro, files the Notion doc, and shows you the done result. You saw it run higher up this page.

Every account we create is in your name. You own the Playbook and you keep it if we stop working together. Nothing is held hostage.

We are in private testing and set each company up by hand, so the number gets agreed on a call, not read off a page. There is no price list yet, and we would rather tell you that than invent one.

Wikis rot because someone has to feed them. This one feeds itself: when the agent hits a question it cannot answer, it asks the person who knows, and the one-line reply lands in the Playbook for good. Nobody schedules documentation time.

That’s the sharpest fit. At that size your knowledge is the company and it lives in your head, so you’re the one who can’t scale what only works when you’re in the room. Founder-led, hiring, nothing written down yet is exactly who this was built for.

You can’t scale what only works when you’re in the room.

You can’t delegate what you haven’t defined. We interview you, build the playbook, and the agent onboards the next person without you in the room.

The guarantee

Every account we create is in your name. You own the Playbook, and you keep it if we ever stop working together.