Polestar Solutions

Field Notes

Every screen now keeps your work

The last surfaces that lost what you typed are fixed. Playbook wizards, agent builds, ISVCOSELL interviews and email drafts now hold their state until you decide.

The problem you already recognise

If you run renewals for a living, you have learned defensive habits. You draft long email in a separate document because you do not trust the in app editor. You avoid uploading a contract into a wizard because you have watched one vanish. You finish an interview with an analyst in a single sitting because you assume an interruption means starting over. These are rational responses to tools that forget. They are also slow, and they quietly move the real work out of the platform and into your inbox and your desktop, which is where knowledge goes to die. This is the same argument we made about team knowledge that survives turnover. Work that lives only in one person's local files is work the team cannot inherit.

The fix here is unglamorous and it is the point. We went surface by surface through the screens that still dropped state and made each one hold what you put into it until you decide to move on. No new feature to learn. The change is that the tools stop punishing you for leaving them.

app.isvcosell.com/home

The analyst desk now shows in progress work that persists across sessions, not just completed reports.

THE SAME JOB, TWICE

TODAY, BY HAND

Read the incumbent contract and note renewal terms into a scratch document because the wizard might lose them

Start the renewal wizard, answer the first questions, then keep the browser tab untouched all day so nothing resets

Re draft the email counter in a separate editor you trust, then paste it back in and hope the formatting survives

Re upload the contract a second time when the vendor playbook did not keep the first copy

Roughly 6 hours, spread across a week, most of it redoing work you had already done once

WITH ISVCOSELL

Open the renewal wizard, answer as far as you get, and let it keep every answer and the step you were on

Drop the contract into the wizard once, where it stays attached instead of orphaning

Write the agent goal, review the chain ISVCOSELL drafts, and come back later to the same draft without paying for another

Edit the email draft in the workroom directly, knowing your edit is what the copy and the log carry forward

About 40 minutes of your attention, in whatever sittings suit you

What changes: roughly 6 hours of rework becomes about 40 minutes of actual thinking. If a procurement lead runs even eight renewals a month, that is close to 40 hours a month recovered, or the better part of a full working week that used to go to redoing lost work.

PART TWO

Renewals, agents, and ISVCOSELL all keep their place

The renewal playbook wizard now keeps every answer and the exact step you were on, and it no longer orphans a contract you uploaded inside it. That matters because the wizard is where a renewal actually starts, and we have long argued you should start the renewal with an interview, not a blank dashboard. An interview that forgets your answers is worse than a blank dashboard, so this was the surface that needed fixing most.

The agent builder keeps the goal you wrote and the chain ISVCOSELL drafted. Coming back to it does not mean paying for another draft, which was the old cost of closing the tab too early. Across our six specialist agents and thirteen inbox agents, the drafts you commission now wait for you. The launch list for a ISVCOSELL run negotiation survives until you launch it, so assembling the list is no longer a race against a timeout. And an interrupted interview with ISVCOSELL comes back with the conversation intact, which means you can stop mid thought, check a figure, and resume the same conversation rather than a fresh one.

"A tool that forgets your answers is worse than a blank page, because it charges you for the work twice."

PART THREE

Decoders and benchmarks hold the small inputs too

Contract decode, the SOW decoder and the MSA decoder, and the rate card benchmark now hold the vendor name you type before you drop the document. This is a small thing that used to cause a specific, annoying failure. You typed the vendor, dropped the file, and the name cleared, so the analysis attached to nothing recognisable. Now the name you type is the name the analysis carries. The report extract also keeps the layout you build, so the 25 plus report types you assemble do not reset their structure while you work. When you are comparing what shifted year over year, as we described in what the vendor quietly changed since last year, keeping the layout means your comparison view stays where you put it.

app.isvcosell.com/decode

The decoders keep the vendor name you type before the drop, so the analysis attaches to the right record.

PART FOUR

Email drafts in the workroom are genuinely editable

The guide always said email drafts in a workroom were editable. Now they genuinely are, and your edit is what the copy button, the mail handoff, and the negotiation log all carry. This closes a quiet trap where you edited a draft, felt satisfied, then discovered the copied version or the logged version was the original machine draft, not your revision. That is the sort of gap that undermines trust in the whole handoff. If you rely on the flow we described in the What Next desk, where every analysis ends with the emails drafted, the edit you make there is now authoritative through the entire chain.

For teams that use the ghost writer to turn a forwarded vendor email into a counter in your voice, this is the difference between a draft you can trust and one you have to double check every time. The version you edit is the version that ships.

1 The renewal wizard keeps your place. Every answer and the step you were on persist, and a contract uploaded inside it stays attached instead of orphaning.

2 The agent builder holds your draft. Your goal and the chain ISVCOSELL drafted survive a return visit, so you do not pay for a second draft of work you already did.

3 ISVCOSELL interviews and launch lists resume. An interrupted interview comes back with the conversation intact, and a negotiation launch list survives until you launch it.

4 Decoders and benchmarks keep small inputs. Contract decode, the SOW and MSA decoders, and the rate card benchmark hold the vendor name you type before the drop, and the report extract keeps your layout.

5 Email edits are authoritative. Your edit is what the copy, the mail handoff, and the negotiation log carry, not the original machine draft.

6 Vendor playbook uploads wait for analysis. Contracts dropped into a vendor playbook wait to be analysed rather than forcing you to upload them twice.

PART FIVE

Honest limits

This release is about persistence, not permanence, and the distinction matters. State is kept while you are working on a piece of work. It is not a version history, and it is not an undo tree. If you deliberately clear a field or overwrite a draft, the platform keeps the new value, not the old one, because it cannot read your intent. If two people open the same renewal wizard at the same time, the platform keeps state per person and per session, so it will not merge two people's edits into one coherent answer. Coordinate who is driving before you both start typing.

There are also boundaries at the edges. Very old sessions may expire for security reasons, in line with the tenant isolation we hold ourselves to, so this is not a promise that a draft abandoned for months will still be waiting. And keeping your work does not make it correct. A persisted goal for an agent is still only as good as the goal you wrote. The value here is narrow and real. The platform stops erasing your progress. What you do with the time you get back, whether that is a sharper counter offer document or a better prepared war room, is still your job to do well.

The weekly licensing brief

Want to be updated when major licensing and pricing changes land? One analyst brief a week: the price rises, metric changes and audit campaigns that move software costs. Work email only.

Get the brief

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 →

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

Start a renewal that remembers where you left off

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 →

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