Everfox: require ~$2M front-loaded year-one payment, reject back-loaded $600k structure

May 4, 2026 at 10:32 PMstrategyhigh

Situation

Peter is requiring a large upfront payment ($2M floor with the proposal team; $4-6M float with Greg) for the new Everfox custom work (legacy CPU support, custom desktop) and rejecting the back-loaded $600k year-one structure. The $20M/10-year deal will be restructured to front-load payments, potentially by reducing total contract value if needed. CIQ will not absorb non-reusable engineering work without immediate funding.

Reasoning

The new work is non-reusable: it does not accrue to other deals, does not strengthen the platform, does not compound. That class of work must be priced as Professional Services (cash up front, full-loaded cost), not enterprise-style amortized over decade ARR. The $4-6M with Greg vs $2M with the proposal team is the negotiation float. The principle being instituted is the same as the Engineering-veto decision: Sales cannot commit Engineering to unfunded research, regardless of how strategic the headline number sounds. Holding the line on the 1/29 Everfox precedent worked; holding it again now keeps that principle durable.

Additional Context

Direct precedent: 2026-01-29 Everfox partnership requires ARR-target-level contract to proceed (outcome ★★★★). Anchored to the Engineering-veto decision logged this session. Verbal $20M agreement at risk if year-one terms get papered before Peter intervenes.

Observed Evidence

Rakuten meeting 5/4: explicit $2M floor stated to proposal team. Greg 1:1 5/4: $4-6M year-one stated to manager. Both reject the $600k back-loaded structure. Direct quote: CIQ cannot take on this work on the come.

Matching Patterns

70%
Protect Engineering Capacity(non-reusable funding pressure, same category)

Confidence Breakdown

33/35
Evidence
28/30
Pattern
19/20
Source
13/15
Corroboration

Reasoning Depth Analysis

Org Signal:Custom work is funded work. No exceptions for relationship-driven deals or 10-year strategic framing.
Who Affected:Ramesh (proposal must front-load), Bjorn (must see the floor before sales review), Brady/Nathan (technical team that would absorb without this gate), every future Everfox-shaped deal
Precedent:Total contract value can shrink to preserve year-one floor. Decade-strategic headlines do not compress year-one funding.
Consequences:Deal may shrink or break. Acceptable vs absorbing $20M of unfunded research liability.
Timing:Before the $600k year-one term gets papered and becomes hard to unwind.

Source

reflection

AI Confidence

93%

Related Context

🎥
Rakuten Proposal Overview 5/4

fathom

Funding Gap: Everfox Offer $600k first-year payment. CIQ Requirement ~$2M first-year payment. Rationale: The work is non-reusable and requires immediate funding for staffing and research. CIQ cannot take on this work on the come.

🎥
Peter <> Greg 1:1 5/4

fathom

Everfox 10-year, $20M deal requires support for legacy Pentium and Itanium hardware. Peter requires a large upfront payment ($4-6M in year one) to fund the necessary engineering work, rejecting the proposed back-loaded payment structure.

Follow-up Todos

Suggest follow-up todo

Talk Everfox custom desktop + legacy CPU 1:1 with Ramesh; align before sales review

@Bjorn

From: Rakuten Proposal Overview action items (Ramesh action: Schedule a separate meeting with Peter on the Everfox custom desktop work). Peter must see the proposal restructure before Suzanne sends the technical draft.

Why: The $2M floor only holds if Peter reviews the restructured proposal before it goes to Everfox. Without this 1:1, the proposal team owns the floor in name but Peter has no veto point — the principle erodes by the time Everfox sees terms.

Outcome

No outcome recorded yet.

Decision ID: d1ea8ed9-f1ca-4804-907d-d7bc89e5c241