Refolk
FrameworkSales and go-to-market

The Incumbent Renewal-Window Read: Dated, Bracketed, Proxy, or Unknown

Grade one incumbent account's renewal evidence on four dimensions, state a date range, and turn it into an outreach date, a dated CRM task, or no timing claim.

21 min readLast reviewed November 14, 2026Read as Markdown

Key takeaways

  • With 87 to 90% of SaaS contracts auto-renewing, the buyer's real decision point is the notice deadline minus their review lead time, not the contract end date.
  • On a 90-day notice period, a buyer starting review 120 days before the notice deadline begins at T-210, so the common advice to reach out 90 days before renewal lands exactly on the notice deadline.
  • Only procurement registers and filed contract exhibits state a contract end date directly; launch announcements and technographic first-seen dates are proxies, and they always run late.
  • A register end date can hold the maximum date including extensions, so a source that looks Dated often has to be bracketed between the base end and the extended end.
  • In Refolk's index there are 2,387 US and 506 UK profiles with the four renewal-owner titles (Software Asset Manager, SaaS Procurement Manager, IT Procurement Manager, Vendor Manager), a thin layer that handles many renewals each.
  • Never state an inferred renewal date to a prospect; name the source type you saw and let them supply the date.

This guide is for the moment you know an account runs a competitor's product and have to decide how far to trust your guess at when that contract comes up. It's written for founders selling their own product, account executives, SDR leads and partnerships teams who time competitive displacement outreach. It gives you four scoring dimensions and four grades (Dated, Bracketed, Proxy, Unknown), each with a stated date range, plus the specific action each grade earns.

What does the renewal-window read decide?

The renewal-window read decides whether your estimate of an incumbent's contract end date is solid enough to time outreach on. It then turns that judgement into one of three actions: an outreach date, a dated CRM task, or no timing claim at all.

Most timing advice skips the grading step. Ranking pages tell reps to reach out "90 to 180 days before the end date" or to "begin outreach 90 days before the estimated renewal date". Some treat the anniversary of a technographic first-seen date as the renewal date. None of them says how wrong that date might be, and none accounts for the notice clause that moves the real decision months earlier.

These terms appear throughout:

  • Term end (T): the date the current contract period finishes.
  • Notice period: how many days before T the buyer must give written notice to stop an auto-renewal.
  • Notice deadline: T minus the notice period. After this date the contract renews whether the buyer wanted it or not.
  • Decision point: the date the buyer's renewal review starts. Your outreach needs to land here.
  • Incumbent: the competitor whose product the account currently runs.

Auto-renewal is the default, which is why the notice deadline matters more than T. Common Paper's benchmark of its own standard agreements finds that about 90% auto-renew, and its latest edition puts the figure at 87%. Vertice puts it at 89% of SaaS contracts. On the same Common Paper benchmark, 70% of agreements use an annual term and 19% run month-to-month.

The read ends in one of four grades:

GradeWhat it meansRange you state
DatedPublished or filed end date, known term, known startOne end date
BracketedHard source, but two plausible end datesEarliest and latest end
ProxyOnly an indirect anchor, such as a launch date"On or before" a month
UnknownNo usable anchor, or anchors conflictNo range

Which public sources carry a competitor contract end date?

Only two kinds of public source state a contract end date directly. Procurement registers publish structured start and end fields for public-sector buyers, and contract exhibits filed with securities regulators carry the term clause as text. Everything else, including launch press releases, case studies and technographic detection dates, is a proxy for when the contract started, not a record of when it ends.

SourceEnd-date fieldKnown flaw
Contracts Finder / Find a TenderContract end date, plus extension endSome date fields unrealistic; duplicate OCIDs
TEDBT-537 Duration End DateCoverage share unpublished
USAspendingCurrent End Date vs Potential End DateTwo end dates
EDGAR Exhibit 10Term clause textRedactions marked [***]
Technographic first-seenNone, only a detection dateLag unpublished; drop-outs from recrawls

Procurement registers

What they prove: the buyer, the supplier and the contracted period, as published by the buyer. Contracts Finder labels the fields "Contract start date" and "Contract end date". Under the UK Procurement Act 2023, a contract details notice is due within 30 days of the contract being entered into. It must state the supply period and the end date of any options to extend or renew. TED carries Duration Start Date (BT-536) and Duration End Date (BT-537). US federal award data uses Period of Performance Start Date and Estimated Ultimate Completion Date, and USAspending separates a Current End Date from a Potential End Date.

How they lie: many registers publish in the Open Contracting Data Standard (OCDS), a shared schema whose end-date field "can be used to express the maximum available date for extension or renewal". A single end date may therefore be the outer limit, not the base term. Open Contracting's review of Contracts Finder data notes that "a minority of date fields are unrealistic", and that includes the contract period start and end fields. Its review of Find a Tender notes that tenders and awards from the same process sometimes appear under different OCIDs (open contracting IDs, the identifier meant to tie one procurement together). Nobody publishes the share of notices that fill in the end-date field at all. One third-party scraper claims Contracts Finder states every end date, but that claim is unverified, so read the notice itself.

Filed contract exhibits

What they prove: the term length, the renewal mechanics and often the notice period, in the contract's own words. Since March 2019, Item 601(b)(10) of Regulation S-K has let a company file redacted material contracts without applying for confidential treatment, as long as the redacted text is not material and would cause competitive harm. Redactions are marked "[***]" in the agreement. SEC full-text search covers every EDGAR filing submitted electronically since 2001, exhibits included. Its JSON endpoint is free and needs no API key, but you must send a User-Agent header that names you.

How they lie: pricing is the usual target for redaction. SEC staff have pushed back on keeping terms confidential beyond "the minimum term of an agreement", but nobody has published which clauses usually survive. A redacted exhibit, or one with omitted schedules, can read as complete when it isn't. An exhibit also exists only when one party is a public company and judged the contract material, so most incumbent relationships will never show up in one.

Proxy anchors

Launch press releases, case studies, review-site dates and technographic first-seen dates all suggest roughly when a product went live. No public source measures how far any of them fall from contract signature, so every rule of thumb about that gap is unverified. Technographic crawlers document first-detected and last-detected fields plus a confidence score from 0 to 1. None of them publishes how long a tool runs before it is first detected, or what share of drop-outs have nothing to do with a vendor switch. A tool that stops being detected may reflect a script change, a recrawl gap or a signature change.

One thing about proxies is reliable: signature comes before go-live, and go-live comes before first detection or a launch announcement. Every proxy anchor is late, so the true start, and the true renewal, is earlier than the proxy suggests.

How do you score the four dimensions?

Score each dimension 0, 1 or 2 using the rubric below, then apply the grade gates. The gates matter more than the total, because one weak dimension can make a precise-looking date unreliable. This rubric is my working model, not a published industry standard. Once the evidence is logged, scoring takes about ten minutes.

DimensionScores 2Scores 1Scores 0
Source typeRegister end date or filed exhibitDated launch release or case studyFirst-seen date only, or nothing
Term-length certaintyTerm stated in register or clauseVendor 10-K describes typical termAssumed annual
Start-date anchorContract start or effective dateLaunch announcement dateTechnographic first-seen
Notice-period knowledgeFiled clause text for this contractVendor's published standard paperAssumed default

What each dimension proves, and how it misleads

  • Source type shows whether anyone with knowledge of the contract published a date. It misleads when a register's single end date is really the extension maximum.
  • Term-length certainty tells you how many cycles separate the start from now. About 70% of Common Paper contracts are annual, but ServiceNow reported a 98% renewal rate on subscriptions that typically run three years. A secondary source reports that multi-year contracts grew from 23% to 38% of SaaS agreements in Zylo's data, though I could not verify the original. Annual is the base rate on standard paper, not a safe assumption for an enterprise platform.
  • Start-date anchor fixes the calendar position of the cycle. A launch date misleads because it always lands after signature.
  • Notice-period knowledge decides how far the decision point sits before T, and the sources disagree. Common Paper calls 30 days the standard, appearing in about 70% of its agreements, and 84% of its auto-renewing contracts require 30 days' notice. ContractKen, without citing its basis, says 60 days is most common at about 40% of B2B technology contracts, with 30 and 90 days at about 25% each. Even single vendors conflict: one page lists Salesforce at 90 days of notice, and another says Salesforce's standard agreement requires 30. Only clause text from this contract scores 2.

Grade gates

  • Dated: source type 2, term 2, start 2, and no separate extension or potential end date left unresolved.
  • Bracketed: source type 2, but term or start scores 1, or the record shows both a base end and an extension or potential end.
  • Proxy: source type 1 or 0, with at least one dated anchor that nothing contradicts. A technographic first-seen date with no second source is Proxy at best.
  • Unknown: no dated anchor, anchors that disagree by more than a full term, or a detection that dropped out and came back.

Term certainty against start-anchor precision

Term length statedTerm length assumed
Known cycle, soft start
Proxy. Set a dated task to find a register or filing start date.
Dated
Set the outreach date from the notice deadline and the review lead.
Proxy or Unknown
Make no timing claim until a second source lands.
Bracketed
Set a task at the earliest plausible decision point.
Start anchor is a proxyStart anchor is published
A precise start date is worth little without a known term length, and a known term is worth little without a real start date.

Why does the notice deadline, not the end date, set outreach timing?

Because roughly 87 to 90% of contracts auto-renew, the buyer's last free exit is the notice deadline, and their review starts well before that. Count back from T by the notice period, then by the buyer's review lead time, and the decision point lands far earlier than "90 days before renewal".

Buyer-side guidance is explicit about the lead time. Zylo advises starting the renewal review 120 days out, with checkpoints at 90, 60 and 30 days, and 180 days out for large or strategic deals. Its schedule has buyers benchmarking pricing and comparing alternate packaging at 60 days and entering negotiations at 45. Vertice, which describes its dataset as drawn from over 250,000 human-negotiated contracts and 32,000+ vendors, reports that buyers who start more than 90 days before the deadline save an average of 49% more than buyers who wait until under 30 days. The disciplined buyers start early, and they're the ones worth displacing.

NoticeNotice deadlineBuyer review startsRanking-page timing
30 daysT-30T-150T-90
60 daysT-60T-180T-90
90 daysT-90T-210T-90

I count Zylo's 120 days back from the notice deadline rather than from T, because the notice deadline is the date a buyer who wants out has to act by. That's my derivation, not Zylo's wording. On a 30-day notice period, "90 days before renewal" arrives 60 days into the buyer's review, around the time they're benchmarking pricing. That's late but workable, and it matches the standard-paper default. On a 90-day notice period it lands exactly on the deadline, after the decision has been made.

T-210
When review starts on a 90-day notice contract
That's 120 days before a notice deadline that already sits 90 days before term end, more than twice as early as the common T-90 advice.

From term end to the date in your CRM

  1. Term end (T)
    Taken from a register, a filed exhibit, or a graded proxy.
  2. Notice deadline
    T minus the notice period; if the notice period is unknown, use 90 days.
  3. Review start
    Notice deadline minus 120 days, or 180 for strategic deals.
  4. Decision point
    Store it as the primary CRM date; T becomes a secondary field.
The primary CRM date is the decision point, reached by subtracting the notice period and then the buyer's review lead from the term end.

When notice-period knowledge scores below 2, compute the decision point for 30, 60 and 90 days and set the task at the earliest result. Arriving early costs one extra follow-up. Arriving late costs the whole cycle.

How does each grade turn into an outreach date, a task, or no claim?

Each grade earns exactly one action. Dated gets an outreach date, Bracketed and Proxy get dated CRM tasks, and Unknown gets an explicit decision to make no timing claim. The point is that you can defend the call in pipeline review by naming the source behind it.

GradeActionWhen
DatedOutreach date in CRMNotice deadline minus 120 days
BracketedDated CRM taskReview start for the earlier end date
ProxyTask to find a second sourceNow; outreach makes no timing claim
UnknownNo timing claimWork the account on other triggers
  • Dated. Put the outreach date at the review start. If the buyer is strategic, use the 180-day lead instead of 120.
  • Bracketed. Set the task for the review start tied to the earlier end date, then re-check the register when the task fires. If the buyer has exercised the extension, roll forward to the later bracket. Don't average the two dates, because the midpoint is a date no contract actually holds.
  • Proxy. Because proxies run late, read the proxy anniversary as "on or before" that month. Set a task to look for a register notice, a filing or a launch announcement that confirms the start. Outreach on other grounds can go ahead, but it carries no timing claim. One ranking page's advice is sound here: prioritise signals from the last 90 days, and verify anything older than six months before acting on it.
  • Unknown. Record the decision so nobody re-derives a date from the same weak evidence next quarter. Work the account on triggers that don't depend on timing.

Who owns the renewal on the buy side?

The renewal owner sits in a thin layer of the org chart. In Refolk's index of professional profiles, four titles cover the role: Software Asset Manager, SaaS Procurement Manager, IT Procurement Manager and Vendor Manager.

Segment (Refolk's index)Profiles
US, 4 renewal-owner titles2,387
UK, 4 renewal-owner titles506
US "software procurement", Director+152
US "software procurement", Senior/Strategic89
2,387
US profiles holding the four renewal-owner titles
In Refolk's index, against 506 in the UK, a 4.7x ratio; Zylo's average organisation handles 211 SaaS renewals a year, about one per business day.

That combination is why outreach timed to the review start beats outreach timed to the end date. One owner is juggling roughly a renewal a day, and they put attention on the ones that are opening, not the ones about to close. The keyword rows above need care. The Director+ figure of 152 is inflated: in a 25-profile sample, most of those titles belonged to founders, CEOs and VPs of Sales at companies selling procurement software, and only one was a sourcing role. The title and company lists come from 25-profile samples, not the full counts.

Finding the right person at a public-sector buyer usually means two searches: the register for the contract, then a people tool for the buyer's staff. Refolk runs both as one plain-English request, so the contract and the person come back together.

Step-by-step: grading one incumbent account

Grading one account takes roughly two hours of SDR and AE time across seven steps, most of it in the source searches. The SDR gathers the evidence, the AE scores and grades, and the SDR lead signs off on the action.

The renewal-window read, one account

  1. Confirm the incumbent and the buying entity
    SDR, about 15 minutes. Write down the incumbent product and the legal buyer name; for public bodies, use the exact name the procuring authority uses on its notices.
  2. Look for a published end date
    SDR, 20 to 40 minutes. Search Contracts Finder, Find a Tender, TED and USAspending, and record the start date, the end date and any extension or potential end date, or a confirmed none.
  3. Search filings if either party is public
    AE, about 30 minutes. Run EDGAR full-text search on the vendor name plus "initial term" or "renewal term", and note every [***] redaction and omitted schedule.
  4. Collect proxy anchors
    SDR, about 20 minutes. Log the launch press release, any case study and the technographic first-seen date, each with its source type, and note any detection drop-out.
  5. Score the four dimensions
    AE, about 10 minutes. Score source type, term-length certainty, start-date anchor and notice-period knowledge from 0 to 2, citing the evidence for each.
  6. Subtract notice and review lead time
    AE, about 5 minutes. From the estimated end date, subtract the notice period, then the 120-day review lead, and store the decision point as the primary CRM date.
  7. Assign a grade and act
    AE, with SDR lead sign-off. Apply the grade gates, state the range, and set the outreach date, the dated task, or a written no-timing-claim decision.

Store the result in the same shape every time, so pipeline review compares like with like.

Renewal-window record (paste into the CRM account note)
Account:
Incumbent product:
Legal buyer name (as on notices):
Sources found (type :: date :: link):
Source type score (0-2):
Term-length certainty score (0-2):
Start-date anchor score (0-2):
Notice-period knowledge score (0-2):
Extension or potential end date present: yes / no
Grade: Dated / Bracketed / Proxy / Unknown
Term end (T) or range stated:
Notice period used, and its basis:
Decision point (primary CRM date):
Action: outreach date / dated task / no timing claim
Re-check date:
Signed off by:

Fill every line; write "none found" rather than leaving a line blank, so a reviewer can tell a gap from a skipped step.

How does the renewal-window read go wrong?

Seven failures account for most bad timing calls. Most of them come from treating a weaker source as a stronger one, or from assuming a standard term or notice period that this contract doesn't have. Each one below names the false positive and the check that catches it.

  1. Treating the technographic anniversary as the renewal date. The false positive is a first-seen date months after signature, or a re-detection after a gap. Check: compare it against a launch press release. Without a second source, the account grades Proxy at best.
  2. Reading a register end date as the final date. The OCDS end field may hold the maximum date including extensions, and USAspending carries both a current and a potential end. Check: look for separate extension or "potential end" dates before grading Dated.
  3. Assuming a standard notice period. Sources conflict on 30 days versus 60, and the Salesforce examples conflict with each other. Check: count notice as known only when you hold the filed clause text for this contract.
  4. Reading a multi-year term as annual. About 70% of Common Paper contracts are annual, but ServiceNow terms typically run three years. If you assume annual on a three-year platform, you'll time two outreaches into years when nothing is renewing. Check: read what the vendor says about typical terms in its 10-K.
  5. Reading a redacted exhibit as complete. A clean-looking term section can sit next to a redacted schedule that changes it. Check: search for [***] markers and for schedules that are referenced but omitted.
  6. Pulling the wrong side with a keyword search. In Refolk's index, Director+ results for "software procurement" were mostly people selling procurement tools. Check: filter on titles, not keywords. In Refolk, asking for the four renewal-owner titles by name returns buyers instead of vendors.
  7. Stating an inferred date to the prospect as fact. It invites correction and burns credibility, and with a late proxy you'll usually be wrong in the direction that makes you look unprepared. Check: outreach copy names the source type and never gives a date.
A date you can't source in pipeline review is just a guess with a calendar invite attached.

Two quieter failures deserve a mention. Duplicate OCIDs on Find a Tender can make one procurement look like two contracts with different dates, so match on buyer, supplier and description before treating them as a conflict. And an unrealistic date field, such as an end before the start, is a data error, not a signal. Grade from the other fields and note it.

How do you write the outreach and keep the read current?

Write outreach that names the type of source you saw and asks about the review, never the date. Then re-run the read on a schedule, because registers get amended, detections drop out, and extensions get exercised.

The prospect knows their real renewal date. Your job is to show you did the work and to arrive while the review is open, not to prove you know their calendar.

Timing-aware outreach that never states a date
Subject: {incumbent} review at {buyer}

Hi {first name},

[Dated or Bracketed] I saw {buyer}'s contract notice for {service} on the public register, and teams in that position usually start reviewing well ahead of the notice deadline rather than at the end date.
[Filed exhibit] {incumbent}'s public filings describe how their agreements renew, which made me think a review might be on your calendar.
[Proxy] Your launch announcement for {product area} caught my eye.
[Unknown] I work with {role} teams who run {incumbent} alongside or instead of {your product}.

If a review is coming up, I can share how {comparable buyer type} compared options and what they asked for in their notice. Worth 20 minutes?

{your name}

Pick the line that matches the grade; Proxy and Unknown accounts use the last line only, with no reference to timing at all.

Keeping the read current

  • Dated: re-check the register at the task date. Contract details can be amended, and an extension notice changes T.
  • Bracketed: re-check at the earlier review start, then resolve to one bracket or roll forward.
  • Proxy: re-search for a second source each time the anchor passes the six-month mark, in line with the ranking-page advice to verify anything older than six months.
  • Unknown: look again whenever a new trigger appears, such as a new register notice, a filing, or a change in detection.
  • Benchmarks: the auto-renew and notice-period figures in this guide come from benchmark reports that are re-issued over time. Re-read the latest Common Paper benchmark before relying on its notice-period default, and note which edition you used.

Before you set the date or the task

  • The legal buyer name in the CRM matches the name on the register notice or filing.
  • Every anchor is logged with its source type, its date and a link.
  • Any extension or potential end date has been checked for and recorded.
  • Notice-period knowledge scores 2 only because clause text for this contract is in hand.
  • Term length was checked against the vendor's 10-K before annual was assumed.
  • Any filed exhibit was checked for [***] markers and omitted schedules.
  • The primary CRM date is the decision point, not the term end.
  • The contact was found by renewal-owner title, not by a procurement keyword.
  • The outreach copy names a source type and contains no date.
  • A re-check date is set and the SDR lead has signed off on the grade.

Questions practitioners ask

How do I find when a competitor's contract with a prospect renews?

Check public procurement registers first if the buyer is public sector, because they publish structured start and end dates. If either the buyer or the vendor is a public company, search SEC EDGAR full text for the vendor name plus "initial term" or "renewal term". Everything else, such as launch press releases and technographic first-seen dates, is a proxy for the start date and runs late, so grade it lower and never treat it as the renewal date.

Is a technographic first-seen date the same as the contract start date?

No. A first-seen date records when a crawler first noticed the tool, which comes after go-live, which comes after signature. No crawler publishes how long that lag is. A tool can also be re-detected after a recrawl gap or a script change, producing a fresh first-seen date with no new contract behind it. Treat it as a late proxy, grade the account Proxy at best, and look for a second source.

How far before contract renewal should I reach out?

Count back from the notice deadline, not the end date. Subtract the notice period from the term end, then subtract about 120 days, which is when buyer-side guidance says renewal reviews start. That puts the decision point at T-150 for a 30-day notice period and T-210 for a 90-day one. Advice to reach out 90 days before renewal only roughly fits 30-day notice contracts.

What if I can't find the notice period in the contract?

Score notice-period knowledge below 2 and compute the decision point under each common notice length: 30, 60 and 90 days. Set the CRM task at the earliest result, the 90-day case, because arriving early costs you one extra follow-up while arriving late costs you the whole renewal cycle. Sources disagree on which notice length is most common, so don't assume one.

Should I tell the prospect when I think their contract renews?

No. An inferred date stated as fact invites correction and burns credibility, especially when it comes from a proxy that runs late. Name the source type instead, such as the public contract notice or the launch announcement, and ask whether a review is on the calendar. The prospect knows their real date and will often tell you once you've shown you did the work.

Can private-company software contracts show up in public records?

Sometimes, but only through the other party. If the vendor is a public company and judged the contract material, it may be filed as an exhibit on EDGAR, often with pricing redacted and marked [***]. If the buyer is a public body, the award may appear on a procurement register. Private-to-private contracts usually leave no record, so most of those accounts will grade Proxy or Unknown.

Try it on the search you came here for

Stop building boolean strings. Just describe the person.

Type one sentence. I plan the search, read GitHub, public LinkedIn and Crunchbase records, and the open web as it is right now, and hand back a ranked list with the reason next to every name.

  1. 01Describe them

    One plain sentence. Role, city, stack, stage, whatever matters to you.

  2. 02I read the web live

    GitHub, public LinkedIn and Crunchbase records, the open web. Not a database that went stale last quarter.

  3. 03You read the shortlist

    Ranked, with the reasoning under every name. Open a profile, ask a follow-up, narrow it down.

  • No boolean, no filters, no seat to buy. One box.
  • Read at search time, so a profile updated yesterday counts today.
  • Every step visible as it runs, every name with its reason.

500 free credits on sign-up. No card, no demo call. See real searches.

Read next