PushFire

The engagement

GrowthOS. PushFire's ongoing operating engagement.

A defined monthly engagement for acquisition, measurement, and execution. Larger implementation work is priced separately. Led directly by PushFire's senior team.

Every month

What leadership receives each month.

  • Executive brief

    A short written summary with the numbers that matter to leadership, sourced from the account records and cross-checked against the CRM.

  • Account reconciliation

    Ad-platform reports reconciled against CRM records. Where they disagree, the disagreement is investigated rather than smoothed over.

  • Decision log

    Each recommendation has a named owner (client or PushFire), a due date, and a defined success signal. Standing document.

  • Tracking change log

    Every change to tracking, tagging, attribution, or reporting is logged with a date and a reason, so month-over-month comparisons don't silently break.

  • What we still cannot count

    A running list of open attribution issues: what cannot yet be counted, why, and what work would make it countable.

  • Competitor activity

    Observed paid-search activity and third-party spend estimates, labeled as estimates. Where a competitor is being cited in AI-assisted answers instead of you.

  • Monthly working session

    Working session with leadership on decisions the account records now support: stop, start, increase, or investigate.

Work outside that scope becomes a separate, separately priced project.

How an engagement runs

Diagnostic → measurement design → execution → monthly review.

  1. 01

    Assess

    A paid diagnostic on the source records before scope is finalized. Fixes the scope and the price at signing rather than discovering them later.

  2. 02

    Architect

    Define what gets measured, where the data lives, who sees what, and which artifacts leadership receives.

  3. 03

    Execute

    Acquisition, automation, CRM, and reporting under the same measurement standard, with a decision register that names who owns what.

  4. 04

    Optimize

    Executive brief, source-account reconciliation, and the standing decision register updated monthly.

The reporting standard

Four rules every GrowthOS artifact has to survive.

Source identified. Period, population, and counting method stated. Estimates and derived figures labeled. Limitations and contrary findings remain in the report.

Read the full standard

Proprietary technology

SignalEar.

With one prompt, SignalEar surfaced every legitimate inquiry PushFire has ever received — across email, phone, text, and WhatsApp — with a detailed summary of every conversation to date. Used inside GrowthOS engagements where relationship signal is a meaningful part of the growth model.

Start with the account records and the decision leadership needs to make.

Bring the account, the question, and any constraints. We'll tell you whether GrowthOS is the right fit.

Inquire