Polestar Solutions

Field Notes

ISVCOSELL in Slack and Teams: the analyst where the conversation is

The question about a vendor price gets asked in a channel, not in an app. ISVCOSELL now answers in Slack and Teams with a grounded verdict, cited figures, and one deep link, or an honest refusal when the data is thin.

Ask in the thread, three ways

In Slack you can reach ISVCOSELL three ways, whichever fits the moment. A slash command for a quick private check, a mention in a channel when the whole thread should see the answer, or a direct message for a one to one. She replies in the thread, so the answer sits with the question rather than scrolling away in a separate app. In Microsoft Teams the same analyst answers through a bot, so a Teams shop gets the identical capability without changing tools.

The connection is made once, at the workspace level, and then the analyst is simply present. There is no per person setup, no new login, no app to install on each desk. The people already talking about the vendor can ask about the vendor, in the place they are already talking.

app.isvcosell.com/settings/integrations

Connected once at the workspace level. After that the analyst is simply present in Slack and Teams.

THE SAME JOB, TWICE

TODAY, BY HAND

A colleague drops the renewal quote into the Slack channel and asks the real question: are we overpaying for this?

Nobody opens the procurement app, finds the right screen, and runs a report, because the decision is moving now.

The channel answers with a guess or a shrug, and the decision moves on without an answer.

If anyone does chase the number, it surfaces days later in an email the thread has already scrolled past.

The question goes unanswered, and the decision goes on feel

WITH ISVCOSELL

Connect Slack or Teams once at the workspace level on the integrations screen; no per person setup, no new login.

Ask ISVCOSELL in the thread: a slash command for a private check, a mention when the whole channel should see it, or a direct message.

Read the reply where the question was asked: a plain verdict, favorable, neutral, or risk, then two to four figures, each labelled as your contract, the benchmark set, or the market.

Follow the single deep link into the app when someone wants the full analysis; when the data is thin, ISVCOSELL says so instead of improvising.

A grounded, cited verdict in the time it takes to read a chat message

What changes: the distance between a question and a grounded answer shrinks from an app, a screen, and a report away to one message away. If a mid size team fields even five of these channel questions a week, that is five decisions a week made against 1,483 vendors and modelled deal cohorts instead of a shrug, and one quote challenged in the thread before it was accepted can pay for the year.

PART TWO

A verdict, cited, in the space of a chat message

A chat answer cannot be a white paper. It has seconds of attention and a few lines of room, so the format is disciplined by design. ISVCOSELL leads with a plain verdict, favorable, neutral, or risk, then gives two to four figures, and every figure carries a provenance label saying whether it came from your contract, the benchmark set, or the wider market. It closes with exactly one deep link, into the app, for the person who wants the full analysis behind the answer.

That structure is deliberate. It is enough to make a decision in the thread, and honest about where every number came from, without pretending a chat reply is the whole report. When someone needs the depth, the one link takes them to it. When they just needed to know whether the quote was fair, the verdict and the figures were already there.

"The best benchmark in the world is useless if it lives one context switch away from the question. So the analyst moved into the thread."

app.isvcosell.com/ask

The same grounded analyst behind the channel reply: a verdict, cited figures, and one link to the full analysis.

PART THREE

What it will not do, on purpose

The channel answer runs on exactly the same discipline as the rest of the platform. It passes through the same grounding, so a figure in Slack carries a citation just like a figure in a report, and when the data does not support an answer, ISVCOSELL says so in the channel instead of improvising a confident guess. An honest "I do not have enough to answer that" in front of the whole thread is worth more than a plausible number someone repeats to a vendor.

The first version is deliberately narrow in another way too. ISVCOSELL replies when asked and does not post on her own, so the channel never fills with unsolicited alerts. She is an analyst you can consult in the conversation, not a bot broadcasting into it. That restraint is the point: the value is a trusted answer on demand, not another feed to mute.

WHAT IT CARRIES

What a channel answer always includes

1 A plain verdict. Favorable, neutral, or risk, stated first, so the thread gets the conclusion before the detail.

2 Cited figures. Two to four numbers, each labelled with where it came from: your contract, the benchmark set, or the market.

3 Exactly one link. A single deep link into the app for the full analysis, so the reply stays short without hiding the depth.

4 An honest refusal. When the data is thin, a clear no answer in the channel, rather than a confident guess someone might repeat to a vendor.

THE HONEST LIMIT

A consultation, not a decision maker

ISVCOSELL in a channel is a place to ask, not a place to commit. She answers, grounded and briefly, and the judgment stays with the people in the thread. The connection is workspace level rather than tied to each person's identity, so the answer reflects the organization's data, and the decision reflects the people reading it.

What changes is the distance between a question and a grounded answer. It used to be an app, a screen, and a report away, which in practice meant the question went unanswered and the decision went on feel. Now it is a message away, cited, in the room where the deal is actually being discussed. That is where an analyst was always most useful, and now that is where she sits.

FF

About the author

Fredrik Filipsson, Cofounder, ISVCOSELL

Fredrik has spent more than twenty years in enterprise software, with time at Oracle, IBM, SAP, and Salesforce before moving to the buy side. He structured and priced the kind of large agreements most buyers only see once or twice in a career, which taught him where the leverage sits and how far a vendor will actually move. He started ISVCOSELL to hand that knowledge to every sourcing team.

More posts by Fredrik Connect on LinkedIn →

See it in the product

How benchmarking works → Browse the use cases → Every feature → Calculate your time saved →

FREE TRIAL · FULL PLATFORM · NO CARD REQUIRED

Put the analyst in your team's channel.

The free trial opens the benchmarking database, 1,483 vendors deep, plus the negotiation guides, playbooks, and talking points for your own renewals. No card needed, a corporate email is all it takes.

Start your free trial → Or decode a contract free, no account

Free for 30 days, no card needed. Your data stays isolated at the database, and you can export or delete it any time.

Watch it in action

ISVCOSELL: the three minute demo What discount should we expect? One question, every agreement

Browse the full demo library →

THE ISVCOSELL AI BRIEF · WEEKLY

The week in enterprise software buying, in one email.

What shipped on the platform, and the pricing and licensing moves worth knowing before your next renewal. One email a week, to your work address. Unsubscribe any time.

Subscribe

More in Field Notes

1,483 vendors, one method: how the benchmark library is built

A benchmark is only as good as the deals behind it and the honesty of how it is compared. How the library is built from modelled deal cohorts, normalized, placed in the right peer cohort, and graded by confidence.

Read

300 vendors, 52 weeks, one team: the renewal calendar problem

The average enterprise runs 300+ software vendors and every one of them renews. Why notice windows are where budgets quietly die, and how a renewal desk with AI agents turns the calendar from a threat into leverage.

Read

A calmer desk, and Main Apps where the work starts

The platform now wears the desktop look: warm paper, one interactive colour, and Main Apps folded into Home so your instruments live where you start.

Read

A live analyst in your ear: inside the call copilot

The vendor call is where prepared positions meet improvisation, and the rep does this every day. The live call copilot runs a whisper rail beside the conversation: live transcript, grounded prompts, and the exact fact you need at the moment the claim is made.

Read

Adobe ETLA vs VIP: seat reclaim, right-profiling, and the walk away

An Adobe ETLA renewal is decided before you discuss price, by how many seats sit idle and how many are over-profiled. How to reclaim the waste, right-profile the rest, and build the VIP walk away Adobe respects.

Read

Agent to agent: how the Agent Negotiation Protocol works

When a buyer's AI agent negotiates with a vendor's AI agent, someone has to keep the record straight. How the open Agent Negotiation Protocol handles identity, mandate, and a ledger neither side can rewrite.

Read

Want help putting this into practice?

Contact us to discuss your project.

Get in Touch