Rippling Jira Asset Mgmt add-on approved — 12mo commit + cancellation push

Situation

In a 5/29 Slack DM with Steve Wallace, Peter approved the Rippling Jira Asset Management add-on under negotiated terms. Rippling proposed a 19-month commit co-termed with the main Rippling agreement (~$21.9k total: $6,420 upfront after 2 free months due 8/21, then annual billing at $12/user/month for 107 users, includes monitoring/maintenance). Peter pushed back on lock-in, accepted one year, asked about cancellation terms. Steve replied he would offer 12-month commit with cancellation for convenience at month 11+ with 30 days notice. Peter said works for me. Decision is contingent on Steve actually securing the cancellation clause.

Reasoning

Pair-pattern with the prior Rippling Asset Mgmt decision: time-and-risk-floor over absolute cost. At 107 users and current company size, build-vs-buy clearly favors buy because building absorbs engineers who would otherwise be on Spark/Fuzzball/Pro AI — exactly the non-differentiating work D1 JPD doctrine extension is designed to keep OFF engineering plates. Build-vs-buy inflection point explicitly named (if we double in size, building might be worth it). Cancellation negotiation move preserves vendor goodwill while not eating lock-in risk.

Additional Context

Pair with the prior Rippling Asset Mgmt — time over cost decision. Ties into the HR Onboarding/Off-boarding Automation TPS top priority for Eng Ops (Jun 18 target, 80% confidence) — Steve owns. Co-term with main Rippling agreement matters for billing simplification.

Observed Evidence

Direct DM thread 5/29 11:51–12:21 PDT between Peter and Steve. Peter explicit build-vs-buy reasoning, explicit cancellation pushback, explicit works for me approval contingent on Steves negotiated terms.

Matching Patterns

Confidence Breakdown

Reasoning Depth Analysis