Refolk
PlaybookSales and go-to-market

The Paper-Path Playbook: Verbal Yes to a Dated, Gate-by-Gate Close

Starting from one account at verbal commit, produce a gate-by-gate paper plan with evidence, owners, staged documents, benchmark durations, and a critical-path close date.

21 min readLast reviewed November 6, 2026Read as Markdown

Key takeaways

  • In Vertice's buyer-side stage benchmarks, legal approval takes a median 11.0 days against 7.3 for IT/security, so legal, not security, is usually the long pole on an enterprise deal.
  • Adding Vertice's six stage medians end to end gives 51.1 days, but that double-counts gates that run in parallel; running security alongside legal alone cuts the path to 43.8 days.
  • APQC's 3.0-day median for supplier setup covers only system setup; among companies with at least $1B revenue, 63% report onboarding times of 15 to 28 days and 31% report 29 to 60.
  • In Refolk's index, 17 US profiles carry a third-party or vendor-risk title against 5 in the UK, and 8 of the top 10 US employers of those staff are banks, brokerages, credit unions or fintechs, so TPRM is a sector gate before it is a size gate.
  • A buyer's real deadline is its internal procurement cutoff, not its fiscal year end: at FSU, competitive requests over $150,000 must arrive by 30 April for a 30 June year end.
  • Above $350,000 a US federal deal leaves FAR Part 13 simplified procedures, so pricing near a threshold changes the procurement route, not just the price.

This is the playbook for the stretch between a champion's verbal yes and a signed order: the procurement, security, legal, and vendor-registration gates an enterprise account will make you clear. It is for founders selling their own product, account executives, SDR leads, and partnerships teams who own a forecast. It ends with a gate-by-gate paper plan, rebuilt from public evidence before you ask the champion, with an owner, a staged packet, a benchmark duration, and a close date the buyer's own process can actually deliver.

Two terms first. The paper path is the sequence of administrative gates a deal must clear after the decision to buy: intake, vendor registration, security review, legal, negotiation, approvals, contracting. The critical path is the longest chain of gates that must run one after another; it sets the earliest date the contract can be signed.

The procedure: verbal yes to a dated paper plan

Mapping an enterprise procurement process takes seven steps: name the threshold route, find the real cutoff date, locate the registration artifact, stage the security packet, name each reviewer, build the critical path, then validate with the champion. The research runs to about half a day per account, plus one to three days of packet preparation if your security library already exists.

The order matters. The first five steps use only public evidence, so you arrive at the champion conversation with a draft plan to correct rather than a blank page to fill. Champions know their own approval chain well and the registration, risk, and legal steps that sit in other departments badly.

From verbal commit to a dated paper plan

  1. Confirm the buyer type and threshold route
    Check contract value against US federal, EU, or UK thresholds, or the account's own published threshold. About 30 minutes; done when the route is named as micro-purchase, simplified, or full tender.
  2. Pull the fiscal calendar and internal cutoffs
    Read the EDGAR company page for a public company or the procurement cutoff page for a university or agency. About 30 minutes; done when you have the fiscal year end and any published cutoff date.
  3. Find the registration artifact
    Search for the account's supplier portal guide, supplier code of conduct, and registration questionnaire. About an hour; done when the portal, the registration contact, and the required fields are known.
  4. Identify the questionnaire standard and stage the packet
    With your security lead, pick HECVAT, SIG, or CAIQ and assemble the packet. One to three days with an existing library; done when SOC 2 report, questionnaire, pen test summary, and DPA are ready to send.
  5. Name the reviewers
    Search public profiles for procurement category, third-party risk, and security roles. About an hour; done when every gate has a named person or function.
  6. Build the critical path
    Assign durations from Vertice stage medians and registration benchmarks, and mark each gate parallel or sequential. Done when the plan is dated and signature lands before the internal cutoff.
  7. Validate with the champion
    Send the draft and ask for corrections gate by gate. Done when every gate and date is confirmed or corrected in writing.

Every gate in the finished plan carries the same five fields. If a field is empty, the gate is marked unconfirmed rather than guessed.

One gate, five fields

  1. Evidence
    The public artifact that proves the gate exists
  2. Owner
    A named reviewer, or at minimum a named function
  3. Packet
    The documents sent before the buyer asks
  4. Duration
    A benchmark range for that gate type
  5. Position
    Parallel or sequential on the critical path
A gate belongs in the plan only when public evidence shows it exists, and it earns a date only when it has an owner, a packet, and a benchmark duration.
Paper plan skeleton
ACCOUNT:
CONTRACT VALUE / ROUTE: (micro-purchase / simplified / full tender / private threshold)
FISCAL YEAR END:            INTERNAL CUTOFF:
TARGET SIGNATURE DATE:      SLACK BEFORE CUTOFF (days):

GATE | EVIDENCE | OWNER | PACKET | DAYS (plan / stress) | RUNS | START | END
Intake | | | | 11.0 / | SEQ | |
Vendor registration | portal guide URL | | W-9 or equivalent, bank details, registration questionnaire | 15 / 28 | PAR | |
Security review | trust page or questionnaire standard | | SOC 2, HECVAT/SIG/CAIQ, pen test summary | 7.3 / | PAR | |
Legal approval | | | DPA, MSA redline position | 11.0 / 15+ | SEQ | |
Customer negotiation | | | | 13.1 / | SEQ | |
Executive approval | | | | 5.7 / | SEQ | |
Contracting | | | | 3.0 / | SEQ | |

OPEN QUESTIONS FOR CHAMPION:
1.
2.

One row per gate; leave a field as UNCONFIRMED rather than guessing, and delete gates the evidence does not support.

Which threshold route is this deal on?

For public-sector buyers, contract value against a published threshold decides the procurement route, and the route decides how many gates exist. Check the value against the regime's thresholds before anything else, because a deal just above a line can need a full advertised tender that no champion can shortcut.

RegimeLight route up toFull or advertised route from
US federal$15,000 (no quotes) / $350,000above $350,000
EU central governmentbelow €140,000€140,000
EU sub-centralbelow €216,000€216,000
UK central (inc. VAT)below £135,018£135,018
UK sub-central (inc. VAT)below £207,720£207,720

How to read the US row. The micro-purchase threshold is the value below which an agency may buy without competitive quotations; it is now $15,000. The simplified acquisition threshold (SAT) is the ceiling for FAR Part 13 simplified procedures, which still expect competition; it is now $350,000. Above it, the deal moves to full negotiation. Separately, the FAR 13.500 ceiling for simplified procedures on commercial items rose from $7.5 million to $9 million.

The EU rows apply to supplies and services; works and concessions start at €5,404,000 and utilities at €432,000. Above the threshold, the contract must be advertised EU-wide on TED, the EU's public tender journal. UK works start at £5,193,000, and UK figures include VAT, which catches people quoting net prices.

What a threshold proves: that a route exists and roughly how long it will take. When it lies: the figure in your template is stale. These thresholds are revised for inflation. The current US set took effect on 1 October 2025 under FAC 2025-06; the EU set under Delegated Regulation (EU) 2025/2152 and the UK set under SI 2025/1200 both run from 1 January 2026 to 31 December 2027. Before relying on any threshold, check the effective date on the source you are reading.

Pricing near a threshold changes the route, not just the price. The US SAT now sits 40% higher than its old $250,000 level, so a deal that needed full negotiation under an old template may now qualify for simplified procedures. For private-sector accounts, look for the company's own published procurement policy; some state the value above which competitive bids or additional approvals are required.

Where does the buyer's real deadline sit?

The buyer's real deadline is its internal procurement cutoff, which falls before the fiscal year end, sometimes by months. Forecasting against the fiscal year end alone is how deals slip a full year.

Find the fiscal year end first:

  • Public companies: the SEC EDGAR company page shows a "Fiscal Year End" field. Confirm it against the latest annual filing before you build dates on it.
  • Universities: most publish year-end procurement guidance on the procurement office's site. Search the account name with "fiscal year end procurement deadlines".
  • US federal agencies: the federal fiscal year is fixed, but each agency issues its own internal cutoff memo.

Then find the cutoff. Florida State University, with a 30 June year end, states that requests over $150,000 received after 30 April may not be processed in that fiscal year, depending on the procurement method. The gap exists because a competitive bid has to finish before the year closes. For federal buyers, the internal cutoff memo typically lands days to weeks before year end. Defense appropriations also generally carry a 20 percent rule, which, according to the Congressional Research Service, limits one-year funds obligated in the last two months of the fiscal year to 20 percent.

The year can also start late. A federal fiscal year can open with a shutdown followed by a continuing resolution that holds agencies at prior-year funding levels for months, which delays new starts at the front of the year as well as the back.

For private companies, evidence of a general signing freeze at year end is not established publicly. Do not invent one. Put the question to the champion directly: does procurement or legal stop accepting new contracts before year end, and from what date?

How do you find a company's supplier portal?

Search the company name with the portal platform and the word "supplier": "[company] Coupa supplier portal", "[company] Ariba supplier registration", "[company] supplier code of conduct", and "[company] trust center". Large buyers publish supplier how-to guides as PDFs on their own domains, and those guides name the platform, the registration contact, and the fields you will need.

Two public examples show what you are looking for. Organon's Coupa guide tells suppliers who have not received an invitation to email its vendor-onboarding address and ask for one. Publicis Groupe's Ariba guide routes suppliers through a Supplier Registration step that requires completing a Supplier Registration Questionnaire. Either document gives you the gate, the contact, and the form before anyone at the account sends it.

What each artifact proves:

  • Portal guide: a registration gate exists, which platform runs it, and who triggers the invitation.
  • Supplier code of conduct: the account will ask you to attest to it, usually during registration or contracting.
  • Trust center or vendor-risk page: a security or third-party risk review exists, even if no one at the account holds a risk title.
  • Registration questionnaire: the exact fields and documents you can prepare now.

How often large companies publish these documents is not established publicly. Absence of a portal guide in search does not prove there is no registration gate; it means you add the question to the champion list.

Registration takes longer than the system setup suggests. Use these figures as the duration range for the vendor-registration gate:

BenchmarkFigureWhat it covers
APQC median3.0 daysSupplier setup in the procurement system only (n=3,047)
HICX, firms with $1B+ revenue63% at 15 to 28 days; 31% at 29 to 60Average full onboarding time
Graphite average18.8 daysOnboarding; range under 3 to over 91 days
APQC median40 daysContract establishment, measured separately

For planning, I use 15 days as the plan figure and 28 as the stress case for a large buyer, and I extend to 60 if the account is in a regulated sector or the champion signals a backlog.

Which security questionnaire should you stage?

Stage the questionnaire the buyer's sector uses: HECVAT for higher education, SIG Core for banks, insurers and large enterprises, and CAIQ for cloud buyers. All three are standard formats, so you can complete them before anyone asks.

StandardWho sends itSize
HECVAT 4Higher education331 question IDs in one public filled Full version
SIG CoreBanks, insurers, large enterprisesAbout 627 questions, 21 risk areas
CAIQ v4.1Cloud buyers283 yes/no questions

HECVAT does the most work per hour. EDUCAUSE designs it to be completed once a year and shared with any institution without changes, and HECVAT 4 rolls the old Full, Lite, and On-Prem versions into one file. Check the EDUCAUSE toolkit page for the current release number before you send; at the time of writing it was 4.1.6. If you want to see what a finished one looks like, 37signals publishes its filled HECVAT 4 Full, with 331 vendor-facing question IDs across eight sections.

SIG Core is the heavier lift and comes from Shared Assessments; CAIQ comes from the Cloud Security Alliance. If you do not know which standard an account uses, its trust center or a vendor-risk page usually names it, and its sector is a strong hint.

The full packet has four parts:

  1. Assurance report. A SOC 2 report. A Type I report, which tests control design at a point in time, is acceptable early but increasingly insufficient for large deals; plan for a Type II, which tests controls over a period, if you are selling into enterprise.
  2. Sector questionnaire. HECVAT, SIG Core, or CAIQ, current and complete.
  3. Pen test summary. The executive summary of your most recent penetration test.
  4. Data processing agreement (DPA). Your standard DPA, ready for legal to redline.

How often enterprise buyers specifically require ISO 27001 is not established in the sources behind this guide. If an account's trust page or supplier code mentions it, add it to the packet; otherwise ask.

Who runs each gate?

Each gate has a function that runs it: a procurement or category manager for intake and registration, a third-party risk (TPRM) team for vendor-risk review, security for the questionnaire, and legal for the contract. TPRM, or third-party risk management, is the function that assesses the risk a supplier brings into the company. Naming a person for each is better; naming the function is the minimum.

In Refolk's index of professional profiles, the most common titles for these gates are "Third Party Risk", "Vendor Risk", "IT Procurement Manager", "IT Category Manager" and "Software Category Manager".

Segment in Refolk's indexProfilesRelative size
TPRM titles, US17baseline
TPRM titles, UK5US is 3.4x UK
IT procurement or category titles, US1639.6x US TPRM
3.4x
US third-party risk titles relative to UK in Refolk's index
17 US profiles against 5 UK carry a third-party, vendor, or supplier-risk title; matching is on exact titles, so both are lower bounds.

The counts are small and the matching is on exact titles, so read them as lower bounds, not market size. What they show reliably is the shape. Procurement and category titles are far more common than risk titles, and in a sample of 25 US procurement-side profiles, "IT Procurement Manager" was the most common title (12 of 25). The U.S. Department of Veterans Affairs ties with Tenneco as the top employer of US IT procurement and category titles in the index, two each.

TPRM looks like a sector gate before a size gate. Among the top 10 US employers of TPRM-titled staff in Refolk's index, 8 are banks, brokerages, credit unions or fintechs: Edward Jones, Citi, Charles Schwab, Block, Payoneer, Western Alliance Bank, Connexus Credit Union, and Farm Credit Financial Partners. All 5 UK employers (LV=, Deutsche Bank, CFC, LSEG, Vanguard) are in financial services or insurance. That fits SIG Core's use at banks and insurers. The company size at which a dedicated TPRM function appears is not established publicly, so do not assume a mid-size bank has none.

What a title proves: someone at the account owns that review. When it lies: the title is absent but the work still happens under a security or procurement title, or the person has moved on. Finding these people by hand means searching title variants company by company. Refolk lets you ask for the role in plain English across public profiles and returns named people with their current employer, which is the hour in step five compressed.

How long does each gate take?

Use Vertice's buyer-side stage medians as the base duration for each gate: customer negotiation 13.1 days, legal approval 11.0, intake 11.0, IT/security approval 7.3, executive approval 5.7, and contracting 3.0. They come from thousands of transactions measured on the buyer's side, which makes them the most defensible numbers available.

StageMedian daysShare of sequential total
Customer negotiation13.126%
Legal approval11.022%
Intake11.022%
IT/Security approval7.314%
Executive approval5.711%
Contracting3.06%

Run in strict sequence, the six stages sum to 51.1 days.

47%
Share of a sequential buyer-side path taken by legal approval and negotiation
Derived from Vertice's stage medians: 24.1 of 51.1 days.

Legal, not security, is now the long pole. Legal approval runs 11.0 days against 7.3 for IT/security, and Vertice reports legal has seen the steepest rise of any stage, up almost 15% across its measured period. The likely reason is that redlining is still manual, while security reviews are increasingly answered by reusable artifacts. SpotDraft's data points the same way: 56% of legal teams cannot execute a standard contract within a week, and one in three take 15 days or more. I use 11 days as the plan figure for legal and 15 as the stress case.

The champion's yes starts the paper path. Legal, not security, decides how long it runs.

Security-review figures that run longer, such as 23 days or two to six weeks, come from vendors selling a fix and have no published method. Treat them as a labelled stress case at most, not a benchmark.

Where the evidence is thin, say so in the plan:

  • By company size or sector: splits of these durations by headcount band or by sector (financial services, healthcare, higher education) are not established in any source with a stated method.
  • Healthcare: one secondary claim puts healthcare contract cycle times at six to eight weeks; it is unverified, so use it only as a question for the champion.

Parallel or sequential

The medians are measured one stage after another, but gates do not have to run that way. Running security review alongside legal removes 7.3 days from a 51.1-day sequential path, leaving 43.8. Vendor registration, at 15 to 28 days, usually belongs alongside both if the invitation is sent early. One sales-cycle guide from Gangly advises bringing legal and procurement in during business-case development, not after, precisely to remove sequential reviews. Whether a given account runs them in parallel is a fact about that account, so it is the first thing you ask the champion to confirm.

Where to spend effort before verbal commit

Long gateShort gate
Legal approval and negotiation
Send the DPA and redline position on day one; this is the critical path
Vendor registration and security review
Stage the packet and registration fields before anyone asks
Executive approval
Book the signer's slot once legal has a finish date
System setup and contracting
Pre-fill fields so they close in days
Hard to pre-stageEasy to pre-stage
Long gates you can pre-stage are where preparation moves the close date most; long gates you cannot pre-stage need to start first.

How the paper plan goes wrong

Most failures come from a real number used for the wrong thing: a setup median quoted as onboarding time, a year end used as a deadline, medians added as if every gate waits on the last. Each failure below has a check you can run in minutes.

  1. Quoting APQC's 3-day median as total onboarding time. It covers system setup only and excludes many compliance, contracting, and readiness steps. How it shows up: a plan with registration closing in the first week. Check: 94% of large firms in the HICX survey take 15 to 60 days.
  2. Treating the fiscal year end as the deadline. The internal cutoff comes earlier: two months earlier for large competitive requests at FSU, and days to weeks earlier for federal agency memos. How it shows up: a June-end signature date for a university that stopped accepting large requests in April. Check: search "[account] fiscal year end procurement deadlines".
  3. Adding Vertice medians end to end. This double-counts gates that run in parallel and produces a 51.1-day plan that looks careful and is too long. The opposite error, assuming everything runs in parallel, is worse. Check: ask the champion whether security and legal run at the same time.
  4. Assuming a stale threshold. Older templates still say a $250,000 SAT or €143,000 for EU central government. How it shows up: a route that requires a tender the buyer no longer needs, or the reverse. Check: the effective dates, 1 October 2025 for the US and 1 January 2026 for the EU and UK.
  5. Counting a visible portal as an open door. Coupa needs a customer invitation or connection request, and some invitations must be actioned within 48 hours. How it shows up: registration stalled for weeks because the invite went to a shared inbox and expired. Check: name the internal person who sends the invite and the person on your side who receives it.
  6. Concluding a firm has no TPRM gate because nobody holds a TPRM title. Index counts are small (17 US profiles), and the work often sits under security or procurement titles. How it shows up: a SIG Core questionnaire arriving in week three of a plan that had no risk gate. Check: the account's trust center or vendor-risk page.
  7. Citing vendor-funded security-review figures as neutral benchmarks. The 23-day and two-to-six-week figures have no published method. How it shows up: a forecast padded or defended with numbers a buyer's procurement team will not recognise. Check: use the Vertice 7.3-day median as the plan figure.

A quieter failure sits under all seven: skipping step seven. A plan built entirely from public evidence is a strong draft, but it is still a draft. A gate the champion has not confirmed is a hypothesis, and a forecast built on hypotheses should say so.

Before you put the date in the forecast

A close date is defensible when every gate in the plan has evidence, an owner, a staged packet, and a benchmark duration, and the champion has confirmed the sequencing in writing. Run the checklist below, then send the validation note.

Paper plan sign-off

  • The procurement route is named and the threshold was checked against its current effective date.
  • The latest signature date is the internal cutoff, or is marked unconfirmed if no cutoff is published.
  • The registration portal, the person who sends the invitation, and the required fields are recorded.
  • The sector questionnaire, SOC 2 report, pen test summary, and DPA are ready to send today.
  • Every gate has a named reviewer or, at minimum, a named function.
  • Each duration cites its benchmark, and vendor-funded figures appear only as labelled stress cases.
  • Every gate is marked parallel or sequential, and the parallel assumptions are on the champion question list.
  • The signature date leaves slack before the cutoff equal to at least the legal stress case.
  • The champion has confirmed or corrected each gate in writing.
Champion validation note
Subject: Paper plan for [product] at [account] - can you sanity-check?

Hi [name],

Thanks for the yes. To avoid surprises between now and signature, I've drafted the steps I expect on your side. Could you correct anything that's wrong?

1. Registration: it looks like you onboard suppliers through [portal]. Who sends the invitation, and should it go to [our contact email]?
2. Security: I've prepared [HECVAT / SIG Core / CAIQ], our SOC 2 report, a pen test summary, and our DPA. Who should receive them, and can that review run alongside legal?
3. Legal: is there anyone in legal we should send our DPA and standard terms to now, before redlines start?
4. Approvals: who signs at this value, and is there a date after which procurement or legal stops processing new contracts this fiscal year?

Based on the above, I have signature landing on [date]. If any step runs in sequence rather than in parallel, that date moves, so I'd rather know now.

Thanks,
[name]

Send after verbal commit with the draft plan attached; replace bracketed fields and keep the questions specific.

Keeping the plan current is mostly a matter of re-checking the things that change on their own schedule:

  • Thresholds: revised for inflation; re-check the effective date on any threshold source before each new public-sector deal.
  • Questionnaire versions: HECVAT is designed for annual refresh; confirm your file matches the current EDUCAUSE release.
  • Duration benchmarks: Vertice publishes stage medians on a recurring basis; when legal or security moves materially, update the plan figures in your template.
  • Reviewers: people change jobs mid-deal. If a named reviewer stops replying, re-run the role search in Refolk for the same account and title before assuming the gate has gone quiet.

The last check is the plainest one. If the critical path, with the parallel gates the champion confirmed, cannot land before the internal cutoff, do not hold the date. Move it, tell your manager why, and show them the plan that proves it.

Questions practitioners ask

How long does enterprise vendor onboarding take?

Plan on weeks, not days. In a HICX survey of companies with at least $1B in revenue, 63% reported average onboarding times of 15 to 28 days and 31% reported 29 to 60 days. Graphite reports an average of 18.8 days, ranging from under three days to more than 91. APQC's 3.0-day median is real but covers only system setup, so never quote it as the full timeline.

Why does security review keep delaying my close date?

Usually because the packet is assembled only after the buyer asks for it. Vertice's buyer-side benchmark puts IT/security approval at a median 7.3 days, shorter than legal at 11.0, because reusable artifacts can answer most of it. Stage the SOC 2 report, the sector questionnaire, a pen test summary, and a DPA before verbal commit, and security stops being the gate that moves your date.

How do I find a company's supplier portal?

Search the company name with the portal platform and the word supplier: for example, the company name plus 'Coupa supplier portal' or 'Ariba supplier registration'. Large buyers often host supplier how-to guides as PDFs on their own domain. Also search for the company's supplier code of conduct and trust center. A visible portal does not mean you can register yourself; Coupa needs a customer invitation.

Should I just ask the champion what the procurement process is?

Ask, but only after you have rebuilt the process from public evidence. Champions often know their own team's approvals and not the vendor-registration, third-party risk, or legal steps that sit elsewhere. Showing up with a draft plan turns the conversation into corrections on a specific document, which is faster and surfaces gates the champion would not have thought to mention.

Do private companies freeze signing at fiscal year end?

There is no public evidence establishing a general private-sector signing freeze. Universities and government agencies do publish internal cutoffs, often weeks or months before year end. For a private account, find the fiscal year end on its EDGAR company page or annual filing, then ask the champion directly whether procurement or legal stops processing new contracts before it.

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