Marketing database & segmentation
Marketo's headline price is set by mailable contact count, so every integration that writes a row, and every stale record you forget to purge, costs you.
What people actually say
✕Marketo's pricing model is based on the number of contacts in the database, and database growth alone can push an organisation into a higher tier even when campaign volume stays constant.
Source: Default, Marketo pricing breakdown ↗✕Going above your contracted tier results in a hefty increase at renewal and limited negotiation power — staying under tier is essentially a contractual obligation, not a UX nudge.
Source: Marketo Community, navigating the renewal process ↗✕Database overages and API-usage overages are listed as the headline hidden costs of running Marketo, alongside paid add-ons and the operational hours you pay specialists to keep the DB clean.
Source: Default, Marketo pricing breakdown ↗
Your contact list is just rows in a Postgres schema you own — hosting 50,000 or 5,000,000 rows costs roughly the same handful of pounds per month. Segmentation is SQL or Drizzle queries you can test in CI, with materialised views for the slow ones. No contact-tier multiplier, no quarterly purge-or-pay anxiety, no negotiation power lost to overages.