Install a pack. Or publish your own.
The marketplace is where operating capability travels. Install a pack to add agents, skills, playbooks, fields, and vocabulary to your workspace in one move. Or package how you run and publish it, to your own clients as a productized vertical, or to other agencies as a complete operating model.
A pack is a working capability, not a feature toggle.
A pack bundles what it takes to actually run something: the agents that do the work, the skills and playbooks they follow, the tools they call, the custom fields they need, and a vocabulary overlay that renames things to match how you talk about the work.
Agents, skills, tools
The working parts, installed together.
Custom fields
The data the pack needs, defined on install.
Methodology overlays
Rename deals, clients, tasks, and deliverables to your vocabulary, with no code change and no schema change.
A look at the kinds of packs that run on Emerjent.
The marketplace is young. Here's the shape of what travels on it.
Peak Paws OS
A vertical built on Emerjent for veterinary and animal-rehabilitation practices: evaluation intake from a patient's vet records, daily treatment notes, recheck timing across providers, and post-session documentation in a rehab therapist's language.
Running a live practice todayHubSpot Activity Sync
Sync HubSpot calls, meetings, emails, and notes into Emerjent on a schedule, resolved to the right client and deal. Packaged as an installable integration.
How it worksA SaaS onboarding pack
The kind of pack an agency could build: a repeatable client-onboarding motion, the pipeline, the deliverables, the playbooks, ready to deliver to every client like it.
A methodology overlay
Rename Emerjent's canonical entities to your firm's vocabulary so the whole workspace speaks your language.
Distribution is live. The catalog is young, you'd be one of the first agencies publishing on it.
Packs compose. Conflicts surface before anything lands.
Packs aren't dumb bundles. A pack can extend another, require another, or declare what it conflicts with. When you install, Emerjent detects conflicts up front and lets you resolve them per workspace, so adding capability doesn't quietly break what's already there.
Package how you run, and offer it.
Most of your best work is something you repeat. The marketplace lets you package it once and offer it, so your methodology is worth more than your hours.
What you can bundle
- Agents and the skills and tools they use.
- Playbooks and the custom fields a methodology needs.
- A vocabulary overlay that renames entities to your language.
- An integration setup, packaged so it travels (the HubSpot sync is the example).
How you offer it
- Choose a price model: free, one-time, or subscription.
- Choose who sees it: public on the marketplace, or private to your own org.
- Draft, then publish: build it as a draft, review it, publish when it's ready.
- Bundle listings together: group related packs into a single discounted bundle.
- Distribute across workspaces: install a pack into a client's or peer agency's workspace, with a permission model you both control and drift indicators so you can see what's running where.
Reselling is a capability you pay for, never a cut of what you make. You set your prices and keep your margin.
Integrations travel the same way. The HubSpot activity sync is packaged as a marketplace integration.
See IntegrationsInstall how others run. Or publish how you do.
Distribution is live. You'd be one of the first agencies publishing on it.