Skip to content

fix(pricing): GOAT card and comparison table disagree on included credits #1032

Open

Description

@coygeek

Summary

The public pricing page gives two different included-credit amounts for the same GOAT plan. Its plan card says $80, while the GOAT column in its comparison table says $70. This leaves a prospective subscriber unable to determine the included amount from that page alone. This report concerns public pricing copy; it does not assert an error in actual billing or account entitlements.

Steps to reproduce

  1. Open the public pricing page in a browser and wait for it to finish loading.
  2. Read the included-credit amount immediately below the GOAT subscription price.
  3. Scroll to the plan-comparison table and read the Monthly credits row under GOAT.
  4. Compare the two amounts for the same plan. The mismatch is also present in the initial HTML response.

Expected behavior

The GOAT card and the GOAT comparison-table cell should state a consistent included-credit amount, or clearly explain any distinction if the two amounts describe different benefits. Both locations currently describe included or monthly credits for the same plan.

Actual behavior

The GOAT card says $80 in credits included. The comparison table's GOAT column gives $70 in the Monthly credits row. The mobile comparison markup also associates $70 with GOAT. The mismatch remains after JavaScript finishes loading. No account or billing action was performed, so these observations do not establish which amount is the intended entitlement.

Evidence

  • Expected source: The public pricing page presents both the GOAT card and the per-plan comparison table as descriptions of the same subscription.
  • Failure source: On that page, the card's included-credit line gives $80, while the Monthly credits row under GOAT gives $70. Both the HTTP response and the settled browser output show the disagreement.
  • Evidence provenance: observed
  • Local verification: reproduced
  • Reproduction completeness: complete

The comparison table orders the columns as Go, GOAT, Pro, Max 10x, and Max 20x. Its Monthly credits values are $10, $70, $80, $150, and $300 respectively, so the $70 cell belongs to GOAT rather than the adjacent Pro plan.

Restoration check

Reload the pricing page and compare the GOAT card with its Monthly credits cell in both the initial HTML and settled browser output. Both should state the intended included-credit amount consistently. Check the mobile comparison representation too. A fix should preserve the distinction between GOAT and the adjacent Pro column rather than merely changing the column association.

Runtime or environment

The live website was fetched on 2026-10-15 with curl and inspected in a JavaScript-enabled Chromium browser at a desktop viewport. Command Code Version: not applicable to this website display; the CLI was not executed. Operating System: Other, because this is public website content. The website deployment revision is not exposed by the inspected pages.

Triage assessment

  • Impact level: P2
  • Assessment status: supported
  • Impact basis: The public purchase-comparison page gives conflicting monetary benefits for the same plan, affecting the information available for a subscription decision. Actual entitlement and billing correctness were not tested.
  • Workaround status: unverified
  • Workaround basis: The conflicting page cannot establish which amount is intended. Asking support may clarify it, but no support response or account entitlement was checked.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions