About CitrusGate

Who runs CitrusGate

CitrusGate LLC sells one fixed-scope, $1,500 private brief for a stalled B2B software deal. Ivan Golovach runs the workflow, reviews the memo, and holds the release stop-line before delivery.

Entity

CitrusGate LLC

The operating entity behind the site, the Stripe checkout, and the private brief release.

Named operator

Ivan Golovach GitHub profile photo

Ivan Golovach

Founder and brief lead

Ivan Golovach built and operates the CitrusGate workflow, holds the release stop-line on the private memo, and answers fit questions directly. The service is sold on inspectable work, clear boundaries, and one accountable operator.

Public profile: GitHub. Questions before purchase: replied to within 1 business day. Send them to [email protected].

Entity clarity

What CitrusGate sells, who it is for, and when not to use it

CitrusGate sells one fixed-scope Decision Friction Brief. It is meant to help a B2B software team diagnose one live buying decision before pricing, proof, or messaging work expands around the wrong explanation.

What you buy

One async-first internal brief priced at $1,500. It names the primary blocker, the tempting wrong move to avoid, and the smallest credible next move.

Who it is for

Best for B2B software teams in multi-stakeholder evaluation when a PMM, product, GTM, or executive lead needs fast clarity on why buying decisions are stalling.

When not to use it

It is a poor fit for battlecards, a generic benchmark deck, a workshop-heavy first engagement, or a full win-loss interview program as the first step.

How the brief is made

The brief is staged, then reviewed

Research is structured first. Decision pressure is ranked next. The first correction is narrowed after that. The memo is then reviewed and released by one accountable operator.

Bounded evidence first

The workflow starts from public company evidence, supporting context, and company-specific inputs. It does not begin by asking for a generic freeform essay.

Staged narrowing, not one-pass drafting

The work moves through separate layers for company intelligence, decision pressure, intervention narrowing, and memo release instead of pretending one prompt can do every job well.

Checked output between stages

Each stage has a fixed structure. If output does not match it, it gets corrected or rerun instead of quietly becoming a finished brief.

Human release stop-line

The memo can be edited, saved as draft, and approved before private delivery. A model-assisted draft is not the same thing as a released brief.

What models do here

What the workflow does and does not do

Models may assist extraction, ranking, and drafting inside the workflow. They do not decide what gets shipped. The private brief is a bounded, reviewed release, not an autonomous answer engine or a pedigree sale.

  1. 01

    The memo stage works from prior structured layers instead of improvising a fresh report from scratch.

  2. 02

    If a run does not match the required structure, it gets corrected or rerun instead of quietly shipping.

  3. 03

    Buyer-submitted context is used to produce the ordered brief and is not republished publicly by default or intentionally used to train CitrusGate public materials.

  4. 04

    Third-party model providers may process submitted context under their own API or business data controls and retention rules.

  5. 05

    If your company needs an NDA or a model-processing restriction before sharing context, email before purchase.

Accountability

One operating entity, one release stop-line, one direct contact path

CitrusGate LLC is responsible for the site, the fixed-price checkout, and the private brief delivery. Ivan Golovach holds the release stop-line on the private memo, and the buyer can inspect the specimen briefs, diagnosis path, and public corpus before deciding whether that trust is earned.

The public trust layer is artifact-led: specimen briefs, one diagnosis path, corpus counts, and explicit boundaries before checkout.

The memo can be edited, saved as draft, and approved before release.

The brief is delivered for internal team use and is not repurposed publicly unless it has been fully abstracted.

Fit guides

If you are deciding whether the brief is the right first move, start here

Trust & Privacy

Private briefs stay private unless they are fully abstracted

If a piece of information only makes sense when the reader knows the exact company, contact, or outreach context, it stays private. CitrusGate does not repurpose client-specific brief detail onto the public site unless it has been fully abstracted and made public-safe.

We publish

Public-safe blocker patterns, recurrence counts, dated dispatches, and specimen materials that show the reasoning without exposing a live company.

We keep private

Raw company notes, contact-level context, outreach state, client-sensitive files, and the private next move for a live team.

Why the boundary exists

If removing company context makes a page stop being useful, it belongs in the private brief instead of the public site.