Skip to main content
Skip to content
Software ProductsPhased rollout

Claude Business Hub

A hub inside Claude where business teams work on top of all their tools, through apps and widgets Claude serves.

two colleagues working at one laptop
  • Workplace toolingIndustry
  • Business teamsClient
  • Software ProductsCategory
  • Phased rolloutTime to impact
CH.01 · The challenge

The challenge

today
  1. Business people lose time switching between a dozen tools and interfaces.
  2. The work is simple; the tool-hopping is what slows it down.
Our answer

A hub inside Claude where business teams work on top of all their tools, through apps and widgets Claude serves.

A private hub built inside Claude for a customer, so their business people can work from one place: Claude web, connected to all their tools. Instead of hopping between systems, Claude provides the apps and widgets that get each job done.

CH.02 · What we built

What we built

A hub inside Claude where business teams work on top of all their tools, through apps and widgets Claude serves.
  1. 01A single hub inside Claude web for the whole team.
  2. 02Connected to the customer’s existing tools and integrations.
  3. 03Claude serves purpose-built apps and widgets for each task.
  4. 04People work on top of Claude instead of jumping between systems.
CH.03 · How it works

How it works

CH.04 · What it can do

What it can do

  • One hub

    The whole team works from Claude web.

  • Tool integrations

    Connected to the systems they already use.

  • Apps & widgets

    Purpose-built surfaces for each job.

  • Less tool-hopping

    Simple work, done in one place.

CH.05 · Who stays in the loop

Who stays in the loop

The call the system deliberately does not take, and what the person is given to take it with.

Runs on its own

A private hub built inside Claude for a customer

Who

The person doing the job

Decidesany action that writes back into a connected tool

Seeswhat the widget is about to do, and in which system it would do it

CH.06 · The payoff

The payoff

What is different once it is running. No invented numbers: these are the changes the work was built to make.

Business teams stop hopping between systems and work from one place: Claude, with all their tools behind it.
  • Less time lost switching between tools.

  • A single place for everyday work.

  • Simpler jobs through purpose-built widgets.

CH.07 · Built with

Built with

The layers this runs on, from what comes in to what it plugs into.

  1. Model layer
    • Claude
  2. What people use
    • Apps & widgets
  3. Connects to
    • MCP integrations
CH.08 · Common questions

Common questions

The same answers as above, written out.

A private hub built inside Claude for a customer, so their business people can work from one place: Claude web, connected to all their tools. Instead of hopping between systems, Claude provides the apps and widgets that get each job done.

Business people lose time switching between a dozen tools and interfaces. The work is simple; the tool-hopping is what slows it down.

Connect the customer’s tools to the hub. Claude serves apps and widgets per task. The team works on top of Claude, in one place.

The person doing the job decides any action that writes back into a connected tool. They see what the widget is about to do, and in which system it would do it.

Model layer: Claude. What people use: Apps & widgets. Connects to: MCP integrations.

Less time lost switching between tools. A single place for everyday work. Simpler jobs through purpose-built widgets.

Start

Bring us the problem nobody has cracked yet.

We are a small team of senior specialists. We pick the right model and the right layer, and we build the least machinery that does the job. You get a call with an engineer, not a sales deck.