All apps

CRM suite

0.1.0

A follow-up agent, its import tool, the backend it answers on, and the board that watches both.

examplesalescontactsfollow-up

InstallDownload ADIOpens in your panel, which asks where it goesFree — then this installs in one click

Already have ADI? Install it from your panel.

What's included

As published. What actually installs is read off the pinned commit's own tree.

Agents
  • sales-bot — Drafts the follow-up.
Tools
  • csv-import — Loads a contacts export.
Dashboards
  • crm — Who has gone quiet, oldest silence first.
LLM backends
  • gpt5 — The model sales-bot answers on.

About

CRM suite — a demo bundle for the ADI Store

Four pieces of one habit, published together: an agent that drafts the follow-up nobody got round to sending, the tool that loads your contacts, the model backend it answers on, and the board that shows who has gone quiet.

It is here to be read as much as to be run. It is the example of a bundle that carries more than one kind — which is what a bundle is for, and what the other demos deliberately do not show. Install it with a click from the ADI Store, or:

adi-mono marketplace install store/crm-suite

What makes this a bundle

Four kind directories at the top level, and every element named by its own filename:

agents/sales-bot.toml        # drafts the message
tools/csv-import.sh          # loads a contacts export
llm/gpt5.toml                # the backend sales-bot answers on
dashboards/crm/…             # the board that watches both

Each of them installs on its own, which is the other half of what a bundle means — take the tool without the agent, or the dashboard without either:

adi-mono marketplace install store/crm-suite/tools/csv-import

The agent names csv-import in its bin_tools, so installing the agent alone leaves it with an empty bin until the tool lands too. That is the ordinary state of an agent whose tools are not ticked, not an error.

Where it goes

Installing asks: a project of its own (recommended — it keeps these four in one place), a project you already have, or globally. A bundle of four elements is exactly the case a project is for.

What it does not do

llm/gpt5.toml names OPENAI_API_KEY; it does not carry one and nothing reads yours. The agent runs when you run it, the dashboard serves when you start it, and the tool runs when something calls it.

Publishing one of your own

  1. Put each element in its kind directory at the root of a repository, as above.
  2. Push it, and take the commit: git rev-parse HEAD.
  3. Add an entry to a marketplace manifest naming that repository and that full 40-hex commit.

elements in the entry is a preview for the listing — what actually installs is read off the pinned commit's own tree.

The format is in docs/marketplace.md.

Where it comes from

Installing clones this repository at this commit. A publisher who pushes something else afterwards changes nothing about what you already read.

Repository
github.com/adi-family/mp-crm-suite
Commit
a0173c4b6f0929657d10635da89ec4f673399d89
Branch
main
Address
store/crm-suite
Contains
agent · tool · dashboard · LLM backend
Manifest
raw.githubusercontent.com/adi-family/marketplace/main/apps/marketplace.json