63 / 100

Zenhub pricing teardown

https://www.zenhub.com/pricing

Zenhub's pricing page is clean and straightforward with a classic three-tier Free/Teams/Enterprise structure built around GitHub-native project management. The page does a decent job of communicating value through a detailed feature comparison table and FAQ, but misses several psychological anchoring opportunities — no plan is visually highlighted as 'recommended,' and the annual discount is undersold despite being substantial (33%). The page balances self-serve conversion for smaller teams with enterprise lead-gen, but the lack of a 'most popular' badge and weak visual hierarchy between tiers leaves conversion potential on the table.

Tier structure

Free

$0/user/mo

Teams

$4.99/user/mo (annual) / $7.50/user/mo (monthly)

Enterprise

Let's talk (annual only)

Value metric

per seat (per user per month)

How limits scale

Team Workspaces 1 → Up to 10 → Unlimited
Users Up to 50 → Up to 50 → Unlimited
Number of Issues Up to 250 → Up to 5,000 → Unlimited
Connected Repositories Up to 2 → Up to 50 → Unlimited
Connected GitHub Organizations 1 → 1 → Up to 10

Escalation logic

Classic good-better-best escalation: Free is capped for small teams with minimal limits, Teams unlocks AI features, automation, and reporting for growing teams, and Enterprise removes all caps while adding security, compliance, and dedicated support. The jump from Free to Teams is feature-gated (AI, advanced reporting) as much as limit-gated.

Psychological anchors

  • Strikethrough / charm pricing on annual toggle — Teams plan shows $7.50 struck through with $4.99 as the annual price, creating a visible savings signal; however the toggle defaults to annual, so the higher monthly price is shown as the 'original' rather than the default experience.
  • Enterprise as high-anchor / price anchor — Enterprise has no public price ('Let's talk'), which makes the $4.99 Teams plan feel affordable by contrast and anchors perception of value upward.
  • Free tier as entry anchor — A permanent $0 free tier lowers the barrier to entry and seeds the funnel, with a 14-day Teams trial auto-applied on signup to drive upgrade consideration.
  • Annual discount framing — FAQ explicitly frames annual billing as '4 months free (33% off)' — stronger than the typical 17-20% SaaS norm — but this framing is buried in the FAQ rather than prominently displayed on the pricing cards.
  • Social proof / testimonial anchor — A Roberto Velazquez (Red Hat) testimonial citing '30% productivity increase' and '4-6 hrs/week saved per user' is placed below the pricing section to reinforce ROI before the final CTA.
  • No 'Most Popular' badge — Neither Free nor Teams is badged as recommended or most popular, missing a classic decoy/anchoring tactic that would direct attention to the Teams plan.

What this page is optimizing for

The page is primarily optimized for self-serve conversion of small-to-mid-size GitHub teams into the Teams paid plan, evidenced by transparent pricing, instant 'Get started' CTAs, and an auto-applied 14-day trial. A secondary enterprise lead-gen track exists via 'Book a call' and 'Let's talk' CTAs, supported by security/compliance content and a dedicated support manager section in the lower page.

Red flags

  • No plan is visually highlighted or badged as 'recommended' or 'most popular,' removing a key conversion nudge toward the Teams plan.
  • Free and Teams both cap users at 50 — this identical user limit across two tiers is confusing and weakens the upgrade trigger narrative between them.
  • The 33% annual discount is only clearly articulated in the FAQ, not on the pricing cards themselves, causing most visitors to miss the strongest savings argument.
  • The annual/monthly toggle defaults to annual, which means visitors see the discounted price first and may not realize the monthly price is significantly higher — reducing perceived urgency to commit annually.
  • Enterprise pricing is fully opaque with no price range or 'starting at' signal, which may deter mid-market buyers who self-qualify before contacting sales.
  • The comparison table is very long (50+ rows) and may overwhelm visitors rather than helping them quickly differentiate tiers — a condensed 'key differences' summary is absent.
  • CTAs ('Get started', 'Book a call') are generic and don't reinforce the value proposition of each specific tier.

Best-practices scorecard

What works · 2

  • FAQ or objection handling — A dedicated FAQ section addresses trial availability, billing mechanics, annual discounts, payment methods, and currency — covering the most common pre-purchase objections.
  • Trust signals present — SOC 2 Type 2 compliance badge, Red Hat testimonial with quantified ROI, and Stripe payment processing mention all serve as credible trust signals.

Half measures · 5

  • Visible prices — Free and Teams prices are clearly visible, but Enterprise has no public price at all, which is standard for enterprise but limits self-qualification.
  • Annual discount offered — An annual option exists with a meaningful 33% discount, but it's the default view and the savings framing is buried in the FAQ rather than prominently called out on the pricing card.
  • Value metric matches usage — Per-seat pricing fits a team collaboration tool, but the identical 50-user cap on both Free and Teams tiers creates an awkward limit that doesn't clearly reward upgrading on the user dimension.
  • Tier differences are scannable — The comparison table is comprehensive but extremely long; there is no short summary card or 'key differences' callout to help visitors quickly understand what they gain by upgrading.
  • Clear CTAs per tier — Each tier has a CTA ('Get started', 'Book a call') but the wording is generic and doesn't reinforce the specific value or urgency of each plan.

What's missing · 1

  • Clear recommended tier — No 'Most Popular' or 'Recommended' badge appears on any plan; the Teams plan — the obvious conversion target — is not visually distinguished from Free.