Polestar Solutions

Field Notes

Peer intros becomes a full-screen workspace

The peer intro room now opens as a full workspace: five pages on one rail, live count badges, a floor view of the whole board, and the same alias-first trust model.

Key points

  • At an illustrative loaded procurement rate of 85 dollars an hour, that is roughly 730 dollars of analyst time returned each time you run this.
  • If your team runs six peer intros a quarter, that is roughly 208 hours, or about 17,700 dollars of capacity a year, on example arithmetic rather than a measured claim.

The modal tax

Until this release, peer intros opened as a modal. A modal is a fine container for a single decision, accept or decline, yes or no. It is a poor container for a standing process. Peer matching is a standing process. You post an alias, requests arrive over days, some counterparties answer fast and some go quiet, and the useful signal is not any single request but the shape of the whole board over time. A modal forces you to reconstruct that shape from memory every time you open it, because it shows you one slice and then closes.

The symptom we saw in usage was predictable. Buyers opened the intro room, handled the single item that had triggered a notification, and closed it. Requests that had not generated a notification aged out. Matches that were live but not urgent were forgotten. The feature was being used as an inbox rather than as a workspace, which meant the network effect that makes pooled leverage worth anything never had a place to accumulate.

app.isvcosell.com/network/intros/floor

The floor page: every alias, request and match on the board in one read.

THE SAME JOB, TWICE

TODAY, BY HAND

Scroll back through two Slack communities and your LinkedIn connections looking for anyone who bought the same vendor on a comparable tier in the last eighteen months.

Build a spreadsheet of candidate names, likely contract dates, estimated seat bands, and what you can safely ask each one without revealing your own position.

Dig through the email archive for the introduction thread from a conference two years ago, and work out who owes whom a favour before you can use it.

Draft four careful outreach notes that request a number while disclosing nothing, then wait, then follow up on the two that went unanswered.

Roughly 9 hours of analyst time, spread across three weeks

WITH ISVCOSELL

Open the peer intro workspace from the network tab and read the floor page for the current state of every alias, request and match.

Filter Requests and matches by vendor, renewal quarter and deal size band, then send talk requests with your alias intact.

Ask ISVCOSELL, grounded on the live board, which counterparties in this cohort have already responded and which are stalled.

Accept a mutual yes, let contacts unlock on both sides, and put the call in the calendar.

About 20 minutes of your attention

What changes: roughly 9 hours becomes about 20 minutes, a saving of about 8.6 hours per peer intro cycle. At an illustrative loaded procurement rate of 85 dollars an hour, that is roughly 730 dollars of analyst time returned each time you run this. If your team runs six peer intros a quarter, that is roughly 208 hours, or about 17,700 dollars of capacity a year, on example arithmetic rather than a measured claim.

PART TWO

Five pages on one rail

The intro room now opens as a workspace, using the same full-screen shell the workrooms already use. That matters less as a design statement than as a muscle memory statement. If you have used the negotiation workroom, you already know how to drive this: five pages on a single left rail, arrow keys to move between them, Esc to close and return to where you were.

The five pages are The floor, Talk requests, Requests and matches, Our profile, and Community network. Each carries a live count badge, so the rail itself tells you where the work is before you click anything. Three pending talk requests and one new match reads differently from zero and zero, and you get that read in under a second rather than by opening four panels in sequence.

"A modal is a container for one decision. Peer matching is a standing process, and standing processes need a room."

PART THREE

The floor page, and why it is the important one

The floor is new. Everything else on the rail existed in some form before. The floor reads the whole board at a glance: who is on it under alias, which cohorts are active for the vendors in your estate, which requests are outbound and waiting, which are inbound and waiting on you, and which have converted to a mutual yes. It is the page that answers the question a modal could never answer, which is not what is my next action but what is the state of my network right now.

Practically, this changes when you open the room. Before, you opened it because a notification told you to. Now it is worth a thirty second look at the start of a renewal cycle, in the same way you would glance at the renewal calendar. If you are already running a structured cycle, this slots in beside the kickoff interview rather than competing with it.

app.isvcosell.com/network/intros/dock/ask

Ask ISVCOSELL in the dock, grounded on the live board rather than the general corpus.

PART FOUR

The dock, and the anonymity ladder in permanent view

Beside every page sits a dock with three things. What now moves is the short list of actions that would change the state of the board today. Ask ISVCOSELL is grounded on the live board, which means it answers about this cohort and these requests, not about the general corpus, so questions like which of my outbound requests have been open longest get a direct answer. The third item is the anonymity ladder, and it is deliberately always visible.

The trust model has not changed by a single rung. Aliases until a match. Contacts exchanged only on a mutual yes. Nobody sees your company name, your spend, or your contract dates because they happened to appear in the same cohort as you. The reason the ladder now sits permanently in the dock rather than behind a help link is that buyers were hesitating at the post step, unsure what they were exposing. Showing the ladder next to the action removes the hesitation without changing the guarantee. The same principle underwrites the verified outcome cohorts: disclosure is a decision you make twice, once to match and once to talk.

1 The room is now persistent. It opens as a full-screen workspace rather than a modal, so the board survives your attention wandering elsewhere. Esc closes it and returns you to your previous view with state intact.

2 Five pages, one rail, keyboard driven. The floor, Talk requests, Requests and matches, Our profile, Community network. Arrow keys page between them. This is the same shell as the workrooms, so there is nothing new to learn.

3 Live count badges replace notification archaeology. The rail shows pending counts per page, updating live. You no longer need to open each section to discover whether anything is waiting.

4 The floor page is a genuine new capability. It is the only view that shows the entire board state at once, which is what makes a thirty second check-in worth doing at the start of a cycle.

5 Ask ISVCOSELL is scoped to the live board. Questions are answered against current cohort and request data rather than the general benchmark corpus, which makes the answers short and specific.

6 The trust model is unchanged. Aliases until a match, contacts only on a mutual yes. No new disclosure surface has been introduced by this release. The ladder is simply now visible at the point of action.

PART FIVE

Honest limits

This release is a shell change, and it is important to be precise about what a shell change cannot do. It does not create peers. If no other member of the network holds the vendor you are renewing, the floor page will tell you that faster and more clearly than the modal did, which is useful, but it is still a no. Cohort depth varies enormously by vendor. The large platform vendors are well populated. A niche vertical tool bought by forty companies worldwide may show you an empty board, and no interface improvement fixes that.

Second, the workspace does not accelerate the other side. Live count badges tell you when a request has been sitting for eleven days. They do not make the counterparty answer. Response rates are a function of how many peers are actively in cycle, and a request sent in the quiet weeks of a fiscal year will sit. Third, the anonymity ladder cuts both ways. Because declines are anonymous, you will sometimes never learn why a request went nowhere, and you cannot chase. That is the deliberate cost of the model, and we are not going to trade it for higher conversion.

Fourth, keyboard paging and the full rail assume a reasonably wide screen. On narrow viewports the workspace falls back to stacked pages without the rail, which works but loses the at a glance property that is the whole point. Fifth, Ask ISVCOSELL in the dock is grounded on the board, which means it is deliberately narrow. It will not answer a pricing question. For that, you still go to the benchmark, or to the call copilot once you are actually on the phone with the vendor.

The honest summary is that this makes an existing capability usable at the cadence it was always designed for. Peer intros were never meant to be a thing you did once under deadline pressure. They were meant to be a slow accumulating asset, posted early and harvested when the renewal arrives. A modal made that impossible. A workspace makes it merely a habit, and habits are the part you control. You can open it now at /network.

MA

About the author

Morten Andersen, Cofounder, ISVCOSELL

Morten brings two decades of enterprise and software procurement, with stints across Oracle, IBM, SAP, and Salesforce shaping how he reads a deal. He has led sourcing through hundreds of renewals, from mid market order forms to nine figure global agreements, and learned that the buyers who win are the ones who walk in knowing the market. He built ISVCOSELL to make that pattern recognition repeatable.

More posts by Morten Connect on LinkedIn →

FREE TRIAL · FULL PLATFORM · NO CARD REQUIRED

Compare notes with a peer who bought the same thing last quarter

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.

V ISVCOSELL

A ISVCOSELL product · © 2026

PLATFORM Benchmarking Negotiations Contract management AI workflows Document search Renewal calendar

PRODUCT Use cases Features Security Pricing Deployment options About

RESOURCES Getting started ROI calculator Agent protocol FAQ Blog Request access

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