Better together

Use two of them, and each gets better.

The four products share one private picture of your world — your emails, contacts, calendar, and data — kept on machines you own. Each product reads from it and adds to it, so they plug into each other instead of starting from zero.

Common Context Your emails, chats, calendar, contacts & data — source-grounded, on your machine
SwarmMarshal Builds the picture from your email and chats — and answers from it.
SwarmMarshal CRM Your team's customers, deals, and support — askable in plain English.
Vibes Little apps and dashboards over any slice of it.
SwarmSpan Carries it across every Mac and PC you own.
The shape of it

One builds it. Two surface it. One spreads it.

SwarmMarshal builds it

Your communication history becomes a private, source-cited knowledge graph — the raw material every other product draws on.

CRM & Vibes surface it

The CRM is the relationship surface for a team; Vibes shapes any structured slice you need. Both run on the same SwarmCore engine.

SwarmSpan spreads it

The utility that lets all of it span your devices, so your context and agents aren't trapped on one computer.

Live today

What they already do together.

Not a roadmap — these ship now. Each one saves you a real, everyday chore: tab-hopping, re-asking, copying between machines, or paying cloud tokens for routine questions.

Now

Ask once, answered from email and CRM together

“What's the status of the Acme deal?” pulls the CRM pipeline stage and the email thread into one answer, cited across both — no hopping between the inbox and the CRM. Scoped to your connected work account.

Now

Start the day already briefed on the team

The CRM's “what needs attention today” feed — overdue follow-ups, scheduled calls, deal next steps, urgent tickets — lands as a card on SwarmMarshal's Today dashboard, right next to your personal briefing.

Now

Your assistant can work the CRM for you

SwarmMarshal finds your connected CRM automatically and can look up contacts, companies, and deals — or put a whole question to the CRM's data agent — mid-conversation. Read-only, and only what your CRM login is allowed to see.

Now

Team dashboards, described in plain English

Vibe apps can read live CRM records — describe a tracker or dashboard and it fills from the team's actual pipeline, read-only. Publish it to the CRM's Vibes gallery and the whole team gets it.

Now

Your own computers do the AI work

Desktops running SwarmMarshal can volunteer their local models to the CRM's compute pool — opt-in per machine, admin-approved. Routine questions run on hardware you already own, at zero per-token cost.

Now

Agents that reach across your desk

When the SwarmSpan tray utility is running, SwarmMarshal's assistant discovers it on its own — so “send that file to the Mac” or “grab what's on the PC clipboard” is just part of the conversation.

Your work email only — never your personal life.

The email–CRM connection is per-account and opt-in. You connect the one work email account that signs in to your CRM, and only that account ever interacts with it. Every other inbox in SwarmMarshal — personal mail, side projects, family — stays completely separate and is never read by, synced to, or exposed to the company CRM. You choose, per account, on the email account settings page, and you can disconnect any time.

Coming next

Where the family compounds from here.

Planned means we're building it; exploring is directional — no dates on either.

Planned

Your CRM fills itself from your work email

The people, companies, last-contact, and open commitments SwarmMarshal already knows from your connected work account flow into the CRM, with citations back to the source message. No more cold, empty CRM.

Planned

Work email logs itself as activity

When your connected work account exchanges mail with a CRM contact, it's logged as an activity automatically — the relationship record keeps itself current.

Exploring

Build a Vibe from your history

“Track every vendor who quoted me this year” builds the tracker and populates the rows from cited messages.

Exploring

Describe new CRM objects into existence

“Add a table for warranty claims” extends the CRM with a new custom object — no bespoke code, on the same engine that powers Vibes.

Start anywhere

Begin with SwarmMarshal — the context everything else shares.

Download the star, then add the CRM, Vibes, or SwarmSpan as you need them.