Product
Routing, revenue truth, and throughput in one system.
From ingest through delivery and billing—so high-volume teams stop reconciling ghosts and start steering with evidence.
- Rules that match real deals. Contracts, caps, targeting, and dedupe—not a dumb router.
- One ledger. Transactions, pivots, and statuses tied to the same outcomes finance sees.
- Built for load. APIs, webhooks, and schedules that keep moving when traffic spikes.
30 days · subset of traffic · no long-term lock-in
What the platform is
One path from lead in to buyer out.
Supasend is the operating layer on top of your marketplace: it models buyers, contracts, pricing, quotas, and targeting, runs ping/post and direct delivery, captures every outcome with reasons, and rolls revenue into reporting your ops and finance teams can share.
- Ingest & qualify. Capture leads with the fields and compliance signals your buyers expect.
- Route & deliver. Apply contract rules, caps, dedupe, and schedules; post to buyers without blocking your front end.
- Diagnose & bill. Standardized statuses, failure reasons, transactions, pivots, and exports when someone asks “why?”
The full loop serious lead businesses run every day.
Routing & rules
Enforce the deal you made with every buyer.
When you are past a handful of buyers, fairness and SLAs live in the details: caps, dedupe windows, and pricing that match what contracts actually say.
Stop paying to send the same lead twice
Buyer- and contract-level dedupe plus quotas on ping so you do not torch buyer trust—or your margin.
Rules you can explain in an audit
Dynamic pricing, contract terms, Lua where you need transforms—encoded where they run, not buried in a spreadsheet.
Right lead, right destination
Targeting, filters, and schedules so campaigns map to the buyers who are supposed to see them.
Revenue & reporting
See which buyers, campaigns, and offers actually pay.
Optimization dies when ops sees queues and finance sees spreadsheets. Supasend ties billing to the same events that drove each outcome.
Numbers finance does not have to rebuild
Transaction records so payouts and balances trace back to real posts. Not manual reconciliation marathons.
Slice the business the way you think about it
Pivot by buyer, contract, campaign, offer, and lead type. Exports when you need to drop into a model.
Know why a lead did not monetize
Shared statuses and rejection reasons so the same story shows up in ops, buyer conversations, and retros.
Buyer Impact Report
See which buyers create lift, and which quietly burn your network.
Operators can pull up any buyer over any date range and see exactly how they behave in your auctions: how often they are in the mix, where their bids usually land, and what that behavior actually does to revenue across your marketplace.
Full buyer profile, not vibes
Total pings, posts, and revenue, share of auctions where they are the top bidder, and their average bid position (mean, median, and mode) so you can see if they live at the top, middle, or bottom of the marketplace.
Contract and lead-type clarity
Break performance down by contract and lead type—accept rates, coverage, and revenue contribution—so you know where a buyer is a healthy partner and where they are misaligned or dragging down outcomes.
Simple behavior labels ops can act on
Each contract gets a clear behavior label: Healthy partner, High-bid rejector, Bottom feeder, or Insufficient data. Based on bid rank, accept rate, and revenue, so reviews move from arguing anecdotes to agreeing on the same facts.
Catch high-bid rejectors early
Spot buyers who often win the auction but still reject: see how many of those high-bid rejects likely turned into tainted leads, and the associated burned revenue your network never recovered elsewhere.
Unique coverage vs. network drag
Separate the revenue you only earn because this buyer exists (unique-coverage pings where they are the sole candidate) from tainted revenue and leads created when they overbid and then walk away—plus a directional net impact estimate if you were to reallocate their volume.
State view where it matters
When US State is on the lead, see per-state volume, accept rates, revenue, unique coverage revenue, and tainted leads. So you can decide whether to scale, coach, or turn a buyer off in specific geos instead of blunt, all or nothing moves.
The result is an admin view that answers the hardest question in lead ops: which buyers quietly help clear inventory, and which overbid, reject, and destroy value across your network.
Delivery & integrations
Keep traffic moving without flying blind.
Heavy work belongs off the request path: async delivery, webhooks with sane thresholds, and alerts when a buyer setup drifts—not every harmless blip.
Front ends stay fast when volume hits
Ping/post and direct post flows push business logic to workers so surveys and forms are not hostage to downstream latency.
Everflow stays aligned with how you sell
Native integration so offers and campaigns sync with the system that actually routes and bills the lead.
Catch buyer misconfigurations early
Slack alerts for buyer audit signals—so the team fixes filters and caps before they silently drain revenue.
In production
It's not slideware. We run Supasend on real traffic before we talk pilots with anyone else.
Compared to our previous lead stack, monthly tooling spend is down roughly 88%, without giving up the controls we needed at scale.
What we operate on it today
100+
Active lead buyers managed on the platform
460+
Lead routes configured to sell leads
170+
Affiliate campaigns supported
How it matured
Shipped in stages. Each one driven by real load.
Supasend started as an internal system when “route the lead” tools stopped matching compliance, volume, and reporting pressure. It hardened because it had to run the business—not win a feature checklist.
- Late 2024 – early 2025 Core rails: workers, Postgres, admin, buyers and contracts, dedupe, ping quotas, compliance-oriented fields, webhooks, accounting skeleton, API tokens—so the model matched how leads actually move.
- Spring 2025 Delivery realism: ping/post and direct post, deeper filters and diagnostics, ping caching and expiry, async work off the web thread, email and integration alerts—volume stopped stalling the team.
- Mid 2025 Revenue surface: dashboards and buyer/campaign reports, exports, audit tooling, credit limits and cherry-pick logic, transaction refinements—ops and finance could argue from the same events.
- Mid-late 2025 Scale and isolation: scheduled delivery MVP, suppression in the path, contract compliance hooks, rate-limited Slack noise, then multi-tenant data paths and tenant-scoped workers.
- Late 2025 - 2026 Performance and API polish: indexing and faster reports, safer concurrent revenue and webhooks, bulk coverage and public API specs, per-tenant tasks and admin scoping, webhook thresholds and delivery diagnostics.
Next in this document: Compliance & consent and Security & isolation. It covers how we built for regulatory pressure and clean tenant separation.
Regulatory posture
Stay disclosable when consent rules move—not as a retrofit.
When regulators tightened 1-to-1 consent, operators had to show clearly who the consumer opted into and under what terms. Many legacy “lead distribution” stacks were never modeled for that level of transparency.
Where traditional platforms cracked
- Routing frozen in code. Changing disclosures or buyer lists meant dev cycles—not same-day operational reality.
- Consent treated as an afterthought. Tags and side tables instead of first-class relationships to buyers and routes.
- Reporting in a different language than compliance. Hard to connect consent, routing decisions, and revenue in one story.
How Supasend is shaped to adapt
Disclosures stay tied to real routing
Buyer contracts and routing rules are the spine of the system—so who you can sell to and how is encoded where ops actually works, not in a PDF nobody updates.
Consent lives next to the lead—not bolted on
Consent and buyer relationships are core data alongside ping/post and delivery—so audits and buyer questions map to the same records your team uses daily.
Every decision leaves a thread you can follow
See which buyers were in play, who received the lead, and why—so you are not reconstructing intent from spreadsheets after the fact.
We use the guided pilot to map how your current flows line up with today’s expectations—and where this model removes drag.
Multi-tenant
One platform for many brands—without mixing their worlds.
Agencies, networks, and multi-brand operators need the efficiency of shared infrastructure with the confidence that customer, buyer, and brand data never bleed across tenants.
Environments that do not cross-pollinate
Each customer runs in a separated environment—configuration and data stay on the right side of the wall.
Access scoped to the tenant you belong to
Admins and users see only the customer context they are assigned—reducing accidental cross-client exposure.
Automations run on your data only
Scheduled deliveries and workflows execute against your tenant’s setup—no cross-customer side effects from shared jobs.
Built for how agencies actually onboard
Add clients without a new stack each time
Onboard brands or buyers under isolated tenants while reusing the same delivery, alerting, and reporting patterns you already trust.
Same playbooks, isolated data
Train the team once on how Supasend runs—apply it per customer without commingling their marketplace.
Oversight without shared buckets
See what is live and how domains map—while raw buyer and lead data stay partitioned for reviews and partner questionnaires.
Stricter buyer or partner requirements are a normal topic in the pilot—we walk your isolation story against what you need to prove.
Guided rollout
30 days. Evidence—not slides.
We mirror a subset of buyers and campaigns, compare outcomes to what you run today, and show where you earn, leak, and stall. If there is no actionable lift, you stop.
Discovery
Map routing, integrations, and the failure modes you already worry about.
Weekly reviews
Operational and revenue signals you can act on within the same week.
Clear stop
No long-term lock-in—continue only if the pilot earns its keep.