Number of Seats/Users: Tower offers discounts based on the number of users or seats. A higher volume typically leads to a better discount structure, especially for enterprise-level usage.

Commitment to a Long-Term Contract: Discounts are often provided to companies that commit to using the service for a longer period (e.g., 1-year or 3-year contracts). A longer commitment shows Tower that the company is serious and willing to invest in the platform long-term.

No Active Discounts: Companies that are not already receiving other active discounts may have a better chance of qualifying for additional discounts from Tower. Tower reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: Tower offers discounts if you agree to a minimum amount of usage or transaction volume. This could be based on data storage, transactions, or other metrics tied to how much you will use the platform.

Enterprise-Level Negotiation: Companies that qualify as “enterprise” due to their size or complexity (e.g., having large teams, multiple departments, or geographical presence) may be eligible for additional discounts from Tower. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: Tower often offers discounts if you renew early or prepay for the entire contract period. This is a common approach to securing a lower price.

Here at Spendbase our internal data shows that Tower is seen as a “daily-driver” Git tool that quickly becomes part of the core engineering toolkit, especially for macOS teams.

Based on what Spendbase clients tell us, the main positive themes are:

• User interface & ease of use
• Clean, intuitive, very “macOS-like”
• Drag‑and‑drop for branches, merges, cherry‑picks
• Clear visualization of history, diffs, and complex operations
• Confidence with complex Git tasks
• Interactive rebase, selective/partial staging, stash & reflog are heavily praised
• Makes merge conflict resolution far less stressful
• Great for people who know Git well but don’t want to risk mistakes in the CLI
• Onboarding & mixed-skill teams
• Non‑expert developers and even research teams can use Git safely
• UI for creating repos, merging, branching, etc., lowers the barrier to entry
• Ecosystem & integrations
• Works well with GitHub, Bitbucket, Azure DevOps and self‑hosted repos
• Good documentation, tutorials, and responsive support
• Many clients explicitly say the time saved justifies the subscription cost

At the same time, our internal data also highlights some consistent friction points:

• Performance constraints
• Noticeable lag or occasional freezing on very large repositories
• Platform gaps
• No Linux client
• Windows version historically behind macOS and only recently catching up (including dark mode)
• UX refinements needed
• Stashing, especially for untracked files, feels unintuitive to some
• Commit message box not ideal for longer messages
• Setup issues reported around SSH keys and 2FA
• Desire for clearer workflows/guardrails so people “can’t click themselves into trouble”
• Limited pull request features (e.g., assigning reviewers, inline comments)

Who benefits most, according to our clients:

• Teams that:
• Are heavily macOS-based
• Handle many branches and frequent rebases
• Have mixed Git skill levels and want a safer, visual Git layer
• Individual developers who:
• Live in Git all day and value speed and clarity
• Are willing to pay for a smoother, more confident workflow vs free tools

From a Spendbase discount perspective, this usually classifies Tower as a high-ROI, power-user tool, where negotiating team or multi-year plans often makes sense once it’s clearly embedded in the dev workflow.