# Infrastructure for launches with thousands of sign-ups

> Thousands of sign-ups from five channels, with no duplicates, assigned to the sales team and measured while the launch is live.

Source: https://fcgsystems.es/en/case-studies/high-volume-launch-infrastructure/ · FCG Systems

- Client: Info-product launch operation
- Year: 2024–2025
- Services: [Launch infrastructure](https://fcgsystems.es/en/services/launch-infrastructure/), [Data, tracking and analytics](https://fcgsystems.es/en/services/data-tracking-analytics/), [Academy and automation](https://fcgsystems.es/en/services/process-automation/)

## Context

An info-product business that runs on launches: intensive campaigns that pack most of its lead capture and sales into a few days.

Sign-ups arrive at the same time from YouTube, Instagram, Telegram, ads and email, with a sales team and several communities waiting on the other side.

## Problem

With thousands of sign-ups in a few days, small errors multiply: the same person registered through two channels, leads called by two reps and sources that can’t be compared.

Launch numbers were pieced together afterwards, when they could no longer help move budget or balance the team’s workload.

## Constraints

- Traffic peaks concentrated in short windows, with no room to fix things live.
- Five acquisition channels with different formats and source data.
- A sales team that needed clean leads right away, not the next day.

## System built

- **Multichannel tracking:** Every sign-up comes in tagged with its channel and campaign, whether from YouTube, Instagram, Telegram, ads or email.
- **Deduplication:** Repeat sign-ups are detected and merged before they reach the CRM or get assigned.
- **Sales assignment:** Leads distributed to the team by rules and capacity, so each contact has a single owner.
- **Community systems:** Users distributed across the launch communities without overloading any group.
- **Launch dashboards:** Sign-ups, assignments and sales by source, visible while the campaign is live.

## Result

The launch now runs with one record per person, one sales owner per lead and a source-level view available during the campaign.

Detailed figures for this operation aren’t published. What remains is a system that carries over from one launch to the next instead of being rebuilt every time.

## Learnings

- Deduplication comes before assignment, never after. Unwinding a distribution full of duplicates costs far more than preventing it.
- A launch gets load-tested before registrations open. There’s no time to diagnose anything during the peak.
- Problems that come back every launch are product candidates. That’s how CommunityRedirect started.

Stack: GA4, Google Tag Manager, Airtable, Postgres, WhatsApp, Telegram, Docker