Derived Success Plan · Sturdy on Yellowsail

Secbase

Renewal defense · 5 standing criteria · status computed from 93 communications · Full read
ARR
$140,000Secbase - Renewal - 2026
Renewal
Apr 1, 2026138 days past · opp still open
Stage
Value Proposition50% · Joel Passen
Last contact
Jul 11, 2026incoming, 37 days ago
Generated
Aug 17, 2026read time, not stored
Serif type marks the declared layer — the only text a human typed. It is the standing criteria in the project configuration and changes rarely.
Sans type marks the derived layer — computed from communications at read time. Nothing here was self-reported.

The declared layer

Standing criteria · project config

Five renewal-defense criteria, written once by a human and applied to every account. Everything below this section is computed against them. This is the complete human input surface — no status field, no percent complete, nothing anyone can color green.

Account
SecbaseAccount.Id · 0018b000020fSK1AAM
Plan type
Renewal defensestanding configuration, not per-account
Criterion C1
Economic sponsor is present — a contact with budget authority (VP or above, or a named approver) authored a message within the last 45 days.match terms: VP, Chief, sponsor, budget, approve, sign off, procurement, leadership
Criterion C2
We are keeping our promises — no vendor commitment open past 14 days, and no customer-last thread unanswered past 10.match terms: I'll send, we'll get, following up, any update, still waiting, as promised, apologies
Criterion C3
Value stated in the customer's own words — a customer-authored message in the last 90 days describes an outcome for their own users or business, unprompted.match terms: our team, our users, saved, reduced, faster, we're seeing, rolled out, went live
Criterion C4
More than one person carries the relationship — at least three distinct customer contacts authored a message in the last 60 days.match terms: looping in, introduce, adding, my colleague, taking over, handing off
Criterion C5
A next thing is live — a named next use case, team, data source, or phase discussed in the last 60 days.match terms: next phase, expand, additional, other teams, new use case, roadmap, pilot, scope

What's actually true

Derived

Secbase renewed — and then everything stopped. After a bruising four-month renewal fight that opened with Holly Langerfield's declaration that the proposed increase left Secbase "forced to evaluate our options" PRICING-CONCERNS·MAY 26 and escalated through named competitor conversations PRICING-CONCERNS·JUN 1, YellowSail conceded a flat Year-1 rate with a 6%-capped Year 2, two included modules, and a formal P1 support SLA PRICING-CONCERNS·JUN 6. Emily Thompson confirmed the multi-year agreement fully executed on July 12 FINALIZE-RENEWAL·JUL 12. Since then: zero communications in either direction for 36 days, across every contact simultaneously.

Salesforce does not know any of this happened. The renewal opportunity sits open at Value Proposition, 50% probability, with an April 1 close date now 138 days past and a next step dated February SF-OPP·AUG 17 — a $140K closed renewal invisible to the forecast.

The signature also closed over unfinished business. Holly asked on June 22 for an official seat count and true-down terms on a roughly 70-seat overage — "this directly affects the renewal number I take to finance" LICENSE-RECON·JUN 22 — was promised both on June 23, followed up on July 4, and never received an answer before the agreement executed. In parallel, a second vendor thread ran the same renewal on different rails: Marcus Williams sent Roger Wakefield proposed terms on June 30, and Roger set hard dates — security addendum by July 15 for compliance sign-off, order form by July 17 PROPOSED-TERMS·JUL 4. Neither deliverable shows in the pipeline, and no one reconciled that track with the executed agreement.

The one clean win is real: the payroll export fix landed ahead of its promised ETA, and Roger confirmed it unprompted — his team's export "now runs clean without the manual workaround" REPORTING-RECAP·JUL 11. That July 11 message is the last word from anyone at Secbase. The FLSA workaround promised in the same review remains undelivered NO-FIX-ETA·JUL 7, the coalition has narrowed from five customer authors in the spring to two, and Sarah Newburg — the business-unit lead who first invoked exploring "all available options" — has been dark for 101 days.

Criteria

Status derived per criterion

Momentum compares the trailing 30 days against the prior 30 for communications matched to each criterion. Note the account has zero communications of any kind in the trailing 30 days, so every criterion reads Stalled on recency; density and last movement carry the signal.

Criterion C1 · Sponsor

Economic sponsor is present

Window: 45 daysPassing, narrowlyExpires ~Aug 25 without new traffic
Momentum
Stalled
Evidence density
9 items · 4 threads · Adequate
Last movement
37d Jul 11, 2026
Ball with
YellowSail

Passes on the letter: Roger Wakefield (VP of HR IT) authored on July 11 and Holly Langerfield (Director of Procurement, explicitly carrying the number to finance) on July 7 — both inside the 45-day window. But the window is emptying in real time; with no traffic since, C1 flips to failing around August 25.

What the pass conceals: the actual economic chain above Holly has never been on a thread. Her CFO appears only by reference ("our CFO is asking questions"), and Sarah Newburg — named in May as the leader of the business unit YellowSail supports — has authored nothing in 101 days. Sponsorship is currently two working-level contacts, both silent since signature.

Evidence · 4 items
Jul 11, 2026IN
Roger Wakefield · VP of HR IT
Confirms the payroll export fix landed and thanks the team — the account's last inbound message.
Jul 7, 2026IN
Holly Langerfield · Director of Procurement
Presses for final pricing, noting her leadership is asking why the renewal isn't closed.
Jun 22, 2026IN
Holly Langerfield
Frames the seat reconciliation as directly affecting the renewal number she takes to finance — budget authority in her own words.
May 8, 2026IN
Sarah Newburg · business-unit lead
Last authored message from the most senior known contact; invoked exploring all available options before another annual commitment.
Criterion C2 · Promises

We are keeping our promises

Threshold: no commitment open >14d, no thread unanswered >10dFailing
Momentum
Stalled
Evidence density
17 items · 6 threads · Thick
Last movement
36d Jul 12, 2026
Ball with
YellowSail

Failing on both prongs. Four vendor commitments are open past the 14-day threshold — the FLSA workaround (46 days), the seat-count and true-down answer (56 days), and Marcus Williams's security addendum and order form, both past customer-set deadlines of July 15 and 17. Seven customer-last threads sit unanswered past 10 days, four of them past 40.

The counter-evidence matters and is genuine: the payroll export fix ETA was promised on the reporting review and the fix itself landed ahead of schedule, confirmed by the customer. The pattern is not indifference — responses to nudges arrive within days — it is deliverables promised in those responses that then vanish. Holly named the mechanism herself in July: leadership involvement in spring, then "I never received the revised pricing we were told to expect."

Evidence · 4 items
Jul 7, 2026IN
Roger Wakefield
Chases the fix ETA promised for end of the prior week; his team is still running manual workarounds each pay cycle.
Jul 4, 2026IN
Holly Langerfield
Second follow-up on the seat count and true-down answer promised June 23; calls it time-sensitive for the finance business case.
Jul 2, 2026OUT
Emily Thompson · YellowSail
Apologizes that the pricing has dragged and promises to confirm revised pricing and send the agreement.
Jul 11, 2026IN
Roger Wakefield
Confirms the payroll fix arrived ahead of the promised ETA — the one commitment closed with customer acknowledgment.
Criterion C3 · Value

Value stated in the customer's own words

Window: 90 daysPassing, thin
Momentum
Stalled
Evidence density
2 items · 2 threads · Thin
Last movement
37d Jul 11, 2026
Ball with
Shared

Two items matched in ninety days — a thin base, and the plan says so rather than dressing it up. Roger's July 11 note is the real article: an unprompted report that his team's full-period payroll export now runs clean without the manual workaround, closing what he called a real pain point. Holly's July 4 note that the NetSuite integration one-pager was exactly what she needed is procurement utility more than business outcome.

The texture worth noticing: both statements describe relief from friction, not value created. Nothing in ninety days describes YellowSail making Secbase's recruiting, payroll, or reporting measurably better — the value language in this corpus is almost entirely vendor-authored, inside the pricing negotiation.

Evidence · 2 items
Jul 11, 2026IN
Roger Wakefield
His team confirmed the full-period export runs clean, no manual workaround — resolution ahead of schedule called a welcome surprise.
Jul 4, 2026IN
Holly Langerfield
Confirmation that the NetSuite integration carries no add-on cost was exactly what her renewal business case needed.
Criterion C4 · Coalition

More than one person carries the relationship

Threshold: ≥3 distinct authors in 60 daysFailing
Momentum
Stalled
Evidence density
2 authors · 60 days · below threshold
Last movement
37d Jul 11, 2026
Ball with
YellowSail

Failing: two distinct customer authors in the last 60 days — Holly Langerfield and Roger Wakefield — against a threshold of three. The 90-day view shows the narrowing: five Secbase authors were active in late April and May (adding Sarah Newburg, Melanie Witherspoon, Chris Donnelly), and every one outside the renewal-critical pair went quiet as the negotiation consumed the relationship.

No introductions, handoffs, or new names appear anywhere in the trailing 90 days. The entire relationship now routes through two people, both of whom stopped writing the day the deal closed.

Evidence · 3 items
Jun 18 – Aug 17IN
Holly Langerfield · Roger Wakefield
Only customer authors in the 60-day window; all traffic is renewal paperwork and the reporting fix.
May 3, 2026IN
Melanie Witherspoon
Last authored message — an FLSA reporting request that went to an external address and never returned.
Apr 27, 2026IN
Chris Donnelly
Last authored message — a routine license reassignment question.
Criterion C5 · Next thing

A next thing is live

Window: 60 daysPassing on paper, dormant in practice
Momentum
Stalled
Evidence density
4 items · 3 threads · Thin
Last movement
44d Jul 4, 2026
Ball with
YellowSail

Named next things exist: expanding the NetSuite integration to sync additional GL detail (raised by Holly June 29, confirmed as a no-cost configuration change), plus two modules — Advanced Reporting and Mobile Career Pages — contractually included in the new 24-month term. That is a concrete expansion surface, and it passes the criterion as written.

None of it has moved since signature. No kickoff, enablement, or configuration thread exists for either included module or the GL expansion. Included-at-no-cost modules that never activate become next April's "we're not using half of what we pay for" — the setup for the exact ROI argument this renewal barely survived.

Evidence · 3 items
Jun 29, 2026IN
Holly Langerfield
Asks whether expanding the GL detail sync changes cost — an expansion scoped in the customer's own planning.
Jul 1, 2026OUT
Emily Thompson
Confirms GL mapping granularity is configuration, not a paid upgrade, and sends a one-pager for the business case.
Jun 6, 2026OUT
Malcolm McCormick · VP Account Management
Final offer includes Advanced Reporting and Mobile Career Pages for the full 24-month term.

Commitment register

Extracted from message text

Explicit promises made in either direction, with the message that made them and whether later traffic shows them kept. Vendor-side misses are listed first because nobody self-reports those. Met requires the artifact or the other party's acknowledgment — never the promiser's own later assertion.

CommitmentMadeAgeState
YellowSail owes Secbase
Official seat count and true-down terms on the ~70-seat overage — "numbers finance can rely on"Emily Thompson · Jun 23 · License count reconciliation Jun 23 56d Open · overdue
Written FLSA export workaround, promised in the reporting-review follow-up; re-requested by RogerEmily Thompson · Jul 2 · Reporting Review Recap Jul 2 46d Open · overdue
Security addendum for Secbase compliance sign-off, customer deadline Jul 15 — deadline Roger explicitly held firmMarcus Williams · Jul 4 · Secbase renewal — proposed terms Jul 4 33d past due Open · no delivery evidence
Updated order form, customer deadline moved to Jul 17 — possibly mooted by the executed agreement, but no one told Roger either wayMarcus Williams · Jul 4 · Secbase renewal — proposed terms Jul 4 31d past due Open · ambiguous
Redlined agreement by EOD Jun 6 with the final flat-Year-1 terms — Holly reported on Jul 2 she never received it; eventually executed Jul 12Malcolm McCormick · Jun 6 · Contract Renewal — Pricing Concerns Jun 6 36d to close Met · late
Payroll export fix ETA from product — fix itself landed ahead of the ETA; customer confirmed clean full-period exportEmily Thompson · Jul 6 · Reporting Review Recap Jul 6 5d to close Met · customer-confirmed
Secbase owes YellowSail
Route the executed agreement through procurement once final numbers arrived in writing — signature processedHolly Langerfield · Jul 7 · Ready to finalize the renewal Jul 7 5d to close Met · vendor-observed
Secure internal approval without a budget amendment if the flat-Year-1 framework was met — condition met, agreement executedHolly Langerfield · Jun 1 · Contract Renewal — Pricing Concerns Jun 1 41d to close Met
Unowned decisions
Which renewal track governs: the executed multi-year agreement (Emily ↔ Holly) or the proposed-terms thread (Marcus ↔ Roger) still awaiting a compliance-gated security addendum. The two ran in parallel and were never reconciled.Raised by the record itself · Jul 4–12 · two threads Jul 12 36d No owner claimed

Friction ledger

Open loops by owner

Eleven threads on this account are unresolved with the customer speaking last. The seven that matter are below, aged from last inbound. Two are substantively closed in parallel threads but were never answered where they were asked — the customer's copy of the record still shows silence.

ThreadLast inboundOutstandingSignals
Secbase renewal — proposed termsRoger Wakefield · security addendum due Jul 15 held firm; order form moved to Jul 17 Jul 4 44d Abandoned
License count reconciliation before renewalHolly Langerfield · ~70-seat overage; "time-sensitive on our side" Jul 4 44d Abandoned
Reporting recap — still no fix ETARoger Wakefield · payroll fix later closed in a parallel thread; FLSA workaround still owed here Jul 7 41d Abandoned · partial
Renewal pricing — we're still not resolvedHolly Langerfield · substantively closed by the Jul 12 execution in a parallel thread Jul 7 41d Closed elsewhere
FSLA Reporting — urgent export issueRoger Wakefield · escalated to David Kim in May; workaround walkthrough proposed, no close Jun 4 74d Abandoned
Mobile Careers Page resolution and next stepsRoger Wakefield · release-communication and technical-POC follow-ups proposed, never scheduled May 24 85d Abandoned
IT/Security docsSarah Newburg · security documentation loop with a third party; last inbound word from the account's most senior contact May 9 100d Abandoned

Coalition map

Participation, not CRM roles

30 people are attached to this account in Sturdy, but only 7 carry identifiable secbase.com addresses — the remainder look like ingestion noise and are grouped out. 0 contacts have authored in the last 14 days; 2 in the last 60. The CFO Holly answers to has never appeared on a thread.

Roger Wakefield
VP of HR IT. Owns the technical relationship — reporting, integrations, compliance gates. His July 11 thank-you is the account's last inbound word.set and held the Jul 15 security-addendum deadline; still owed the FLSA workaround
Decaying · 37d
Holly Langerfield
Director of Procurement. Ran the entire renewal negotiation and carries the number to finance. Went silent the week the agreement executed — with her seat-count question still unanswered.disclosed competitor conversations Jun 1; escalated to leadership Jul 7
Decaying · 41d
Sarah Newburg
Leads the business unit YellowSail supports — the closest thing to an economic sponsor in the corpus. Her last two messages were the pricing-frustration escalation and a security-docs thread that died unanswered.sponsor decay: senior contact dark while working-level traffic continued
Gone dark · 101d
Melanie Witherspoon
Raised an FLSA reporting need in May; the thread went to an external address and never returned to the pipeline.her issue resurfaced later through Roger — same gap, different person
Gone dark · 106d
Chris Donnelly
Working-level user; last seen asking to reassign a license in April.
Gone dark · 112d
Mary Hawkins · Brittany Witherspoon
On the Salesforce contact roster; neither has authored a message in the observable corpus.
Silent · never authored

Language drift

Hypothesis · quotes attached

How the customer talks about this relationship now versus at plan inception. Directional reading, not a score.

The arc runs from exit language to closing urgency to genuine warmth — and then to nothing. In late May, Holly's vocabulary was that of a buyer with a foot out the door: frustration, disappointment, options. By early July the same voice was fighting to close with YellowSail, not away from it — her pressure was about paperwork velocity, not vendor choice. Roger's final message is the warmest customer-authored text in the corpus. The risk reading is not the drift, which is favorable; it is that the drift ends at July 11 and the silence since is unreadable. A relationship that communicates only when something is broken or unsigned has no baseline to drift from.

May 26, 2026
Holly Langerfield
"We need to resolve this before March 15 or we will be forced to evaluate our options."
Jul 7, 2026
Holly Langerfield
"We're now well past our renewal date and my leadership is asking why this still isn't closed."
Jul 11, 2026
Roger Wakefield
"Thanks for staying on this; it had been a real pain point."

Watch list

Derived risk

A $140K closed renewal is invisible to Salesforce

The opportunity sits at Value Proposition, 50%, close date April 1 — 138 days past — under Joel Passen, while the pipeline shows the agreement fully executed July 12. Forecast, comp, and any renewal-date automation downstream of Renew_Date__c (currently null) are all running on fiction.

Trigger: any forecast review, or the first automated renewal-workflow touch built on the stale stage.

The agreement executed over an unanswered seat-count dispute

Holly flagged a ~70-seat overage on June 22 and was promised an official count and true-down terms. No answer ever arrived; the multi-year agreement was signed anyway. If the executed paperwork bakes in the disputed count, the first invoice is a credit-demand and goodwill fight waiting to happen — with procurement, the least forgiving audience on the account.

Trigger: first invoice under the new term, or any Secbase finance query about seats.

Two renewal tracks were never reconciled — and one has a compliance gate

Marcus Williams's proposed-terms thread with Roger carried hard deliverables: a security addendum by July 15 for Secbase compliance sign-off and an order form by July 17. Neither shows as delivered, and no message tells Roger his track was superseded. If the addendum was a genuine compliance condition, the executed agreement may be sitting unblessed inside Secbase.

Trigger: any compliance or security inquiry from Secbase, or Roger reviving the thread.

Total silence since signature, with the sponsor layer already dark

Zero communications in either direction for 36 days — every contact went quiet simultaneously the week the deal closed. Sarah Newburg, the business-unit lead who invoked exploring all options, is 101 days dark; the coalition narrowed from five authors to two; the CFO was never on a thread. This renewal was saved by concession, not by demonstrated value, and the value-proof clock for the next one started July 12 with nobody talking.

Trigger: 60 days of continued silence, or the first Year-2 pricing conversation (6% step-up lands ~Apr 2027).

The negotiated SLA and included modules are commitments with no activity behind them

The deal closed on a 4-hour-acknowledgment / 24-hour-P1 SLA addendum and two included modules — Advanced Reporting and Mobile Career Pages, the latter tied to a bug saga Roger escalated in May. No enablement or kickoff thread exists for either module, and the FLSA workaround from the same product area is still owed. The first P1 under the new SLA, and next April's usage review, are both credibility tests YellowSail is currently not preparing for.

Trigger: next support escalation from Roger's team, or 90 days with no module-activation traffic.