Contract Renewal

Contract management

2026

Product Designer

I redesigned how AlphaSights renews client Access Plans, moving the renewal out of inboxes and documents and into one product workflow.

Mobile views presenting a chat and a map view

Contract Renewal

Contract management

2026

Product Designer

I redesigned how AlphaSights renews client Access Plans, moving the renewal out of inboxes and documents and into one product workflow.

Mobile views presenting a chat and a map view
Mobile views presenting a chat and a map view

Contract Renewal

I redesigned how AlphaSights renews client Access Plans, moving the renewal out of inboxes and documents and into one product workflow.

Contract management

2026

Product Designer

Mobile views presenting a chat and a map view
Mobile views presenting a chat and a map view

Project summary

Scope

Renewing and setting up client Access Plans, from the renewal date to the configuration going live.

Challenge

Renewals were negotiated over email, contracts were edited back and forth by hand, and Commercial Ops set up each plan by reading free-text clauses.

Solution

Treat the agreement as structured data, so the same information drives the renewal, the contract and the system setup.

Problem

Every team re-entered the same agreement

I followed one renewal from the first email to the plan going live. It broke down in three places, each owned by a different team:

  1. Negotiation. Each renewal was negotiated in someone's own Gmail. The renewal date, what had been offered and where things stood lived in one inbox, out of sight of everyone else.

  2. The contract. Every change was made by editing the contract itself, so each round meant rewriting and rechecking legal text.

  3. Setup. After signing, Commercial Ops read the free-text clauses and set up the plan by hand. Every setup started with working out what the legal wording meant.

On the surface these were three problems, but they shared one cause. The agreement only existed as text, in an inbox or a document, so every team had to read it and type it in again. That changed the brief from fixing three screens to changing where the agreement lives.

Tracking renewals

Move renewals out of personal inboxes

Because negotiations ran through personal Gmail, the state of a renewal lived in one person's head. Nobody else could see when a plan was due, what had been agreed so far, or whether it had stalled. Covering for a colleague meant forwarding email threads.

Decision

I made the Access Plan the shared home of the renewal. A board shows every renewal by stage, from In progress through review, price letter and Sent to client to Client signed. Each card shows the plan's dates, its status and the one action needed next.

I also brought the emails to the plan. Users add the client's email addresses, and the plan's Activity panel shows the renewal emails with those contacts. They can search the thread by keyword, such as "contract terms", and jump to the matching email.

Outcome

The renewal date, the conversation and the negotiation now sit next to the plan, where anyone involved can find them, instead of in one person's inbox.

Building the contract

Generate the contract from a guided form

Editing the contract directly meant every change, even a new price or end date, was another round of rewriting and rechecking legal text. The document was doing a job that data should do.

Decision

I replaced the document with a guided flow that generates the contract. Its first step works out which template the renewal needs, so users no longer choose it. After that, it only asks what applies: follow-on terms carry over read-only, and the end date is calculated from one question.

A standard renewal's price fills in from the contractual increase. A bespoke one points back to the original contract.

Review moved into the plan too. When a change needs approval, the system tags the right team with the reason, and every version sent to the client is kept on the plan.

Outcome

The right template is chosen for them, and a change means updating a field, not rewriting the contract. Reviewers see exactly what changed and why, and every version and decision is kept in one place.

Setting up the plan

Let the renewal's data set up the plan

The renewal didn't end when the client signed. Commercial Ops still had to read the whole signed contract to set up the plan in the system: the dates, the price, the payment terms and every clause, which was always free text. They were translating legal wording back into the values someone had typed in the first place.

Decision

Because the whole renewal is now entered as data, the setup reads from it directly. The start date, plan length, price and payment terms from the form become the plan's configuration, with no one re-typing them.

Clauses were the hard part. The PM worked with Commercial Ops, Legal and Finance to turn the standard clauses into structured clauses with defined values. I designed the clause step as building blocks: users pull a clause in from that library, fill in its values, such as a price protection period, and the product writes the wording. Every value has downstream logic behind it, so the plan's configuration can be filled out automatically. Each clause also shows whether it needs Legal or Finance approval.

A free-text clause is still available for the cases no standard clause covers, but it's the exception, not the default.

Outcome

For standard renewals, Commercial Ops no longer read legal wording to set up a plan. The configuration fills itself in from the values entered during the renewal.

Reflection

One fix for all three teams

I used to think of simplifying as removing things: fewer fields, fewer steps. Renewals didn't allow that. Every rule behind a contract, from plan length to approvals, exists for a commercial or legal reason, and none of them went away in the new design.

What changed was who carries them. Before, people held the rules in their heads and applied them again at every step: in the email thread, in the contract and in the setup. Now the product applies the rules it can apply reliably, like picking the template, working out the end date and filling in the configuration. People only see the ones that need their judgement, like a bespoke price or a clause that needs approval.

So I now look at a complex workflow by asking one question: does the user need to know a rule to get this step right? If they do, either the product should apply that rule for them, or the screen should make the decision clear and say who owns it.