Engineering veto required on custom deals and new lines of business

May 4, 2026 at 10:31 PMstrategyhigh

Situation

Peter is implementing a formal process where Engineering has review-and-veto authority on custom deals and new lines of business. Engineering must be consulted to assess cost and feasibility before any deal is finalized. Discussed in Peter <> Chris 5/1 and applied immediately to the Everfox proposal restructuring on 5/4.

Reasoning

Everfox is the test case: Sales committed Engineering to custom work where current scope requires MORE work than the original scope at a fraction of the originally projected revenue. The prior precedent (AMD deal) was the same shape — leadership stated no Engineering responsibility, but work was required. Peter has determined that informal Engineering influence is failing, so the fix must be structural authority, not louder advocacy. The mirror to 4/30 Slack-only refusal: externalize friction back to the requester so they internalize cost. CIQ cannot grow ARR by signing unprofitable deals nor keep relying on Engineering to absorb sales mistakes after-the-fact.

Additional Context

Direct precedent: 2026-01-29 Everfox partnership requires ARR-target-level contract to proceed. Direct sibling: 2026-04-15 Sales Scope Discipline on Nokia. Same externalize-friction lever as 2026-04-30 refuse-Slack-only-requests. Discussed during P+E QBR planning with Chris Baek who owns process implementation.

Observed Evidence

Peter <> Chris (5/1): Engineering Stance: The deal is unprofitable and should be rejected. This feedback is not being heard. Solution: formal process where Engineering has veto. Greg 1:1 (5/4): Peter requires a large upfront payment to fund engineering work, rejecting back-loaded payment structure. Rakuten meeting (5/4): CIQ cannot take on this work on the come.

Matching Patterns

65%
Protect Engineering Capacity(scope keyword match, same category)

Confidence Breakdown

32/35
Evidence
27/30
Pattern
20/20
Source
13/15
Corroboration

Reasoning Depth Analysis

Org Signal:Engineering owns deal viability as a peer to Sales, not as downstream absorber of sales decisions. Same authority structure as Product over priority.
Who Affected:Bjorn (Product), Ramesh + Suzanne (sales engineering), Chris Baek (process owner), every AE running custom-scope deals, future-Peter who will not need to fight every Everfox-shaped deal individually
Precedent:Every custom deal or new line-of-business commitment now requires Engineering review before finalization. Mirrors Product priority gate.
Consequences:Some deals slow or die at the gate. Acceptable tradeoff vs absorbing unprofitable work post-signature.
Timing:Before Everfox closes badly and becomes another GDC-style anchor. The structural fix lands while Everfox is still negotiable, not after.

Source

reflection

AI Confidence

92%

Related Context

🎥
Peter <> Chris Sync 5/1

fathom

Solution: Implement a formal process where Engineering has a veto on custom deals and new lines of business. Engineering must be consulted to assess cost and feasibility before any deal is finalized.

🎥
Rakuten Proposal Overview 5/4

fathom

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

Peter requires a large upfront payment ($4-6M in year one) to fund the necessary engineering work, rejecting the proposed back-loaded payment structure.

Outcome

No outcome recorded yet.

Decision ID: 13beac71-81bd-4ad3-8655-075084dd9f0a