<?php
$page_lang = 'en';
$page_title = 'Case study: B2B SaaS in Mexico uses merch to grow the account';
$page_description = 'B2B SaaS company expanding in Mexico: onboarding kits for new accounts, channel-partner gifts, customer-success material and annual event swag.';
$og_image = '/assets/images/og-case.png';
$page_section = 'case-studies';
$page_slug = 'saas-growth-merch-en';
$labels = [
    'name' => 'Name',
    'name_placeholder' => 'Who should we contact?',
    'contact' => 'Work email',
    'contact_placeholder' => 'you.name@saas.mx',
    'company' => 'SaaS company',
    'company_placeholder' => 'Legal name',
    'message' => 'Tell us the scope',
    'message_placeholder' => 'Programme size, active accounts, partners, regions and items under consideration.',
    'submit' => 'Request quote',
    'sending' => 'Sending…',
    'turnstile_error' => 'Security check failed. Please reload the page.'
];
require __DIR__ . '/../../../includes/header.php';
?>
<link rel="alternate" hreflang="es" href="https://corp-merch.com.mx/es/pages/case-studies/saas-growth-merch">
<link rel="alternate" hreflang="en" href="https://corp-merch.com.mx/en/pages/case-studies/saas-growth-merch">
<link rel="alternate" hreflang="ru" href="https://corp-merch.com.mx/ru/pages/case-studies/saas-growth-merch">
<nav class="breadcrumbs"><a href="/en/">Home</a><span class="sep">&rsaquo;</span><a href="/en/pages/case-studies/">Case studies</a><span class="sep">&rsaquo;</span><span>SaaS growth</span></nav>
<section class="hero"><div class="container"><div class="hero-content"><p class="eyebrow">Case study &middot; B2B SaaS</p><h1>A B2B SaaS platform uses merch to move pipeline and reward channel partners</h1><p class="hero-subtitle">How a software-as-a-service company with 1,800 active accounts in Mexico moved from buying swag per event on an urgent basis to running an annual programme with onboarding kits for new customers, channel-partner gifts, customer-success material and pieces for the annual customer event. Figures are anonymised but representative of a real programme coordinated from the Mexico City hub.</p><div class="hero-cta"><a class="btn btn-primary" href="#contact-form">Request a similar quote</a><a class="btn btn-secondary" href="/en/services/saas-merch/">SaaS merch service</a></div></div></div></section>

<section class="section"><div class="container"><h2>The programme at a glance</h2>
<dl class="event-facts">
<dt>Client</dt><dd>Vertical B2B SaaS company with operations in Mexico and LATAM (composite case)</dd>
<dt>Industry</dt><dd>Software as a service, enterprise segment with average ticket between USD 12,000 and USD 80,000 annually</dd>
<dt>Coverage</dt><dd>1,840 active accounts, 65 channel partners, customer success team of 22</dd>
<dt>Volume</dt><dd>4,620 pieces delivered across 12 months, in four lines with independent calendars</dd>
<dt>Period</dt><dd>2024-2025 annual cycle, with four waves aligned to quarterly sales kickoffs and the annual customer event</dd>
<dt>Compliance</dt><dd>Internal gift policy, AML guidance for gifts to public officials when applicable, and per-recipient traceability</dd>
</dl>
<p>Marketing and commercial operations used to buy swag separately, every time a quarterly kickoff or an event approached. Quality varied from supplier to supplier, corporate colours sometimes drifted off tone, and the customer success team received a different kit every two months to hand to accounts moving up plan tiers.</p>
</div></section>

<section class="section section-alt"><div class="container"><h2>Context and problem</h2>
<p>The first problem was brand. The company had rebranded two years earlier and the institutional palette — two specific blues identified by Pantone number — was never reproduced the same way across orders. A tee could come out cobalt instead of the institutional blue, a notebook could land in a grey tone not in the manual. Marketing noticed that at some accounts the first visual contact with the brand was through swag outside the palette.</p>
<p>The second problem was budget. Every team — marketing, operations, customer success, events — bought through its own supplier and its own budget. Total annual merch spend was high, visibility into what was delivered to whom was zero, and there was no way to know whether swag was actually moving pipeline or just being given out by inertia.</p>
<p>The third was logistics coordination. A SaaS company with 1,800 active accounts in Mexico onboards new customers every week, refreshes kits quarterly and gifts channel partners who can be anywhere in the country. Without a single interlocutor, every team managed its own courier and its own delivery times, with uneven outcomes.</p>
</div></section>

<section class="section"><div class="container"><h2>How we approached it</h2>
<p>The programme was built as an annual catalogue with four lines and independent calendars. Line A was the onboarding kit for new accounts: a rigid cardboard box with magnetic closure, an A5 hard-cover notebook, a roller pen, an isotype sticker and a welcome card carrying the new customer's name. The box was delivered in the first kickoff call with the customer success team, within 14 days of contract signature.</p>
<p>Line B was the channel-partner gift: a technical backpack with laptop compartments, a stainless thermal bottle with a laser engraving of the partner's name and a hand-stitched notebook with a fabric-wrapped cover in the institutional colour. This line shipped at the close of every quarter to partners who had hit channel quota, with SKU selection by partner tier (silver, gold, platinum).</p>
<p>Line C was customer-success material: an organic cotton tote with the embroidered isotype, a pique tee with the name of the internal programme and a sticky-notes set in the institutional palette. This line was handed to the CS team so they could gift it during quarterly review meetings with strategic accounts, without going through an external courier.</p>
<p>Line D was the annual customer event material: a jute tote with screen print, a combed-cotton tee, a ceramic mug with engraving and an A5 notebook carrying the event agenda. This line was delivered on site, at event check-in, counted per table and replenished daily from the regional distribution centre.</p>
<h3>Annual calendar</h3>
<p>The four lines ran on different calendars but with one interlocutor and one catalogue. Line A ran continuously, with production every 14 days and delivery to the client's office or to the lead CS's home. Line B activated four times a year, aligned with quarter close. Line C shipped to the CS team at the start of every fiscal quarter, without external courier. Line D concentrated in the two weeks before the annual event, with delivery to the host hotel.</p>
<p>Each shipment left with a CFDI 4.0 stamped by Corp-Merch, with the Carta Porte 3.0 complement when the move crossed SAT thresholds. Per-recipient traceability lived on a consolidated sheet the commercial operations team pulled monthly to cross-check against the CRM, without asking Corp-Merch for reports each time.</p>
</div></section>

<section class="section section-alt"><div class="container"><h2>Results, figures and timeline</h2>
<p>The 4,620 pieces shipped across the 2024-2025 cycle without palette deviations detected in brand audit. The promise to the CS team to deliver the onboarding kit within 14 days of signature was met on 96% of cases, with a real average of 9.4 days.</p>
<p>Commercial operations consolidated annual merch spend through one supplier and one monthly report. Average unit cost dropped 14% versus the previous cycle, mostly because the closed catalogue let us consolidate fabric, cardboard and stainless purchases, and because the four annual waves shipped from the same distribution centre on a single price table.</p>
<p>Marketing measured, through a survey sent to 240 new accounts, that brand recall of the onboarding kit was still at 71% at the 90-day mark. The channel-partner gift correlated with a 9-point improvement in the partner programme's Net Promoter Score, compared with partners who had not received a gift the previous quarter.</p>
<h3>What the client measured</h3>
<ul>
<li>14-day onboarding kit window met: <strong>96%</strong>, average <strong>9.4 days</strong>.</li>
<li>Brand recall at 90 days: <strong>71%</strong> of 240 new accounts surveyed.</li>
<li>Average unit cost: <strong>-14%</strong> versus the previous cycle.</li>
<li>Active SKUs: <strong>14 pieces</strong> across four lines.</li>
<li>Partner-programme NPS for partners with gift: <strong>+9 points</strong> vs partners without.</li>
</ul>
</div></section>

<section class="section"><div class="container"><h2>What we learned</h2>
<ul>
<li><strong>The annual catalogue changes the conversation.</strong> When every team knows what they can ask for and when, the urgent purchase goes away and off-palette swag stops being the brand's first impression.</li>
<li><strong>Per-recipient traceability is worth as much as the piece.</strong> When commercial operations can cross merch with the CRM, spend stops being opaque and becomes a retention lever.</li>
<li><strong>The channel-partner gift is what moves NPS.</strong> Partners who received a quarterly gift improved their NPS by nine points over those who did not, enough to justify the cost of the programme.</li>
</ul>
</div></section>
<script type="application/ld+json">{"@context":"https://schema.org","@type":"Article","headline":"Case study: B2B SaaS in Mexico uses merch to grow the account","datePublished":"2026-09-30","inLanguage":"en-US","author":{"@type":"Organization","name":"Corp-Merch"},"publisher":{"@type":"Organization","name":"Corp-Merch"},"mainEntityOfPage":"https://corp-merch.com.mx/en/pages/case-studies/saas-growth-merch"}</script>
<?php require __DIR__ . '/../../../includes/footer.php'; ?>