Number of Seats/Users: iBuildApp 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 iBuildApp 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 iBuildApp. iBuildApp reserves discounts for new customers or those not currently under promotional pricing.

Volume or Usage Commitment: iBuildApp 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 iBuildApp. Such companies are often in a position to negotiate for better pricing.

Early Renewal or Prepayment: iBuildApp 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 iBuildApp sits in a “strong idea, but uneven execution” category, with clear savings potential if you negotiate the right terms.

Key positives our Spendbase clients highlight:
– Very easy, no‑code app creation
– Fast build times – APKs available within minutes
– Ability to publish under your own Apple/Google developer accounts
– Large choice of templates, widgets and integrations (ecommerce, media, social)
– Previewer to test apps on simulated devices
– Option for a lifetime support plan on a single app (good value for a flagship app)
– Potential to resell apps and generate extra revenue

Main pain points our internal data shows:
– Reliability:
– Features sometimes “don’t work as planned”
– Occasional build failures or downloads stuck partway
– Some layout/display issues on Android devices
– Support:
– Heavy reliance on Zendesk tickets
– Response times can feel long for urgent outages
– Submission service not consistently working for everyone
– Billing & contracts:
– Auto‑renew charges even when clients believed they had disabled renewal
– No refund policy enforced quite strictly
– Lack of proactive billing emails/invoices when charging cards
– Perceived value:
– Pricing seen as “on the high side” for the stability and support level
– Some apps look “clunky” and not very polished without extra work

From a Spendbase discount and procurement perspective, our internal data suggests a few smart levers to pull:

1) Pricing & plan structure
– Use the mixed satisfaction on stability and support to negotiate:
– Lower annual rates or volume discounts
– Credits or extended trial periods before committing long term
– Bundling the lifetime support plan for at least one critical app

2) Contract & billing protections
– Insist on:
– Clear opt‑out for auto‑renew and written confirmation when disabled
– Mandatory email notification before each renewal charge
– Documented refund/credit rules when services don’t work as advertised

3) Support guarantees
– Push for:
– Defined SLA for ticket response and resolution, especially for production outages
– Escalation paths beyond standard Zendesk queues

If you’re considering or already using iBuildApp, Spendbase can usually improve the cost‑to‑value ratio by tightening these terms and pushing down the effective price to match the actual reliability and support you receive.