Cresca Success Stories: What Changed, Concretely
Case studies usually read the same way: a bold metric, a testimonial, a call to action. That format teaches you nothing, because the numbers are selected after the fact and the process that produced them is left out. What follows describes three common scenarios in those terms instead: the problem, what was actually changed, and what improved.
Scenario one: a SaaS team with an unmanaged list
The problem. A B2B software company had accumulated contacts across three years and two marketing tools. Their contact count had grown past what they were actively mailing, they were paying for a tier they did not need, and their bounce rate was climbing. The list had never been cleaned because nobody could identify which contacts were real.
What changed. They stopped adding contacts for a month and spent that time auditing the list instead. Contacts were classified by last engagement date and by source. Addresses that had hard-bounced were suppressed permanently. Contacts with no engagement in 18 months were moved to a separate re-permission campaign rather than being mailed again as part of the main list.
What improved. Their mailable list fell substantially, which moved them down a pricing tier rather than up. Their bounce rate dropped because invalid addresses were no longer being attempted. Delivery to the remaining contacts improved, since mailbox providers weight engagement rates across a sending domain and a cleaner list raises them.
Nothing about that process required new tooling. It required stopping the inflow long enough to see what was already there.
Scenario two: an ecommerce store with no post-purchase flow
The problem. A small online retailer was sending a weekly newsletter and nothing else. Every customer acquired was mailed the same broadcast regardless of what they had bought, and there was no sequence triggered by a purchase or an abandoned cart.
What changed. They built three automations before touching the newsletter. A post-purchase sequence confirming the order and setting expectations. A cart abandonment workflow firing an hour after abandonment with a single reminder, not a discount. A replenishment trigger for consumable products, timed to the customer's actual reorder interval rather than a fixed 30 days.
What improved. The measurable change was in repeat purchase rate among the cohort that entered the post-purchase sequence, compared against customers from the preceding period. The cart abandonment workflow recovered a meaningful share of abandoned carts, and because it was built to fire once rather than as a discount sequence, it did not train customers to abandon carts deliberately.
The newsletter still runs. The point is that the newsletter was not the highest-return channel, and it was the only one being used.
Scenario three: an agency managing multiple client accounts
The problem. An agency ran email for around a dozen clients, each with its own sending domain and its own approach to authentication. Onboarding a client took weeks, usually because DNS changes sat with whoever controlled the domain and nobody was tracking which records were still outstanding.
What changed. They standardised the onboarding process: a single checklist covering SPF, DKIM and DMARC for each client domain, with authentication status checked continuously rather than only at setup. They also standardised reporting categories across clients, so they could tell which campaigns were working without rebuilding the analysis each time.
What improved. The main change was not a metric but a reduction in incidents. Previously, authentication failures were discovered when a client noticed poor delivery. With continuous checks, a misconfigured record surfaced before a send rather than after.
What these have in common
None of the three were fixed by a feature the team was not already paying for. In each case the work was to stop, look at what was already happening, and change a process.
The recurring pattern is that the visible activity, the weekly newsletter, the campaign calendar, was not where the problem or the opportunity was. In all three cases the improvement came from something that ran without attention: list hygiene, a triggered sequence, an authentication check.
On numbers
This article deliberately avoids specific percentage improvements, because a figure without its baseline, time period and cohort is not evidence. If you want to know whether something would help your account, the useful question is not what result someone else got, but whether your list is clean, whether your authentication is current, and whether your triggered sequences exist at all.
Pricing
Everything described here runs on standard plans:
| Plan | Price | Contacts | Emails / month |
|---|---|---|---|
| Free | $0 | 50 | 50 |
| Professional | $29/mo | 5,000 | 5,000 |
| Premium | $49/mo | 25,000 | 25,000 |
| Ultra | $99/mo | 55,000 | 55,000 |
What to ask a reference customer
If you talk to an existing customer of any platform, ask about the unglamorous parts rather than the features. How often does something break, and how do you find out? What happens when delivery to a specific recipient fails, and can you see why?
How long does it take to export your list? Has a pricing change caught you out?
Those answers differentiate platforms far better than a feature list, because they describe what operating the product is actually like.
A realistic migration picture
Moving platforms takes longer than expected in one specific way: the list. Exporting contacts is quick; deciding which of them are worth keeping is not. Budget the time for the audit, not the export.
Automations do not migrate. Every platform models triggers, conditions and delays differently, so a workflow will need rebuilding even if the logic is simple. Expect to rebuild your highest-value sequences by hand and to run both platforms in parallel briefly while you verify the new ones.
Templates usually do not migrate cleanly either, because layout formats differ. Budget for rebuilding the three or four formats you actually reuse.
Why we avoid percentages in these writeups
Three reasons, and they apply to any case study you read including ones about competitors.
First, the baseline is usually unknown. "Open rate increased 40%" means something different from 12% to 17% than from 40% to 56%. Without the starting point the figure conveys almost nothing.
Second, the period is usually unstated. A metric measured over a week after a change includes novelty effects; the same change measured after three months typically shows a smaller, more honest result.
Third, the cohort is frequently undefined. A result among engaged subscribers is not comparable to a result across an entire list, and case studies rarely say which was measured.
If a platform publishes a specific improvement, the useful follow-up questions are: from what baseline, over what period, among which contacts.
What separates a scenario that works from one that does not
Across the three cases above, the differences that mattered were not about tooling.
- Someone owned the maintenance. List hygiene and authentication checks both decay without an owner. In each scenario a specific person was responsible.
- The team stopped adding volume long enough to look. Every fix began with a period of not growing the list.
- Triggered sequences existed at all. In two of the three, the largest improvement came from an automation that had simply never been built.
The short version
Three scenarios, one pattern: the fix came from maintenance and triggered sequences rather than from campaign activity. Audit the list before growing it, build post-purchase and abandonment automations before optimising broadcasts, and check authentication continuously rather than at setup. None of it requires a higher tier.
Continue learning
Related Cresca resources
External references