Rune works where you already work, and connects to what you need.

SHPwLOA

One of these is enough. The workflow does not ask for all of them.

The company that appeared in the registers, in the pipeline you already run

Fourteen official business registers across seventeen markets, filtered to what you sell, landing as a real record in your own CRM with the reasoning attached.

1. 1Reads your seed: your site, what you sell, and who you sell it to.
2. 2Finds the companies in the registers whose shape matches, and takes your competitors out of that list rather than showing them to you as customers.
3. 3Measures each one's cloud and tech stack from the outside, with no login and no scraping of anyone's inbox.
4. 4Writes the dossier: who to reach out to, why now, and what to engage on.
5. 5Creates the company and the contact in your CRM, deduplicated against what you already hold.

SHPwLO

One of these is enough. The workflow does not ask for all of them.

Your won deals tell Rune who to look for next

Your ideal customer profile as revealed by who actually bought, not as described in a workshop two years ago.

1. 1Reads closed-won out of your CRM, and where the books are connected, reads who actually paid and renewed.
2. 2Derives the shape those customers share: sector, size, stack, region, and the funding door where one exists.
3. 3Searches the registers for that shape across your entitled zones.
4. 4Ranks what comes back by how closely it matches the customers you already kept.

AAM

One of these is enough. The workflow does not ask for all of them.

The meeting recorded, the opportunity drafted, a person submits

The chain from a Teams call to a co-sell opportunity AWS can score, with a human at the one point where it matters.

1. 1Joins the Teams or Meet call as a notetaker, recorded and transcribed in the EU.
2. 2Qualifies what was actually said into a draft opportunity or lead, grounded in the transcript and not in a summary of it.
3. 3Puts the draft on an approval queue with the evidence beside it.
4. 4On approval, writes it into Partner Central against the catalog you chose.

SM

One of these is enough. The workflow does not ask for all of them.

The reply reaches the room you are already in

A prospect answers, and the follow-up is drafted and waiting where your team already works.

1. 1Triages the inbound reply against what was said before, including the things already tried.
2. 2Drafts the follow-up in your voice, with the account's own facts in it.
3. 3Posts it into Slack or Teams, in the thread, with the reasoning visible.

P

Sell the week you can actually staff

For anyone selling time and material: capacity is a sales signal, and no other tool in this market reads it.

1. 1Reads utilisation and forecast out of Pace: time entered, absence booked, what is committed to which project.
2. 2Works out which skills are free, and when.
3. 3Ranks the accounts in your pipeline against the capacity you actually have, rather than against the capacity you wish you had.
4. 4Names the opener that matches: the consultant who is free, the competence, the week.

Hiring is the loudest why-now there is

Their advert says what they are about to need. Your advert says what you are about to be able to sell.

1. 1Reads the public job feeds in the registers layer for the roles that mean a project is starting.
2. 2Reads your own hiring out of Ashby, Greenhouse, Lever, Workable or SmartRecruiters, so the offer keeps pace with the bench.
3. 3Puts the two together: their need, dated, next to your capability, dated.

The books say who actually pays

A closed deal is an opinion. An invoice that was paid, twice, is a fact.

1. 1Reads the ledger from Fortnox, Xero, QuickBooks, Sage, NetSuite or Pennylane.
2. 2Separates the customers who renewed from the customers who signed.
3. 3Feeds that back into the profile, so the next search looks for the ones who stayed.

SM

One of these is enough. The workflow does not ask for all of them.

Ask Rune from the tool you are already in

He is a terminal that talks, reasons and builds. He should not need his own tab to do it.

1. 1Answers in the Slack thread, grounded in the account you are looking at.
2. 2Answers over MCP to Claude, Cursor or ChatGPT, from three read-only tools.
3. 3Reads aloud when you want it read, and stays quiet when you do not.

One of these is enough. The workflow does not ask for all of them.

Your own agent, on your own market

The library is the same for everyone. What Rune knows about you is not, and that part never leaves.

1. 1Serves the shelf over MCP so your agent can read it: aggregates and banded posture, never a person.
2. 2Reads the server you run, so your internal systems join the reasoning without leaving your estate.