# Goodie agency cost and attribution

Compare the full client workload and the evidence behind revenue claims. Record pitch workspaces separately from paying client workspaces, then reconcile the quote and attribution definitions.

Worksheet version 1.0 · 17 September 2026. Complete one record per candidate. Blank fields request your evidence; this pack does not report vendor account tests or executed pilots.

Complete comparison: https://rankecho.io/compare/goodie-ai-alternatives

## 1 Define clients and workload

A requested workload is not a purchased allowance. Twenty prompts across five surfaces daily for 30 days requests 3000 responses before repeats.

**Decision and approver** — Record agency, client owners, required outcome and review date.

[Enter your response]

**Workspace schedule** — List active clients, new pitches, pitch duration, conversion dates and required ongoing brand plans.

[Enter your response]

**Requested panel** — Record prompt IDs, surfaces, regions, languages, frequency, days and retries per client.

[Enter your response]

**Vendor consumption rules** — Record prompt, response, optimization or weighted credit units. For AthenaHQ, save calculator inputs including model weights and fan out; confirm the quote.

[Enter your response]

## 2 Reconcile the twelve month cost

Keep billing commitment and cash payments separate from a monthly equivalent. Unknown charges stay visible.

**Quote and billing basis** — Record quote URL, date, currency, tier, tax, renewal, quarterly or annual commitment and cancellation terms.

[Enter your response]

| Payable component | Quantity and rate basis | Annual cost or unknown |
| --- | --- | --- |
| Agency subscription | [Pitch allowance and billing term] | [Amount or unknown] |
| Active client plans | [Each brand, start date, plan and term] | [Amount or unknown] |
| Extras and retained tools | [Credits, API, integrations and other subscriptions] | [Amount or unknown] |
| Implementation and labor | [Setup, review, publishing and reconciliation hours] | [Amount or unknown] |

## 3 Reconcile attribution

Separate observed referral and conversion revenue, modeled influence and a causal claim. Preserve source records so another analyst can reproduce the result.

**Definitions and common filters** — Record GA4 property, date window, timezone, currency, identity rules, referral exclusions and conversion event.

[Enter your response]

**Raw join evidence** — Link referral, session, conversion and revenue records with join keys; record unmatched rows and agreed tolerance.

[Enter your response]

**Revenue reconciliation** — Compare totals to the source; record deduplication, refunds, missing identifiers and unexplained differences.

[Enter your response]

**Claim boundary** — Label observed versus modeled results. Leave unobserved prompts unmapped; causal lift requires a separate study design.

[Enter your response]

## 4 Review execution and decide

A report or suggested action is not a shipped page change. Keep approval and publication evidence in the decision record.

**Execution acceptance** — Save one approved task and resulting brief, draft or page diff; record native, external and manual work plus publishing owner.

[Enter your response]

**Required conditions** — Mark each workload, cost, export and attribution requirement pass, fail or unknown with evidence.

[Enter your response]

**Decision and migration** — Choose stay, switch, supplement or hold; retain old answers, reports, definitions and permissions for an overlap period.

[Enter your response]

**Sign off and revisit** — Record approver, quote expiry, unresolved conditions and next review date.

[Enter your response]

## Complete comparison guide

Stay with Goodie when its integrated visibility, optimization, and revenue-reporting workflow passes your execution and attribution tests. Consider AthenaHQ for credit-metered visibility and actions with analytics connections, or RankEcho for bounded fixes and post-shipment observations alongside your own analytics and CMS. For agency cost, price every active client separately from pitches, then separate tracked revenue, modeled influence, and causal claims before switching.

Original guide and evidence records: 12 September 2026. Companion and pricing recheck: 17 September 2026. Confirm the current plan, billing commitment and exact workload in a written quote.

Goodie pricing rechecked 17 September 2026: Core has 120 prompts and 50 monthly optimizations; Pro has 100 monthly optimizations. Agency Growth is $330 per month equivalent billed quarterly or $275 billed annually, plus active client plans. Brand prices are unchanged. The illustrative annual budget below uses the refreshed rates; confirm a written quote before purchase. [Goodie pricing](https://higoodie.com/pricing/)

## Which option fits your workflow and budget?

Choose the operating model before the entry price. Goodie combines visibility, action, pitch, and revenue-reporting scope; AthenaHQ meters AI responses; RankEcho centers a smaller review-and-retest loop. Those units and outputs are not interchangeable.

Published by RankEcho from official documentation, without account-level product tests. Prices and public product claims were checked on September 12, 2026; they exclude tax, implementation, negotiated terms, and unlisted add-ons.

| Option | Strong fit | Published cost basis | Poor fit or must-have gate |
| --- | --- | --- | --- |
| Goodie | An integrated visibility, optimization-action, and revenue-reporting workflow, with temporary agency pitch workspaces. | Brand monthly / per month billed annually: Core $478.80 / $399; Pro $1,198.80 / $999. Agency Growth is $330 per month equivalent billed quarterly or $275 per month equivalent billed annually. Enterprise is custom. | Core: one brand, 120 prompts, 50 optimizations/month, five surfaces. Pro: one brand, 250 prompts, 100 optimizations/month, eight surfaces. Growth includes 10 seven-day pitch workspaces monthly; each ongoing client needs a brand plan. |
| AthenaHQ | Visibility and action workflows with GA4, Search Console, Shopify and Webflow integrations, plus CSV exports. | Starter is $295 monthly for 3,600 credits; Enterprise is custom. A 17% annual discount is advertised. API access and extra credits are paid add-ons priced by contact. | Credits are weighted by model: use AthenaHQ's current calculator for the chosen panel and fan-out, then confirm the allowance and any overage or add-on terms in a written quote. Starter covers 11 models but one region and language. Multi-region, SSO, audit logs, and advanced optimization require Enterprise. Unlimited seats do not establish unlimited brands; agencies need a written client and website quote. |
| RankEcho | Reviewable fix artifacts, manual shipment, and same-prompt observations for a team that already owns its analytics and CMS workflow. | Monthly: Solo $49, Growth $149, Agency $399; annual billing gives two months free. Full-page writing requires a paid base plan plus a content add-on starting at $99 monthly for 10 pieces. | Solo, Growth, and Agency include 100, 500, and 2500 prompt slots across 1, 3, and 25 domains. No native GA4 connector, automatic publishing, CRM revenue attribution, commerce-catalog execution, or Copilot checks are included. |

- [Goodie pricing](https://higoodie.com/pricing/)
- [AthenaHQ plans](https://athenahq.ai/plans)
- [RankEcho pricing](https://rankecho.io/pricing)
- [RankEcho content add-on](https://rankecho.io/pricing/content)
- [AthenaHQ weighted credit calculator](https://athenahq.ai/credit-calculator)

## When should you stay with Goodie?

Stay when one integrated workflow reduces real handoffs and its optimization and attribution outputs pass your acceptance tests. Keeping existing client configuration and reporting history can be more valuable than replacing a working system for a lower headline price.

Goodie is a poor fit when active-client economics, billing commitment, action allowance, execution controls, export terms, or the distinction between attributed and influenced revenue fails a must-have.

Change only for a documented failure and a replacement that passes the same task. A connector, generated recommendation, or before-and-after chart alone does not establish correct implementation or incremental revenue.

- [Review Goodie's optimization-action description](https://higoodie.com/features/ai-optimization-actions/)
- [Review Goodie's attribution definitions](https://higoodie.com/features/ai-analytics-attribution/)

## When do AthenaHQ or RankEcho fit?

AthenaHQ fits when a response-credit budget and its connected action workflow pass the same evaluation. Apply the row's region, API, and agency gates as exclusions, and price a representative response workload before signing.

RankEcho fits when the team wants one reviewable finding turned into bounded artifacts, will publish through its own workflow, and will assess the same configured prompts later. Free audits check Perplexity and Gemini once per prompt. Paid and trialing accounts add ChatGPT, Claude, and Google AI Overviews when configured for the account, for up to 5 engines. Google AI Overviews is reported only when an overview is shown and retrievable; otherwise that cell is marked skipped/unavailable rather than counted as a citation miss. RankEcho does not currently run Microsoft Copilot checks. The public sample is fictional and deterministic; the Proof Loop reports correlation with controls, not causation. RankEcho is a poor fit when automatic publishing, native GA4 or CRM revenue attribution, commerce-catalog execution, or a bundled full-page writer is required.

- [Review AthenaHQ plan and add-on gates](https://athenahq.ai/plans)
- [Inspect RankEcho's sample fix](https://rankecho.io/sample-fix)
- [Review the Proof Loop method](https://rankecho.io/product/proof-loop)

## How should an agency price the workload?

Make one row per pitch and active client. Record the brand, stage, start and end dates, required surfaces, country and language, prompts, cadence, actions or response credits, content, seats, integrations, implementation time, reporting time, add-ons, billing period, and commitment end date.

Twenty prompts × five surfaces × daily collection for 30 days equals 3,000 requested responses before repeats. That is a workload, not a plan entitlement: vendors meter prompts, responses, actions, credits, and retries differently.

At public rates rechecked on 17 September 2026, Goodie Agency Growth billed annually plus three annual Core client plans is $1,472 per month equivalent before tax, extras, and labor: $275 + 3 × $399. Each component carries an annual commitment. This is arithmetic from public rates, not a customer invoice or monthly cancellation price.

For AthenaHQ, convert the required responses into credits and obtain a client and website quote. For RankEcho, map active clients to domain and prompt allowances and add content only where needed. Keep setup and recurring staff time visible for every option.

- [Recheck Goodie billing periods and client-plan terms](https://higoodie.com/pricing/)

## What counts as accepted execution?

Give each applicable option the same real page gap, approved facts, source pack, and reviewer. The output passes only when the team understands what the vendor produced and can control the change.

- Classify every output as a recommendation, editable draft, direct CMS change, or outreach task. Record the human work and system boundary instead of grouping all four as execution.
- Verify roles, permissions, approval, dry-run behavior, the proposed diff, source ownership, version history, rollback, access ownership, and the usage or action units consumed.
- For an owned-page change, compare the approved metadata, schema, visible copy, and links with the actual published result. For outreach, preserve approval, recipient, status, and evidence without treating a status as earned coverage.
- Save the original, proposed output, approval, shipment record, and failure or rollback result. Apply the same control requirements to Goodie, AthenaHQ, RankEcho, and the team's existing stack.
- Observe the fixed prompt panel later, but report improvement, decline, no change, and unavailable results. Timing does not prove that the action caused visibility or revenue movement.
- [Goodie optimization actions](https://higoodie.com/features/ai-optimization-actions/)
- [Preview a bounded RankEcho fix](https://rankecho.io/sample-fix)

## What counts as accepted attribution?

Maintain three distinct statements: revenue traced through observed referral and conversion records, influence estimated by a documented model, and a causal claim that a channel or change created incremental revenue. A connector or before-and-after trend does not supply the third statement.

- Use the same GA4 property, AI-source filters, date window, timezone, key-event definitions, identity rules, currency, and revenue field on both sides of the reconciliation.
- Trace a small sample from session to conversion or CRM record. Set an acceptable tolerance before testing, explain every excluded or delayed record, and retain the raw comparison.
- Report modeled influence separately. Record model inputs, category or prompt mapping, assumptions, lookback, uncertainty, and refresh date; label inferred mappings and prevent overlapping attributed and influenced series from being added twice.
- Ask how an AI referral is associated with a prompt or category. Importing an event does not by itself show which prompt caused the session, and a visibility-based impression estimate is not an observed page view.
- Use before-and-after trends as dated observations. Incrementality requires a suitable design and evidence beyond the connector and chart; leave the causal field unresolved when that evidence is absent.
- [Goodie attribution description](https://higoodie.com/features/ai-analytics-attribution/)
- [Verify AI referrals in GA4](https://rankecho.io/resources/prove/ga4-ai-referrals)
- [Reconcile citation, session, and revenue units](https://rankecho.io/resources/prove/citation-to-session-to-conversion)

## What must you preserve when migrating clients?

Before cancelling, export every permitted prompt, model or surface, country, language, cadence, raw answer, source URL, configuration, timestamp, metric definition, action, draft, approval, report, role, client owner, billing date, attribution rule, and modeled-influence method.

Test one client handoff field by field. Run a fixed prompt panel in parallel for one reporting cycle when practical; if history, sampling, availability rules, or denominators are not portable, close the old series and start a dated baseline rather than joining incompatible percentages.

Assign ownership for files, CMS changes, reports, analytics access, integration credentials, and open actions. After the approved handoff, revoke vendor and former-team access through the normal account controls and retain the offboarding record.


## What should you verify again before signing?

Recheck billing periods, plan names, client-workspace fees, pitch duration, prompts, surfaces, countries, languages, actions, response or content credits, seats, permissions, approval and rollback behavior, integrations, attribution definitions, exports, retention, and contract terms. For RankEcho, also recheck engine configuration, Copilot, native-connector, content-add-on, manual-shipment, sample, and Proof Loop boundaries.

Save the dated pricing page, quote, order form, attribution definition, export sample, acceptance record, and unresolved questions. Resolve a decision-critical conflict in the tested account and signed terms before cancelling the incumbent.


## Are attributed revenue and influenced revenue the same?

No. Treat revenue joined to observed referral and conversion records separately from influence estimated for zero-click demand. Preserve the model's inputs, assumptions, uncertainty, and deduplication rule instead of adding the two series together.

## Can prompts, response credits, and optimization actions be compared directly?

No. Convert the planned brands, prompts, surfaces, locales, cadence, and repeats into each vendor's documented billing units. Then test one representative collection and action to capture actual consumption, plan gates, add-ons, and staff work.

## Can RankEcho replace Goodie's revenue attribution workflow?

Not by itself. RankEcho does not include a native GA4 connector or CRM revenue-attribution model. It can support bounded fixes and later observations, while the team keeps referral, conversion, and revenue reconciliation in its analytics and CRM workflow.

## Preserved dated evidence

- [Goodie pricing](https://higoodie.com/pricing/) — checked 2026-09-12. Goodie's brand and agency headline rates use different billing periods; ongoing clients require separate plans. Annual and monthly brand views and annual and quarterly agency views were checked. Checkout was not tested; confirm client billing and model coverage in the order form.

- [Goodie AI analytics and attribution](https://higoodie.com/features/ai-analytics-attribution/) — checked 2026-09-12. Goodie distinguishes attributed revenue traced through AI referral traffic and conversion or CRM data from influenced revenue modeled for zero-click demand. It describes identifying AI referrals through Google Analytics, estimating impressions from visibility data, and showing before-and-after optimization trends. This is a documentation review, not a connector or outcome test. No analytics property, CRM, event, source filter, revenue record, impression estimate, model, reconciliation, prompt mapping, or causal effect was inspected.

- [Goodie AI optimization actions](https://higoodie.com/features/ai-optimization-actions/) — checked 2026-09-12. Goodie's optimization-actions page was reviewed for action categories, owned-site changes, competitor comparisons, outreach tracking, and follow-up observations. No product account was used. Recommendation quality, generated output, permissions, approval, CMS execution, outreach, credits, version history, rollback, later visibility, and commercial outcomes were not tested.

- [AthenaHQ plans](https://athenahq.ai/plans) — checked 2026-09-12. AthenaHQ Starter includes a credit allocation and charges extra for API access; Enterprise expands governance and regional scope. Use the separate calculator record for weighted credit consumption. The public plan page was reviewed. No account, response, action, export, integration, API, credit meter, website allowance, annual checkout, or agency quote was tested.

- [RankEcho pricing](https://rankecho.io/pricing) — checked 2026-09-12. RankEcho's public Solo, Growth, and Agency pricing was reviewed for billing, prompt, domain, seat, and re-test limits and paid Fix and Proof access. The public page was checked against billing plan limits in source. No customer account, engine run, fix, report, analytics connection, attribution, or post-change result was tested.

- [RankEcho content pricing](https://rankecho.io/pricing/content) — checked 2026-09-12. RankEcho full-page writing and refreshing is a separate add-on that requires a paid visibility plan. Its three tiers differ in monthly price and piece allowance, with a piece defined as 1,500 generated words rounded up to a one-piece minimum. The add-on dependency, prices, allowances, and piece definition were checked against source. No content was generated, reviewed, exported, or published.

- [RankEcho sample fix](https://rankecho.io/sample-fix) — checked 2026-09-12. RankEcho's public sample fix is a deterministic example for a fictional brand. It shows editable answer-block, schema, brief, source-plan, and review artifacts and says the example is not customer data, a universal requirement, or a promised outcome. The sample was inspected as a documented output preview. It does not establish fit for another page or show that publishing an artifact changes an answer, citation, visit, or sale.

- [RankEcho Proof Loop](https://rankecho.io/product/proof-loop) — checked 2026-09-12. RankEcho's Proof Loop records a baseline, shipment, and later observations for the same configured prompts and engines. Its public method describes the comparison as correlation with controls, not proof that the shipment caused a ranking, mention, citation, referral, or revenue change. The documented workflow and limits were reviewed. No customer series, causal effect, analytics property, attributed revenue, or modeled influence was tested.

- [AthenaHQ credit calculator](https://athenahq.ai/credit-calculator) — checked 2026-09-12. AthenaHQ's public calculator assigns one credit to ChatGPT, Google AI Overview, and Perplexity responses and five to Claude, Grok, DeepSeek, Meta AI, and Mistral; enabling fan-out adds three variations and multiplies projected use by four. Public UI and weighted scenarios were checked. No account usage, invoice, persona configuration, add-on purchase or entitlement was tested.

## Product next step

Inspect a reviewed change at https://rankecho.io/sample-fix and the Fix Engine at https://rankecho.io/product/fix-engine. Full-page writing is separate and requires a paid base plan plus a content add-on: https://rankecho.io/pricing/content.
