<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd" xmlns:googleplay="http://www.google.com/schemas/play-podcasts/1.0"><channel><title><![CDATA[Alex Sergeev]]></title><description><![CDATA[A must-read for anyone building or scaling a dating app.
Practical insights on launching, monetizing, and growing real dating businesses.]]></description><link>https://alexsergeev.com</link><image><url>https://alexsergeev.com/img/substack.png</url><title>Alex Sergeev</title><link>https://alexsergeev.com</link></image><generator>Substack</generator><lastBuildDate>Sun, 22 Nov 2026 20:08:56 GMT</lastBuildDate><atom:link href="https://alexsergeev.com/feed" rel="self" type="application/rss+xml"/><copyright><![CDATA[Alex Sergeev]]></copyright><language><![CDATA[en]]></language><webMaster><![CDATA[alexsergeev@substack.com]]></webMaster><itunes:owner><itunes:email><![CDATA[alexsergeev@substack.com]]></itunes:email><itunes:name><![CDATA[@alexsergeev]]></itunes:name></itunes:owner><itunes:author><![CDATA[@alexsergeev]]></itunes:author><googleplay:owner><![CDATA[alexsergeev@substack.com]]></googleplay:owner><googleplay:email><![CDATA[alexsergeev@substack.com]]></googleplay:email><googleplay:author><![CDATA[@alexsergeev]]></googleplay:author><itunes:block><![CDATA[Yes]]></itunes:block><item><title><![CDATA[Email for Dating Apps: Deliverability, Retention, and Revenue]]></title><description><![CDATA[A founder&#8217;s guide to how email works, how to reach the inbox, and how to turn notifications into conversations and subscriptions.]]></description><link>https://alexsergeev.com/p/email-for-dating-apps-deliverability</link><guid isPermaLink="false">https://alexsergeev.com/p/email-for-dating-apps-deliverability</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Mon, 02 Nov 2026 16:02:53 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/cb34403c-3433-4d71-a1de-7a27c8c343a9_1672x941.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h1><strong>Why I care about email</strong></h1><p>I was configuring mail servers before I started building dating businesses.</p><p>While studying computer science at university, I worked part time as a system administrator. I set up Linux servers and email for organizations. SMTP and POP3 were things I had to make work. I also dealt with NNTP newsgroups, a separate system for discussions that people still used, and configured WinGate on Windows.</p><p></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><p>When someone could not receive a message, there was a concrete problem to investigate. A service had stopped. A name did not resolve. A server was rejecting a connection. A configuration that looked correct was wrong in one small but consequential way.</p><p>The interfaces have changed enormously since then. Hosted services handle much of the infrastructure. Gmail has become the default mailbox for many people. Sending an application email can be a single API request.</p><p>That convenience makes it easy to overlook what happens afterward.</p><p>Today, when I look at email in a dating product, I see a direct connection between infrastructure and growth. A verification message helps someone finish registration. A message notification helps two people continue a conversation. An appropriate reminder can bring a user back while a potential match is still interested.</p><p>If those emails arrive late, disappear into spam, or become annoying enough that people block them, the effect reaches far beyond an email dashboard. Fewer people respond. Conversations stall. Other users experience the product as inactive. Retention suffers.</p><p>In <a href="https://alexsergeev.com/p/retention-is-king">Retention is King: How to Balance Your Unit Economics</a>, I explained why retention determines whether acquisition costs can turn into a profitable dating business. In <a href="https://alexsergeev.com/p/how-to-actually-grow-a-dating-business">How to Actually Grow a Dating Business</a>, I described the user journey from registration to meaningful engagement. Here, I want to explain one of the technical foundations underneath those growth loops.</p><p>You do not need to become a mail administrator to understand this article. You do need enough understanding to choose your tools, ask useful questions, and recognize when a reassuring dashboard is showing you only part of the story.</p><p>At SkaDate, our usual stack is Amazon SES for transactional email and Sendy connected to Amazon SES for marketing email. I will use that setup throughout the article, while explaining the decisions that apply to other providers too.</p><h1><strong>The business outcome behind an email</strong></h1><p>Imagine a small dating app with a promising new conversation.</p><p>Anna sends Daniel a message. Daniel has already closed the app. The product sends an email telling him there is something to reply to. He returns that evening, responds, and Anna receives a notification of her own.</p><p>The value comes from the conversation continuing. The email helps that happen.</p><p>Now change one detail. Daniel&#8217;s email never reaches his inbox. He returns three days later. Anna has stopped checking. Both people can come away believing that nobody replies on this app, even though the original interest was mutual.</p><p>This is a hypothetical example, but it captures a practical problem: dating depends on coordination between people whose attention is elsewhere much of the time.</p><p>A large registration count can hide this problem. Your database may contain thousands of profiles while a particular user sees very few relevant, responsive people nearby. What matters is the availability of compatible people within a useful period of time. Product teams often call this marketplace liquidity. I explain the challenge of creating that initial network in <a href="https://alexsergeev.com/p/the-foundation-solving-the-cold-start">The Foundation: Solving the Cold Start Problem in Dating</a>. Email helps people return while other relevant people are still active.</p><p>Email can improve the timing of participation. It can also waste attention. Bringing a user back to an irrelevant recommendation, a deleted profile, or an already-read message teaches that user to ignore the next notification.</p><p>I therefore evaluate an email program at several levels. Can we reach the user? Does the message accurately describe something useful? Does the user return? Does a valuable action happen after the return? Does the program improve retention without generating excessive complaints or opt-outs?</p><p>Email and push are the two main notification channels in this technical series. For a mobile dating product, I would normally prioritize push for immediate events such as a new message or match, then use email selectively. Push puts the alert on the device where the app already lives, and a tap can return the user straight to the conversation. That can make responding easier for the user and reduce the business&#8217;s dependence on inbox placement, email volume, and email sending costs.</p><p>Large mobile apps make extensive use of push. <a href="https://www.help.tinder.com/hc/en-us/articles/115003340683-Managing-your-notifications">Tinder supports both push and email notifications</a>; its public documentation does not establish how often it emails every user. My recommendation is to use the channels according to the situation: a timely push for an active mobile user, and a useful email when push is unavailable or a different reminder is appropriate.</p><p>Permissions, delivery systems, and failure modes differ. Push requires permission and can be disabled; an uninstalled app cannot receive its usual app notifications. Email remains valuable for account communication, web users, and appropriate reactivation. Coordinate both channels so one event does not produce several redundant interruptions. This article focuses on email.</p><h1><strong>Where email lives</strong></h1><p>Start with four separate things: your application, a sending service, a mailbox provider, and an email client.</p><p>Your dating application knows that Anna sent Daniel a message. It decides whether to create a notification and what that notification should contain.</p><p>A sending service, such as Amazon SES or SendGrid, takes responsibility for attempting delivery. It connects to the receiving system, handles the transport, and produces information about delivery attempts and failures.</p><p>A mailbox provider stores the recipient&#8217;s email. For Daniel&#8217;s Gmail address, that provider is Google. For an employee using a company email address, the underlying provider might be Google Workspace, Microsoft 365, or another mail host.</p><p>An email client displays the mailbox. Apple Mail, Outlook, and a browser tab open to Gmail are examples of ways to read email. The client and the mailbox provider can be different companies. Someone can read a Gmail mailbox in Apple Mail.</p><p>That distinction matters when interpreting statistics. An Apple Mail open does not mean the recipient has an iCloud address. A company domain does not tell you which software the recipient uses to read its messages.</p><p>Your website host is another separate decision. Hosting a dating site on one cloud does not require using that cloud for employee mailboxes or application delivery. You can host the application in one place, send through Amazon SES, and receive support emails through Google Workspace.</p><p>For a founder, the useful question is who owns each part. Who decides to send? Who transports the email? Who stores the recipient&#8217;s mailbox? Who monitors failures? Confusion between those responsibilities leads to support conversations in which every vendor correctly explains that the problem belongs somewhere else.</p><h1><strong>SMTP, POP3, IMAP, and the browser</strong></h1><p>A protocol is an agreed set of rules that computers use to communicate. Email uses several, because sending a message and reading a mailbox are different jobs.</p><p>SMTP means Simple Mail Transfer Protocol. It is the core protocol used to submit and relay email. A sending server establishes a conversation with a receiving server, identifies the sender and recipients, transfers the message, and receives a response.</p><p>When your application calls an email provider&#8217;s HTTP API, your developers may never write SMTP commands. The provider still uses email transport protocols downstream. The API changes how you hand the message to your provider; it does not make the recipient&#8217;s mail system disappear.</p><p>POP3 means Post Office Protocol version 3. It retrieves messages from a mailbox. Historically, it was common to download mail to a desktop computer. Depending on settings, copies may remain on the server or be removed after retrieval.</p><p>IMAP means Internet Message Access Protocol. It supports working with a mailbox stored on the server, including folders and message state. It is useful when the same mailbox is accessed from a phone, laptop, and other devices.</p><p>Webmail adds a browser interface. Your browser communicates with the web service over HTTPS; the provider manages the mailbox and delivery infrastructure behind it. Gmail&#8217;s interface is therefore one layer of a larger system.</p><p>TLS encrypts connections between systems that support and negotiate it. It helps protect a message in transit over that connection. This is different from the domain authentication mechanisms we will discuss later, and from end-to-end encryption in which only the intended participants can decrypt the content.</p><p>The practical lesson is simple: POP3 and IMAP belong primarily to mailbox access. For a dating application&#8217;s outbound notifications, your team will mostly work with an email API or SMTP submission, DNS, authentication, delivery events, and recipient preferences.</p><h1><strong>Follow one message from the app to the inbox</strong></h1><p>Let us return to Anna and Daniel.</p><p>First, the application records Anna&#8217;s message. Next, it determines whether Daniel should receive an email. Perhaps he is currently reading the conversation. Perhaps he disabled message emails. Perhaps the account has been paused. The notification decision should account for those conditions.</p><p>If the email is appropriate, the application prepares it and hands it to a sending service. In our SkaDate transactional setup, it connects to the Amazon SES SMTP endpoint. Amazon SES also offers an API, which is another way software can submit mail. The important distinction is that the application requests the send; the sending service then attempts delivery.</p><p>Amazon SES accepting the request means it has accepted responsibility for processing that request. It does not establish that Daniel has received or read anything.</p><p>The sending infrastructure finds the destination&#8217;s mail servers through DNS and attempts SMTP delivery. The receiving server may accept the message, temporarily defer it, or reject it. If accepted, the mailbox system applies its own filtering and placement decisions.</p><p>Daniel may receive it in an inbox category, in spam, or in another destination affected by mailbox rules. If he sees it, he still has to understand the message and decide whether to act.</p><p>These are separate milestones:</p><ol><li><p><strong>Notification created:</strong> The product decided an email was eligible.</p></li><li><p><strong>Provider accepted:</strong> The sending service accepted the request.</p></li><li><p><strong>Receiving server accepted:</strong> The destination server accepted responsibility for the message.</p></li><li><p><strong>Inbox placement:</strong> The message reached an inbox rather than spam or another destination.</p></li><li><p><strong>Human engagement:</strong> A person interacted with it.</p></li><li><p><strong>Product outcome:</strong> The person returned and did something valuable.</p></li></ol><p>An email provider&#8217;s delivery event usually refers to receiving-server acceptance. The remaining milestones require other evidence. This is why a high delivery rate can coexist with a weak notification program.</p><h1><strong>The visible sender and the envelope sender</strong></h1><p>An email has information that the recipient normally sees and routing information that is usually hidden.</p><p>The visible From address might be notifications@notify.example.com. The display name might be Example Dating. A Reply-To address can tell the email client where a human reply should go, such as your support mailbox.</p><p>The SMTP envelope has its own sender address, called MAIL FROM. This address is used for delivery-status messages such as bounces. When the message reaches final delivery, its Return-Path header normally records this reverse-path address. Reply-To and Return-Path therefore serve different purposes. <a href="https://docs.aws.amazon.com/ses/latest/dg/mail-from.html">[1]</a></p><p>Think of a parcel that contains a letter. The name on the letter, the address for a personal response, and the logistics address for a failed delivery can differ. Email has a similar separation, although the precise routing rules are more technical.</p><p>Other headers help reconstruct what happened. Message-ID identifies a message for tracing, although your application also needs its own identifiers. Received headers record transport hops. Authentication-Results records checks performed by a receiving system. When investigating a problem, your team needs the original message or full headers, not only a screenshot of the visible body.</p><p>MIME describes how a message can contain different content types. A typical notification can include both plain text and HTML alternatives. The email client chooses an appropriate representation. Attachments and inline resources also use MIME structures.</p><p>Founders rarely need to inspect these details daily. They should know that an email is a structured message with routing and authentication information. A beautiful HTML template is only one component.</p><p></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><h1><strong>DNS records that matter for email</strong></h1><p>DNS is the internet&#8217;s naming system. It publishes information that other systems need when interacting with your domain. Several record types matter for mail.</p><p>An MX record identifies servers that accept incoming email for a domain. If someone sends mail to support@example.com, the sending system looks up the relevant mail routing information. MX records can include priorities so that multiple receiving servers can be used.</p><p>An A record maps a hostname to an IPv4 address. An AAAA record does the equivalent for IPv6. A PTR record works in the reverse direction, associating an IP address with a hostname. Receiving systems often expect valid forward and reverse DNS for outbound mail infrastructure.</p><p>TXT records can contain policy information such as SPF and DMARC. DKIM public keys may be published directly in DNS or reached through provider-supplied CNAME records. A CNAME is an alias from one DNS name to another.</p><p>These records are connected, but they do different jobs. An MX record tells the world where to deliver incoming mail. It does not, by itself, authorize a service to send mail using your identity.</p><p>In practice, your email sending service supplies DNS records for your team to publish. The important step is putting each record under the correct domain name. Your developer or service provider can do this for you; as a founder, you should ask them to show that a real outgoing message passes the checks.</p><p>DNS changes also take time to become visible because systems cache answers. When a provider says a record is missing, check the exact name, value, authoritative DNS service, and caching behavior before repeatedly changing settings.</p><p>My recommendation is to maintain a small inventory: every sending domain, the service using it, its purpose, and the person responsible for its DNS configuration. That inventory becomes valuable when you add a campaign tool or migrate providers.</p><h1><strong>SPF: the DNS record that authorizes sending servers</strong></h1><p>SPF means Sender Policy Framework. It is a policy published as a TXT record in your domain&#8217;s DNS. In plain English, the record tells receiving mail systems which servers are allowed to send using your domain in the message&#8217;s delivery envelope.</p><p>Suppose your dating site uses Amazon SES to send notifications. Your SPF setup authorizes the appropriate Amazon SES sending infrastructure. When a message reaches Gmail, Gmail can compare the sending server with that published authorization.</p><p>Why does this matter? Email was not originally designed to make every sender prove who they were. A spammer can put someone else&#8217;s domain into parts of an outgoing message. Without an SPF policy, receiving systems cannot use your published SPF authorization to check whether the server is allowed to send for that envelope domain.</p><p>With SPF configured, an unauthorized server can fail that check. This helps receivers identify impersonation attempts and gives legitimate mail a stronger technical foundation. It does not make it impossible for a criminal to type your brand into the visible From address. DKIM and DMARC add other checks, especially the connection to the address the user actually sees. <a href="https://www.rfc-editor.org/info/rfc7208/">[2]</a></p><p>The practical task is to authorize all the services that genuinely send for you. Here, &#8220;services&#8221; means tools such as Amazon SES, SendGrid, your support platform, or your employee email system when it sends using the relevant domain. It does not mean adding Gmail and Yahoo merely because your customers receive mail there.</p><p>Your team should maintain one valid SPF policy for each relevant domain, incorporating its legitimate senders. Creating a separate SPF record for every sending tool at the same domain can break the configuration.</p><p>For a quick technical check, ask your developer to use <a href="https://mxtoolbox.com/SuperTool.aspx">MXToolbox SuperTool</a>. It includes SPF, DKIM, DMARC, DNS, and blocklist lookups. These tests help find configuration problems; a test email received in a real mailbox is still useful evidence.</p><h1><strong>DKIM and message signatures</strong></h1><p>DKIM means DomainKeys Identified Mail. It adds a digital signature to an outgoing email. Your sending service creates the signature, and the receiving system checks it using information published in your domain&#8217;s DNS.</p><p>Think of your company sealing an outgoing document. Someone receiving it needs a way to check that the seal is genuine and that the protected content has not changed. DKIM provides a technical version of that seal for email. <a href="https://www.rfc-editor.org/info/rfc6376/">[3]</a></p><p>Why does this matter? A fake dating-site security message might look convincing: your brand name, logo, and a link asking the user to sign in. A visual imitation alone cannot produce a valid DKIM signature for your domain without access to its signing key.</p><p>If DKIM is not configured, your legitimate messages arrive without that domain-backed signature. Receivers lose an important way to check your mail, and your domain also lacks the DKIM evidence that DMARC can use to distinguish your own messages from impersonation. Missing DKIM does not itself give a criminal access to your servers; it leaves an important protection unused.</p><p>For a founder, the implementation is usually straightforward: enable the sending service&#8217;s DKIM setup and publish the DNS records it provides. Amazon SES and other major sending services handle the actual signing. Your team checks that messages received in Gmail or another mailbox pass DKIM for the intended domain.</p><p>If you change sending providers or domains, test the new setup before moving all your traffic. Also test after introducing a service that rewrites email content, because changing protected content after signing can invalidate the signature.</p><h1><strong>DMARC and the identity people recognize</strong></h1><p>DMARC means Domain-based Message Authentication, Reporting, and Conformance. It is another policy published in DNS. It connects the domain in the visible From address with the domain authenticated through SPF or DKIM.</p><p>This solves a problem founders can easily recognize. Your customer sees notifications@yourdatingapp.com and assumes the message came from your business. A successful technical check for some unrelated domain would not establish that connection. DMARC asks whether the authentication supports the sender identity the user actually sees.</p><p>A message can pass DMARC when SPF or DKIM passes with an appropriately matching domain. Your team should configure both, even though an individual message does not need both to pass DMARC. <a href="https://www.rfc-editor.org/info/rfc9989/">[4]</a></p><p>DMARC also lets you state how you want receivers to treat messages that fail. The common policy choices are none, quarantine, and reject. Start by monitoring legitimate sending, then move toward quarantine or rejection once your own services are configured correctly.</p><p>Without DMARC, you have not published that visible-domain protection and handling policy. Criminals may attempt to impersonate your domain in fake password resets, payment notices, or &#8220;you have a new match&#8221; messages. A correctly configured enforcement policy helps receiving systems keep those unauthenticated impersonations away from users.</p><p>No single record prevents every kind of deception. Someone can register a lookalike domain or misuse a compromised legitimate account. The benefit here is protection against unauthorized use of your actual domain, alongside clearer authentication for your own mail.</p><p>DMARC reports can also show which sending systems are using your domain and whether their authentication passes. A reporting service can turn those technical reports into a dashboard. For a founder, the useful question is simple: are all our real senders configured, and are outsiders trying to impersonate us?</p><h1><strong>SPF, DMARC, and DKIM working together: a hacker&#8217;s email</strong></h1><p>Let us use two domains:</p><ul><li><p><strong>dating.site</strong> &#8212; our dating business.</p></li><li><p><strong>atacker.site</strong> &#8212; the hacker&#8217;s domain.</p></li></ul><p>The hacker wants to send our users a fake security email. The goal is to make them open a fraudulent login page and enter their passwords.</p><p>The fake email looks like this:</p><blockquote><p><strong>From:</strong> support@dating.site</p><p><strong>Delivery address:</strong> bounce@dating.site</p><p><strong>Message:</strong> &#8220;Your account has been blocked. Follow this link to restore access.&#8221;</p></blockquote><p>An email has two sender addresses that matter for this example.</p><p>The <strong>From address</strong> is the sender address presented to the user. The <strong>delivery address</strong> is a separate address used behind the scenes, including for delivery failures.</p><p><strong>Gmail&#8217;s normal message view does not display this delivery address.</strong> Finding it requires inspecting technical message details.</p><p>The hacker can put <strong>dating.site</strong> into both addresses without owning our domain. Let us see what changes as we add protection.</p><h3><strong>We configure SPF: Gmail can check the sending server</strong></h3><p>We publish an SPF record in our domain&#8217;s DNS. It identifies the servers authorized to send mail using <strong>dating.site</strong> as the delivery domain.</p><p>For example, our setup authorizes the Amazon SES infrastructure we use.</p><p>The hacker sends the fake email from their own server, keeping <strong>bounce@dating.site</strong> as the delivery address.</p><p>Gmail checks the SPF record for <strong>dating.site</strong> and discovers that the hacker&#8217;s server is not authorized.</p><p><strong>The hacker can still send the message. What changes is that Gmail can now detect the unauthorized sending through SPF.</strong> Gmail decides how to handle that result alongside its other checks.</p><p>The hacker has another option: use their own domain in the delivery address.</p><blockquote><p><strong>From:</strong> support@dating.site</p><p><strong>Delivery address:</strong> bounce@atacker.site</p><p><strong>Message:</strong> The same fake account warning.</p></blockquote><p>The hacker configures SPF for <strong>atacker.site</strong>, authorizing their own server.</p><p>Now SPF can pass &#8212; <strong>for atacker.site, the hacker&#8217;s domain.</strong></p><p><strong>But the user does not see that delivery address in Gmail&#8217;s normal message view.</strong> They see <strong>support@dating.site</strong> in the From field and may believe the email came from our dating business.</p><p>The hidden delivery address is <strong>bounce@atacker.site</strong>. If Gmail displayed it alongside the From address, the user could notice the unfamiliar domain and recognize the mismatch. In the normal view, that clue is hidden.</p><p>That is the problem: <strong>SPF successfully checks the hacker&#8217;s hidden domain, while the user sees and trusts our domain.</strong></p><p>We therefore need a check that connects authentication to the visible From address. That is what DMARC provides.</p><h3><strong>We configure DMARC: reject emails that impersonate our visible From</strong></h3><p>The hacker&#8217;s email has already passed SPF:</p><blockquote><p><strong>From:</strong> support@dating.site</p><p><strong>Hidden delivery address:</strong> bounce@atacker.site</p><p><strong>SPF:</strong> Passed for atacker.site.</p></blockquote><p>The user sees <strong>support@dating.site</strong>. They do not see the hacker&#8217;s delivery address in Gmail&#8217;s normal message view.</p><p>We now publish a DMARC policy for <strong>dating.site</strong> and choose <strong>reject</strong>. Our instruction to receiving services is:</p><blockquote><p>&#8220;If an email shows dating.site in From, but its authentication does not confirm dating.site, reject it.&#8221;</p></blockquote><p>At this stage of our example, we have not configured DKIM for our domain, so DMARC relies on the SPF result.</p><p>Gmail sees that SPF authenticated <strong>atacker.site</strong>. But the email claims to come from <strong>dating.site</strong>.</p><p>The hacker has proved their right to send for <strong>atacker.site</strong>. They have provided no authentication for <strong>dating.site</strong>.</p><p><strong>The email therefore passes SPF but fails DMARC.</strong></p><p>Our reject policy tells Gmail to reject this impersonation. For a receiving service following that policy, the result is rejection: the fake email is not delivered to the user.</p><p>This closes the gap left by SPF alone. The hacker cannot satisfy DMARC merely by passing SPF for their own hidden delivery domain while displaying our domain in From.</p><p>Our legitimate emails can pass because their authentication corresponds to <strong>dating.site</strong>. DKIM provides another way to supply that confirmation.</p><h3><strong>We configure DKIM: our real emails carry a digital signature</strong></h3><p>When our sending service sends a genuine email, it adds a digital signature associated with <strong>dating.site</strong>.</p><p>The signature is created using a secret signing key. The corresponding public key is published in DNS so receiving services can check it.</p><p>The signature is tied to protected parts of the email, including the From address and message content.</p><p><strong>Gmail reads the signing domain from the DKIM signature itself.</strong> It then retrieves the public key for that signing domain and checks the signature.</p><p>It does not simply take the visible From address and assume that its domain signed the message.</p><p>Now consider the hacker&#8217;s options.</p><p><strong>Option A: claim that dating.site signed the fake email.</strong></p><p>The hacker does not have our secret signing key, so they cannot create a valid signature for <strong>dating.site</strong> using their own key. The signature check will not pass.</p><p><strong>Option B: sign the email using atacker.site.</strong></p><p>That signature can be completely valid. Gmail can confirm that <strong>atacker.site</strong> signed the message.</p><p>But the visible From still says <strong>support@dating.site</strong>.</p><p>DMARC detects that the valid signature belongs to <strong>atacker.site</strong>, while the visible From belongs to <strong>dating.site</strong>.</p><p>In our example, both SPF and DKIM now authenticate the hacker&#8217;s domain. Neither authenticates our domain.</p><p><strong>The email still fails DMARC, and our reject policy still asks Gmail to reject it.</strong></p><p><strong>Option C: send the email without a DKIM signature.</strong></p><p>There is no signature to verify, so the message provides no authentication through DKIM. Its SPF result still confirms only <strong>atacker.site</strong>, so it fails DMARC again.</p><p>The hacker also cannot take a genuine signed email, replace a protected login link with a fraudulent one, and keep the signature valid. Changing the signed content causes verification to fail.</p><h3><strong>Why have both SPF and DKIM?</strong></h3><p>They provide different evidence:</p><ul><li><p><strong>SPF:</strong> Is the sending server authorized for the delivery domain?</p></li><li><p><strong>DKIM:</strong> Is the signing domain&#8217;s signature valid, and is the signed content intact?</p></li><li><p><strong>DMARC:</strong> Does successful SPF or DKIM authentication correspond to the domain in the visible From address?</p></li></ul><p>Having both is useful when a legitimate email is forwarded.</p><p>Gmail may receive our genuine email from a forwarding server that our SPF record does not authorize. SPF can then fail, while the DKIM signature remains valid if the protected content is preserved.</p><p>DMARC can accept that matching DKIM signature as confirmation of <strong>dating.site</strong>.</p><p>The rule to remember is that <strong>DMARC can pass through either matching SPF authentication or a matching DKIM signature. Both do not have to pass.</strong></p><p>A missing or failed DKIM signature therefore does not automatically send an email to Spam. A message can still pass DMARC through matching SPF authentication. The receiving service considers these results, our DMARC policy, and its own filtering rules.</p><p>Together, these tools help receiving services distinguish mail authorized by <strong>dating.site</strong> from messages that merely display our name and address.</p><p></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><h1><strong>Reputation and the difference between delivery and visibility</strong></h1><p>SPF, DKIM, and DMARC are email authentication tools: they help a receiving service check whether a message&#8217;s claimed sender identity is supported by the domain&#8217;s configuration. Reputation answers the next question: given this sender&#8217;s behavior, how should the receiving service treat the message?</p><p>That second question affects visibility. Gmail might accept an email from your authenticated domain and still place it in Spam, where the user is unlikely to read it. Good authentication creates the foundation; a history of wanted, relevant messages helps your emails remain visible.</p><p>A domain can authenticate perfectly while sending messages people dislike. A technically valid message can contain a misleading subject, arrive too frequently, or refer to an account the recipient barely remembers creating.</p><p>Receiving systems can evaluate domains, sending IPs, message content, links, traffic patterns, and recipient behavior. Their decisions are proprietary and can differ between providers. There is no universal public score that fully predicts where every email will land.</p><p>For a founder, this means reputation is partly a product outcome. Your onboarding controls affect address quality. Your notification frequency affects complaints. Your moderation system determines whether you repeatedly promote interactions from accounts that users later discover are fraudulent.</p><p>Suppose your application sends a new-message email for every message a scammer generates before being banned. Your delivery infrastructure may work exactly as configured. The product has still sent unwanted mail and damaged trust. Reputation management therefore requires cooperation between engineering, growth, support, and trust and safety.</p><p>Inbox categories also deserve a sensible interpretation. An email in Gmail&#8217;s Promotions category is not the same as an email in spam. A promotional campaign can legitimately belong in Promotions. Your objective is wanted, usable communication, with measurement of the outcome that matters to the product.</p><p>When someone says, &#8220;Our delivery rate is 99%,&#8221; ask what event that rate counts. Then ask how performance differs across Gmail, Outlook, Yahoo, and other destinations. A blended number can hide a severe problem with the mailbox provider used by most of your audience.</p><h1><strong>Shared IPs, dedicated IPs, and warmup</strong></h1><p>An IP address identifies a sending server on the network. When Amazon SES delivers your email to Gmail, Gmail sees the IP address of the Amazon SES server making that connection. That address has its own sending history and reputation.</p><p>With shared IPs, your mail travels through a pool used by other customers of the sending service. The service manages that pool. It can be a sensible starting point because it already carries regular traffic, although other customers&#8217; behavior can affect the shared reputation.</p><p>With dedicated IPs, the sending addresses are reserved for your account. This gives you more control and a clearer relationship between your own sending behavior and the IP&#8217;s reputation.</p><p>Within Amazon SES, standard dedicated IPs provide known, static addresses. Managed dedicated IPs automate more of the work and can add or remove addresses as your traffic changes. For a small dating site with low or irregular volume, shared IPs can be a better fit than a dedicated address that receives little consistent traffic. <a href="https://docs.aws.amazon.com/ses/latest/dg/dedicated-ip.html">[5]</a></p><p>Warmup means gradually building a new sending IP&#8217;s history. A brand-new address that suddenly sends hundreds of thousands of emails gives receiving systems little evidence that this is normal, wanted traffic.</p><p>You can use provider automation for this. Amazon SES enables automatic warmup by default for standard dedicated IPs. Its managed dedicated IP service goes further, adapting warmup to actual sending patterns and to each receiving provider, such as Gmail or Yahoo. <a href="https://docs.aws.amazon.com/ses/latest/dg/dedicated-ip-warming.html">Amazon SES warmup documentation</a> and <a href="https://docs.aws.amazon.com/ses/latest/dg/managed-dedicated-sending.html">managed dedicated IPs</a> explain the options.</p><p>Other providers offer similar features: <a href="https://www.twilio.com/docs/sendgrid/concepts/reputation/warm-up-ip-addresses">SendGrid supports automated IP warmup</a>. Ask which feature is included in your chosen plan and whether it is enabled.</p><p>Automatic warmup takes care of a technical ramp-up. You still choose the audience and the messages. Start with people who recently joined or actively use the product, monitor results, and avoid introducing an old, unresponsive list as your first major campaign.</p><p>For an early dating product, I would prioritize correct setup, useful notifications, and a suitable managed service. Dedicated IPs become a business decision when your sending volume and need for control justify them.</p><h1><strong>Separate email streams according to their purpose</strong></h1><p>The word transactional is used loosely. Some teams use it to mean every email their application sends automatically. That is too broad for decisions about preferences, risk, and legal classification.</p><p>A password reset responds to a specific account-access request. A receipt records a purchase. A digest of recommended profiles encourages future activity. All can be automated, but users have different expectations for each.</p><p>I find three operational categories useful:</p><ul><li><p><strong>Essential account messages:</strong> Dating examples: Verification, password reset, security notice, receipt; Product treatment: Clear purpose and appropriate urgency.</p></li><li><p><strong>Subscribed product notifications:</strong> Dating examples: New messages, matches, activity digests; Product treatment: User controls and event relevance.</p></li><li><p><strong>Marketing:</strong> Dating examples: Offers, newsletters, reactivation campaigns; Product treatment: Appropriate permission and easy opt-out.</p></li></ul><p>The table is a product design framework. Legal treatment depends on the actual message and jurisdiction. Adding an offer to an otherwise transactional message can change the analysis.</p><p>Marketing often reaches less-engaged users and can produce more complaints. Operational separation helps prevent a campaign backlog from delaying password resets and makes it easier to diagnose the stream causing trouble.</p><p>You can separate streams through subdomains, provider configuration, queues, credentials, reporting tags, and, where justified by volume, IP pools. For example, notify.example.com and news.example.com can make the distinction explicit.</p><p>Subdomains improve organization but do not create complete isolation. Mailbox providers can associate related identities, and Gmail aggregates some compliance assessments at the primary-domain level. Separate root domains introduce their own brand and reputation costs. I would make that decision deliberately rather than buying a disposable-looking domain whenever a campaign performs badly.</p><p>Keep your identity recognizable. The recipient should understand which product is contacting them regardless of the technical stream behind the message.</p><h1><strong>Blocklists and what a listing actually means</strong></h1><p>A blocklist is a database used to identify infrastructure or domains associated with unwanted or risky activity. Some lists concern IP addresses; others concern domains, including domains used in links.</p><p>Spamhaus is one prominent operator. Its IP and domain lists serve different purposes, and an individual mailbox provider decides how to use external intelligence alongside its own filtering. <a href="https://www.spamhaus.org/faqs/spamhaus-blocklist/">[6]</a></p><p>A public listing can explain a rejection. The absence of a public listing does not establish good inbox placement. Gmail can make a negative decision using information that never appears on a public lookup site.</p><p>When a listing appears, begin with the exact evidence. Which IP or domain is listed? On which list? Does an actual receiving-server error reference it? Is the affected IP controlled by your company or by your email provider?</p><p>Next, investigate the cause. It could involve an old imported audience, a compromised credential, excessive invalid recipients, or another sender in shared infrastructure. The corrective action depends on that cause.</p><p>If you control the problem, fix it before requesting removal. If the IP belongs to a provider, give that provider the rejection details and message identifiers. Its team generally controls the relevant IP-level remediation.</p><p>For a dating business, an especially damaging reaction is to keep sending the same unwanted campaign through fresh domains. It leaves the audience and product problem intact while adding inconsistent branding. A sustainable recovery requires changing the behavior that caused the issue.</p><h1><strong>Choosing the sending service and the campaign tool</strong></h1><p>For a founder launching a new dating site, I would usually start with a managed email service. Early sending volumes are often modest, so the monthly cost can be a reasonable price for a system that is ready to use.</p><p>By &#8220;managed service,&#8221; I mean a provider that combines sending infrastructure with a useful interface for logs, delivery statistics, templates, and routine email operations. Depending on the product and plan, you may also get bounce and complaint handling, unsubscribe tools, campaign features, team access, and support.</p><p>SendGrid is one example. Resend, Mailgun, Postmark, and Mailchimp Transactional, also known as Mandrill, offer different combinations of these capabilities. Compare the actual product and plan: an email API subscription does not always include a complete marketing campaign tool.</p><p>The early benefit is time. Your developers can integrate a service and use its existing reports instead of building every dashboard and operational screen. You can spend more attention on registration, conversations, payment conversion, and retention.</p><p>As the product grows, the calculation changes. Higher email volume makes the per-message premium more noticeable. Your team may also want greater control over infrastructure, reporting, and the campaign software it uses.</p><p>That is when I would consider a setup such as Amazon SES for transportation and Sendy for marketing campaigns. It can reduce sending costs and give you more flexibility, provided someone owns the setup and maintenance.</p><p>There are two purchases hidden inside many email subscriptions: the transport that attempts delivery, and the software that manages audiences, templates, campaigns, and reporting. Comparing those separately makes the price difference easier to understand.</p><p>My recommendation is to start with the service your team can operate reliably, then revisit the economics as usage grows. Also confirm that the provider accepts your specific dating use case and content before investing in the integration.</p><h1><strong>Our SkaDate stack and the role of Amazon SES</strong></h1><p>At SkaDate, we usually use Amazon SES for transactional mail and Sendy connected to Amazon SES for marketing campaigns.</p><p>In the transactional path, the dating application decides what to send and submits the message to Amazon SES using SMTP. In the marketing path, Sendy manages the campaign and uses Amazon SES for delivery. Amazon SES provides the email transport underneath both paths.</p><p>This gives the application a straightforward way to send registration, account recovery, and notification emails, while the marketing team gets a campaign interface for audiences and newsletters.</p><p>Amazon SES requires verified sending identities. New accounts begin with sandbox restrictions, which include limited sending and restricted recipients. Production access removes the sandbox recipient restriction, but does not remove the need to verify your sending identities. Sending quotas and throughput limits remain separate controls, and configuration is region-sensitive. <a href="https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html">[7]</a></p><p>You may hear this process described as getting &#8220;whitelisted.&#8221; I would use more precise language. Verifying a domain proves control of a sending identity. Production approval permits broader sending. A recipient&#8217;s allowlist is a separate concept. A suppression list prevents certain sends. None of these is a universal promise of inbox placement.</p><p>A custom MAIL FROM domain lets you use your own bounce-domain identity rather than the default Amazon SES domain. It needs the DNS configuration specified by AWS and can help achieve SPF alignment. Aligned DKIM can also satisfy DMARC. <a href="https://docs.aws.amazon.com/ses/latest/dg/mail-from.html">[1]</a></p><p>Configuration sets let your team associate sending behavior and event reporting with particular streams. Operationally, you want to distinguish account messages, product notifications, and campaigns in your data even when they use the same provider.</p><p>We also connect email events to Mixpanel. In our Amazon SES setup, we track Sent, Delivered, Opened, and Clicked so we can connect email activity with what people do in the dating product. This reporting connection is part of our implementation. A more integrated service such as SendGrid already provides built-in email statistics, although you may still send selected events to Mixpanel for product analysis. <a href="https://docs.aws.amazon.com/ses/latest/dg/monitor-sending-activity-using-notifications.html">[8]</a></p><h1><strong>What Sendy adds</strong></h1><p><a href="https://sendy.co/">Sendy</a> is email campaign software that you install on a server and connect to Amazon SES. Its license is a one-time purchase: the current listed price is $69, rather than a recurring monthly platform subscription. Amazon SES sending and your hosting are separate costs. <a href="https://sendy.co/">[9]</a></p><p>Sendy provides a campaign interface, audience lists, templates, autoresponders, and reports, including opens, clicks, bounces, and complaints. For a dating business, it can be a practical way to run newsletters, recommendation campaigns, and appropriate reactivation emails.</p><p>The one-time license is only part of the cost. Someone still needs to run the server, apply Sendy updates, maintain the operating system and supporting software, protect access, keep backups, and monitor that scheduled campaigns actually send. Minor updates are included until the next major version; major-version upgrades can require another payment.</p><p>This is why we offer Managed Sending for clients on <a href="https://www.skadate.com/prime/">SkaDate Prime Ultimate</a>, including a SkaDate-hosted Sendy account. The founder gets the campaign tool with an operational service around it.</p><p>If you self-host, budget for the person who maintains it. If you use our managed option or another provider&#8217;s hosted service, include that subscription in your total cost. The useful comparison is what the whole system costs to run reliably.</p><h1><strong>The actual economics of email</strong></h1><p>Email transportation can be remarkably inexpensive. The confusion begins when founders compare the raw sending fee of one service with a complete software subscription from another.</p><p>As checked on October 28, 2026, AWS lists outbound Amazon SES &#224; la carte sending at $0.10 per 1,000 emails. Its Essentials plan lists $0.16 per 1,000 in the first volume tier. Additional features and data charges can apply, so the selected plan matters. <a href="https://aws.amazon.com/ses/pricing/">[10]</a></p><p>Here is the sending-charge arithmetic before those extras:</p><p><strong>Monthly recipient deliveries submitted:</strong></p><ul><li><p><strong>10,000:</strong> Amazon SES &#224; la carte base sending: $1.00; Amazon SES Essentials first-tier sending: $1.60.</p></li><li><p><strong>100,000:</strong> Amazon SES &#224; la carte base sending: $10.00; Amazon SES Essentials first-tier sending: $16.00.</p></li><li><p><strong>1,000,000:</strong> Amazon SES &#224; la carte base sending: $100.00; Amazon SES Essentials first-tier sending: $160.00.</p></li></ul><p>Sendy adds its license and your hosting and maintenance costs to the applicable Amazon SES bill. It does not replace Amazon SES charges.</p><p>For a concrete comparison, Resend currently lists a $20-per-month Pro transactional plan with 50,000 emails, and a $90-per-month Scale plan with 100,000. At the latter volume, $90 is nine times Amazon SES&#8217;s $10 &#224; la carte base sending fee. That comparison concerns the listed sending volume and entry subscription, not feature equivalence or a universal cheapest configuration. <a href="https://resend.com/pricing">[11]</a></p><p>The absolute difference matters more than the headline multiplier. A $10 infrastructure bill becoming a $90 managed bill may be acceptable if it saves engineering work. A large monthly premium at higher volume deserves closer review. Use the vendor&#8217;s applicable tier, overages, and negotiated terms rather than extrapolating a small plan indefinitely.</p><p>SendGrid distinguishes its Email API offering from Marketing Campaigns. Mailchimp Transactional has its own purchasing model and relationship to Mailchimp plans. Their quotes should be built around the same workload before comparison. <a href="https://www.twilio.com/en-us/products/email-api/pricing">[12]</a><a href="https://mailchimp.com/help/about-transactional-email/">[13]</a></p><p>I would calculate total cost as software plus sending plus infrastructure plus optional services plus the people required to operate the system. Include dedicated IPs, event processing, retained logs, and support where relevant.</p><p>Then connect that bill to the product. A cheaply sent campaign that produces complaints and few valuable returns can be more expensive than its invoice suggests. Conversely, a modest investment that protects account access and improves replies can be worth far more than the sending fee.</p><h1><strong>Hard bounces, soft bounces, and retries</strong></h1><p>Imagine your dating site sends Daniel a new-message notification. Amazon SES takes that email to the mail system responsible for Daniel&#8217;s address, such as Gmail. That receiving system may be unable to accept or deliver it. The failure information travels back to your sending service. That is a bounce.</p><p>A hard bounce usually means a permanent problem with delivery to that address. The simplest example is an address that does not exist. If Daniel mistyped his email during registration, there may be no mailbox to receive the message. Repeating the attempt will not create one.</p><p>A soft bounce usually means a temporary problem. A familiar example is a full mailbox: the address exists, but its owner has run out of storage. A temporary receiving-server problem is another example. Delivery may become possible later, so the sending service can retry before reporting a final failure.</p><p>These are the useful terms for a founder. You do not need to read SMTP response codes to understand the business issue: some addresses cannot receive your mail permanently, while others may be reachable after a temporary problem clears.</p><p>Modern delivery services do much of the bounce handling for you. Amazon SES, SendGrid, and Mailchimp Transactional have mechanisms for recognizing failed deliveries and avoiding repeated attempts to addresses that should no longer be used. Amazon SES also handles delivery retries for temporary failures. <a href="https://docs.aws.amazon.com/ses/latest/dg/monitor-sending-activity-using-notifications.html">[8]</a></p><p>A suppression list is a &#8220;do not send&#8221; list maintained by the provider. With Amazon SES bounce suppression enabled, an address that produces a hard bounce can be added automatically. Later send requests to that address can be accepted by Amazon SES without another delivery attempt because the address is suppressed. Your team should confirm that the relevant suppression settings are enabled. <a href="https://docs.aws.amazon.com/ses/latest/dg/sending-email-suppression-list.html">[21]</a></p><p>This protects you from repeatedly sending to an address already known to be invalid. It also protects the provider&#8217;s infrastructure. Repeated failures are a warning sign of poor address quality and can harm the sender&#8217;s reputation.</p><p>Automation cannot undo the first failed attempt. If a signup flow produces thousands of mistyped or invented addresses, those initial hard bounces still create a problem. The founder&#8217;s job is to watch the rate, find where bad addresses enter the database, and fix that source.</p><p>You generally do not need to build an entire bounce-management system yourself. Choose a provider with these capabilities, configure them correctly, and use its reports to understand what is happening.</p><h1><strong>Spam complaints and the feedback you can receive</strong></h1><p>A spam complaint is a recipient telling their mailbox provider that they consider your message unwanted. Someone can register for your dating app and later decide that its emails are too frequent, irrelevant, or difficult to stop.</p><h2><strong>The Gmail exception: Report spam does not identify the recipient</strong></h2><p><strong>In the dating products I work with, Gmail can account for 85% or more of user email addresses. This is my observation from those products, not a universal market statistic. With that audience mix, Gmail&#8217;s behavior is central to how you manage email.</strong></p><p>Imagine a user receives a notification from our dating app at user@gmail.com and clicks Report spam. Gmail receives the complaint, but <strong>it does not provide our sending service with a traditional recipient-level feedback report saying &#8220;user@gmail.com reported your message.&#8221;</strong></p><p><strong>Amazon SES therefore cannot automatically add that specific address to its suppression list solely because the user clicked Report spam in Gmail.</strong> The same limitation applies to SendGrid and Mailchimp Transactional, also known as Mandrill. A more expensive sending service does not make Gmail reveal the complaining recipient.</p><p>This means we can continue requesting emails to that address without knowing that the person complained. Gmail may filter later messages into Spam, while our sending service still records receiving-server acceptance as delivery. <strong>Delivered does not mean visible in the inbox, and no recorded complaint does not mean that no Gmail user complained.</strong></p><p><a href="https://www.twilio.com/docs/sendgrid/ui/sending-email/google-feedback-loop">SendGrid&#8217;s documentation</a> explicitly distinguishes Gmail&#8217;s anonymous, aggregate reporting from traditional feedback loops that can identify recipients.</p><p>From the user&#8217;s point of view, there are several ways out. They can unsubscribe from a mailing list, block a sender, or report a particular email as spam. These actions have different consequences.</p><p>Gmail introduced its Block sender feature on September 22, 2015. Future messages from a blocked address are directed to that user&#8217;s Spam folder. The sender can still attempt delivery; the messages are filtered away from the inbox. Blocking also does not automatically remove the user from your mailing list. <a href="https://workspaceupdates.googleblog.com/2015/09/block-and-unsubscribe-in-gmail.html">Google&#8217;s launch announcement</a> and <a href="https://support.google.com/mail/answer/8151?hl=en">current Gmail help</a> describe this behavior.</p><p>&#8220;Report spam&#8221; is a separate action. It tells Gmail that the message is unwanted; Google says it receives a copy and may analyze it to help protect users from spam and abuse. Google&#8217;s public guidance describes Block and Report spam separately. It does not establish that every Block click generates the same complaint event in a sender&#8217;s reporting. <a href="https://support.google.com/mail/answer/1366858?hl=en">Report spam in Gmail</a></p><p>For the business, either outcome matters. A blocked sender loses visibility in that person&#8217;s inbox. Spam reports can also affect how the mailbox provider treats the sender&#8217;s mail. Making unsubscribe easy gives users a clear way to stop optional emails before frustration escalates.</p><p>Some receiving providers share individual complaint information through feedback loops. When a supported report identifies the recipient, Amazon SES with complaint suppression enabled, SendGrid, or Mailchimp Transactional can use it to stop further sending to that address. Yahoo operates a complaint feedback loop for enrolled DKIM domains. <strong>This individual-report-and-suppression workflow must not be assumed for Gmail.</strong> <a href="https://senders.yahooinc.com/complaint-feedback-loop/">[14]</a></p><p></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><h2><strong>What Feedback-ID actually tells you</strong></h2><p>Gmail&#8217;s Feedback Loop helps identify problematic campaigns or categories of mail. A Feedback-ID header lets us associate messages with identifiers such as new-message, weekly-digest, or reactivation. Gmail can then provide aggregate complaint information associated with those identifiers. <a href="https://support.google.com/mail/answer/6254652?hl=en">[15]</a></p><p>For example, the reporting may show that reactivation emails generate more spam complaints than new-message notifications. That tells us which campaign, audience, or notification type needs investigation. <strong>It does not give us the email addresses of the people who complained. Feedback-ID is a campaign-diagnostics tool, not a recipient-level suppression feed.</strong></p><p>Use Google Postmaster Tools to understand Gmail&#8217;s reported spam rate and the feedback data available for your traffic. A low or zero complaint count in Amazon SES is not a substitute for Gmail&#8217;s own reporting.</p><p><strong>Report spam and Unsubscribe are separate actions.</strong> An unsubscribe request can identify the relevant recipient or subscription, allowing our system or campaign service to stop that sending. If Gmail also offers an unsubscribe action when someone reports spam, that unsubscribe request is a separate mechanism; the spam report itself is not a personalized unsubscribe notification.</p><p>For our Gmail-heavy audience, the practical approach is to make unsubscribe easy, watch Postmaster and campaign-level feedback, and use product activity and notification preferences to decide when optional mail should stop. Provider-managed suppression still handles the failures and identifiable complaints the provider actually receives.</p><p>Watch the pattern behind complaints. Did a reactivation campaign reach people who no longer remembered the service? Did a &#8220;new match&#8221; email exaggerate what was actually waiting in the app? Did an opt-out stop working?</p><p>The delivery service can handle supported complaint and suppression mechanisms. Your team still controls the product decisions that make people want, ignore, or complain about the messages.</p><h1><strong>Validate addresses without blocking registration</strong></h1><p>Address quality begins during registration. Suppose someone mistypes their address and your application immediately starts sending welcome emails, match alerts, and reminders. The receiving system may report that the address does not exist, producing a hard bounce. A large number of such failures can damage your sending reputation.</p><p>With bounce suppression correctly configured, Amazon SES can add that failed address to its suppression list and avoid subsequent delivery attempts. That prevents repetition; it does not erase the initial failure. Preventing obvious address mistakes before sending is therefore useful. <a href="https://docs.aws.amazon.com/ses/latest/dg/sending-email-suppression-list.html">[21]</a></p><p>I would not automatically make email confirmation a blocking step in every dating signup flow. Asking someone to leave registration, open their inbox, find a message, and return can create substantial friction on mobile and desktop. Some people never make it back.</p><p>My preferred starting point is address validation with a service such as <a href="https://debounce.com/solutions/api/">DeBounce</a>, whose API uses the debounce.io domain. Your application submits the address for a technical check. The service can check its format, the domain&#8217;s mail setup, common domain typos, and signs that the mailbox is invalid, disposable, or uncertain.</p><p>This helps catch mistakes before your sending service attempts delivery. For example, an obvious typo in a Gmail domain can prompt the user to correct the address while they are still on the form.</p><p>Validation and ownership confirmation answer different questions. Validation asks whether the address appears usable. A confirmation link or code asks whether this particular person can receive mail there. An address can pass technical validation while belonging to someone else, and some servers make mailbox checks inconclusive.</p><p>I would use that distinction to design a gradual flow. Let the person enter the product where appropriate, then ask for a usable email address and encourage confirmation at a sensible moment. If signup does not collect email, invite the user to add it later. Explain the benefit: account recovery and useful reminders about conversations. An optional request can build the channel without blocking the whole experience.</p><p>Then test the tradeoff. Measure how many people leave at the confirmation step, how many complete registration, how many addresses bounce, and whether the users who continue reach meaningful conversations. If confirmation causes little abandonment and improves address quality, making it mandatory can be the better choice.</p><p>For Google or Apple single sign-on, when the integration supplies a verified email address, a second confirmation email is generally unnecessary. Use the verified identity returned by the sign-in service. In products I work with, manually entered email/password registrations can account for roughly 20% of signups; that is my observation, not an industry benchmark. <a href="https://developers.google.com/identity/sign-in/web/backend-auth">[16]</a><a href="https://developer.apple.com/documentation/signinwithapple/receiving-a-users-identity-token">[17]</a></p><p>A later change to the email address deserves a fresh ownership check. And a usable or verified email address does not by itself prove that a profile is genuine or that its owner consented to every marketing campaign.</p><h1><strong>Apple private relay addresses</strong></h1><p>When Sign in with Apple requests an email address, the user can choose Share My Email or Hide My Email. With Hide My Email, your app receives a private relay address instead of the person&#8217;s actual mailbox address. Apple forwards eligible mail from your app to that mailbox.</p><p>That gives a privacy-conscious user a way to register without revealing their everyday address. The relay address is legitimate and should be treated as a usable contact address, rather than rejected merely because it looks unfamiliar.</p><p>To reach it, your sending setup must satisfy Apple&#8217;s rules. Register the sending sources Apple requires and configure email authentication correctly. Test your real templates through Amazon SES, including your actual sending domain. A message that reaches an ordinary Gmail address can still fail Apple&#8217;s relay requirements. <a href="https://developer.apple.com/help/account/capabilities/configure-private-email-relay-service/">[18]</a></p><p>For retention, the limitation is that this channel remains under the user&#8217;s control. They can turn off forwarding for your app or developer in Apple Account settings. Once forwarding is disabled, your emails no longer reach their personal inbox. You cannot assume that an address collected at signup remains a permanent route back to the user. <a href="https://support.apple.com/en-us/102571">Manage Sign in with Apple settings</a></p><p>Simply uninstalling the app should not be treated as proof that forwarding has stopped. Removing an app from the phone, deleting an account inside the app, and disabling Apple&#8217;s forwarding are different actions. For reactivation, the relevant questions are whether the user still permits contact and whether the relay is still forwarding.</p><p>In August 2026, Apple announced that new relay addresses would begin using private.icloud.com later in the year; existing privaterelay.appleid.com addresses continue to work. Your address checks should allow both. <a href="https://developer.apple.com/news/?id=1ptvdtcm">[19]</a></p><p>My practical test is straightforward: register using Hide My Email, send an actual notification through the production configuration, and confirm that it arrives. Repeat that check when you change email providers or sending domains.</p><h1><strong>Let the provider handle bounces and suppression</strong></h1><p>In the days of running your own mail server, your team had to build or maintain much more of the logic for handling failed deliveries. Modern email delivery services take over much of that work.</p><p>Amazon SES, SendGrid, and similar providers can recognize failures and maintain suppression lists that prevent repeated sending to addresses already known to be invalid. With the appropriate bounce and complaint settings enabled, supported events can update those lists automatically.</p><p>For Amazon SES, think of the suppression list as the provider&#8217;s memory: &#8220;We already learned that sending to this address should stop.&#8221; If your application later requests another send to an address covered by the active suppression settings, Amazon SES can accept the request without attempting delivery. <a href="https://docs.aws.amazon.com/ses/latest/dg/sending-email-suppression-list.html">[21]</a></p><p>The recommendation for a founder is simple: use the provider&#8217;s built-in bounce handling and suppression features. Ask whoever configures the service to confirm that they are enabled and working. You usually do not need your developers to recreate that transport logic.</p><p>User preferences are a separate product responsibility. A marketing unsubscribe, a paused dating account, or an account deletion should also stop the appropriate optional mail. Your application and campaign tool must respect those choices even when the address is technically deliverable.</p><p>The provider protects delivery operations; your product decides which valid messages the user has asked to receive. Both can be handled with existing service capabilities and a clear configuration.</p><h1><strong>Unsubscribe that works for people and mailbox providers</strong></h1><p>Before looking at the technical implementation, consider what the user now sees. For years, many readers looking to leave a newsletter, including a Substack subscription, would scroll to the bottom of an email to find the unsubscribe link. Mailbox interfaces now make that choice much more visible.</p><p>In Gmail, eligible subscription messages can show an Unsubscribe link next to the sender&#8217;s name at the top. The user can act there instead of searching the email footer or recovering a forgotten account password. Gmail may show a confirmation dialog; a properly implemented one-click unsubscribe request does not require logging in to your service. <a href="https://support.google.com/mail/answer/15433283?hl=en">Gmail&#8217;s unsubscribe guide</a></p><p>Gmail can also suggest unsubscribing from mailing lists based on signals such as how often a sender emails and how often the recipient reads those messages. Google introduced these suggestions in 2018. This makes sending more mail to an increasingly disengaged audience an especially weak retention strategy. <a href="https://blog.google/products-and-platforms/products/workspace/new-security-and-intelligent-features-new-gmail-means-business/">Google&#8217;s explanation</a></p><p>In July 2025, Gmail introduced Manage subscriptions: a dedicated view of active subscription senders, with recent sending frequency and an Unsubscribe option. It gives people a single place to review mailing lists and ask Gmail to unsubscribe on their behalf. <a href="https://workspaceupdates.googleblog.com/2025/07/manage-email-subscriptions-in-gmail.html">Manage subscriptions announcement</a></p><p>For your dating business, the implication is practical: the mailbox itself helps users decide which senders deserve attention. Make leaving optional email easy, and give people useful reasons to keep the messages they value.</p><p>The technical setup below is what lets your sending system cooperate with those mailbox controls.</p><p>Make the option visible in marketing and subscribed notification messages. A preference center can let users choose message alerts, match alerts, digests, and promotions separately. Include a straightforward way to stop all marketing mail.</p><p>Avoid asking someone to recover a forgotten password just to unsubscribe. A user who cannot easily stop unwanted mail has an obvious alternative: the spam button.</p><p>Gmail&#8217;s one-click requirement for affected marketing and subscribed mail involves message headers and an automated endpoint. The essential headers are List-Unsubscribe, containing an HTTPS URL, and List-Unsubscribe-Post, signaling List-Unsubscribe=One-Click. Under RFC 8058, the relevant headers must be protected by a valid DKIM signature. <a href="https://www.rfc-editor.org/info/rfc8058/">[22]</a></p><p>When the mailbox provider sends the unsubscribe POST request, your server must process it without a login, an additional confirmation page, or a redirect. Use a hard-to-forge token identifying the subscription so the action can work safely without exposing personal data in a simple readable URL.</p><p>The visible link in the email body and the header-based mechanism serve related but separate paths. Implement both. An ordinary preference-page link alone does not fulfill Gmail&#8217;s RFC 8058 requirement. <a href="https://support.google.com/mail/answer/14229414?hl=en">[23]</a></p><p>Handle the request promptly and propagate it to future campaigns. Yahoo requires honoring these requests within two days; Google recommends fulfillment within 48 hours. Designing for immediate internal suppression is a practical way to avoid delays between systems. <a href="https://senders.yahooinc.com/best-practices/">[24]</a><a href="https://support.google.com/mail/answer/14229414?hl=en">[23]</a></p><p>Essential transactional messages have different treatment. A user-requested password reset is not equivalent to a subscription promotion. In the United States, the FTC&#8217;s CAN-SPAM guidance distinguishes transactional or relationship messages from commercial email according to their purpose and content. Other jurisdictions have their own rules. <a href="https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business">[25]</a></p><p>For your product design, allow users to stop optional activity emails even when a team has labeled them &#8220;transactional&#8221; internally. A software label does not determine how a recipient experiences the message.</p><h1><strong>Mailbox provider requirements</strong></h1><p>Gmail, Yahoo, and Outlook publish sender requirements. Treat them as operating conditions for the destinations your audience uses.</p><p>For Gmail bulk sending, the requirements include SPF and DKIM, DMARC with alignment, appropriate DNS, TLS, low spam rates, and unsubscribe support for relevant messages. Gmail&#8217;s bulk classification considers traffic from the same primary domain, including subdomains. Splitting a campaign across subdomains does not automatically avoid that classification. <a href="https://support.google.com/mail/answer/81126?hl=en">[26]</a></p><p>Yahoo publishes its own requirements covering authentication, complaints, unsubscribe handling, and infrastructure. Microsoft has authentication requirements for high-volume senders to its consumer email services. The exact definitions and enforcement details should be checked in their current documentation. <a href="https://senders.yahooinc.com/best-practices/">[24]</a><a href="https://support.microsoft.com/en-gb/outlook/fix-ndr-error-550-5-7-515-in-outlook-com">[27]</a></p><p>I would not turn compliance into a one-time launch task. A new vendor can introduce an unaligned sender. A template change can remove unsubscribe headers. A broken webhook can leave opt-outs unprocessed. A DNS cleanup can delete a record that another team still needs.</p><p>Assign an owner who can see across the whole email program. Growth should know when a campaign changes the audience. Engineering should know when a new sender changes authentication. Support should know how to distinguish a preference issue from a delivery issue.</p><p>Use actual received messages and provider observations to verify the configuration. A DNS record can exist while the production message uses a different identity from the one the team intended to configure.</p><p>Provider compliance is a baseline for reliable operation. Useful content, clear expectations, and respectful frequency remain necessary after every technical check passes.</p><h1><strong>Google Postmaster Tools deserves its own place in your routine</strong></h1><p>In the dating products I work with, Gmail can account for roughly 85% of user email addresses. That is my observation, not a claim about the global dating market. Your own distribution may differ, so measure it.</p><p>For an audience with that composition, understanding Gmail&#8217;s view of your traffic is essential. Google Postmaster Tools is one of the first tools I would configure.</p><p>It provides destination-side information that complements the events from Amazon SES. Add and verify your relevant domains, then give the people responsible for delivery access to the dashboards. Its data concerns personal Gmail accounts, arrives with a delay, and may be limited when volume is low. <a href="https://support.google.com/mail/answer/14668346?hl=en">[28]</a></p><p>The Compliance dashboard in the newer interface makes the basic question much easier to answer: does Gmail consider our sending compliant with its applicable requirements?</p><p>It reports statuses such as Compliant, Needs work, or No data found. The checks include authentication, DNS, message formatting, encryption, spam rate, and relevant unsubscribe requirements. Compliance uses primary-domain reporting that incorporates subdomain traffic, and changes can take several days to be reflected. <a href="https://support.google.com/mail/answer/14668346?hl=en">[28]</a></p><p>That last point matters for our separated sending streams. If marketing and transactional email use related subdomains, a green result for one piece of your setup does not justify ignoring the rest of the primary domain&#8217;s traffic.</p><p>The operational views I would review are summarized below. <a href="https://support.google.com/mail/answer/14289100?hl=en">[32]</a></p><ul><li><p><strong>Compliance:</strong> Which requirement needs investigation.</p></li><li><p><strong>Spam rate:</strong> Whether recipients are rejecting the email program.</p></li><li><p><strong>Authentication:</strong> Whether legitimate mail is passing the expected checks.</p></li><li><p><strong>Delivery errors:</strong> Which failures or deferrals require action.</p></li><li><p><strong>Encryption:</strong> Whether transport is protected as expected.</p></li><li><p><strong>Feedback Loop:</strong> Which identified campaign or stream is associated with complaints.</p></li><li><p><strong>Deliverability analysis:</strong> Which diagnostic recommendations deserve attention.</p></li></ul><p>Older guides often show Domain Reputation and IP Reputation charts. Google says these legacy charts are being retired and excluded from v2. If you follow older troubleshooting instructions, check which interface they describe and use the current compliance and diagnostic views available to your account. <a href="https://support.google.com/mail/answer/16594218?hl=en">[29]</a></p><p>Spam rate needs careful interpretation. Google recommends keeping it below 0.1% and avoiding 0.3% or higher. Those are operational thresholds, not targets to approach deliberately. <a href="https://support.google.com/mail/answer/14229414?hl=en">[23]</a></p><p>The denominator is not simply every email your application attempted to send. Google&#8217;s metric concerns eligible inbox-delivered mail that users mark as spam. If much of your traffic is already filtered into spam, a low reported rate can be misleading. <a href="https://support.google.com/mail/answer/14668346?hl=en">[28]</a></p><p>Here is a simplified hypothetical illustration. Fifty complaints divided by 100,000 attempted sends looks like 0.05%. If the relevant inbox-delivered denominator were 20,000, the ratio would be 0.25%. The events and eligibility rules behind the denominators explain why dashboards can disagree.</p><p>I would check Postmaster routinely and after substantial changes. Put campaign dates, volume changes, new templates, and DNS deployments on the same timeline. If complaints rise after a reactivation campaign, that context is more useful than staring at the graph alone.</p><p>When a status says No data found, investigate volume and data availability. Do not treat missing data as proof of compliance or failure. When a change has just been deployed, give delayed reporting time to catch up while checking real messages and sending logs immediately.</p><p>At larger scale, Postmaster&#8217;s v2 API can feed internal monitoring. Google now exposes compliance and statistics capabilities through that API. The human responsibility stays the same: someone needs to understand the signal and decide what to change. <a href="https://developers.google.com/workspace/gmail/release-notes">[30]</a></p><h1><strong>Content that earns the next open</strong></h1><p>The technical system gets your message to a place where it can be seen. The content determines whether seeing it was worthwhile.</p><p>Use a recognizable sender name and an accurate subject. If the email says someone sent a message, that message should exist and be available to the recipient. If it says there is a new match, the product should have created a real match under its actual rules.</p><p>Dating users are especially sensitive to the possibility that activity is manufactured. A misleading notification can undermine confidence in the whole service. A short-term increase in clicks is a poor trade if the return experience makes the user trust you less.</p><p>Make the main action easy to understand. A new-message notification should lead to the relevant conversation. A recommendation digest should lead to the promised recommendations. If the user needs to sign in, preserve the destination through that process.</p><p>On mobile, test the handoff to the app and the fallback to the web. A deep link is simply a link intended to open a specific destination within an application. Its value disappears if it opens the wrong screen or strands a user who does not have the app installed.</p><p>Use readable text and a layout that survives blocked images. Provide a plain-text alternative where appropriate. Test common clients, dark mode, narrow screens, and accessibility settings. A template should communicate its purpose even when decorative elements fail.</p><p>Keep tracking infrastructure understandable. A branded tracking domain can make links easier to recognize, but redirects still add dependencies. Your unsubscribe, security, and action links should continue working through the full production path.</p><p>Finally, monitor replies. People often reply to a notification when they need help or want it to stop. A valid, monitored response path can turn confusion into a support resolution before it becomes a complaint.</p><h1><strong>Privacy is part of the email experience</strong></h1><p>A dating notification can reveal something the user considers private before they click anything.</p><p>Email previews can appear on a lock screen, shared computer, or work device. A subject line containing a name, photo-related detail, sexual preference, or explicit message excerpt may disclose more than the user expected.</p><p>Decide how much information belongs outside the authenticated product. A generic message alert gives less context but provides more discretion. A personalized preview may help someone recognize an interaction but creates more exposure. Offer sensible controls where the product calls for them.</p><p>Consider the sender name too. A brand name alone can reveal membership in a specialized dating service. The onboarding and preferences experience should make the notification behavior understandable.</p><p>Your internal systems also need restraint. Avoid putting private conversation text into analytics event names, unnecessary logs, or tracking URLs. Use identifiers that let authorized systems find the relevant record without copying sensitive content everywhere.</p><p>Account-access links need special care. A magic link signs a person in or authorizes an action through a token. Tokens should expire and have a clearly limited purpose. Avoid sending them through tracking arrangements that expose the token to additional services without a deliberate reason.</p><p>Automated scanners can inspect links before the person clicks. Design verification and account-access flows so those scans do not unexpectedly consume a one-time action or change account state merely by fetching a URL. Your engineering team should test the chosen flow in real mail environments.</p><p>Privacy and conversion are connected here. A user who feels exposed by your emails may disable the whole channel or leave the service. Respecting their expectations protects your future ability to communicate.</p><h1><strong>The notification program I would build</strong></h1><p>I would begin with messages tied to concrete user value and expand only when their behavior is measured.</p><p>Account emails come first. Verification, password recovery, significant security changes, and payment-related communication need clear wording and a dependable path. They should explain what happened, what the user can do, and how to get help when the action was unexpected.</p><p>Next come conversation notifications. An unread message from a legitimate account is a clear reason to return. Before sending, check that the message remains unread and accessible. If a person sends several messages in a short burst, grouping them can be more useful than creating one email per message.</p><p>Match notifications can also be valuable, provided they accurately reflect the product&#8217;s matching behavior. Make the next step obvious. A user should understand why opening the app now creates a useful opportunity.</p><p>Likes and profile activity need more judgment. An individual popular user may receive enough activity to generate excessive mail. A digest or frequency limit can preserve the signal. Describe activity accurately, especially when access to details depends on a subscription.</p><p>Recommendation emails should reflect actual preferences, location, availability, and account quality. Sending a person back to profiles outside their criteria wastes both their attention and your sending reputation.</p><p>Onboarding reminders should help someone reach the first valuable interaction. If a missing profile photo prevents meaningful participation, explain the reason and provide a direct path to upload it. Repeating &#8220;Complete your profile&#8221; without understanding the blocker may achieve little.</p><p>Winback campaigns need a stronger reason than the passage of time. Perhaps there are now relevant new members nearby, a requested feature has improved, or an unfinished conversation remains useful. If nothing meaningful has changed, repeated reminders can reinforce the user&#8217;s original reason for leaving.</p><p>Offers and subscription promotions belong in their own category. Measure the resulting purchases, refunds, retention, and complaints. A discount can produce short-term revenue while bringing back users who still have a poor experience.</p><p>Here is a practical starting matrix, to be adapted to the product rather than copied blindly:</p><ul><li><p><strong>Verify address:</strong> Check before sending: Still unverified and within resend limits; Destination: Confirmation flow.</p></li><li><p><strong>Password reset:</strong> Check before sending: Valid recent request and unexpired token; Destination: Secure reset flow.</p></li><li><p><strong>New message:</strong> Check before sending: Unread and accessible conversation; Destination: That conversation.</p></li><li><p><strong>New match:</strong> Check before sending: Match remains valid and visible; Destination: Match or conversation screen.</p></li><li><p><strong>Activity digest:</strong> Check before sending: Relevant activity remains available; Destination: Accurate activity summary.</p></li><li><p><strong>Profile reminder:</strong> Check before sending: Specific unfinished step still matters; Destination: That onboarding step.</p></li><li><p><strong>Reactivation:</strong> Check before sending: Credible value and eligible audience; Destination: The promised opportunity.</p></li><li><p><strong>Subscription offer:</strong> Check before sending: Eligible user and marketing permission; Destination: Clear offer and terms.</p></li></ul><p>The same event can be appropriate for one user and excessive for another. The notification system needs enough product context to tell the difference.</p><h1><strong>Frequency, timing, and coordination with push</strong></h1><p>Sending more emails can increase immediate visits while making the channel less effective over time. That tradeoff needs measurement.</p><p>Apply frequency limits across the whole program. If every team owns its own limit, a user can still receive a message alert, a match alert, a digest, an onboarding reminder, and a promotion in the same hour.</p><p>A shared notification decision should consider message importance and the user&#8217;s recent experience. Essential requested account messages may need different rules from optional engagement emails. Within optional traffic, prioritize events that are most likely to lead to a valuable action.</p><p>Timing also changes meaning. A new-message alert can be useful immediately. A recommendation digest might work better when the user is likely to have time to browse. Use the user&#8217;s timezone when you know it and define a reasonable fallback when you do not.</p><p>Coordinate with push and in-app activity. If Daniel has already opened the conversation, suppress the delayed email. If he is active in the app, another out-of-app interruption may add little value. If push is unavailable, email can play a more important role, subject to his preferences.</p><p>Do not assume push delivery means the notification was seen. The decision should use reliable product activity where possible, and experiments where the evidence is ambiguous.</p><p>Batch related events. Ten unread messages from the same conversation may justify one useful reminder. The content should remain accurate when the person eventually opens it.</p><p>I would test frequency changes with a broad set of outcomes. Did replies increase? Did weekly active participation improve? Did complaints and opt-outs increase? Did the apparent gain disappear after the first few days? A sustainable schedule should improve participation without exhausting the audience.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><h1><strong>Define every email metric before comparing it</strong></h1><p>At SkaDate, we track the main email events in Mixpanel: Sent, Delivered, Opened, and Clicked. For our Amazon SES setup, we connect the email events to product analytics ourselves, so we can follow what happens after the user returns: profile completion, a reply, a subscription purchase, or another useful action.</p><p>A more integrated service such as SendGrid has built-in email activity and statistics. That can save a new team time. Connecting selected events to Mixpanel can still be useful because it puts email activity next to the rest of the dating user journey.</p><p>Regardless of the dashboard, define the events before comparing them. Sent means the sending service accepted a submission; Delivered usually means the recipient&#8217;s mail server accepted it. Opened and Clicked are tracked interactions whose limitations we discuss in the next section. These are useful milestones, but they do not all establish that a human read the email.</p><p>Send rate can mean throughput, such as messages or recipients submitted per second. It can also be used informally for the proportion of intended notifications that were submitted. These should be separate metrics in your reporting.</p><p>Track the funnel from eligible events to actual submissions. If the product decides to send 10,000 notifications but only submits 7,000 because a worker stopped, an excellent downstream delivery rate will hide a substantial failure.</p><p>For a defined cohort of attempted recipient deliveries, track provider acceptance, receiving-server acceptance, unresolved deferrals, and failures. Allow enough observation time for the delivery outcome to mature. A message still being retried should not silently disappear from the accounting.</p><p>For campaign reporting, the following definitions are a useful starting point:</p><ul><li><p><strong>Delivery rate:</strong> Example definition: Receiving-server acceptances divided by attempted recipient deliveries; Interpretation limit: Does not measure inbox placement.</p></li><li><p><strong>Bounce rate:</strong> Example definition: Recorded final failures divided by attempted recipient deliveries; Interpretation limit: Depends on classification and observation window.</p></li><li><p><strong>Unique open rate:</strong> Example definition: Recipients with a tracked open divided by delivered recipients; Interpretation limit: Image fetching is an imperfect proxy for reading.</p></li><li><p><strong>Unique click rate:</strong> Example definition: Recipients with a tracked click divided by delivered recipients; Interpretation limit: Scanners and bots can create clicks.</p></li><li><p><strong>Click to open rate:</strong> Example definition: Unique clickers divided by tracked unique openers; Interpretation limit: Inherits uncertainty in both measures.</p></li><li><p><strong>Unsubscribe rate:</strong> Example definition: Recorded opt-outs divided by delivered recipients; Interpretation limit: State the scope and collection method.</p></li><li><p><strong>Product return rate:</strong> Example definition: Recipients with a qualifying return divided by the chosen recipient cohort; Interpretation limit: Attribution does not establish causation.</p></li></ul><p>Suppose a hypothetical campaign attempts delivery to 10,000 recipients. It records 9,800 receiving-server acceptances and 300 unique clickers. Under the definitions above, delivery rate is 98% and unique click rate is about 3.06%.</p><p>The arithmetic is simple. The interpretation requires care. Some clicks may be automated. Some accepted messages may be in spam. Some people may return without clicking the email, perhaps by opening the app directly.</p><p>Also distinguish unique recipients from total events. One person opening five times is different from five people opening once. A message-level view and a person-level view answer different questions.</p><p>Complaint rates require especially careful labeling. The complaint events your ESP receives are an incomplete view of recipient behavior, and mailbox providers use their own eligibility and denominator rules. Keep Gmail&#8217;s Postmaster rate identified as Gmail&#8217;s metric rather than treating it as interchangeable with a campaign dashboard percentage.</p><p>Break the results down by mailbox provider, message type, acquisition source, and user cohort. Use enough volume to avoid reacting to statistical noise, while still investigating concrete incidents involving essential account mail.</p><h1><strong>Email-attributed revenue: connecting emails to purchases</strong></h1><p><strong>The most important business metric is the revenue attributed to our emails.</strong> We should understand which transactional notifications and marketing campaigns bring users back and lead to subscriptions, in-app purchases, or other payments.</p><p>An email can serve several purposes at once. A notification tells someone about a new message or like. It also brings that person back into the product, where they may continue a conversation, discover a useful feature, or decide to purchase a subscription.</p><p>Consider this example:</p><ol><li><p>Daniel receives an email: &#8220;Someone liked your profile.&#8221;</p></li><li><p>He clicks the email and returns to the app.</p></li><li><p>He visits the likes screen and decides to upgrade.</p></li><li><p>He purchases a $30 subscription.</p></li></ol><p>Under our attribution rules, we can associate that purchase with the email that brought Daniel back.</p><p>This means a product notification can contribute to revenue even when the email itself contains no discount or subscription offer. <strong>We should measure revenue from both transactional emails and marketing emails.</strong></p><h2><strong>Track the revenue associated with each email type</strong></h2><p>Our reporting should help us answer questions such as:</p><ul><li><p>How much subscription revenue was attributed to new-like notifications?</p></li><li><p>Which recommendation emails led to in-app purchases?</p></li><li><p>How much revenue was attributed to a reactivation campaign?</p></li><li><p>Which email types generate the most revenue relative to the number of people receiving them?</p></li></ul><p>In Mixpanel or another analytics tool, we connect the email interaction with the user&#8217;s return and subsequent purchase. This lets us follow the journey beyond Sent, Delivered, Opened, and Clicked.</p><h2><strong>Measure both total revenue and revenue per recipient</strong></h2><p>Total attributed revenue tells us how much money is associated with an email campaign or notification type.</p><p><strong>Revenue per recipient</strong> helps us compare emails sent to audiences of different sizes:</p><p><strong>Revenue per recipient = attributed revenue &#247; number of recipients sent the email</strong></p><p>Here is a hypothetical example:</p><ul><li><p><strong>Recipients sent the email:</strong> 10,000.</p></li><li><p><strong>Purchases attributed to the email:</strong> 100.</p></li><li><p><strong>Revenue attributed to those purchases:</strong> $3,000.</p></li><li><p><strong>Revenue per recipient:</strong> $0.30.</p></li></ul><p>Under this definition, the campaign generated $0.30 in attributed revenue per recipient. We can compare that figure across campaigns, notification types, and user groups.</p><p>Delivery, open, and click metrics help explain how the email performed along the way. Revenue connects those interactions to a business outcome.</p><h2><strong>Define how a purchase gets credited to an email</strong></h2><p>Attribution needs a clear rule. For example:</p><blockquote><p>&#8220;Credit a purchase to the most recent email the user clicked within the previous 24 hours.&#8221;</p></blockquote><p>That is an illustrative rule, not a universal standard. The appropriate window depends on the product and the buying journey.</p><p>Use consistent rules when comparing results. Decide whether revenue means the first payment only or also includes later renewals. Also define how you handle refunds and purchases influenced by several channels, such as email, push, and advertising, so the same revenue is not counted multiple times in your overall totals.</p><p><strong>Attribution shows which purchases get credited to email under our chosen rules. It does not prove that every credited purchase happened because of the email.</strong> Some users would have purchased anyway. Experiments with a holdout group help measure the additional revenue the emails actually create.</p><p>For a dating business, the reporting should connect the complete journey: <strong>email &#8594; return to the product &#8594; useful activity &#8594; purchase &#8594; revenue.</strong></p><h1><strong>Why opens and clicks require interpretation</strong></h1><p>Traditional open tracking uses a small remote image. When the email client fetches it, the tracking system records an event. That mechanism observes an image request, which can differ from a person consciously reading the message.</p><p>Apple&#8217;s Mail Privacy Protection can download remote content in the background regardless of whether the user engages with the email. It also changes the network information exposed to the sender. An apparent open can therefore occur without a human reading the message. <a href="https://www.apple.com/legal/privacy/data/en/mail-privacy-protection/">[31]</a></p><p>Other factors can make opens disappear. A client may block images, a recipient may read only plain text, or caching may affect repeated requests. The measurement error goes in more than one direction.</p><p>Clicks have their own complications. Security systems can fetch links to inspect their destinations. That can create activity before the recipient has interacted. A spike in immediate clicks across every link in a message deserves investigation before anyone celebrates the campaign.</p><p>Use the provider&#8217;s available bot-filtering features, but retain a realistic view of their limits. A useful product event after the click is stronger evidence of human engagement: an authenticated session, a viewed conversation, a reply, or another meaningful action.</p><p>This affects experimentation. Choosing a subject-line winner solely by tracked open rate can reward differences in client mix or automated behavior. A more useful test connects the subject to qualified clicks, returns, and the desired product outcome.</p><p>It also affects list hygiene. If a privacy feature generates opens automatically, a person can look engaged in the email tool while being absent from the dating app for months. Use the product&#8217;s own activity history when deciding whether ongoing email is appropriate.</p><p>Opens remain a directional signal in a consistent context. I would use them alongside other evidence and avoid presenting them as an exact count of people who read the message.</p><h1><strong>Measure incremental conversations and retention</strong></h1><p>The strongest question is whether the email program causes additional valuable participation.</p><p>Attribution answers which activity followed an email interaction under a chosen rule. Incrementality asks what would have happened without that email. Active users often both click messages and return frequently, so attributing their entire activity to email can overstate the channel&#8217;s contribution.</p><p>A holdout group helps. For an optional engagement campaign, randomly select eligible users who will not receive it, then compare outcomes over a predefined period. Keep essential account and safety communications outside that marketing experiment.</p><p>Here is an illustrative test, not a claim about SkaDate results:</p><p><strong>Outcome over the test window:</strong></p><ul><li><p><strong>Eligible users:</strong> Email group: 10,000; Holdout group: 10,000.</p></li><li><p><strong>Users who return:</strong> Email group: 1,800; Holdout group: 1,500.</p></li><li><p><strong>Users who participate in a qualifying conversation:</strong> Email group: 600; Holdout group: 450.</p></li></ul><p>The observed return difference is three percentage points, equivalent to 300 additional returns in the treated group under the test&#8217;s assumptions. The conversation difference is 1.5 percentage points, equivalent to 150 additional participating users.</p><p>If the campaign&#8217;s relevant cost were $300, the simple observed cost would be $1 per incremental return or $2 per incremental conversation participant. That is more useful than dividing cost by every return after the send. A real analysis also needs uncertainty estimates and checks that the groups were comparable.</p><p>Dating creates an extra complication: users influence one another. An emailed user may reply to someone in the holdout group, improving that other person&#8217;s experience. This spillover can affect the measured difference. At sufficient scale, your analyst may use geographic or other suitable clusters, or explicitly account for network effects.</p><p>Look beyond the immediate session. Measure later participation, conversations with reciprocal replies, subscription outcomes where relevant, complaints, and opt-outs. Define a qualifying conversation clearly so the metric does not reward empty or abusive message volume.</p><p>Retention should reflect the value your product promises. A user who leaves because they formed a successful relationship is different from a user who leaves after finding nobody responsive. Email should help people make progress toward worthwhile interactions and dates.</p><h1><strong>A practical incident investigation</strong></h1><p>Suppose support reports that Gmail users are missing message notifications.</p><p>First, define the scope. Which stream is affected? When did the problem start? Does it affect Gmail only? Are messages absent, delayed, or found in spam? Are password resets affected too?</p><p>Next, trace a few real examples through the system. Confirm that the original product event occurred, the user was eligible, a job was created, and the provider accepted it. Match internal identifiers to provider events.</p><p>If the job was never created, investigate product logic. If it is waiting, investigate the queue and worker capacity. If the provider rejected the submission, inspect its error. If the destination deferred or rejected it, inspect the receiving response. If the receiving server accepted it, investigate placement and mailbox behavior with the recipient-side evidence available.</p><p>Then compare the timeline with recent changes: DNS edits, a new sender, a provider migration, a large campaign, an acquisition source, or a template deployment. Check Postmaster for the same period, allowing for reporting delays.</p><p>The following matrix keeps the investigation focused:</p><ul><li><p><strong>No provider event:</strong> First evidence to inspect: Application event and queue history; Likely action area: Application or worker logic.</p></li><li><p><strong>Authentication failure:</strong> First evidence to inspect: Original headers and exact DNS identities; Likely action area: Sender configuration.</p></li><li><p><strong>Temporary rejection:</strong> First evidence to inspect: SMTP response and retry history; Likely action area: Throttling and backoff.</p></li><li><p><strong>Invalid-recipient spike:</strong> First evidence to inspect: Bounce reasons and signup source; Likely action area: Verification and list quality.</p></li><li><p><strong>Complaint spike:</strong> First evidence to inspect: Campaign identifiers and audience history; Likely action area: Frequency, content, or consent.</p></li><li><p><strong>Accepted but unseen:</strong> First evidence to inspect: Recipient folder evidence and Postmaster; Likely action area: Filtering and recipient experience.</p></li><li><p><strong>Apple relay failures:</strong> First evidence to inspect: Registered sources and authentication; Likely action area: Relay configuration.</p></li></ul><p>Pause the problematic optional stream when necessary while preserving legitimate account operations where feasible. After fixing the cause, resume cautiously and monitor results. Avoid changing several infrastructure variables at once unless the incident requires it.</p><p>Write down what happened and the preventive change. If the incident came from a broken unsubscribe sync, the lasting fix is an observable, tested sync with an owner, not merely a one-off database correction.</p><h1><strong>A reference architecture for a dating product</strong></h1><p>Here is how I would turn these ideas into a coherent system using the stack discussed in this article.</p><p>The application knows the user&#8217;s account state, contact address, and notification preferences. It decides whether a useful notification should be sent, then submits the email to Amazon SES using SMTP.</p><p>Campaigns are managed through Sendy and sent through Amazon SES. The campaign audience is built from eligible users, with suppression and preference checks that remain effective when new data is imported.</p><p>Amazon SES handles email transport, retries, and its configured bounce and complaint suppression. Sendy provides campaign management and supported subscriber handling. The product respects notification preferences and account status, while email events feed the reporting tools.</p><p>Postmaster and other destination-specific tools provide an external view. Product analytics connects messages to subsequent sessions, replies, and retention. These are complementary data sources with different coverage.</p><ul><li><p><strong>Application database:</strong> Account state, contact addresses, and preferences.</p></li><li><p><strong>Notification decision:</strong> Relevance, eligibility, frequency, and channel choice.</p></li><li><p><strong>Notification sending:</strong> Submit appropriate application emails through SMTP.</p></li><li><p><strong>Amazon SES:</strong> Sending and provider delivery events.</p></li><li><p><strong>Sendy:</strong> Marketing audience and campaign workflow.</p></li><li><p><strong>Provider delivery reports:</strong> Delivery outcomes and configured automatic suppression.</p></li><li><p><strong>Postmaster and destination tools:</strong> Receiver-side diagnostics.</p></li><li><p><strong>Product analytics:</strong> Returns, conversations, experiments, and retention.</p></li></ul><p>For a small product, keep the setup understandable. Your sending provider can handle the transport details. Your team needs to configure it, monitor results, and decide which notifications actually help users.</p><p>As volume grows, invest where evidence shows a constraint. That may be dedicated IP management, better automation, stronger event retention, more sophisticated preferences, or a different campaign platform. The architecture should allow these changes without losing recipient history or breaking account messages.</p><h1><strong>The questions I would ask as a founder</strong></h1><p>You can review your email program without personally editing DNS records.</p><p>Ask your team to show a real notification email and confirm that SPF, DKIM, and DMARC pass for your sending domain. Open the provider&#8217;s bounce and suppression screens together and check that invalid addresses are handled automatically. Unsubscribe a test account and confirm that optional campaigns stop.</p><p>Open Google Postmaster Tools together. Identify any Needs work statuses, explain the spam-rate trend, and compare the period with recent campaigns. If there is no data, establish why and decide what other evidence is available.</p><p>Look at your notification inventory from the user&#8217;s perspective. Which messages can a person receive in one day? What stops duplication across email and push? What happens after an account is paused, deleted, or moderated? Where does each link take a person on a phone?</p><p>Then review the economics. Separate raw sending costs from software and operational costs. Confirm which provider plan is actually active. Make sure the most expensive line items correspond to capabilities your team uses.</p><p>Finally, ask for a product result. Which emails increase meaningful participation? Which ones generate activity that would have happened anyway? Which ones create complaints without improving conversations?</p><p>The value of understanding SMTP, DNS, authentication, and feedback loops is that you can connect the technical evidence to those business questions. You can distinguish an address-quality issue from a broken worker, a filtering problem from an inaccurate template, and a useful retention experiment from a campaign that merely produces clicks.</p><p>When Anna sends Daniel a message, the system should give him a timely, trustworthy opportunity to respond. When he has already responded, it should know that. When he asks for fewer emails, it should remember. When something fails, your team should be able to explain where and why.</p><p>That is the email foundation I want underneath a dating business.</p><h1><strong>Appendix A: A launch and audit checklist</strong></h1><p>Use this as a working review with the person responsible for your email program.</p><ul><li><p>Every sending service and domain has an identified owner and documented purpose.</p></li><li><p>A real message from each stream passes the intended authentication and alignment checks.</p></li><li><p>Forward and reverse DNS meet the requirements of the sending infrastructure.</p></li><li><p>The selected Amazon SES region has the required production access and sending capacity.</p></li><li><p>The active provider pricing plan and optional features are understood.</p></li><li><p>Essential account mail has appropriate priority over campaigns.</p></li><li><p>Notifications recheck read state, account state, and eligibility before sending.</p></li><li><p>Duplicate tasks and repeated provider events are handled safely.</p></li><li><p>Temporary failures have a controlled retry policy and stale notifications expire.</p></li><li><p>Invalid addresses and identifiable complaints trigger the appropriate suppression.</p></li><li><p>Marketing and subscribed notifications have functional opt-out paths.</p></li><li><p>One-click unsubscribe is implemented for the mail that requires it.</p></li><li><p>Opt-outs survive imports, queued campaigns, and provider migrations.</p></li><li><p>Google and Apple sign-in are configured to use the verified email identity supplied by the service.</p></li><li><p>Apple private relay delivery is tested through the actual sending configuration.</p></li><li><p>Gmail Postmaster is configured and reviewed by an accountable person.</p></li><li><p>Metrics name their denominator, time window, and provider coverage.</p></li><li><p>Open and click statistics are interpreted with privacy and automation limitations.</p></li><li><p>Important mobile links and fallback destinations work.</p></li><li><p>Product experiments measure useful returns and conversations alongside complaints.</p></li></ul><h1><strong>Appendix B: Reading a message with your developer</strong></h1><p>Ask for the full original message from a test mailbox. The following is an illustrative map using reserved example domains; it is not a copy-and-paste configuration.</p><ul><li><p><strong>Visible From:</strong> Example Dating at notifications@notify.example.com.</p></li><li><p><strong>Reply-To:</strong> support@example.com for human replies.</p></li><li><p><strong>Return-Path:</strong> A bounce address under bounce.notify.example.com.</p></li><li><p><strong>DKIM signing domain:</strong> notify.example.com.</p></li><li><p><strong>Authentication-Results:</strong> Receiver-reported SPF, DKIM, and DMARC results.</p></li><li><p><strong>Message-ID:</strong> The message identifier used in tracing.</p></li><li><p><strong>Feedback-ID:</strong> Campaign or stream identifiers for supported aggregate feedback.</p></li><li><p><strong>List-Unsubscribe:</strong> An HTTPS unsubscribe endpoint for the applicable subscription.</p></li></ul><p>Have the developer identify the domain checked by SPF and the domain signing with DKIM. Compare them with the visible From domain under the configured alignment rules. Then find the provider event for that same message.</p><p>For DNS, inspect the records supplied by the sending provider in the authoritative DNS service. SPF and DMARC normally appear as TXT records; DKIM uses the DNS records or aliases supplied by the provider. A custom Amazon SES MAIL FROM domain needs the exact MX and SPF configuration AWS specifies.</p><p>The point of this exercise is to connect names that otherwise look abstract. You should be able to see how your brand identity, provider configuration, DNS, and received message relate to one another.</p><h1><strong>Appendix C: A short glossary</strong></h1><ul><li><p><strong>API:</strong> An interface software uses to request work from another system.</p></li><li><p><strong>SMTP:</strong> Rules used to submit and transfer email.</p></li><li><p><strong>POP3:</strong> A protocol for retrieving mailbox messages.</p></li><li><p><strong>IMAP:</strong> A protocol for accessing and synchronizing a server mailbox.</p></li><li><p><strong>DNS:</strong> The naming system that publishes routing and policy information.</p></li><li><p><strong>MX:</strong> A DNS record identifying incoming mail servers.</p></li><li><p><strong>PTR:</strong> A DNS record associating an IP address with a hostname.</p></li><li><p><strong>SPF:</strong> A policy authorizing infrastructure for an envelope sender identity.</p></li><li><p><strong>DKIM:</strong> A domain-linked cryptographic message signature.</p></li><li><p><strong>DMARC:</strong> A policy connecting the visible sender domain to aligned authentication.</p></li><li><p><strong>TLS:</strong> Encryption protecting a connection between systems.</p></li><li><p><strong>ESP:</strong> Email service provider.</p></li><li><p><strong>Return-Path:</strong> The recorded address for delivery failure handling.</p></li><li><p><strong>Bounce:</strong> A delivery failure.</p></li><li><p><strong>Deferral:</strong> A temporary refusal that can be retried under a controlled policy.</p></li><li><p><strong>Feedback loop:</strong> A mechanism providing information about spam complaints.</p></li><li><p><strong>Suppression:</strong> A rule preventing a message from being sent to an ineligible recipient.</p></li><li><p><strong>Spam trap:</strong> An address used to detect unwanted sending or poor list practices.</p></li><li><p><strong>Warmup:</strong> Gradually establishing legitimate sending activity while monitoring responses.</p></li><li><p><strong>Webhook:</strong> An automated event notification sent between systems.</p></li><li><p><strong>Holdout:</strong> A comparison group excluded from an optional intervention.</p></li></ul><h1><strong>Sources and further reading</strong></h1><p>Technical documentation and listed pricing checked on October 28&#8211;29, 2026. Worked examples in this article are illustrative unless explicitly described as personal experience. Provider interfaces, policies, and prices can change.</p><p>[1] Amazon SES &#8212; Custom MAIL FROM domains. <a href="https://docs.aws.amazon.com/ses/latest/dg/mail-from.html">Open source</a></p><p>[2] IETF &#8212; Sender Policy Framework RFC 7208 and linked updates. <a href="https://www.rfc-editor.org/info/rfc7208/">Open source</a></p><p>[3] IETF &#8212; DKIM signatures RFC 6376 and linked updates. <a href="https://www.rfc-editor.org/info/rfc6376/">Open source</a></p><p>[4] IETF &#8212; DMARC RFC 9989 and aggregate reporting RFC 9990. These replace the relevant material in RFC 7489. <a href="https://www.rfc-editor.org/info/rfc9989/">Open source</a> and <a href="https://www.rfc-editor.org/info/rfc9990/">Open source</a></p><p>[5] Amazon SES &#8212; Shared and dedicated IP considerations. <a href="https://docs.aws.amazon.com/ses/latest/dg/dedicated-ip.html">Open source</a></p><p>[6] Spamhaus &#8212; Spamhaus Blocklist explanations. <a href="https://www.spamhaus.org/faqs/spamhaus-blocklist/">Open source</a></p><p>[7] Amazon SES &#8212; Requesting production access. <a href="https://docs.aws.amazon.com/ses/latest/dg/request-production-access.html">Open source</a></p><p>[8] Amazon SES &#8212; Event notifications and event data. <a href="https://docs.aws.amazon.com/ses/latest/dg/monitor-sending-activity-using-notifications.html">Open source</a> and <a href="https://docs.aws.amazon.com/ses/latest/dg/event-publishing-retrieving-sns-contents.html">Open source</a></p><p>[9] Sendy &#8212; Product features and licensing. <a href="https://sendy.co/">Open source</a></p><p>[10] Amazon SES &#8212; Pricing plans and &#224; la carte pricing. <a href="https://aws.amazon.com/ses/pricing/">Open source</a></p><p>[11] Resend &#8212; Transactional email pricing. <a href="https://resend.com/pricing">Open source</a></p><p>[12] Twilio SendGrid &#8212; Email API pricing and links to Marketing Campaigns. <a href="https://www.twilio.com/en-us/products/email-api/pricing">Open source</a></p><p>[13] Mailchimp &#8212; About Transactional Email. <a href="https://mailchimp.com/help/about-transactional-email/">Open source</a></p><p>[14] Yahoo &#8212; Complaint Feedback Loop. <a href="https://senders.yahooinc.com/complaint-feedback-loop/">Open source</a></p><p>[15] Google &#8212; Gmail Feedback Loop and Feedback-ID. <a href="https://support.google.com/mail/answer/6254652?hl=en">Open source</a></p><p>[16] Google &#8212; Backend authentication and authoritative email identities. <a href="https://developers.google.com/identity/sign-in/web/backend-auth">Open source</a></p><p>[17] Apple &#8212; Receiving a user identity token. <a href="https://developer.apple.com/documentation/signinwithapple/receiving-a-users-identity-token">Open source</a></p><p>[18] Apple &#8212; Configure private email relay service. <a href="https://developer.apple.com/help/account/capabilities/configure-private-email-relay-service/">Open source</a></p><p>[19] Apple &#8212; New domain for Sign in with Apple announced August 24 2026. <a href="https://developer.apple.com/news/?id=1ptvdtcm">Open source</a></p><p>[20] Spamhaus &#8212; Spam traps and the limits of apparent engagement. <a href="https://www.spamhaus.org/resource-hub/deliverability/unravelling-the-myths-of-spamtraps-clicking-links/">Open source</a></p><p>[21] Amazon SES &#8212; Account-level suppression lists. <a href="https://docs.aws.amazon.com/ses/latest/dg/sending-email-suppression-list.html">Open source</a></p><p>[22] IETF &#8212; One-click unsubscribe RFC 8058. <a href="https://www.rfc-editor.org/info/rfc8058/">Open source</a></p><p>[23] Google &#8212; Email sender guidelines FAQ including spam thresholds and unsubscribe. <a href="https://support.google.com/mail/answer/14229414?hl=en">Open source</a></p><p>[24] Yahoo &#8212; Sender requirements and recommendations. <a href="https://senders.yahooinc.com/best-practices/">Open source</a></p><p>[25] US Federal Trade Commission &#8212; CAN-SPAM compliance guide. <a href="https://www.ftc.gov/business-guidance/resources/can-spam-act-compliance-guide-business">Open source</a></p><p>[26] Google &#8212; Email sender guidelines. <a href="https://support.google.com/mail/answer/81126?hl=en">Open source</a></p><p>[27] Microsoft &#8212; Outlook high-volume sender authentication requirements. <a href="https://support.microsoft.com/en-gb/outlook/fix-ndr-error-550-5-7-515-in-outlook-com">Open source</a></p><p>[28] Google &#8212; Postmaster Tools dashboards. <a href="https://support.google.com/mail/answer/14668346?hl=en">Open source</a></p><p>[29] Google &#8212; Transition from the legacy Postmaster interface. <a href="https://support.google.com/mail/answer/16594218?hl=en">Open source</a></p><p>[30] Google &#8212; Gmail and Postmaster API release notes. <a href="https://developers.google.com/workspace/gmail/release-notes">Open source</a></p><p>[31] Apple &#8212; Mail Privacy Protection and privacy. <a href="https://www.apple.com/legal/privacy/data/en/mail-privacy-protection/">Open source</a></p><p>[32] Google &#8212; Sender requirements and Postmaster Tools FAQ. <a href="https://support.google.com/mail/answer/14289100?hl=en">Open source</a></p><p>Related articles by Alex Sergeev: <a href="https://alexsergeev.com/p/retention-is-king">Retention is King: How to Balance Your Unit Economics</a>; <a href="https://alexsergeev.com/p/how-to-actually-grow-a-dating-business">How to Actually Grow a Dating Business</a>; <a href="https://alexsergeev.com/p/the-foundation-solving-the-cold-start">The Foundation: Solving the Cold Start Problem in Dating</a></p><p></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p>]]></content:encoded></item><item><title><![CDATA[The Unit Economics of Dating Apps (Part 3): How to Scale Paid Ads]]></title><description><![CDATA[How to build a self-funding Growth Loop by mastering media buying and product conversion.]]></description><link>https://alexsergeev.com/p/the-unit-economics-of-dating-apps-5bc</link><guid isPermaLink="false">https://alexsergeev.com/p/the-unit-economics-of-dating-apps-5bc</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Wed, 25 Feb 2026 16:01:20 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/f8e645d9-fe60-4f5e-9361-cc15af258bfe_1376x768.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Welcome to the final piece of the puzzle. <a href="https://alexsergeev.com/p/the-unit-economics-of-dating-apps?r=459ko">In Part 1</a>, we dissected LTV (Customer Lifetime Value). In <a href="https://alexsergeev.com/p/the-unit-economics-of-dating-apps-a01?r=459ko">Part 2</a>, we broke down how to convert New Buyers.</p><p>Now, it is time to bring it all together and talk about the variable that bankrupts 90% of dating startups in their first year: <strong>Marketing Costs</strong>.</p><p>Let&#8217;s revisit the Golden Formula of the dating business:</p><blockquote><p><strong>Expected Revenue = (New Buyers &#215; LTV) &#8211; Marketing Costs</strong></p></blockquote><p>Why is it that when we talk about &#8220;marketing costs&#8221; in a scalable business, we almost exclusively mean paid traffic (Performance Marketing)? Because businesses require predictability. This formula only works when you know with absolute certainty: <em>if I invest $1 today, I am guaranteed to get $2 tomorrow.</em> Only paid channels provide that level of control.</p><p>But before we dive into the brutal mathematics of media buying, we need to establish one critical baseline.</p><h4>The Foundation: The Cold Start Problem Must Be Solved</h4><p>Paid traffic is not a magic wand you wave over an empty app. Think of it as a pure multiplier. You do not apply a multiplier to zero; you apply it to an ecosystem that is already working.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>For this article, we are assuming you have already solved the &#8220;Cold Start Problem.&#8221; You have basic liquidity, your ecosystem is alive, and new users are hitting their &#8220;Aha-Moment&#8221; (receiving their first like or message) organically.</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;2af3ab50-18d6-4f5e-b27e-577777879afd&quot;,&quot;caption&quot;:&quot;Today, we are looking at the single biggest hurdle for any new dating business: The Cold Start Problem.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;The Foundation: Solving the Cold Start Problem in Dating&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-12T21:32:42.682Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/0954e898-ca70-4ffb-aee2-1fcde1066515_1024x559.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/the-foundation-solving-the-cold-start&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:181462712,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p><em>(Note: If your product is still a ghost town, stop right here. Paid ads will kill your startup. Focus on building your initial base for free first).</em></p><h4>The Organic Trap: Great for Starting, Terrible for Scaling</h4><p>How did you acquire those first few hundred users? Most likely, you relied on guerrilla tactics and organic channels:</p><ul><li><p><strong>SEO and ASO</strong> (App Store Optimization)</p></li><li><p><strong>Content Marketing</strong> (YouTube, TikTok, Instagram Reels)</p></li><li><p><strong>Community Building</strong> (Facebook groups, WhatsApp chats, Reddit)</p></li><li><p><strong>Offline Events</strong> (Local parties, speed dating)</p></li></ul><p>These channels are fantastic for getting off the ground. But they share a fatal flaw: <strong>they do not scale predictably.</strong></p><ul><li><p><strong>SEO and ASO (The Glass Ceiling):</strong> These channels rely on <em>Demand Capturing</em>. You are capturing people who are already searching for &#8220;vegan dating in London.&#8221; That yields a hyper-targeted audience, but if only 500 people search for that a month, you hit a glass ceiling immediately.</p></li><li><p><strong>YouTube and TikTok (The Viral Lottery):</strong> Virality is amazing, but it is a lottery. You cannot walk into a Monday meeting and say, &#8220;We need 10,000 paying users in New York by Friday; let&#8217;s shoot a viral video.&#8221; The algorithm does not work for you.</p></li><li><p><strong>Communities and Offline (Manual Labor):</strong> Hustling in Facebook groups is grinding, manual labor. It simply does not allow for exponential growth.</p></li></ul><p>To control your growth with a budget slider, you have to step into the open market of paid advertising.</p><h4>The Proving Ground: What to Do With Your First $500 in Revenue?</h4><p>Let&#8217;s say your organic traffic is flowing, and the app is generating a modest $500 to $1,000 a month. You might think, <em>&#8220;Great! I&#8217;ll take $3,000, dump it into Facebook Ads, and 5x my revenue!&#8221;</em></p><p><strong>Stop.</strong> Organic traffic is warm and forgiving. If your free users coming from highly specific search terms are converting into paying subscribers at a 1% rate, cold traffic from Facebook will likely convert at 0.1%. You will burn through your runway in a weekend.</p><p>This is exactly where the concept of the <strong>Growth Loop</strong> comes into play. Let&#8217;s look at our formula again:</p><blockquote><p><strong>Expected Revenue = (New Buyers &#215; LTV) &#8211; Marketing Costs</strong></p></blockquote><p>For your business to scale, your Expected Revenue must be strictly greater than zero (&gt; 0). That positive difference is your true margin. In a sustainable business, you take that margin and immediately reinvest it back into buying more ads. This creates a compounding Growth Loop where the business systematically funds its own escalating turnover.</p><p>But&#8212;and this is the critical catch&#8212;this loop only spins if your <em>product</em> actually converts. It is not just about buying high-quality traffic; the app itself must be a ruthless conversion machine that reliably extracts LTV from subscribers so that your Expected Revenue stays above zero. Only then do you have the margin to feed back into the ad networks.</p><p>Throughout my 15+ years in this industry&#8212;building platforms like SkaDate and observing the inner workings of giants like Seeking, Meetville, and Dil Mil&#8212;I&#8217;ve seen this exact scenario play out constantly. The core of my growth work with existing dating projects is turning the product into a conversion machine <em>before</em> we open the floodgates to expensive ad networks.</p><p>Your organic traffic is your testing ground. Before buying a single click, you must extract maximum value from your current base and patch the holes in your funnel:</p><ol><li><p><strong><a href="https://alexsergeev.com/p/how-to-actually-grow-a-dating-business">Stop Building Random Features; Fix the Funnel</a>:</strong> Break down your &#8220;New Buyers&#8221; into two highly specific metrics: <strong>Paywall View Rate</strong> (the percentage of users who actually see your premium offer) and <strong>Purchase Conversion</strong> (the percentage of those who buy). As a former UX engineer, I can tell you that fixing the friction on these two screens will yield higher returns than any new matching algorithm.</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;515acccb-5bb2-4bfd-ac29-1da4fa26e3f1&quot;,&quot;caption&quot;:&quot;So, you already have your own dating app or site. It&#8217;s live on the App Store and Google Play. You have some sign-ups, maybe even a few purchases.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;How to Actually Grow a Dating Business&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-29T17:03:32.063Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/61e81450-8733-4753-9f29-21c6e7b39dff_1024x572.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/how-to-actually-grow-a-dating-business&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:182666813,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:1,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div></li><li><p><strong><a href="https://alexsergeev.com/p/the-unit-economics-of-dating-apps-a01">Engineer Motivation</a>:</strong> To maximize buyers, you must remove friction during the profile setup phase, but drastically spike the user&#8217;s motivation right before the paywall. Make staying on the &#8220;free tier&#8221; feel frustratingly inefficient.</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;bf263316-8fea-44c4-ba22-68be6c44749c&quot;,&quot;caption&quot;:&quot;Let&#8217;s continue studying the core formula of the dating business.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;The Unit Economics of Dating Apps (Part 2)&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-16T04:13:25.538Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/05ac2234-4f88-4230-bb5d-43ee0cf26929_1024x506.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/the-unit-economics-of-dating-apps-a01&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:181752542,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:1,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div></li><li><p><strong><a href="https://alexsergeev.com/p/retention-is-king">Patch the Leaky Bucket</a>:</strong> There is zero point in buying expensive traffic if users churn on Day 1 before experiencing the core value of the app. Rely on hard cohort analysis&#8212;tracking specific groups of users over time&#8212;not just blind faith in your product.</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;151a8912-0614-4b1d-b0d7-54b17c644a97&quot;,&quot;caption&quot;:&quot;Introduction: The Math That Doesn&#8217;t Forgive&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;Retention is King: How to Balance Your Unit Economics&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2026-02-01T22:53:02.909Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b5f68700-323e-4129-8779-5e3c90dd9245_1376x768.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/retention-is-king&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:186544971,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:1,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div></li></ol><p>Only when your product is efficiently converting free organic signups into paid subscriptions are you actually ready for Performance Marketing.</p><p></p><h4>Entering a Different World: Your Guide to the Ad Market</h4><p>Media buying for dating apps is nothing like running ads for a local bakery or a standard SaaS tool. If you are new to this, here is your step-by-step operational manual.</p><p><strong>Step 1: Face Control</strong></p><p>Dating is considered a &#8220;Restricted Category&#8221; across all major ad networks. You cannot just attach a credit card and launch a campaign. Before creating a single ad, you must apply for a specific Dating Certificate from Meta, Google, or TikTok.</p><p>Human moderators will review your website, privacy policy, age gates (strictly 18+), and user moderation mechanics. If you try to run dating ads without being on the official White List, your entire Business Manager account will receive an instant, permanent ban. Start this compliance process a month before your planned launch.</p><p><strong>Step 2: Platform Choice and Why Meta Rules Dating</strong></p><p>Historically, Meta (Facebook and Instagram) captures about 80% of dating ad budgets. Why not Google Search?</p><p>Because Google is <em>Demand Capturing</em> (catching existing intent). Meta is <em>Demand Generation</em>. A user scrolling Instagram is looking at memes; they aren&#8217;t actively trying to find a date. Our job is to interrupt their scrolling with a high-emotion video and generate the desire to download the app right now.</p><p>Furthermore, Meta has an absolute monopoly on one vital data point: the <strong>Relationship Status</strong> profile field. Neither TikTok nor Google has a database of billions of people who have voluntarily labeled themselves as &#8220;Single.&#8221; Targeting only single users means you don&#8217;t waste a single cent showing ads to married couples. Your Click-Through Rate (CTR) spikes, and your acquisition costs plummet.</p><p><strong>Step 3: How the Algorithm Actually Works</strong></p><p>Beginners think media buying is about manually guessing and selecting user interests like &#8220;single&#8221; or &#8220;likes dating.&#8221; Today, the AI does all the heavy lifting via Smart Bidding.</p><p>But the AI is blind until you train it. Here is exactly how it works:</p><p>You install a tracking code (an SDK or Facebook Pixel) into your app. This tracker acts as a direct communication line back to Facebook. When someone downloads your app, it sends a signal: <em>&#8220;Event: Install.&#8221;</em> But the magic happens deeper in the funnel. When a user finally swipes their card to buy a premium subscription, the tracker sends the ultimate signal: <em>&#8220;Event: Purchase.&#8221;</em> The Smart Bidding algorithm takes that specific buyer, analyzes thousands of their hidden data points (what they click, when they are active, what other apps they use), and automatically hunts for their behavioral &#8220;lookalikes&#8221; across the entire platform.</p><p>You are essentially saying to the machine: <em>&#8220;Here is exactly what a paying customer looks like; go find me a thousand more just like them.&#8221;</em> You do not manually find the users; you feed the algorithm purchase data so it can find them for you.</p><p><strong>Step 4: The Creative Testing Pipeline</strong></p><p>Because we are interrupting people, our only weapon is the &#8220;creative&#8221; (the ad itself). In dating, this almost exclusively means UGC (User-Generated Content)&#8212;videos that look like raw, authentic selfie-cam footage.</p><p>Creatives suffer from &#8220;ad fatigue&#8221; quickly, so you need a constant assembly line. Before you spend a dime, open the <strong><a href="https://www.facebook.com/ads/library/?active_status=active&amp;ad_type=all&amp;country=US&amp;is_targeted_country=false&amp;media_type=all&amp;q=tinder&amp;search_type=keyword_unordered&amp;sort_data[direction]=desc&amp;sort_data[mode]=total_impressions">Meta Ads Library</a></strong> (Facebook&#8217;s free public database of active ads). Type in competitors like Tinder, Bumble, or Hinge, and study exactly what video ads they are actively paying to run right now.</p><p>Use a two-stage launch strategy:</p><ul><li><p><strong>Test for Installs (Cheap Data):</strong> Launch 5-10 different videos optimized purely for &#8220;App Installs.&#8221; The goal isn&#8217;t profitability yet; it&#8217;s to cheaply discover which video stops the scroll and gets clicks (highest CTR).</p></li><li><p><strong>Optimize for Purchases (The Money Maker):</strong> Take the winning video and launch your core campaign. Now, command the Smart Bidding algorithm to find only users likely to trigger the &#8220;Purchase&#8221; event. The AI will squeeze maximum paying customers out of your proven ad.</p></li></ul><p><strong>Step 5: The Margin Battle</strong></p><p>If you send Facebook traffic directly to the App Store or Google Play, you are bleeding money.</p><ul><li><p><strong>The Baseline Fix:</strong> Apple and Google take a standard 30% cut of every transaction. Apply for the Small Business Program immediately. Until you hit $1 million in annual revenue, they drop the fee to 15%. This 15% margin swing is life or death for early startups.</p></li><li><p><strong>The Pro Move (Web2App):</strong> When Apple introduced iOS 14.5 (App Tracking Transparency), they severely restricted Facebook&#8217;s ability to track what users do inside your app. To bypass both the 30% store tax and the tracking blackout, industry leaders use Web-to-App funnels. The user clicks the ad, lands on a mobile website, completes an onboarding quiz, buys the subscription via Stripe (which only charges a 3% processing fee), and <em>only then</em> is directed to download the app.</p></li></ul><p><strong>Step 6: The Price of Admission</strong></p><p>Here is the hardest truth about Smart Bidding: the machine demands volume to learn. To exit the &#8220;learning phase&#8221; and stabilize, Facebook&#8217;s algorithm requires a minimum of 50 &#8220;Purchase&#8221; events per week per campaign.</p><p>Let&#8217;s do the math. If a registration costs you $5, and your purchase conversion rate is a healthy 5%, you need 20 registrations to get one paying user ($5 &#215; 20 = $100). That is a $100 Cost Acquisition Cost (CAC).</p><p>To get your 50 purchases a week, you must spend $5,000 weekly ($100 &#215; 50) just to train the algorithm properly. Launching a $300 &#8220;test&#8221; campaign is practically a charitable donation to Mark Zuckerberg.</p><h4>Death by Cash Flow and the Savior of Blended CAC</h4><p>Once your campaigns are running, your entire existence revolves around <strong>CAC</strong>&#8212;the exact dollar amount it costs to buy one paying subscriber.</p><p>Let&#8217;s say in the US market, a high-quality registration costs $7. At a 5% conversion rate, your CAC is $140. If your LTV (Lifetime Value) is only $40, you are losing $100 per user. Why do companies still play this game? Two reasons:</p><ol><li><p><strong>Blended CAC (The Halo Effect):</strong> When you buy one user for $140 via Meta, they do not arrive in a vacuum. Their download pushes your app higher in the App Store rankings, they tell their single friends, and they trigger organic virality. That one paid user might bring in 3 free organic users. Suddenly, your <em>total</em> acquisition cost (Blended CAC) drops from a ruinous $140 to a sustainable $35. Your organic foundation subsidizes your paid scaling.</p></li><li><p><strong>The Payback Period &amp; Growth Tools:</strong> Even if your LTV is a fantastic $150, you can still go bankrupt. If you pay Facebook $140 today, but collect that $150 from the user in $25 monthly increments, you will run out of cash before month three. Worse, Apple holds your App Store revenue for up to 45 days before paying it out.</p><p>If you are aggressively feeding your Growth Loop, a 45-day delay is a death sentence. This is why founders use revenue-based financing tools like <strong>Braavo</strong> (Braavo Capital). These platforms connect to your App Store and advance your incoming revenue to you by the next week. You bypass Apple&#8217;s 45-day wait, ensuring you always have immediate cash to reinvest into tomorrow&#8217;s ads.</p></li></ol><h4><br>The Ultimate Marketing Paradox</h4><p>The great secret that performance agencies won&#8217;t tell you is this: <strong>You cannot win a marketing war with marketing alone.</strong></p><p>Traffic costs have a market floor dictated by the auction. The only mathematically viable way to make the formula <em><strong>Revenue = (New Buyers &#215; LTV) &#8211; Marketing Costs</strong></em> work is to relentlessly improve your product. The better your onboarding converts free traffic into upfront cash, the more aggressively you can spin your Growth Loop and outbid your competitors. Product dictates marketing, not the other way around.</p><p>In my next article, I&#8217;ll show you how to tie all of this together. I&#8217;ll share my exact playbook for stepping in as a Growth Partner for dating apps, absorbing the heavy lifting of &#8220;product mathematics&#8221; so founders can focus entirely on vision and scale.</p><p></p><h3>Why Build From Scratch?</h3><p>You just learned the brutal math of Blended CAC and Growth Loops. To make this math work and actually scale your ads, your app cannot be a leaky bucket. It must be a ruthless conversion machine.</p><p>Building a high-converting onboarding funnel, testing optimal paywall placements, and coding complex monetization mechanics like &#8220;Super Like&#8221; or &#8220;See Who Liked Me&#8221; from scratch will drain your runway before you even launch your first campaign.</p><p><strong>This is why we built SkaDate.</strong></p><p>We provide a battle-tested dating engine engineered specifically for <strong>maximum subscriber conversion</strong>. We have already done the heavy lifting&#8212;from frictionless registration flows to aggressive paywall triggers and out-of-the-box premium features. You do not need to hire a dev team to reinvent the wheel.</p><p>Stop treating your MVP like an expensive IT research project. Buy the engine, launch faster, and deploy your capital where it actually scales your business: <strong>buying traffic and feeding your Growth Loop.</strong></p><p>Ready to skip the development nightmare?</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://calendly.com/alex-funnelflex/skadate-qa&quot;,&quot;text&quot;:&quot;Discuss Your Project with Me&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://calendly.com/alex-funnelflex/skadate-qa"><span>Discuss Your Project with Me</span></a></p><p><em>You focus on finding the users; we&#8217;ll make sure the technology keeps them there.</em></p><h3></h3>]]></content:encoded></item><item><title><![CDATA[How 3 simple features created an $8 billion dollar dating empire]]></title><description><![CDATA[We analyzed Tinder, Bumble, and Hinge to find the three universal monetization features shared by every major dating app.]]></description><link>https://alexsergeev.com/p/how-3-simple-features-created-an</link><guid isPermaLink="false">https://alexsergeev.com/p/how-3-simple-features-created-an</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Sun, 15 Feb 2026 19:16:05 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/3088dbb3-eea0-4d7c-8a1d-772754267083_1392x768.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Let&#8217;s get straight to the point.</p><p>The dating industry is not a monolith. The Hinge audience, looking for &#8220;the one,&#8221; is radically different from college students on Tinder looking for a weekend adventure. The matriarchy of Bumble feels nothing like the conservative ecosystem of Plenty of Fish. Niche apps like BLK or Chispa create entirely unique cultural micro-climates.</p><p>These are different products, different brands, and completely different people with different goals.</p><p>But if you look &#8220;under the hood&#8221; of their financial reports, you will see a startling picture.</p><p>Take the two giants of the market:</p><ul><li><p><strong>Match Group</strong> (owners of Tinder, Hinge, OkCupid, Match, BLK, Chispa): Market Cap ~$7.36B.</p></li><li><p><strong>Bumble Inc.</strong> (Badoo, Bumble): Market Cap ~$781.5M.</p></li></ul><p>Combined, this is an empire worth over <strong>$8 billion</strong>.</p><p>And the most amazing thing about this machine is that <strong>90% of all that money is generated by the exact same three features.</strong></p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>I&#8217;ve conducted deep product analysis on the market flagships: from mass-market Tinder to &#8220;ethical&#8221; Bumble, from marriage-oriented Hinge to ethnic niches. Despite different designs, philosophies, and demographics, they all exploit the same fundamental human vulnerabilities: <strong>Impatience, Ego, and Fear.</strong></p><p>In this article, we will dissect the &#8220;Holy Trinity&#8221; of dating monetization. We aren&#8217;t talking about abstractions. We are breaking down the concrete mechanics of three buttons that uphold the economy of love in the 21st century:</p><ol><li><p><strong>See Who Liked You</strong> (Selling Certainty).</p></li><li><p><strong>Super Like</strong> (Selling Dominance and Visibility).</p></li><li><p><strong>Unlimited Swipes</strong> (Selling Air).</p></li></ol><p>Welcome to the real world of the dating business.</p><h2><br>1. The Anatomy of &#8220;See Who Liked You&#8221;</h2><p>To understand how this function generates billions, you first need to understand the basic architecture of any swipe-based dating app. If you&#8217;ve never used Tinder, imagine the app is divided into two distinct &#8220;rooms.&#8221;</p><div class="image-gallery-embed" data-attrs="{&quot;gallery&quot;:{&quot;images&quot;:[{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/4a1dff07-c87a-400d-ac56-b5741552108b_1320x2868.png&quot;},{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/c9c7d791-9c26-4b28-9b24-49c1286c57fe_1320x2868.png&quot;},{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bd844b03-1cd2-4e21-b08b-5470b856a81d_1320x2868.png&quot;},{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/228fe35a-e5ba-489a-b782-862a14d7d38a_1320x2868.png&quot;}],&quot;caption&quot;:&quot;Comparison of the \&quot;See Who Liked You\&quot; feature interface across Tinder, Bumble, Hinge, and BLK.&quot;,&quot;alt&quot;:&quot;A collage of screenshots from Tinder, Bumble, Hinge, and BLK dating apps showing the \&quot;likes sent to you\&quot; section. The interface displays a grid of profile cards with blurred user photos, names like Gauri and Stephanie, and status labels such as \&quot;Recently Active\&quot; or \&quot;Liked your photo.\&quot;&quot;,&quot;staticGalleryImage&quot;:{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/63d32d91-3c7a-4b8a-8b68-cb7406fbd6b9_1456x1456.png&quot;}},&quot;isEditorNode&quot;:true}"></div><p></p><h3>The Architecture: Two Rooms</h3><p><strong>Room #1: The Stack (The Feed)</strong></p><p>This is the main screen where the work happens. You see profile cards one by one.</p><ul><li><p>Swipe Right: &#8220;Like.&#8221;</p></li><li><p>Swipe Left: &#8220;Pass.&#8221;</p></li><li><p><strong>The Blind Spot:</strong> In this feed, you see people, but you don&#8217;t know if they have liked you or not. To you, every card looks the same.</p></li></ul><p><strong>Room #2: The &#8220;Likes You&#8221; Grid (The Secret Room)</strong></p><p>This is the backlog where the profiles of everyone who has <em>already</em> swiped right on you are stored.</p><ul><li><p><strong>In the Free Version:</strong> The door to this room is transparent but frosted. You see that people are there (a &#8220;99+ Likes&#8221; badge) and you see blurred silhouettes. But you cannot see faces or names.</p></li></ul><h3>The Fundamental Problem: &#8220;The Tragedy of the Left Swipe&#8221;</h3><p>In the free version, the user is forced to play a game of <em>Minesweeper</em> in Room #1.</p><p>Imagine this scenario: You are shown a card of a girl. She is cute, but not perfect. You hesitate... and you swipe left.</p><p><strong>The Problem:</strong> In that moment, you may have made a fatal error. Perhaps that girl had already liked you. By swiping left, you destroyed the Match. You will never know that you just missed out on a person who was genuinely interested in you.</p><p>This is <strong>Information Asymmetry</strong>, and it is exactly where Match Group prints money.</p><h3>The Mechanics of Pain: Abundance vs. Scarcity</h3><p>Users live in two different realities, but the solution (buying a subscription) is the same for both.</p><p><strong>Problem A: &#8220;The Curse of Abundance&#8221; (Typically Women)</strong></p><p>For a popular woman, the Feed is an endless stream. She has 1,000+ likes sitting in her &#8220;Secret Room.&#8221;</p><ul><li><p><strong>The Pain:</strong> If she wants to find a date <em>right now</em>, she has to spend hours scrolling through the general feed, hoping to stumble upon one of the men who already liked her. It&#8217;s like finding a needle in a haystack.</p></li><li><p><strong>The Solution:</strong> She buys Gold, opens the &#8220;Likes You&#8221; list, and picks the best candidate in 60 seconds.</p></li></ul><p><strong>Problem B: &#8220;FOMO&#8221; (Typically Men)</strong></p><p>For the average guy, every like is precious.</p><ul><li><p><strong>The Pain (Fear Of Missing Out):</strong> He is tormented by paranoia: <em>&#8220;What if that blonde I just swiped left on actually liked me? I just killed my own chance!&#8221;</em></p></li><li><p><strong>The Solution:</strong> He buys Gold to insure his risks. He wants to see who liked him so he doesn&#8217;t accidentally reject an interested woman.</p></li></ul><h3>Product Metaphor: Cassette vs. Spotify</h3><p>As a Product Manager, I explain the difference between the free and paid versions through the evolution of music.</p><ul><li><p><strong>Free Version = The Cassette Tape (Sequential Access).</strong> You are forced to &#8220;listen&#8221; (swipe) through everything in order. You waste time fast-forwarding through songs you don&#8217;t like. You never know if the next track will be a hit (a Match). You are working blindly.</p></li><li><p><strong>Paid Version = Spotify / CD (Random Access).</strong> The &#8220;See Who Liked You&#8221; function gives you a dashboard. You go into the list, see everyone who wants you, and you press &#8220;Play&#8221; (Match) on the ones you like.</p></li></ul><p><strong>The Verdict:</strong> We are selling <strong>Certainty</strong> and <strong>Time</strong>. We move dating from a Probabilistic model (&#8221;maybe I&#8217;ll meet someone&#8221;) to a Deterministic one (&#8221;here is the list, choose one&#8221;). Without a subscription, you are a slave to the algorithm. With a subscription, you are the master of the data.</p><h2><br>2. The Anatomy of &#8220;The Super Like&#8221;</h2><p>To understand why this button generates hundreds of millions of dollars, we need to take off the rose-colored glasses and look at the <strong>Fundamental Imbalance</strong> of the market.</p><div class="image-gallery-embed" data-attrs="{&quot;gallery&quot;:{&quot;images&quot;:[{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/0751fe38-3636-48b2-ab7c-866cb89316ad_1320x2868.png&quot;},{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/b575511a-6fb5-4585-ba68-9ed872579a07_1320x2868.png&quot;},{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/cf3938e2-be95-4c0a-a581-f2d9a07d5e9e_1320x2868.png&quot;},{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/0edbcc72-2b9a-4687-991d-c718fb1be29d_1320x2868.png&quot;}],&quot;caption&quot;:&quot;The \&quot;Super Like\&quot; mechanics: How Tinder, Bumble, and Hinge sell visibility and priority access.&quot;,&quot;alt&quot;:&quot;Screenshots of \&quot;Super Like\&quot; monetization features: Hinge&#8217;s Roses, Bumble&#8217;s SuperSwipes, and Tinder&#8217;s Super Likes. The images show pricing tiers and marketing copy promising users they will \&quot;stand out\&quot; and bypass the standard match queue.&quot;,&quot;staticGalleryImage&quot;:{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/f77afc1c-73be-4929-8c68-10a2f98ac5d9_1456x1456.png&quot;}},&quot;isEditorNode&quot;:true}"></div><p></p><h3>The Problem: Invisibility and Inflation</h3><p>In the free version of a dating app, the average man is invisible.</p><ul><li><p><strong>The Male Strategy (&#8221;Spray and Pray&#8221;):</strong> Men tend to swipe right on 40&#8211;60% of all women. This creates massive outbound noise.</p></li><li><p><strong>The Female Reality (Overload):</strong> A verified girl in a major city has a Stack clogged with thousands of profiles.</p></li><li><p><strong>The Tragedy of the Ordinary Like:</strong> When you send a standard like, you get in the back of the line. You might be number 3,548 in her queue. She physically cannot swipe enough to reach you. Even if you are the ideal candidate, your like drowns in inflation. <strong>She will never see your card.</strong></p></li></ul><p><strong>The Solution:</strong> You need a tool to elbow your way to the front.</p><h3>How It Works: Blindness vs. Insight</h3><p><strong>Scenario A: Ordinary Like (The Blind Game)</strong></p><p>Even if she eventually reaches your card, she <em>doesn&#8217;t know</em> if you liked her.</p><ul><li><p><strong>Risk:</strong> She hesitates and swipes left.</p></li><li><p><strong>Result:</strong> Match destroyed. Mutual attraction killed by algorithmic blindness.</p></li></ul><p><strong>Scenario B: Super Like (Cards on the Table)</strong></p><p>A Super Like changes the UI physics. When the algorithm serves her your card, it looks different.</p><ul><li><p><strong>She sees it immediately:</strong> The card is highlighted blue, has a star, or says <em>&#8220;Super Liked You.&#8221;</em></p></li><li><p><strong>She knows BEFORE she decides:</strong> The moment she looks at your photo, she knows you have already shown strong interest&#8212;and spent money to do so.</p></li><li><p><strong>Result:</strong> She makes a decision with her eyes open. The risk of accidentally swiping left on an interested person vanishes.</p></li></ul><h3>Technical Mechanics: Queue Injection</h3><p>Many founders think a Super Like is just a sticker. It&#8217;s not. The primary value you are selling is <strong>Priority</strong>.</p><ol><li><p><strong>Queue Jumping:</strong> The backend takes your card and physically moves it from position #3,548 to position #1.</p></li><li><p><strong>Impressions:</strong> You are buying a guaranteed view. Next time she opens the app, you are the first thing she sees.</p></li><li><p><strong>Visibility:</strong> You penetrate &#8220;banner blindness&#8221; with visual dominance (blue borders, animations).</p></li></ol><h3>The Economics of &#8220;Costly Signaling&#8221;</h3><p>Why is the conversion rate of a Super Like 3x higher than a regular like? In economics, this is called <strong>Costly Signaling</strong>.</p><p>Signals that cost nothing (regular likes) are ignored because they are cheap to produce.</p><ul><li><p><strong>Inflation:</strong> &#8220;Spray and Pray&#8221; devalues the regular like.</p></li><li><p><strong>Value:</strong> A Super Like costs real money or is strictly rationed.</p></li><li><p><strong>The Message:</strong> The blue star says: <em>&#8220;I chose you specifically out of thousands. I am not a bot. I spent resources on you.&#8221;</em></p></li></ul><p><strong>Pricing Strategy: Controlling the Supply</strong></p><p>Match Group defends the value of this signal by keeping the price high and the supply low.</p><p><strong>1. The Subscription Hook (&#8221;Use it or Lose it&#8221;)</strong> Subscribers get a &#8220;drip feed&#8221; of Super Likes to keep them logging in weekly.</p><ul><li><p><strong>Tinder Gold:</strong> 2 Free Super Likes per week.</p></li><li><p><strong>Tinder Platinum:</strong> 3 Free Super Likes per week.</p></li><li><p><em>The Catch:</em> They do not rollover. If you don&#8217;t use them, they burn.</p></li></ul><p><strong>2. A La Carte Pricing (The Revenue Driver)</strong> If you want more than your weekly ration, you have to pay a premium. The current US pricing tiers are aggressive:</p><ul><li><p><strong>3 Super Likes:</strong> ~$9.99 (~$3.33 / unit)</p></li><li><p><strong>15 Super Likes:</strong> ~$35.00 (~$2.33 / unit)</p></li><li><p><strong>30 Super Likes:</strong> ~$60.00 (~$2.00 / unit)</p></li></ul><p><strong>The Psychological Anchor:</strong> By setting the base price at <strong>~$3.33</strong>&#8212;roughly the cost of a cup of coffee&#8212;the app converts a &#8220;mindless digital action&#8221; into a considered <strong>investment</strong>. You don&#8217;t spam a button that costs $3 to press. You use it only when it matters.</p><h2><br>3. The Anatomy of &#8220;Unlimited Swipes&#8221;</h2><p><strong>What we are selling:</strong> Air, an &#8220;All-You-Can-Eat Buffet,&#8221; and the Right to be Wrong.</p><p>This feature is the foundation of the basic paid tier. To understand its value, you have to ask a counter-intuitive question: <strong>&#8220;Why limit swipes in the first place?&#8221;</strong></p><p>After all, a swipe is a digital action. It costs the company nothing. The servers won&#8217;t melt down if a user swipes 1,000 times instead of 100.</p><p>The answer is cynical: <strong>The swipe limit is an artificial scarcity upon which the entire economy of the app rests.</strong></p><h3>Why Limits Exist: Inventory Management</h3><p>We limit free users (usually ~100 likes per 12 hours) not because we are greedy, but to save the ecosystem from burning out.</p><p><strong>1. Inventory Management</strong></p><p>Dating is a business with <strong>finite inventory</strong>. Unlike TikTok, where content is infinite, the number of active single people within 10 miles of Walnut Creek is strictly limited.</p><ul><li><p><strong>The &#8220;Vacuum&#8221; Scenario:</strong> An active male user can physically evaluate 2,000 profiles in an evening. In a mid-sized city, he will &#8220;burn through&#8221; the entire database of active women in 48 hours.</p></li><li><p><strong>Churn Risk:</strong> On day 3, he opens the app, sees the &#8220;No new people around&#8221; screen, decides the app is dead, and deletes it.</p></li><li><p><strong>The Fix:</strong> We ration profiles. We artificially stretch consumption so the user comes back for 30 days, rather than eating everything in two.</p></li></ul><p><strong>2. The Psychological Trap: &#8220;The Hot State Paywall&#8221;</strong></p><p>The limit doesn&#8217;t hit randomly. The algorithm blocks you exactly when you are most engaged.</p><ul><li><p>You are in a &#8220;Flow&#8221; state. You&#8217;ve caught a rhythm. You see the girl of your dreams on the screen... and <strong>BAM!</strong></p></li><li><p><em>&#8220;Out of Likes. Want to like her? Pay up.&#8221;</em></p></li><li><p>This is selling at peak demand. It is physically painful for a human to stop when they are &#8220;heated up&#8221; with dopamine.</p></li></ul><h3>The Hidden Mechanic: The Noise Generator (Cross-Side Network Effect)</h3><p>And now, the <strong>key insight</strong> you won&#8217;t read in standard blogs.</p><p>Why does Tinder sell &#8220;Unlimited Swipes&#8221; in its cheapest subscription tier? Why not make this an elite feature?</p><p>Because users with unlimited swipes are the <strong>unpaid workforce</strong> of Tinder.</p><ol><li><p><strong>Notification Generation:</strong> A man with unlimited swipes starts liking thousands of women.</p></li><li><p><strong>Creating Hype:</strong> These likes trigger push notifications for women: <em>&#8220;Someone likes you!&#8221;</em> This brings women back into the app (Retention).</p></li><li><p><strong>Selling Gold:</strong> The woman logs in, sees &#8220;99+ Likes,&#8221; and feels overwhelmed. To sort through the noise, she is forced to buy <strong>Tinder Gold</strong> (See Feature #1).</p></li></ol><blockquote><p><strong>The Brutal Truth:</strong> By selling cheap &#8220;Unlimited Swipes&#8221; to one group (men), the app uses their labor to create an &#8220;Abundance Problem&#8221; for the other group (women), forcing the latter to buy expensive filters.</p><p>The guy with the unlimited subscription thinks he bought an advantage for himself. In reality, he paid to become a traffic generator for the platform.</p></blockquote><h3>Summary</h3><p><strong>Unlimited Swipes</strong> is the sale of air. The application takes an artificial restriction&#8212;which it created itself to protect its own economy&#8212;and sells the removal of that restriction as a premium feature. It is a tax on impatience and the primary tool for pumping activity into the ecosystem.<br><br></p><h2>Conclusion</h2><p>Let&#8217;s be honest: The $8 billion empire of Match Group wasn&#8217;t built on &#8220;better matching algorithms&#8221; or &#8220;true love.&#8221; It was built on these three buttons.</p><p><strong>Impatience. Ego. Fear.</strong></p><p>These are the raw materials of the dating business. If you are building a dating app in 2026, you don&#8217;t need to reinvent the wheel. You don&#8217;t need to dream up some complex, never-before-seen monetization model. You simply need to give your users the tools they are already willing to pay for.</p><p>The market has already been trained. Users <em>expect</em> to pay for certainty (&#8221;Who Liked Me&#8221;), for priority (&#8221;Super Like&#8221;), and for freedom (&#8221;Unlimited Swipes&#8221;).</p><p>The only question left is: Are you going to spend the next 12 months trying to code these psychological triggers from scratch, or are you going to start generating revenue on Day 1?</p><h2>Why Build From Scratch?</h2><p>You are entering a market where speed and execution are everything. Your job as a founder is to focus on <strong>User Acquisition</strong> and <strong>Unit Economics</strong>, not on debugging the backend logic of a &#8220;queue injection&#8221; for a Super Like feature.</p><p>Coding these monetization layers is deceptively difficult. You have to handle the blurred image layering, the database queries for &#8220;who liked me&#8221; (which are resource-heavy), and the precise countdown timers for swipe limits.</p><p><strong>This is why we built <a href="https://skadate.com">SkaDate</a>.</strong></p><p>We have already engineered these exact revenue generators. You don&#8217;t need to hire a dev team to build them; you just need to activate them.</p><p>The SkaDate engine offers <a href="https://www.skadate.com/plugins/?type=premium">ready-to-deploy plugins</a> for the &#8220;Holy Trinity&#8221; of monetization:</p><ul><li><p><strong>&#8220;See Who Liked You&#8221; Plugin:</strong> Out-of-the-box functionality to blur profiles and upsell the &#8220;reveal&#8221; to your users.</p></li><li><p><strong>&#8220;Super Like&#8221; Plugin:</strong> Native logic that highlights profiles and pushes them to the top of the matching queue.</p></li><li><p><strong>&#8220;Swipe Volume Control&#8221; Plugin:</strong> Flexible settings to limit free users and instantly unlock &#8220;Unlimited Swipes&#8221; for premium subscribers.</p></li></ul><p>Stop treating your MVP like a research project. Buy the engine, install the plugins, and launch a product that is ready to monetize from the first download.</p><p>Ready to skip the development nightmare?</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://calendly.com/alex-funnelflex/skadate-qa&quot;,&quot;text&quot;:&quot;Discuss Your Project with Me&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://calendly.com/alex-funnelflex/skadate-qa"><span>Discuss Your Project with Me</span></a></p><p><em>You focus on finding the users; we&#8217;ll make sure the technology keeps them there.</em></p>]]></content:encoded></item><item><title><![CDATA[Retention is King: How to Balance Your Unit Economics]]></title><description><![CDATA[We break down what retention actually is, how to measure it, and why it&#8217;s the only way to align your $140 CAC with your $30 LTV.]]></description><link>https://alexsergeev.com/p/retention-is-king</link><guid isPermaLink="false">https://alexsergeev.com/p/retention-is-king</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Sun, 01 Feb 2026 22:53:02 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/b5f68700-323e-4129-8779-5e3c90dd9245_1376x768.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<h3>Introduction: The Math That Doesn&#8217;t Forgive</h3><p>The dating industry has fundamentally changed. The era of &#8220;growth at all costs&#8221; is dead and buried. As I mentioned in my previous post, <strong><a href="https://alexsergeev.com/p/paid-ads-are-suicide-the-real-math">Paid Ads Are Suicide,</a></strong> trying to solve your growth problems by simply throwing money at them is now a death sentence for startups.</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;9924462e-aaf5-4f28-a6f1-63b3914efdc8&quot;,&quot;caption&quot;:&quot;In a previous post, we defined the Cold Start Problem.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;Paid Ads Are Suicide: The Real Math of Dating Growth&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2026-01-23T20:06:56.995Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/514dc030-f282-4435-af01-5bfb54b73522_1376x768.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/paid-ads-are-suicide-the-real-math&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:185560875,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:1,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:false,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p>Let&#8217;s look at the brutal reality of the numbers. I&#8217;ve run these calculations hundreds of times across products like Seeking, Dil Mil, and now with SkaDate clients.</p><p>In the US market, the Cost Per Action (CPA) for a single registration via Meta (Facebook/Instagram) or TikTok currently hovers between <strong>$5 and $10</strong>.</p><p>But here is the catch: a registration is not money in the bank. In the mass dating market, the average conversion rate from a free user to a paid subscriber is roughly <strong>5%</strong> (and for brand new products without liquidity, it&#8217;s often much lower).</p><p><strong>Let&#8217;s do the math:</strong></p><ul><li><p>To get <strong>1</strong> paying client, you need to acquire <strong>20</strong> free registrations (at a 5% conversion rate).</p></li><li><p>If you pay $7 per registration, your real <strong>Customer Acquisition Cost (CAC) is $140</strong> ($7 &#215; 20).</p></li></ul><p>Now, look at your revenue. The average monthly subscription price in mass dating is <strong>$30&#8211;$40</strong>.</p><p>The math is cruel: <strong>You are spending $140 to earn $30.</strong></p><p>You are losing $110 on every single customer you acquire. This model is fundamentally broken if the user only pays once.</p><p>The only way to survive in this new era of efficiency is <strong>Retention</strong>. If you cannot keep a user active and paying for months, your unit economics will never balance.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><h2>Chapter 1: What is Retention, Really?</h2><p>Many founders have a simplistic view of retention. They ask, <em>&#8220;Did the user open the app again?&#8221;</em> But in the dating industry, that definition is too shallow.</p><p><strong>Retention is a measure of the value a user gets from your product over time.</strong></p><p>If a user opens your app, stares at a blank screen, doesn&#8217;t like anyone, and sends no messages, that is not retention. That is <strong>&#8220;Zombie Traffic.&#8221;</strong> True retention isn&#8217;t built on &#8220;App Opens&#8221;; it is built on performing a <strong>Core Action</strong>. In dating, that Core Action is a conversation.</p><h3>The &#8220;Leaky Bucket&#8221; Economy</h3><p>Think of your product as a bucket. Marketing is the hose pouring water (users) into it. Retention is the structural integrity of that bucket.</p><ul><li><p><strong>The Cold Start Problem:</strong> In a new app with an empty database, the average subscriber <strong>Lifespan</strong> often collapses to just <strong>1 month</strong>. The user enters, sees no one nearby, gets no matches, and churns immediately.</p></li><li><p><strong>The Mature Product:</strong> In a product with liquidity and established retention loops, the average Lifespan is <strong>3&#8211;4 months</strong>.</p></li></ul><p>Let&#8217;s revisit our formula:</p><div class="pullquote"><p>Expected Income = (New Buyers x LTV) - Marketing Costs</p></div><ul><li><p><strong>The Leaky Bucket Scenario:</strong> You spend $140 to acquire a customer. They stay 1 month ($40 revenue). <strong>Net Loss: -$100.</strong></p></li><li><p><strong>The Retention Scenario:</strong> You extend the user&#8217;s life to 4 months ($40 &#215; 4 = $160 revenue). <strong>Net Profit: +$20.</strong></p></li></ul><p>Retention is the <em>only</em> lever that transforms a bleeding startup into a profitable business.</p><p></p><h2>Chapter 2: The Reforge Methodology and Engagement Loops</h2><p>You cannot simply order a user to &#8220;Stay!&#8221; Retention is the result of carefully engineered product loops. In my article <strong><a href="https://alexsergeev.com/p/how-to-actually-grow-a-dating-business">How to Actually Grow a Dating Business</a></strong> I broke down the user journey using the <strong>Reforge</strong> framework.</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;7c4be99d-ffb1-4bc2-a791-887028bb3c21&quot;,&quot;caption&quot;:&quot;So, you already have your own dating app or site. It&#8217;s live on the App Store and Google Play. You have some sign-ups, maybe even a few purchases.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;How to Actually Grow a Dating Business&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-29T17:03:32.063Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/61e81450-8733-4753-9f29-21c6e7b39dff_1024x572.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/how-to-actually-grow-a-dating-business&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:182666813,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:1,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p>To build retention, a user must pass through specific, sequential stages:</p><p><strong>Setup &#8594; Aha &#8594; Habit &#8594; Engagement.</strong></p><h3>2.1. The Setup Moment (Foundation)</h3><p>Just because a user downloaded the app doesn&#8217;t mean you&#8217;ve won. The <strong>Setup Moment</strong> is when the user has done the bare minimum required to actually receive value. In dating, this means:</p><ul><li><p>A completed profile.</p></li><li><p>An uploaded photo (that passed moderation).</p></li><li><p>Approval by your trust &amp; safety team.</p></li></ul><p>If a user doesn&#8217;t complete the Setup, they technically <em>cannot</em> be retained because they are invisible to the rest of the network.</p><h3>2.2. The Aha Moment (First Value)</h3><p>Retention is born the moment a user gets a result. In dating, the <strong>Aha Moment</strong> is the <strong>first conversation</strong>.</p><p>Notice I didn&#8217;t say &#8220;Match.&#8221; Matches are vanity metrics&#8212;they feel good but often lead nowhere. A <em>dialogue</em> is value. If a user chats with at least one person within their first week, their probability of retention skyrockets.</p><h3>2.3. The Habit Moment (Cementing Behavior)</h3><p>To turn a one-time action into a routine, you need repetition. The <strong>Habit Moment</strong> occurs when a user has engaged meaningfully&#8212;for example, chatting with 10 different people in their first week. At this point, checking your app becomes part of their daily ritual, like checking email or Instagram.</p><h3>How it Works: The Engagement Loop</h3><p>To move users through these stages, we design loops based on behavioral psychology:</p><ol><li><p><strong>Trigger:</strong> A push notification (&#8221;You have a new like&#8221; or &#8220;Someone messaged you&#8221;).</p></li><li><p><strong>Action:</strong>&nbsp;The user opens the app, likes back, and matches with someone or replies to a message.</p></li><li><p><strong>Variable Reward:</strong> They receive a new match or a like at a random time.</p></li><li><p><strong>Investment:</strong> They reply to the message. By replying, they are &#8220;investing&#8221; in the platform and creating a trigger for their <em>next</em> visit (waiting for a reply).</p></li></ol><p><em>&gt; <strong>Note:</strong> Building effective Engagement Loops (often called Habit Loops) is a complex engineering and psychological task. It&#8217;s not just about spamming push notifications; it&#8217;s about designing behavior. I will dedicate a future deep-dive article solely to constructing these loops from scratch.</em></p><p></p><h2>Chapter 3: Cohort Analysis</h2><p>How do you know if your Engagement Loops are working?</p><p>Do not look at general top-line charts like DAU (Daily Active Users) or MAU (Monthly Active Users). <strong>They lie to you.</strong> They blend your loyal, old users with the flood of new users who are churning immediately, hiding the true health of your product.</p><p>You need <strong>Cohort Analysis</strong>.</p><h3>What is a Cohort?</h3><p>A cohort is a group of users who entered your product during the same time period (usually grouped by week or month). We track the behavior of this specific group over time, isolated from everyone else.</p><h3>Why does this matter?</h3><p>Imagine you launched a buggy version of your app in January, and a fixed version in February. If you look at total retention, you see an &#8220;average.&#8221; But Cohort Analysis reveals the truth:</p><ul><li><p><strong>January Cohort:</strong> By Month 3, only <strong>2%</strong> remain.</p></li><li><p><strong>February Cohort:</strong> By Month 3, <strong>15%</strong> remain.</p></li></ul><p>This proves your product changes worked. Without cohorts, you are flying blind.</p><p></p><h2>Chapter 4: Practice in Mixpanel</h2><p>As a product expert, I don&#8217;t trust intuition; I trust data. In analytics tools like <strong>Mixpanel</strong> or <strong>Amplitude</strong>, there are two specific reports you must monitor daily.</p><h3>4.1. The Retention Report (Linear Retention)</h3><p>This chart answers the question: <em>"What percentage of users from a specific cohort came back to the product N days/weeks later?"</em></p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!uOrC!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!uOrC!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png 424w, https://substackcdn.com/image/fetch/$s_!uOrC!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png 848w, https://substackcdn.com/image/fetch/$s_!uOrC!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png 1272w, https://substackcdn.com/image/fetch/$s_!uOrC!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!uOrC!,w_2400,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png" width="1200" height="600" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:false,&quot;imageSize&quot;:&quot;large&quot;,&quot;height&quot;:728,&quot;width&quot;:1456,&quot;resizeWidth&quot;:1200,&quot;bytes&quot;:578407,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://alexsergeev.com/i/186544971?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:&quot;center&quot;,&quot;offset&quot;:false}" class="sizing-large" alt="" srcset="https://substackcdn.com/image/fetch/$s_!uOrC!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png 424w, https://substackcdn.com/image/fetch/$s_!uOrC!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png 848w, https://substackcdn.com/image/fetch/$s_!uOrC!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png 1272w, https://substackcdn.com/image/fetch/$s_!uOrC!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F2b898404-df66-4314-8823-e65197f5b7f2_3964x1982.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><strong>Figure 1: The Linear Retention Report in Mixpanel.</strong> </p><p>This chart tracks users who performed <strong>&#8220;Join Completed&#8221;</strong> and returned to do <strong>&#8220;Any Event.&#8221;</strong></p><p><strong>How to Read This Chart (Step-by-Step)</strong> </p><p>If you are new to analytics, this heatmap can look intimidating. Let&#8217;s break it down column by column to understand exactly what you are looking at.</p><ol><li><p><strong>The Left Column: Weekly Cohorts</strong> </p><p>Look at the list of dates on the far left (Aug 4, Aug 11, etc.). These are your <strong>Cohorts</strong>. Each row represents a specific group of real people who triggered the &#8220;Join Completed&#8221; event (registered) during that specific 7-day period. We track them separately so we can see if your product is getting better or worse week over week.</p></li><li><p><strong>The Columns: Day 1, Day 2...</strong> </p><p>The columns to the right show what percentage of those specific people came back N days later.</p><ul><li><p><strong>Day 1:</strong> This is the most critical column. It shows the percentage of users who registered and then returned the very next day.</p></li><li><p><strong>Weighted Average:</strong> The top row (purple) summarizes the average performance across all the weeks listed below. In this example, the Weighted Average for Day 1 is <strong>40.61%</strong>. This means that out of <em>everyone</em> who signed up in this period, roughly 40% opened the app again the next day.</p></li></ul></li><li><p><strong>The Curve: The Flattening (Day 30)</strong> </p><p>Follow the data to the right. In the first few days, the numbers drop fast&#8212;this is natural. But look at Day 30. The curve stops crashing. It becomes parallel to the X-axis, stabilizing around <strong>8&#8211;10%</strong>. This stabilization is what we call <strong>&#8220;The Flattening.&#8221;</strong></p></li></ol><p><strong>The Verdict: Is This Good?</strong> </p><p>To understand if these numbers are a success or a failure, we need to look at industry benchmarks.</p><ul><li><p><strong>The &#8220;Cold Start&#8221; Benchmark:</strong> For a brand new dating app with zero liquidity (an empty database), Day 1 Retention is usually around <strong>10&#8211;15%</strong>. Users enter, see nobody, and leave.</p></li><li><p><strong>The &#8220;Mature Product&#8221; Benchmark:</strong> Established giants with massive user bases and high liquidity often see Day 1 Retention hit <strong>50%</strong> or higher.</p></li></ul><p><strong>Conclusion for Figure 1:</strong> Based on these benchmarks, the chart above is <strong>excellent</strong>.</p><ol><li><p><strong>High Liquidity:</strong> The Day 1 retention of <strong>40.61%</strong> proves that new users are finding immediate value (likely chatting with existing users). The &#8220;Empty Room&#8221; problem is solved.</p></li><li><p><strong>Product-Market Fit:</strong> Because the curve flattens at Day 30 and does not hit zero, we can confidently say <strong>Product-Market Fit has been achieved.</strong> We have found a core group of users who stick around.</p></li></ol><h3>4.2. Frequency of Use (The Power User Curve)</h3><p>The Linear Retention report we just looked at tells us <em>if</em> a user came back. But it doesn&#8217;t tell us <em>how addicted</em> they are.</p><p>You can have high retention but low engagement. For example, a user might open your app once a week just to check if they have notifications, but never actually talk to anyone. We call these users &#8220;Zombies.&#8221; They look alive in your DAU stats, but they generate zero value.</p><p>To spot this, we need the <strong>Frequency Report</strong> (often called the <strong>Power User Curve</strong> or <strong>L30</strong>).</p><p><strong>What is this chart?</strong> Instead of showing <em>when</em> users return, this chart shows the <strong>intensity</strong> of their usage over a 30-day window.</p><ul><li><p><strong>X-Axis:</strong> The number of days a user performed an action (from 1 to 30).</p></li><li><p><strong>Y-Axis:</strong> The percentage of your user base.</p></li></ul><p>Ideally, you want a &#8220;Smile Graph&#8221;&#8212;high on the left (new users) and high on the right (addicted power users).</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!v65V!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!v65V!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png 424w, https://substackcdn.com/image/fetch/$s_!v65V!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png 848w, https://substackcdn.com/image/fetch/$s_!v65V!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png 1272w, https://substackcdn.com/image/fetch/$s_!v65V!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!v65V!,w_2400,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png" width="1200" height="557.967032967033" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:false,&quot;imageSize&quot;:&quot;large&quot;,&quot;height&quot;:677,&quot;width&quot;:1456,&quot;resizeWidth&quot;:1200,&quot;bytes&quot;:425935,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://alexsergeev.com/i/186544971?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:&quot;center&quot;,&quot;offset&quot;:false}" class="sizing-large" alt="" srcset="https://substackcdn.com/image/fetch/$s_!v65V!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png 424w, https://substackcdn.com/image/fetch/$s_!v65V!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png 848w, https://substackcdn.com/image/fetch/$s_!v65V!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png 1272w, https://substackcdn.com/image/fetch/$s_!v65V!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F6eafadac-3572-4816-8658-3564af8a3f3c_3938x1832.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-tqxFUX" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-tqxFUX" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p><strong>Figure 2: The Frequency Report (L30) for "Message Sent"</strong></p><p>Now, let&#8217;s analyze the real-world report in <strong>Figure 2</strong>. This chart tracks the frequency of the <strong>&#8220;Message Sent&#8221;</strong> event.</p><p>This is a classic example of a product that has retention, but <strong>no habit</strong>.</p><ol><li><p><strong>The &#8220;Tourist&#8221; Cliff (Left Side):</strong> Look at the start of the curve.</p><ul><li><p><strong>18.86%</strong> of users sent messages on <strong>2 days</strong> out of the month.</p></li><li><p>By <strong>4 days</strong>, this drops to <strong>7.4%</strong>.</p></li><li><p>This indicates that users are coming in, chatting for a weekend (like tourists), and then losing interest.</p></li></ul></li><li><p><strong>The &#8220;Power User&#8221; Void (Right Side):</strong></p><ul><li><p>Look at the tail of the graph (Days 20&#8211;30). The line is flatlining near <strong>0%</strong>.</p></li><li><p>This means <strong>almost nobody</strong> is chatting daily. You have no core group of addicted users.</p></li></ul></li><li><p><strong>The Verdict:</strong></p><ul><li><p>If this were a healthy dating app, you would see an uptick on the right side (the &#8220;Smile&#8221;).</p></li><li><p>The fact that this chart dies out completely on the right suggests your <strong>Engagement Loops are broken</strong>. Users do not feel the psychological need to check their messages every day.</p></li></ul></li></ol><h3>Summary: The &#8220;Zombie Product&#8221; Trap</h3><p>Why is it critical to look at <strong>both</strong> charts?</p><p>If you only looked at the <strong>Retention Report (Figure 1)</strong>, you would pop the champagne. You have 40% retention! You have Product-Market Fit! You might think you are ready to scale.</p><p>But if you overlay the <strong>Frequency Report (Figure 2)</strong>, you see the grim reality. Yes, users are coming back, but they are not <em>engaging</em>. They are &#8220;Zombies&#8221;&#8212;walking around your app, looking at profiles, but not talking.</p><p><strong>The Golden Rule of Analytics:</strong></p><ul><li><p><strong>Linear Retention</strong> measures if your product is <strong>valid</strong> (Do they delete it?).</p></li><li><p><strong>Frequency</strong> measures if your product is <strong>monetizable</strong> (Do they use it enough to pay?).</p></li></ul><p>You cannot build a billion-dollar business on Retention alone. You need the <strong>Flattening</strong> in Chart 1 <em>and</em> the <strong>Smile</strong> in Chart 2. Until you have both, your unit economics will remain under pressure.</p><h3>Implementation Note: Don&#8217;t Code This From Scratch</h3><p>Setting up these specific events (<code>Join Completed</code>, <code>Message Sent</code>, <code>Subscription Started</code>) incorrectly is the #1 reason founders get bad data.</p><p>If you are using <strong><a href="https://skadate.com">SkaDate</a></strong> to launch your product, we have already done this work for you. Our platform has a <strong><a href="https://www.skadate.com/skadate-mixpanel-product-analytics/">native integration with Mixpanel</a></strong><a href="https://www.skadate.com/skadate-mixpanel-product-analytics/">.</a> You don&#8217;t need to hire developers to map these events&#8212;just enable the plugin, and your dashboard will automatically start populating with the exact charts I showed above from Day 1.</p><h2>Conclusion</h2><p>In 2026, the unit economics of the dating industry are no longer about finding cheap traffic. That ship has sailed. The game is now entirely about the battle for <strong>LTV (Lifetime Value)</strong>.</p><ul><li><p><strong>Your Formula:</strong> Expected Income = (New Buyers x LTV) - Marketing Costs.</p></li><li><p><strong>Your Lever:</strong> Retention, which multiplies LTV.</p></li><li><p><strong>Your Tool:</strong> Engagement Loops (Setup &#8594; Aha &#8594; Habit) that engineer user behavior.</p></li><li><p><strong>Your Validation:</strong> Cohort Analysis in Mixpanel.</p></li></ul><p>Stop building features based on guesses. Start measuring retention by cohorts and optimizing the user&#8217;s path from registration to that first dialogue. That is the only way to make the math work.</p><p></p><h2>Why Build From Scratch?</h2><p>You are already fighting a war for Retention and LTV. Setting up <strong>monetization logic</strong>, fighting <strong>SMS fraud</strong>, and optimizing the <strong>onboarding flow</strong> is hard enough without having to code the entire platform yourself.</p><p><strong>This is why we built <a href="https://www.skadate.com">SkaDate</a>.</strong></p><p>We provide the complete technical engine&#8212;native mobile apps, flexible paywalls, and robust anti-spam tools&#8212;ready from Day 1.</p><p>Ready to skip the development nightmare?</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://calendly.com/alex-funnelflex/skadate-qa&quot;,&quot;text&quot;:&quot;Discuss Your Project with Me&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://calendly.com/alex-funnelflex/skadate-qa"><span>Discuss Your Project with Me</span></a></p><p><em>You focus on finding the users; we&#8217;ll make sure the technology keeps them there.</em></p>]]></content:encoded></item><item><title><![CDATA[Paid Ads Are Suicide: The Real Math of Dating Growth]]></title><description><![CDATA[Why your ad budget will fail you, and how POF, Badoo, and Tinder acquired millions of users for $0.]]></description><link>https://alexsergeev.com/p/paid-ads-are-suicide-the-real-math</link><guid isPermaLink="false">https://alexsergeev.com/p/paid-ads-are-suicide-the-real-math</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Fri, 23 Jan 2026 20:06:56 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/514dc030-f282-4435-af01-5bfb54b73522_1376x768.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In a previous post, we defined the <strong>Cold Start Problem</strong>. </p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;134d5609-9b09-4615-bb6c-c2306f7b2899&quot;,&quot;caption&quot;:&quot;Today, we are looking at the single biggest hurdle for any new dating business: The Cold Start Problem.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;The Foundation: Solving the Cold Start Problem in Dating&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-12T21:32:42.682Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/0954e898-ca70-4ffb-aee2-1fcde1066515_1024x559.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/the-foundation-solving-the-cold-start&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:181462712,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:false,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p>But let&#8217;s be honest: most founders underestimate just how brutal this math actually is.</p><p>When you launch a dating app, your database is empty. New users sign up, see an empty feed, and leave immediately. This is the classic &#8220;Empty Bar&#8221; syndrome.</p><p>Dating is a <strong>hyper-local marketplace</strong>. It is significantly harder to scale than an e-commerce marketplace like Amazon or Etsy. For Amazon, a seller in Texas can ship a book to a buyer in New York. In dating, your supply (users) must be physically near your demand (other users), <em>and</em> they must match specific criteria (age, gender, intent).</p><p>If you don&#8217;t solve the liquidity problem (having enough people in one specific area), your product fails. Period.</p><p>Many founders think, &#8220;I&#8217;ll just buy ads.&#8221; Let&#8217;s look at the unit economics and see why that is a suicide mission for a bootstrap startup.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><h2>The Math of Failure: Why You Can&#8217;t Buy Your Way Out</h2><p>Let&#8217;s look at the funnel. In the US market, a Paid Registration (via Meta Ads, Google, or TikTok) will cost you anywhere from <strong>$5 to $10</strong>.</p><p>But a registration is not a paying customer.</p><ul><li><p><strong>Average conversion from Reg to Subscriber:</strong> ~5% (For a new, unoptimized product, it&#8217;s usually lower).</p></li><li><p><strong>The Multiplier:</strong> To get <strong>1 subscriber</strong>, you need <strong>20 registrations</strong>.</p></li></ul><p>Let&#8217;s do the math:</p><div class="pullquote"><p>$7 (CPA) x 20 (Users) = $140</p></div><p><strong>It costs you roughly $140 to acquire one paying subscriber.</strong></p><p>Now, look at your revenue.</p><ul><li><p><strong>Retention:</strong> The average dating user lifecycle is 3&#8211;4 months. For a new app with a &#8220;thin&#8221; database, it&#8217;s likely <strong>1 month</strong>. They will sign up, look around, maybe pay, realize there are no dates, and cancel immediately.</p></li><li><p><strong>Pricing:</strong> Unless you are a niche &#8220;Sugar&#8221; site like Seeking (where LTV is high), you are likely charging $30&#8211;40/month.</p></li></ul><p><strong>The Result:</strong> You pay <strong>$140</strong> to make <strong>$30</strong>.</p><p>You are losing $110 on every customer. You cannot scale this. You will burn through your seed round before you get your first 1,000 active users.</p><p>To solve the Cold Start Problem, you need an <strong>&#8220;Unfair Advantage&#8221;</strong>&#8212;a channel that delivers users for free (or very cheaply) to offset the paid acquisition costs.</p><p>Let&#8217;s look at how the &#8220;Old Guard&#8221; solved this. While the specific tactics have changed, the <em>principles</em> of finding a viral loop remain the same.</p><p></p><h2>Case Study 1: Plenty of Fish (The &#8220;Craigslist&#8221; SEO Strategy)</h2><p>Markus Frind, the founder of Plenty of Fish (POF), famously ran the company with almost no employees for years. While competitors had massive teams, Markus was alone in his apartment, managing millions of users.</p><p>How? By mastering <strong>SEO (Search Engine Optimization)</strong>.</p><p>POF was the <strong>Craigslist</strong> of dating. It was ugly, utilitarian, and raw. At <strong>Meetville</strong> (my previous company), we were obsessed with sleek UI/UX. Back in 2010, we used to look at POF and spit on the design. We would say, <em>&#8220;What is this horror? How can anyone use this?&#8221;</em></p><p>But while we were polishing pixels, Markus was printing money. He understood that users didn&#8217;t care about pretty buttons; they cared about <em>results</em>.</p><h4>The Strategy: Radical Openness </h4><p>At the time, most dating sites (like Match.com) were &#8220;walled gardens.&#8221; You couldn&#8217;t see anything unless you registered. Google&#8217;s bots cannot index content behind a login wall, so those sites were invisible to search engines.</p><p>Markus made profiles public.</p><ul><li><p>If a user named &#8220;Mike&#8221; created a profile in Vancouver, POF created a public page for him.</p></li><li><p>When someone searched for &#8220;Men in Vancouver,&#8221; POF ranked #1.</p></li></ul><h4>The Business Model: Arbitrage </h4><p>Markus acquired users for <strong>$0</strong> (via SEO) and monetized them for <strong>pennies</strong> (via Google AdSense). Since his cost was zero, his profit margin was 100%. In 2015, this strategy paid off when <strong>Match Group acquired Plenty of Fish for $575 million</strong>.</p><ul><li><p><em>Read more: <a href="https://www.bbc.com/news/business-33528271">Match Group Buys PlentyOfFish for $575M</a></em></p></li></ul><h4>The Modern Problem: AI and &#8220;Zero-Click&#8221; Search</h4><p>Today, you cannot just copy POF&#8217;s strategy. Why? Because Google is changing. With the rise of AI (like ChatGPT and Google&#8217;s AI Overviews), users often get answers directly on the search page without clicking a link. The era of &#8220;10 blue links&#8221; is fading.</p><p>To grow via SEO in 2026, you need <strong>Programmatic SEO</strong>.</p><p><strong>What is Programmatic SEO?</strong> Instead of manually writing one blog post at a time, you use code and data to generate thousands of high-quality landing pages automatically.</p><ul><li><p><em>Example:</em> Instead of writing one article about &#8220;Dating in California,&#8221; you programmatically generate pages for <strong>&#8220;Best Date Spots in Walnut Creek,&#8221; &#8220;Best Date Spots in Oakland,&#8221; &#8220;Best Date Spots in Palo Alto,&#8221;</strong> etc.</p></li></ul><p>You create thousands of &#8220;doors&#8221; for Google to find, capturing &#8220;long-tail&#8221; traffic that is less competitive. This is the only way to replicate POF&#8217;s scale in the modern era.</p><p></p><h2>Case Study 2: Badoo (The Viral Graph)</h2><p>Badoo was founded by Andrey Andreev, the product genius behind Mamba. When he expanded Badoo globally, he didn&#8217;t rely on SEO. He hacked the <strong>Facebook Social Graph</strong>.</p><p>To understand Badoo&#8217;s success, you first have to understand the specific loophole in how the internet worked in 2010.</p><h4>The &#8220;Open Door&#8221; (Permission to Spam) </h4><p>Today, if an app wants to post to your social media, it has to ask you for permission every single time. But in 2010, Facebook had an <strong>Open Graph API</strong> that worked very differently.</p><p>The API allowed apps to publish posts to your friends&#8217; walls <strong>automatically</strong>.</p><p>Once you clicked &#8220;Allow&#8221; just one time, the app had the keys to your account. It could post messages to the News Feeds of all your friends without asking you again. <strong>Imagine this scenario today:</strong> Imagine if your friend could post a photo or a status update on <em>your</em> Instagram profile without even telling you. That is exactly what the API allowed.</p><p>It was the &#8220;Wild West.&#8221; This lack of friction was the key to their growth.</p><h4>The Viral Loop </h4><p>Badoo built a mechanism to exploit this &#8220;auto-posting&#8221; capability perfectly. They created a quiz app that lived inside Facebook.</p><p>Here is the exact <strong>Viral Loop</strong> that generated millions of users:</p><ol><li><p><strong>The Trigger:</strong> You are using the app and you answer a question about one of your friends.</p><ul><li><p><em>Example:</em> &#8220;Will your friend <strong>John</strong> help an old lady to cross the road?&#8221;</p></li><li><p><em>Your Answer:</em> &#8220;Yes.&#8221;</p></li></ul></li><li><p><strong>The Auto-Post (Crucial Step):</strong> Badoo immediately publishes a post to <strong>John&#8217;s</strong> personal feed:</p><ul><li><p><em>The Message:</em> &#8220;Your friend answered a question about you: &#8216;Will you help an old lady to cross the road?&#8217; Click here to see the answer.&#8221;</p></li><li><p><em>The Multiplier:</em> Because this is posted on John&#8217;s wall, <strong>all of John&#8217;s friends</strong> see this note too. This is where the visibility explodes.</p></li></ul></li><li><p><strong>The Click:</strong> John (or one of his curious friends) clicks the link to see the answer.</p></li><li><p><strong>The Gate:</strong> A popup appears: <em>&#8220;To enter Badoo and see the answer, you must grant access to your profile.&#8221;</em> John agrees and enters the app.</p></li><li><p><strong>The Viral Cost:</strong> Now the app tells John: <em>&#8220;To see the answer, you need to score 10 points. To score 1 point, you need to answer a question about YOUR friend.&#8221;</em></p></li><li><p><strong>The Loop:</strong> John answers a question about <em>his</em> friend Mike... and the cycle repeats instantly.</p></li></ol><p><strong>The Billion-Dollar Checkbox:</strong> This is what the interface looked like at Badoo&#8217;s peak. Notice the tiny, pre-checked box at the bottom: <em>&#8220;Publish on your friend&#8217;s wall.&#8221;</em> This subtle UI detail meant that every interaction automatically spammed a friend&#8217;s feed, driving the K-Factor through the roof.</p><div class="captioned-image-container"><figure><div class="image-link image2" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!mJcW!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29eba809-d18d-4e0d-a94b-28ec38e8fe6f_574x238.jpeg 424w, https://substackcdn.com/image/fetch/$s_!mJcW!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29eba809-d18d-4e0d-a94b-28ec38e8fe6f_574x238.jpeg 848w, https://substackcdn.com/image/fetch/$s_!mJcW!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29eba809-d18d-4e0d-a94b-28ec38e8fe6f_574x238.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!mJcW!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29eba809-d18d-4e0d-a94b-28ec38e8fe6f_574x238.jpeg 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!mJcW!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29eba809-d18d-4e0d-a94b-28ec38e8fe6f_574x238.jpeg" width="574" height="238" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/29eba809-d18d-4e0d-a94b-28ec38e8fe6f_574x238.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:238,&quot;width&quot;:574,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:null,&quot;alt&quot;:&quot;&quot;,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" title="" srcset="https://substackcdn.com/image/fetch/$s_!mJcW!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29eba809-d18d-4e0d-a94b-28ec38e8fe6f_574x238.jpeg 424w, https://substackcdn.com/image/fetch/$s_!mJcW!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29eba809-d18d-4e0d-a94b-28ec38e8fe6f_574x238.jpeg 848w, https://substackcdn.com/image/fetch/$s_!mJcW!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29eba809-d18d-4e0d-a94b-28ec38e8fe6f_574x238.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!mJcW!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F29eba809-d18d-4e0d-a94b-28ec38e8fe6f_574x238.jpeg 1456w" sizes="auto, 100vw" loading="lazy"></picture><div></div></div></div></figure></div><p><strong>The End of the Era (Autumn 2012):</strong> When Facebook restricted the Open Graph API, Badoo was forced to change the mechanics. Notice the shift from "Friend's wall" to <em>&#8220;Publish on your own wall.&#8221;</em> This small text change effectively killed the viral loop and brought their explosive growth to a halt.</p><div class="captioned-image-container"><figure><div class="image-link image2" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!J9zQ!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10a2335b-dfaf-475a-90e0-f0b1a3e5374f_551x186.jpeg 424w, https://substackcdn.com/image/fetch/$s_!J9zQ!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10a2335b-dfaf-475a-90e0-f0b1a3e5374f_551x186.jpeg 848w, https://substackcdn.com/image/fetch/$s_!J9zQ!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10a2335b-dfaf-475a-90e0-f0b1a3e5374f_551x186.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!J9zQ!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10a2335b-dfaf-475a-90e0-f0b1a3e5374f_551x186.jpeg 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!J9zQ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10a2335b-dfaf-475a-90e0-f0b1a3e5374f_551x186.jpeg" width="551" height="186" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/10a2335b-dfaf-475a-90e0-f0b1a3e5374f_551x186.jpeg&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:186,&quot;width&quot;:551,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:null,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:null,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:null,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!J9zQ!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10a2335b-dfaf-475a-90e0-f0b1a3e5374f_551x186.jpeg 424w, https://substackcdn.com/image/fetch/$s_!J9zQ!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10a2335b-dfaf-475a-90e0-f0b1a3e5374f_551x186.jpeg 848w, https://substackcdn.com/image/fetch/$s_!J9zQ!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10a2335b-dfaf-475a-90e0-f0b1a3e5374f_551x186.jpeg 1272w, https://substackcdn.com/image/fetch/$s_!J9zQ!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F10a2335b-dfaf-475a-90e0-f0b1a3e5374f_551x186.jpeg 1456w" sizes="auto, 100vw" loading="lazy"></picture><div></div></div></div></figure></div><p></p><p><strong>The Metric: K-Factor</strong> In growth marketing, we measure virality using the <strong>K-Factor</strong>.</p><ul><li><p>If <strong>K = 1</strong>, every new user brings in exactly one other user.</p></li><li><p>If <strong>K &gt; 1</strong>, growth is exponential.</p></li><li><p>Badoo&#8217;s K-Factor was roughly <strong>10</strong>. Every single person who joined brought in ten more people.</p></li></ul><p>This allowed Badoo to gather hundreds of millions of users faster than any company in history. Eventually, Facebook realized these apps were spamming users and shut down the API, but Badoo had already won.</p><ul><li><p><em>Deep Dive: I wrote a detailed breakdown of this era on Medium:<a href="https://medium.com/@humanoit/boosting-the-audience-from-12m-to-375m-myth-or-reality-dbfc38e9540b"> Boosting the audience from 12M to 375M: Myth or Reality?</a></em></p></li></ul><blockquote></blockquote><p></p><h2>Case Study 3: &#8220;Are You Interested?&#8221; (The Rise and The Crash)</h2><p>While Badoo was huge, another app called <strong>&#8220;Are You Interested?&#8221; (AYI)</strong> mastered this Facebook era so well that they actually went public based on this strategy alone.</p><p>AYI was built by Cliff Lerner. His strategy was to gamify dating notifications. They would send you a notification saying: <em>&#8220;2 of your friends have a crush on you! Click to see who.&#8221;</em> Of course, to see who, you had to invite <em>more</em> friends. They optimized every pixel of their notifications to maximize the Click-Through Rate (CTR).</p><h4>The IPO and The Crash </h4><p>The parent company, <strong>SNAP Interactive</strong>, was publicly traded. When their Facebook strategy started working, the stock went crazy.</p><ul><li><p><strong>The Start:</strong> The stock was a &#8220;penny stock,&#8221; trading for around <strong>$0.20 - $0.25</strong>.</p></li><li><p><strong>The Peak:</strong> In late 2010, after announcing massive user growth from Facebook, the stock surged <strong>2,000%</strong> in just a few days, hitting over <strong>$4.00</strong>. The market cap exploded overnight.</p></li><li><p><strong>The Crash:</strong> However, building a business on someone else&#8217;s land (Facebook) is dangerous. When Facebook changed their algorithms and shut down the viral channels, the free traffic stopped. The stock eventually lost over <strong>90%</strong> of its value, crashing back down to pennies.</p></li></ul><p>Cliff Lerner documented this entire rollercoaster in his book, <strong>&#8220;Explosive Growth.&#8221;</strong> It is a must-read for any founder to understand how to engineer viral loops, and the dangers of relying on a single platform.</p><ul><li><p><em>Recommended Reading: &#8220;Explosive Growth&#8221; by Cliff Lerner -<a href="https://www.amazon.com/Explosive-Growth-Things-Learned-Growing/dp/1619617696"> Buy on Amazon</a></em></p></li></ul><blockquote></blockquote><p></p><h2>Case Study 4: Tinder (The Physical &#8220;Hack&#8221;)</h2><p>Tinder didn&#8217;t use SEO or Facebook spam. They solved the problem <strong>physically</strong>.</p><p>Most dating apps fail because they try to launch &#8220;everywhere&#8221; at once. Having 1,000 users spread across the entire USA is useless&#8212;they will never match with each other. But having 1,000 users in <strong>one university dorm</strong> is a massive success. This is called <strong>Liquidity</strong>.</p><p><strong>The Strategy: The USC Party</strong> Tinder was incubated inside Match Group, but they acted like a scrappy startup. The team, led by Whitney Wolfe Herd (who later founded Bumble with Andrey Andreev from Badoo), went to the University of Southern California (USC).</p><ul><li><p><strong>Supply First:</strong> Whitney went to the <strong>sororities</strong> first. She convinced the influential girls on campus to download the app.</p></li><li><p><strong>Demand Second:</strong> Then she went to the <strong>fraternities</strong>. She told the guys, <em>&#8220;All the cute girls from the sororities are on this app.&#8221;</em> Naturally, the guys downloaded it immediately.</p></li></ul><p><strong>The Execution:</strong> They threw a massive launch party at a fraternity house.</p><ul><li><p><strong>The Ticket:</strong> There was a bouncer at the door. To get into the party, you didn&#8217;t pay cash. You had to <strong>show the bouncer your phone</strong> with the Tinder app installed.</p></li><li><p><strong>The Result:</strong> 500 students entered the party. They were all young, single, attractive, and&#8212;most importantly&#8212;<strong>in the same room</strong>.</p></li></ul><p><strong>The Psychological Effect</strong> Once inside, students opened the app and saw the faces of the people standing right next to them. This created instant <strong>Social Proof</strong>. It wasn&#8217;t a &#8220;creepy internet thing&#8221;; it was something the &#8220;cool kids&#8221; at the party were doing. Matches happened instantly. The &#8220;Cold Start&#8221; problem for USC was solved in one night. Then, they simply moved to the next campus and repeated the process.</p><p><em>Read my full analysis of Tinder&#8217;s start here:<a href="https://alexsergeev.com/p/the-foundation-solving-the-cold-start"> The Foundation - Solving the Cold Start Problem</a></em></p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;3724e44a-df76-492a-be21-48daa93f1305&quot;,&quot;caption&quot;:&quot;Today, we are looking at the single biggest hurdle for any new dating business: The Cold Start Problem.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;The Foundation: Solving the Cold Start Problem in Dating&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-12T21:32:42.682Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/0954e898-ca70-4ffb-aee2-1fcde1066515_1024x559.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/the-foundation-solving-the-cold-start&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:181462712,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p></p><h2>So, what now?</h2><p>The &#8220;Old Guard&#8221; had their unfair advantages. <strong>What is yours?</strong></p><p>In my next article, I will move away from history and look at the <strong>Modern Playbook</strong>. We will analyze dating apps that launched in the last 2&#8211;3 years and successfully cracked the Cold Start Problem without bankrupting themselves on Meta Ads.</p><p>Stay tuned.</p><p></p><h2>Why Build From Scratch?</h2><p>As you just read, solving the <strong>Cold Start Problem</strong> requires 100% of your focus&#8212;and your budget&#8212;on marketing.</p><p>Developing a sophisticated dating engine from scratch will cost you tens of thousands of dollars before you even launch. Why burn your runway reinventing the wheel?</p><p><strong>That is our territory.</strong></p><p><strong><a href="http://skadate.com/">SkaDate</a></strong> provides you with a battle-tested engine that is ready to generate revenue from Day 1.</p><p>We don&#8217;t just give you code; we provide the <strong>proven business models</strong>, <strong>premium features</strong>, and <strong>monetization logic</strong> that successful dating apps rely on.</p><p>We save you months of development time and huge capital. You focus on the growth strategy; we provide the engine to power it.</p><p>Ready to launch with a pro-level product?</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://calendly.com/alex-funnelflex/skadate-qa&quot;,&quot;text&quot;:&quot;Discuss Your Project with Me&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://calendly.com/alex-funnelflex/skadate-qa"><span>Discuss Your Project with Me</span></a></p><p><em>You focus on finding the users; we&#8217;ll make sure the technology is ready to monetize them.</em></p>]]></content:encoded></item><item><title><![CDATA[How to Measure What Really Matters in Your Dating App]]></title><description><![CDATA[In our previous discussions, we covered the high-level Growth Methodology required to scale a dating product.]]></description><link>https://alexsergeev.com/p/how-to-measure-what-really-matters</link><guid isPermaLink="false">https://alexsergeev.com/p/how-to-measure-what-really-matters</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Fri, 16 Jan 2026 17:46:58 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/19e1a5e0-7914-40b1-b981-cf96fece241f_1424x752.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>In our previous discussions, we covered the high-level <strong>Growth Methodology</strong> required to scale a dating product. We established the strategy; now, we move to the execution.</p><p></p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;287a293a-77b7-4032-872d-062878a2760c&quot;,&quot;caption&quot;:&quot;So, you already have your own dating app or site. It&#8217;s live on the App Store and Google Play. You have some sign-ups, maybe even a few purchases.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;How to Actually Grow a Dating Business&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-29T17:03:32.063Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/61e81450-8733-4753-9f29-21c6e7b39dff_1024x572.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/how-to-actually-grow-a-dating-business&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:182666813,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:false,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p><br>The first rule of implementation is simple: <strong>You cannot grow what you cannot measure.</strong> If you aren&#8217;t tracking the right metrics, you aren&#8217;t managing your product&#8212;you&#8217;re just guessing.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>To make this manageable, we break the dating app ecosystem into two global funnels:</p><ol><li><p><strong>The Value Funnel:</strong> This measures how much value users get from your product. In dating, value equals human connection (dates, chats). The more value users receive, the longer they stay. This directly drives <strong>LTV (Lifetime Value)</strong> because retention is the baseline for monetization.</p></li><li><p><strong>The Revenue Funnel:</strong> This measures how effectively you convert free users into paid subscribers. It determines your <strong>Number of First Buyers</strong>.</p></li></ol><p>If we look at the fundamental Unit Economics formula:</p><div class="pullquote"><p><code>Profit = (First Buyers x LTV) - Marketing Costs</code></p></div><p>The <strong>Value Funnel</strong> drives the <em>LTV</em>, and the <strong>Revenue Funnel</strong> drives the <em>First Buyers</em>.</p><p>Today, we are focusing exclusively on the Value Funnel. We will break it down into five critical steps:</p><blockquote><p><strong>Sign up &#8594; Setup &#8594; Aha &#8594; Habit &#8594; Engagement</strong></p></blockquote><p></p><h2>1. Sign Up</h2><p><em>The goal: Get them through the door.</em></p><p>We define <strong>Sign Up</strong> as the moment a user completes the entire registration process&#8212;entering data, uploading photos, answering profile questions&#8212;and actually lands inside the app&#8217;s main interface.</p><p>Here, we track our first critical conversion metric, <em>C1 (Visitor to Registration)</em>.</p><p>To calculate this, divide the number of users who completed registration by the number of users who opened the first screen of the app.</p><h3>Tracking with Mixpanel</h3><p><em>A quick side note for non-technical founders:</em> We track this using <strong>Product Analytics</strong> tools like <a href="https://mixpanel.com/">Mixpanel</a>. Unlike Google Analytics (which tracks traffic), Mixpanel tracks <strong>Events</strong> (actions users take) and <strong>User Properties</strong> (attributes like age, gender, subscription status). Check out this <a href="https://mixpanel.com/compare/google-analytics/">comparison between Mixpanel and Google Analytics</a>.</p><p>If you are using the <strong>SkaDate</strong> platform, our Premium plugin automatically sends these events to Mixpanel. You can read more about our plugin in this article - How <a href="https://www.skadate.com/skadate-mixpanel-product-analytics/">Mixpanel Product Analytics Can Unlock Your Dating App Growth Potential</a>.</p><p>To optimize your Sign Up flow, you need a <strong>Funnel Report</strong>. You cannot just look at the start and end; you need to see every hurdle in between. In our architecture, we track:</p><ol><li><p><strong>Onboarding Create Account Clicked:</strong> User taps the button on the landing screen.</p></li><li><p><strong>Sign Up Completed:</strong> User inputs email/password or authenticates via SSO (Google/Apple).</p></li><li><p><strong>Profile Step Completed:</strong> User fills in text fields (name, age, etc.).</p></li><li><p><strong>Photo Step Completed:</strong> User uploads media.</p></li><li><p><strong>Join Completed:</strong> The user is fully registered and lands on the discovery screen.</p></li></ol><p></p><p>Here is a sample Mixpanel report built using the events above:</p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!vCII!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff173f473-6443-49e0-af95-8e6a64376457_2094x1354.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!vCII!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff173f473-6443-49e0-af95-8e6a64376457_2094x1354.png 424w, https://substackcdn.com/image/fetch/$s_!vCII!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff173f473-6443-49e0-af95-8e6a64376457_2094x1354.png 848w, https://substackcdn.com/image/fetch/$s_!vCII!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff173f473-6443-49e0-af95-8e6a64376457_2094x1354.png 1272w, https://substackcdn.com/image/fetch/$s_!vCII!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff173f473-6443-49e0-af95-8e6a64376457_2094x1354.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!vCII!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff173f473-6443-49e0-af95-8e6a64376457_2094x1354.png" width="1456" height="941" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/f173f473-6443-49e0-af95-8e6a64376457_2094x1354.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:941,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:189657,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://alexsergeev.com/i/184704053?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff173f473-6443-49e0-af95-8e6a64376457_2094x1354.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!vCII!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff173f473-6443-49e0-af95-8e6a64376457_2094x1354.png 424w, https://substackcdn.com/image/fetch/$s_!vCII!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff173f473-6443-49e0-af95-8e6a64376457_2094x1354.png 848w, https://substackcdn.com/image/fetch/$s_!vCII!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff173f473-6443-49e0-af95-8e6a64376457_2094x1354.png 1272w, https://substackcdn.com/image/fetch/$s_!vCII!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2Ff173f473-6443-49e0-af95-8e6a64376457_2094x1354.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p></p><h3>Analyzing the Data</h3><p>When you look at this report in Mixpanel, you are looking for two things:</p><ol><li><p><strong>Overall Conversion:</strong> (e.g., 72.93%). If 100 people start, how many finish?</p></li><li><p><strong>Time to Convert:</strong> This is often overlooked. If the gap between <em>Sign Up Completed</em> and <em>Profile Step Completed</em> is 168 seconds, that&#8217;s nearly three minutes of friction.</p></li></ol><p><strong>Founder Tip:</strong> Your goal is to increase the conversion % and decrease the time. High friction during registration is the silent killer of paid acquisition campaigns. You can also segment this data: Do iOS users convert faster than Android users? Do men drop off at the photo step more than women?</p><h2>2. Setup</h2><p><em>The goal: Ready to mingle.</em></p><p>Let&#8217;s define what the <strong>Setup Moment</strong> actually is. <strong>The Setup Moment is considered complete when the user has performed the minimum necessary actions required for the product to work for them.</strong></p><p>In a dating app, this means two things must happen:</p><ol><li><p><strong>The User&#8217;s Job:</strong> They must fill out their profile and upload photos. (Usually, they do this during the Sign-Up flow).</p></li><li><p><strong>The Platform&#8217;s Job:</strong> The profile must be <strong>verified and approved</strong>.</p></li></ol><p>You cannot consider a user &#8220;Set Up&#8221; just because they finished registration. If their photos are pending or their bio is empty, the product <em>does not work</em> for them yet because they are invisible to others.</p><p>This brings us to <strong>Moderation</strong>. Moderators must review not just the photos, but also open-ended text fields like &#8220;About Me&#8221; or Profile Prompts.</p><ul><li><p><strong>Photos:</strong> Users might upload inappropriate content that violates store policies.</p></li><li><p><strong>Text:</strong> Users often use the &#8220;About Me&#8221; section for spam, ads, or offensive content.</p></li></ul><p>Until this content is vetted, the user cannot be shown in the discovery pool. In SkaDate, we track the event <em>Avatar Approved</em>.</p><p>This is your operational bottleneck. If a user registers on Friday night but isn&#8217;t approved until Monday morning, they are <strong>&#8220;invisible inventory.&#8221;</strong> They can&#8217;t get likes, they can&#8217;t get matches, and they certainly won&#8217;t feel any value.</p><p>Below is the funnel showing the path from Registration to Approval. </p><div class="captioned-image-container"><figure><a class="image-link image2 is-viewable-img" target="_blank" href="https://substackcdn.com/image/fetch/$s_!_RCr!,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png" data-component-name="Image2ToDOM"><div class="image2-inset"><picture><source type="image/webp" srcset="https://substackcdn.com/image/fetch/$s_!_RCr!,w_424,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png 424w, https://substackcdn.com/image/fetch/$s_!_RCr!,w_848,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png 848w, https://substackcdn.com/image/fetch/$s_!_RCr!,w_1272,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png 1272w, https://substackcdn.com/image/fetch/$s_!_RCr!,w_1456,c_limit,f_webp,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png 1456w" sizes="auto, 100vw"><img src="https://substackcdn.com/image/fetch/$s_!_RCr!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png" width="1456" height="943" data-attrs="{&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png&quot;,&quot;srcNoWatermark&quot;:null,&quot;fullscreen&quot;:null,&quot;imageSize&quot;:null,&quot;height&quot;:943,&quot;width&quot;:1456,&quot;resizeWidth&quot;:null,&quot;bytes&quot;:151166,&quot;alt&quot;:null,&quot;title&quot;:null,&quot;type&quot;:&quot;image/png&quot;,&quot;href&quot;:null,&quot;belowTheFold&quot;:true,&quot;topImage&quot;:false,&quot;internalRedirect&quot;:&quot;https://alexsergeev.com/i/184704053?img=https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png&quot;,&quot;isProcessing&quot;:false,&quot;align&quot;:null,&quot;offset&quot;:false}" class="sizing-normal" alt="" srcset="https://substackcdn.com/image/fetch/$s_!_RCr!,w_424,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png 424w, https://substackcdn.com/image/fetch/$s_!_RCr!,w_848,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png 848w, https://substackcdn.com/image/fetch/$s_!_RCr!,w_1272,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png 1272w, https://substackcdn.com/image/fetch/$s_!_RCr!,w_1456,c_limit,f_auto,q_auto:good,fl_progressive:steep/https%3A%2F%2Fsubstack-post-media.s3.amazonaws.com%2Fpublic%2Fimages%2F295015ca-cb97-48db-a369-9264798c5a37_2108x1366.png 1456w" sizes="auto, 100vw" loading="lazy"></picture><div class="image-link-expand"><div class="pencraft pc-display-flex pc-gap-8 pc-reset"><button class="pencraft pc-reset pencraft icon-container restack-image buttonBase-GK1x3M" tabindex="0" type="button"><svg aria-hidden="true" width="20" height="20" viewBox="0 0 20 20" fill="none" stroke-width="1.5" stroke="var(--color-fg-primary)" stroke-linecap="round" stroke-linejoin="round" xmlns="http://www.w3.org/2000/svg" class="icon-noB79L"><g><path d="M2.53001 7.81595C3.49179 4.73911 6.43281 2.5 9.91173 2.5C13.1684 2.5 15.9537 4.46214 17.0852 7.23684L17.6179 8.67647M17.6179 8.67647L18.5002 4.26471M17.6179 8.67647L13.6473 6.91176M17.4995 12.1841C16.5378 15.2609 13.5967 17.5 10.1178 17.5C6.86118 17.5 4.07589 15.5379 2.94432 12.7632L2.41165 11.3235M2.41165 11.3235L1.5293 15.7353M2.41165 11.3235L6.38224 13.0882"></path></g></svg></button><button class="pencraft pc-reset pencraft icon-container view-image buttonBase-GK1x3M" tabindex="0" type="button"><svg xmlns="http://www.w3.org/2000/svg" width="20" height="20" viewBox="0 0 24 24" fill="none" stroke="currentColor" stroke-width="2" stroke-linecap="round" stroke-linejoin="round" class="lucide lucide-maximize2 lucide-maximize-2 icon-noB79L"><polyline points="15 3 21 3 21 9"></polyline><polyline points="9 21 3 21 3 15"></polyline><line x1="21" x2="14" y1="3" y2="10"></line><line x1="3" x2="10" y1="21" y2="14"></line></svg></button></div></div></div></a></figure></div><p>Looking at the chart above, you can see that the average approval time is <strong>10.3 hours</strong>. This is a major issue because during these 10 hours, the user is completely <strong>invisible</strong> in the catalog. Other people cannot see them, cannot like them, and cannot match with them. We clearly need to accelerate this process&#8212;ideally reducing it to minutes&#8212;to prevent that user from churning before they even start.</p><h2>3. The &#8220;Aha!&#8221; Moment</h2><p><em>The goal: Proof of value.</em></p><p>First, let&#8217;s define it. The <strong>Aha! Moment</strong> is the precise instant a new user experiences the core value of your product for the first time. It&#8217;s the moment the lightbulb turns on, and they stop wondering <em>&#8220;Why am I here?&#8221;</em> and start thinking <em>&#8220;I get it.&#8221;</em></p><p>In a dating app, the Aha! Moment isn&#8217;t when a user sees a pretty profile. It is <strong>when they get a reply to a message.</strong> That is the moment they realize: <em>&#8220;This works. There are real people here.&#8221;</em></p><p>But you need to understand: if you have a <strong>Freemium</strong> app and a business model like Tinder, users can usually only chat for <em>free</em> if they have Liked each other and formed a Match.</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;e3c5b843-a0e6-4c28-9b05-78f59178edd2&quot;,&quot;caption&quot;:&quot;I spent some time considering the best starting point for this Substack series. After drafting a few articles, I realized the single most critical topic for anyone planning to launch a dating product is choosing the business model. It&#8217;s the foundation of your entire strategy and, in classic terms, the core of your business plan.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;The Foundation: 5 Core Business Models in Dating&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-11T19:09:39.784Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/261a97c1-6721-4239-8f8d-e5dd001b171f_1536x1024.png&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/the-foundation-5-core-business-models&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:181353844,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:1,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p>Therefore, it is important to track the intermediate events: specifically, that the user is <strong>Liking</strong> other profiles, and that the user is forming <strong>Matches</strong> with them.</p><p>So, I recommend building a funnel consisting of these events:</p><ol><li><p><strong>Join Completed</strong></p></li><li><p><strong>Profile Liked</strong> (User takes action)</p></li><li><p><strong>Profiles Matched</strong> (Mutual interest)</p></li><li><p><strong>Conversation Started</strong> (First move)</p></li><li><p><strong>Conversation Replied</strong> (The Aha! Moment)</p></li></ol><p>Your job is to widen this funnel. If users are registering but not Liking anyone, you likely have an <strong>Inventory problem</strong> (an empty database or bad search results). If they are Liking but not Matching, you have a <strong>Liquidity problem</strong> (inactive users or poor matching algorithms). And if they are Matching but not talking, you face a <strong>Psychological barrier</strong>&#8212;users are often too shy to initiate or simply don't know what to say.</p><p></p><h2>4. Habit</h2><p><em>The goal: Retention.</em></p><p>Once a user experiences &#8220;Aha!&#8221;, we need them to build a habit. A habit means they use the product automatically&#8212;checking for matches while waiting for coffee or lying in bed.</p><p>How do we define a Habit Moment?</p><p>Slack defines a habit as: &#8220;The user exchanged at least one message 4 days out of their first 7 days.&#8221;</p><p>In dating, we can use a similar metric. We want to track users who engage in a core action (messaging or swiping) repeatedly within their first week.</p><p>By the way, Mixpanel has a chart that allows you to see very interesting information regarding this: specifically, how many days within a single week users performed a certain action (for example, sending a message).</p><div class="image-gallery-embed" data-attrs="{&quot;gallery&quot;:{&quot;images&quot;:[{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/9ab13db5-0903-4113-8867-2371341eee51_1768x1218.png&quot;}],&quot;caption&quot;:&quot;&quot;,&quot;alt&quot;:&quot;&quot;,&quot;staticGalleryImage&quot;:{&quot;type&quot;:&quot;image/png&quot;,&quot;src&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/9ab13db5-0903-4113-8867-2371341eee51_1768x1218.png&quot;}},&quot;isEditorNode&quot;:true}"></div><p></p><p>For example, looking at this data, we see that <strong>24%</strong> of users sent messages on at least 2 days in a week. However, only <strong>0.14%</strong> communicated on the site every single day.</p><p>I would recommend tracking this Habit Moment with a separate Mixpanel event. For example, as soon as a user sends a message on their 4th day out of 7, we fire the event <em>Habit Moment Happened</em>. This allows you to track the conversion rate and time-to-conversion from <em>Join Completed</em> to this specific <em>Habit Moment Happened</em>.</p><div><hr></div><h2>5. Engagement</h2><p><em>The goal: Liquidity and Depth.</em></p><p>Many founders mistake <strong>DAU (Daily Active Users)</strong> for Engagement. They think, &#8220;People are opening the app, so we are good.&#8221;</p><p><strong>This is wrong.</strong> In dating, a user can open the app, swipe 100 times, get zero matches, and leave angry. That user is an &#8220;Active User,&#8221; but they are actually churning.</p><p>Following the <strong>Reforge</strong> methodology, we measure Engagement based on <strong>Value</strong>, not just activity. We look at this on three levels:</p><h3>Level 1: Total Engagement (Volume)</h3><p>This is the pulse of your marketplace. We track:</p><ul><li><p><strong>Messages Sent (Total)</strong></p></li><li><p><strong>Conversations Started (Total)</strong></p></li></ul><p><strong>Red Flag:</strong> If your Registrations are skyrocketing but your <em>Messages Sent</em> is flat, you are acquiring low-quality traffic. You have users, but you don&#8217;t have liquidity.</p><h3>Level 2: Engagement Per Active User (Density)</h3><p>We need to know how effective the average user is.</p><p>Metric: Average Conversations Started per User (Total Conversations / WAU).</p><p>If last month your average user started 3 chats a week, and this month it&#8217;s only 1, your product experience is diluting. This often happens when you scale marketing too fast and bring in &#8220;tourists&#8221; rather than serious daters.</p><h3>Level 3: Segmentation (The Power User Curve)</h3><p>Never look at &#8220;average&#8221; users alone. Split them into buckets using a Frequency Report (often called the L30 or Power User Curve):</p><ol><li><p><strong>Casual Users (&#8221;Tourists&#8221;):</strong> Log in rarely, minimal action.</p></li><li><p><strong>Core Users:</strong> Regular usage, consistent swiping. The foundation of your retention.</p></li><li><p><strong>Power Users (&#8221;Whales&#8221;):</strong> These users send dozens of messages a day.</p></li></ol><p><strong>Industry Insight:</strong> In dating apps, Power Users are critical because they generate the liquidity for everyone else. They are the ones initiating chats and keeping the ecosystem alive. You need to monitor this segment closely&#8212;if they burn out, your ecosystem dies.</p><div><hr></div><h2>Summary</h2><p>You now have the framework for the Value Funnel:</p><p>Sign up &#8594; Setup &#8594; Aha &#8594; Habit &#8594; Engagement</p><p>You have the events to track in Mixpanel. Now you can find your bottleneck:</p><ul><li><p>Losing people at photo upload? <strong>Fix your Setup UI.</strong></p></li><li><p>People register but nobody talks? <strong>Fix your Liquidity (Aha Moment).</strong></p></li><li><p>People talk for two days and leave? <strong>Fix your Habit loops.</strong></p></li></ul><p>But remember, making users happy is only half the battle. We are running a business. In the next article, we will tackle the <strong>Revenue Funnel</strong>&#8212;how to turn this engagement into money, optimize paywalls, and maximize LTV.</p><p>Stay tuned.</p><h2>Why Build From Scratch?</h2><p>Implementing the Value Funnel strategy we just discussed requires more than just a good idea - it requires a sophisticated technical foundation.</p><p>Coding every single event, integrating SDKs, and setting up the logic to track &#8220;Habit Moments&#8221; or &#8220;Conversion Time&#8221; is a massive development drain. Most founders skip it to save time, and then they launch blind.</p><p><strong>This is exactly why we built <a href="https://www.skadate.com/">SkaDate</a>.</strong></p><p>We don&#8217;t just give you a dating app script; we give you observability out of the box. The Mixpanel integration, the event tracking, and the data structures I described in this article are already built into our core. You don&#8217;t need to spend weeks coding analytics. You just turn it on, look at the dashboards, and start optimizing your growth immediately.</p><p>Stop guessing. Start measuring.</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://calendly.com/alex-funnelflex/skadate-qa&quot;,&quot;text&quot;:&quot;Discuss Your Project with Me&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://calendly.com/alex-funnelflex/skadate-qa"><span>Discuss Your Project with Me</span></a></p>]]></content:encoded></item><item><title><![CDATA[How to Actually Grow a Dating Business]]></title><description><![CDATA[Stop building features. Start fixing your funnel.]]></description><link>https://alexsergeev.com/p/how-to-actually-grow-a-dating-business</link><guid isPermaLink="false">https://alexsergeev.com/p/how-to-actually-grow-a-dating-business</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Mon, 29 Dec 2025 17:03:32 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/61e81450-8733-4753-9f29-21c6e7b39dff_1024x572.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>So, you already have your own dating app or site. It&#8217;s live on the App Store and Google Play. You have some sign-ups, maybe even a few purchases.</p><p>But you&#8217;re stuck at a plateau. There is no growth. Registrations aren&#8217;t climbing, revenue isn&#8217;t increasing, and you don&#8217;t have the budget to pour into paid acquisition. You feel your hands tied, and you just want to give up.</p><p>However, you keep building new features, believing they will fix everything: <em>&#8220;I&#8217;ll just ship this one feature, then that one, and then the money will start rolling in!&#8221;</em> That&#8217;s what you tell yourself.</p><p>You spend more money and time. The features go live. Revenue stays flat. You get frustrated. Then, you repeat the cycle. This goes on for years.</p><p>Let me give it to you straight: You have fallen into the classic &#8220;Build Trap&#8221;.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>This is when you measure product success by the quantity of features released, rather than whether those features actually solve real problems for your users and your business.</p><p>This is even more painful for entrepreneurs investing their own hard-earned cash. You are spending your blood, sweat, and tears releasing new features, yet the business isn&#8217;t growing. Worse yet, you don&#8217;t even know how these features are being used. Who is actually using them? What percentage of people even know they exist? I call this the &#8220;Blind Build Trap&#8221;.</p><p>The problem isn&#8217;t that you aren&#8217;t doing enough. The problem is that you don&#8217;t know <strong>why</strong> you are doing it or <strong>what</strong> it influences.</p><h3><strong>The Way Out: Goals Over Features</strong></h3><p>The good news is that there is a way out of this trap. It doesn&#8217;t start with a new feature, a redesign, or an ad campaign. It starts with properly formulated product and business goals.</p><p>It&#8217;s easy to say &#8220;set goals&#8221;, but what kind? Ideally, we move away from generic wishes like <em>&#8220;I want growth&#8221;,</em> <em>&#8220;I want more money&#8221;,</em> or <em>&#8220;I want more users&#8221;.</em> These are impossible to manage directly, and they lead you right back to developing random features.</p><p>To set the right goals, we need to understand the dating business on a deeper level. </p><blockquote><p>I have written previously about the primary formula for any dating business - </p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;e18daedd-f749-4cef-bf9e-2dffd4df62d6&quot;,&quot;caption&quot;:&quot;It is time to dive into the most critical topic for any entrepreneur planning to launch a dating business: Money.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;The Unit Economics of Dating Apps (Part 1)&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-12T22:12:32.004Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/dc3895e7-dabc-443c-9efe-5764ac86c33f_1536x1024.png&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/the-unit-economics-of-dating-apps&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:181467243,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div></blockquote><p></p><p>Here is the formula:</p><blockquote><p><strong>Expected Income = (Number of New Buyers &#215; LTV) &#8211; Marketing Costs</strong></p></blockquote><p>This formula ties marketing and product together:</p><ul><li><p><strong>Number of New Buyers:</strong> How well your product converts sign-ups into customers.</p></li><li><p><strong>LTV (Lifetime Value):</strong> How much you earn from one customer over their entire &#8220;life&#8221; in the app.</p></li><li><p><strong>Marketing Costs:</strong> Your acquisition spend.</p></li></ul><p>We say &#8220;Expected Income&#8221; because people don&#8217;t always buy immediately after registration, and ideally, they buy more than once.</p><p>Imagine a user buys a one-month subscription but then realizes your user base is small or full of spammers (or worse, thinks you created fake profiles yourself) and cancels. You get only one payment.</p><p>But, if you solve the <strong><a href="https://alexsergeev.com/p/the-foundation-solving-the-cold-start">Cold Start Problem</a> </strong>and the user receives tangible value after subscribing, they will stay for a second cycle, maybe a third. In this case, our Expected Income includes all these payments thanks to the LTV parameter.</p><p>This formula sheds light on the economics, but it isn&#8217;t fully actionable yet. Goals based on it&#8212;like &#8220;Increase LTV&#8221;&#8212;are still too abstract.</p><p>To make them practical, we need to go one level deeper: <strong>User Behavior.</strong></p><p>The formula explains where the money comes from, but it doesn&#8217;t answer <strong>why</strong> some users convert and stay while others leave. To answer this, we need to map the complete user journey, specifically including the stage where they actually experience the product:</p><p><strong>Ad Click &#8594; App Download &#8594; Registration &#8594; Onboarding (Setup)  &#8594; Activation (Aha Moment) &#8594; Freemium Usage (Habit + Engagement) &#8594; Paywall View &#8594; Purchase &#8594; Repeat Purchase</strong></p><p>To manage this journey effectively, we must look at it through two lenses simultaneously: <strong>Value </strong>(why they stay) and <strong>Money </strong>(why they pay).</p><h3><strong>1. The Value Lens: Retention &amp; Engagement</strong></h3><p>This lens corresponds directly to the LTV component of our income formula.</p><p>It&#8217;s simple math: You cannot have high <em>Lifetime Value</em> if the user&#8217;s &#8220;Life&#8221; in the app is short. Higher retention and deeper engagement mean the user stays longer, creating more payment cycles and driving LTV up. Conversely, if the user doesn&#8217;t find value immediately, they won&#8217;t stay, and LTV collapses to zero.</p><p>I prefer using the <a href="https://www.reforge.com/">Reforge</a> methodology (from their <a href="https://www.reforge.com/courses/retention-and-engagement/details">Retention + Engagement program</a>), which helps us understand if we are successfully keeping the user. They highlight these key stages:</p><p><strong>Sign up &#8594; Setup &#8594; Aha &#8594; Habit &#8594; Engagement</strong></p><ul><li><p><strong>Sign up:</strong> The user registered. They haven&#8217;t received value yet.</p></li><li><p><strong>Setup:</strong> They performed the minimum actions to make the product work (filled out their profile, added photos, were approved by moderators, and became discoverable and able to connect with other users).</p></li><li><p><strong>Aha:</strong> The key moment when the user <em>actually feels</em> the value (received a meaningful reply).</p></li><li><p><strong>Habit:</strong> The user formed a habit after interacting with several people.</p></li><li><p><strong>Engagement:</strong> They constantly return to the product to chat and date.</p></li></ul><p>Now, let&#8217;s see how adopting this framework shifts our focus from simply shipping features to actually solving user problems. Let&#8217;s apply this to a specific feature, like Video Chat.</p><p>The goal is not to &#8220;build a video chat feature.&#8221; The goal is to remove the friction between the stages (Sign up &#8594; Setup &#8594; Aha &#8594; Habit &#8594; Engagement):</p><ul><li><p>If users drop off at Setup, building a cool &#8220;video chat&#8221; is useless - they aren&#8217;t even completing their profiles! You need to fix the onboarding flow.</p></li><li><p>If users finish Setup but don&#8217;t reach Aha (no matches/replies), you need to fix the matching algorithm or user liquidity, not change the color of the buttons.</p></li><li><p>If they reach Aha but don&#8217;t form a Habit, you need re-engagement mechanics (push notifications, digests).</p></li><li><p>But if users are engaged but leaving the app to talk on WhatsApp, <em>then</em> you build Video Chat &#8212; to keep that value inside your product (Engagement stage).</p></li></ul><p>We stop guessing and start building specific paths to move the user from one stage to the next.</p><h3><strong>2. The Money Lens: Decomposing &#8220;New Buyers&#8221;</strong></h3><p>Delivering value keeps them in the app, but you still need to get paid. Many founders treat monetization as a passive event. It isn&#8217;t.</p><p>We need to look at the <strong>Number of New Buyers</strong> part of our formula and decompose it. It is a structural funnel:</p><blockquote><p><strong>New Buyers = (Registrations &#215; Paywall View Rate) &#215; Purchase Conversion</strong></p></blockquote><p>This formula reveals that &#8220;Monetization&#8221; isn&#8217;t a single task. It consists of two distinct levers that you must optimize separately:</p><p><strong>A. Paywall View Rate (Visibility)</strong></p><p>You can&#8217;t sell what people can&#8217;t see.</p><ul><li><p><strong>Subscription:</strong> Do they see the offer during onboarding? On a new session start?</p></li><li><p><strong>Feature Unlocks:</strong> Think about Tinder&#8217;s &#8220;See Who Liked You&#8221;. This is a massive revenue driver. If you hide this feature deep in a menu, your Paywall View Rate is near zero. If you show a blurred photo teaser at the start of the session, and on a separate tab, and in the Messages section, your View Rate skyrockets.</p></li><li><p><strong>Consumables:</strong> Think about &#8220;Super Likes,&#8221; &#8220;Boosts&#8221;, etc. Are these offers visible on the swipe card or in other places?</p></li></ul><p><strong>B. Purchase Conversion (Effectiveness)</strong></p><p>Of the people who clicked &#8220;See Who Liked Me&#8221; or tried to send a &#8220;Super Like,&#8221; how many actually paid?</p><ul><li><p>If 100% of users see the &#8220;Who Liked You&#8221; teaser, but only 0.1% buy, your value proposition or pricing is off.</p></li><li><p>If 5% see it, but 20% buy, you have a <strong>visibility problem</strong>. You need to show that teaser more aggressively.</p></li></ul><p><strong>The Lesson:</strong> Don&#8217;t just &#8220;add payments.&#8221; Analyze specifically: <em>Are users seeing the paid features? And if they see them, are they converting?</em></p><h3><strong>The Metrics Tree: Connecting Value and Money</strong></h3><p>Now we combine these two views into a Metrics Tree. This prevents you from drowning in data by organizing metrics into a logical hierarchy of <strong>Outputs (Results)</strong> and <strong>Inputs (Levers)</strong>.</p><p>You start at the top and drill down to find the root cause:</p><p><strong>Level 1: The Output (Business Health)</strong></p><p>At the top is <strong>Net Revenue</strong>. This is your root metric, but it&#8217;s a <em>lagging indicator</em>. You can&#8217;t impact it directly; it merely tells you what happened in the past.</p><p><strong>Level 2: The Drivers (Strategic Focus)</strong></p><p>To move Revenue, you break it down into its core components:</p><ul><li><p><strong>Monetization Velocity:</strong> New Buyers (How well you convert demand).</p></li><li><p><strong>Retention Strength:</strong> LTV &amp; Churn (How much value users get).</p></li></ul><p><strong>Level 3: The Inputs (Product Levers)</strong></p><p>This is where the &#8220;Value Lens&#8221; takes over. These are <em>leading indicators</em>&#8212;user behaviors you can actually influence through product changes:</p><ul><li><p><strong>To improve New Buyers:</strong> Look at Paywall Visibility and Registration-to-Purchase Conversion. Registration-to-Purchase Conversion can be decomposed into these specific sub-metrics:</p><ul><li><p><strong>1. Onboarding Completion (Inventory Generation):</strong> If a user doesn&#8217;t upload a photo during onboarding, they won&#8217;t get any Likes. If they have 0 Likes, the &#8220;Who Liked Me&#8221; screen is empty. There is nothing to sell.</p></li><li><p><strong>2. Notification Deliverability (The Hook):</strong> Most Likes happen when the user is offline. You need to bring them back. If your <strong>Push/Email Delivery Rate</strong> is low (or going to Spam), or your Open Rate is low (boring copy), the user never returns to the app to see the blurred photo.</p></li><li><p><strong>3. Teaser Visibility (In-App Paywall View):</strong> Once they are in the app, do they see the teaser? Is there a &#8220;Red Dot&#8221; badge on the tab? Is the blurred photo visible on the main screen?</p></li><li><p><strong>4. Close Rate (The Offer):</strong> When they tap the blurred photo, how many actually pay? This tests your pricing and value proposition.</p></li></ul></li></ul><ul><li><p><strong>To improve LTV:</strong> Look at Activation and Habit Formation.</p><ul><li><p>Why aren&#8217;t they retaining? &#8594; Maybe the &#8220;Aha Moment&#8221; is broken or there is technical friction (e.g., transactional emails are going to Spam instead of Inbox).</p></li><li><p>Why no &#8220;Aha Moment&#8221;? &#8594; Check <strong>Liquidity Metrics</strong>: Visit-to-Like Rate, Match Rate, and Reply Rate.</p></li><li><p>Let&#8217;s decompose the &#8220;Reply Rate&#8221;. If users match but don&#8217;t talk, they churn. Why is the Reply Rate low?</p><ul><li><p><strong>1. Notification Speed &amp; Deliverability:</strong> Speed is critical in chat. If a push notification arrives 5 minutes late (or goes to spam), the &#8220;emotional moment&#8221; is lost, and the user might have already closed the app.</p></li><li><p><strong>2. Opening Message Quality (The &#8220;Hi&#8221; Problem):</strong> Analyze the content. If 80% of first messages are just &#8220;Hey&#8221;, the Reply Rate will be low.</p></li><li><p><strong>3. Profile Trust Signals:</strong> Does the sender look real? Users often ignore messages from profiles with 1 photo or no bio, fearing bots or scammers.</p></li><li><p><strong>4. Active Status:</strong> Was the message sent to a user who hasn&#8217;t logged in for 30 days? (This is an Inventory currency problem&#8212;you are showing inactive users).</p></li></ul></li></ul></li></ul><p><strong>Real-World Example: The &#8220;Who Likes Me&#8221; Trap</strong> Imagine your overall Subscription Conversion drops by 10%. You drill down and see the drop is specifically coming from your top revenue source: the &#8220;See Who Likes You&#8221; paywall trigger.</p><p>Your first instinct might be to change the text on the button or lower the price. But the Metrics Tree forces you to look deeper to find where the problem is actually buried:</p><ul><li><p><strong>Trace it down:</strong> Users are hitting the paywall, but the Close Rate has dropped. Why?</p></li><li><p><strong>Dig deeper:</strong> You investigate the &#8220;Inventory&#8221; behind the paywall. You discover that the average number of &#8220;Incoming Likes&#8221; per user has dropped significantly. Instead of seeing &#8220;You have 10 new likes,&#8221; users now see &#8220;You have 1 new like.&#8221; The curiosity gap has collapsed.</p></li><li><p><strong>Hypothesize &amp; Analyze:</strong> Why did the Like Volume drop? You generate three hypotheses:</p><ol><li><p><strong>Traffic:</strong> Did fewer users log in today? (Data check: No, DAU is stable).</p></li><li><p><strong>Tech:</strong> Is the &#8220;Like&#8221; button broken? (Data check: No, API logs are clean).</p></li><li><p><strong>Relevance:</strong> Are users seeing people they don&#8217;t like? (Data check: <strong>Yes. The &#8220;Swipe Left&#8221; rate has spiked by 15%</strong>).</p></li></ol></li><li><p><strong>The Root Cause:</strong> The issue isn&#8217;t the paywall price&#8212;it&#8217;s the <strong>Feed Algorithm</strong>. You are showing users profiles that they don&#8217;t find attractive.</p></li><li><p><strong>Result:</strong> You improve feed relevance &#8594; Global Like Rate goes up &#8594; Users see &#8220;You have 15 new likes&#8221; &#8594; Curiosity peaks &#8594; Subscription Conversion recovers.</p></li></ul><p>You stop worrying about the top-level number and focus on the specific input metric (Swipe Left Rate) that is actually broken.</p><h3><strong>OMTM: Focus on One Lever</strong></h3><p>Once the Metrics Tree is built, you will see problems everywhere. However, you cannot fix everything at once. You must select your <strong>OMTM (One Metric That Matters)</strong>. This is the single specific metric the team will focus on for the next quarter.</p><p><strong>1. How to Select the OMTM (The Bottleneck Principle)</strong></p><p>You look at your tree and identify the &#8220;Constraint&#8221;&#8212;the step in the funnel with the biggest drop-off or the lowest performance compared to benchmarks.</p><ul><li><p><em>Example:</em> If your Registration-to-Purchase conversion is healthy, but your Day-1 Retention is terrible, it often means users aren&#8217;t finding anyone attractive to interact with. They browse but don&#8217;t swipe right and don&#8217;t get matches as a result. You shouldn&#8217;t waste time A/B testing the paywall or chat features. Your OMTM becomes <strong>Signup-to-Match Rate</strong>.</p></li></ul><p><strong>2. From Metric to Action: The Hypothesis Loop</strong></p><p>Once the OMTM is set (e.g., Signup-to-Match Rate), you switch from &#8220;Analysis Mode&#8221; to &#8220;Execution Mode.&#8221; You don&#8217;t just stare at the metric; you launch a process to move it:</p><ul><li><p><strong>Generate Ideas:</strong> Brainstorm specific features or changes that could impact this metric.</p><ul><li><p><em>Idea A:</em> Show the most attractive users first.</p></li><li><p><em>Idea B:</em> Improve the default sorting (Active users first).</p></li><li><p><em>Idea C:</em> Increase the like limit from 10 to 20.</p></li></ul></li><li><p><strong>Prioritize (ICE Framework):</strong> To avoid chaos, evaluate every idea using the ICE Score:</p><ul><li><p><em>Impact:</em> How much will this move the OMTM? (1&#8211;10)</p></li><li><p><em>Confidence:</em> How sure are we that it will work? (1&#8211;10)</p></li><li><p><em>Ease:</em> How easy is it to build? (1&#8211;10)</p></li></ul></li><li><p><strong>Execute:</strong> Pick the ideas with the highest ICE score and run them as experiments (A/B tests).</p></li><li><p><strong>Analyze &amp; Decide (The Critical Step):</strong> An experiment is useless without a decision. Look at the data and take action:</p><ul><li><p><strong>Ship:</strong> If the hypothesis is confirmed and the metric went up &#8212; roll it out to 100% of users.</p></li><li><p><strong>Kill:</strong> If the metric didn&#8217;t move (or dropped) &#8212; <strong>delete the code</strong>. Do not keep &#8220;zombie features&#8221; that didn&#8217;t prove their value. They only add technical debt.</p></li><li><p><strong>Learn:</strong> Even a failed test is a success if you learned <em>why</em> users didn&#8217;t engage. Use this insight to update your Hypothesis List.</p></li></ul></li></ul><p>This turns your strategy into a clear, repeatable pipeline: <strong>Tree &#8594; Bottleneck &#8594; OMTM &#8594; Ideas &#8594; ICE &#8594; Experiment &#8594; Analysis (Ship or Kill)</strong></p><h3><strong>What to Do Next: Your Growth Algorithm</strong></h3><p>If your dating app isn&#8217;t growing, <strong>stop shipping random features</strong>. You cannot code your way out of a strategy problem. Instead, follow this diagnostic loop:</p><p><strong>1. Audit the Journey (Two Tracks)</strong></p><p>Map out your user flows specifically for <strong>Value</strong> (Sign up &#8594; Setup &#8594; Match &#8594; Chat) and <strong>Money</strong> (Registration &#8594; Paywall Trigger &#8594; Purchase). Do not mix them yet.</p><p><strong>2. Build the Metrics Tree</strong></p><p>Stop looking at &#8220;Revenue.&#8221; Connect your bank account to user behavior.</p><ul><li><p>Revenue (Output) depends on Purchases.</p></li><li><p>Purchases depend on Paywall Views.</p></li><li><p>Paywall Views depend on Matches (if you use a &#8220;Who Likes Me&#8221; model).</p></li><li><p>Matches depend on Likes (Input).</p></li></ul><p><strong>3. Locate the Leak (The Bottleneck)</strong></p><p>Look at the data. Where is the biggest drop-off relative to benchmarks?</p><ul><li><p>Is it a <strong>Money Problem</strong>? (Users see value but the price/offer is wrong).</p></li><li><p>Is it a <strong>Value Problem</strong>? (Users aren&#8217;t swiping, matching, or chatting).</p></li><li><p>Crucial Check: Is it a <strong>Technical Problem</strong>? (Are emails hitting spam? Is the chat server laggy?)</p></li></ul><p><strong>4. Pick Your OMTM</strong></p><p>Select the <strong>one</strong> metric that represents that bottleneck.</p><ul><li><p>Example: &#8220;We will ignore Revenue for this quarter and focus 100% of our energy on increasing <strong>Signup-to-Match Rate</strong>.&#8221;</p></li></ul><p><strong>5. Run the ICE Cycle</strong></p><p>Don&#8217;t just &#8220;redesign.&#8221;</p><ul><li><p><strong>Brainstorm</strong> 10 ideas to move that OMTM.</p></li><li><p><strong>Score</strong> them (Impact, Confidence, Ease).</p></li><li><p><strong>Implement</strong> the winner.</p></li><li><p><strong>Analyze &amp; Iterate:</strong> Look at the data. Did the metric move? Regardless of the outcome, extract the lesson (&#8221;Why did users behave this way?&#8221;). Use this insight to refine your understanding of the user and sharpen your ideas for the next cycle.</p></li></ul><h3><strong>Why This Strategy Fails Without Analytics</strong></h3><p>Everything discussed above, the Metrics Tree, the OMTM, the ICE framework, is impossible to execute on &#8220;gut feeling.&#8221;</p><p>Unless you can measure:</p><ul><li><p>The exact drop-off rate during <strong>Setup</strong>,</p></li><li><p>The metric <strong>Signup-to-Match Rate</strong></p></li><li><p>The visibility of the <strong>Who Liked You paywall</strong>,</p></li><li><p>The percentage of users reaching the <strong>Aha Moment</strong> (First Chat),</p></li><li><p>The actual conversion to <strong>Paid Subscriber</strong>,</p></li></ul><p>...you are not managing the product&#8212;you are just <em>believing</em> in it.</p><p>The logical next step is <strong>Product Analytics</strong>. Tools like Mixpanel, Amplitude, or PostHog allow you to see the real user path, build these funnels, and manage through hard data, not guesses.</p><p><strong>In the next articles, I will move from strategy to implementation:</strong></p><ol><li><p><strong>Conversion Mechanics:</strong> How to measure the <strong>Sign-up to Purchase, Signup-to-Match Rate</strong> rates correctly and identify exactly where users drop off in the funnel.</p></li><li><p><strong>Retention Deep Dive:</strong> What is cohort analysis?</p></li><li><p><strong>The Tracking Plan:</strong> Which specific events you <em>must</em> track to build these dashboards and visualize your OMTM.</p></li></ol>]]></content:encoded></item><item><title><![CDATA[The Unit Economics of Dating Apps (Part 2): How to Turn Free Users into Paying Subscribers]]></title><description><![CDATA[The Golden Formula for Scalable Growth.]]></description><link>https://alexsergeev.com/p/the-unit-economics-of-dating-apps-a01</link><guid isPermaLink="false">https://alexsergeev.com/p/the-unit-economics-of-dating-apps-a01</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Tue, 16 Dec 2025 04:13:25 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/05ac2234-4f88-4230-bb5d-43ee0cf26929_1024x506.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Let&#8217;s continue studying the core formula of the dating business.</p><blockquote><p><strong>Expected Income = (Number of New Buyers &#215; LTV) &#8211; Marketing Costs</strong></p></blockquote><p>Last time, we examined <strong>LTV</strong> in detail in this article:</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;d69debe0-9e89-4982-be1e-729b38f4b42e&quot;,&quot;caption&quot;:&quot;It is time to dive into the most critical topic for any entrepreneur planning to launch a dating business: Money.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;The Unit Economics of Dating Apps (Part 1)&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-12T22:12:32.004Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/dc3895e7-dabc-443c-9efe-5764ac86c33f_1536x1024.png&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/the-unit-economics-of-dating-apps&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:181467243,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:false,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p></p><p>Today, we will talk about the <strong>Number of New Buyers</strong>.</p><p></p><h3>Generating the Energy</h3><p>You launched a Facebook campaign.</p><p>In the video banner, for instance, you show a successful man: you show how he cooks, how he goes to the gym, and how he walks his dog on the beach.</p><p>If a user is allergic to dogs, they obviously won&#8217;t click on this banner. But let&#8217;s assume they have no allergies and no life partner&#8212;they are single. And the time has come for them to find a partner.</p><p>They are tired of endlessly scrolling through their Instagram feed, and they are frankly sick of the photos of their mega-successful acquaintances. The moment is right, and with great hope, they click on this banner.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>The banner created a vision of a desired goal; the user is excited and wants to find a partner right now.</p><p>Of course, they won&#8217;t land on a date with this handsome man from the banner immediately after the click. But the banner and the image of the goal have charged them with energy, and they are ready to overcome almost any difficulty. Thank this banner for that energy; we will still need it in the future.</p><p></p><h3>The Harsh Reality</h3><p>Next, the harsh reality begins. The user lands on your app listing in the App Store (or Google Play).</p><p>Also, <strong>Web2App funnels</strong> have become very popular recently: this is when you send users from an ad to your web application, where they undergo registration, fill out a profile, buy a subscription, and only after that proceed to the listing to download the app from the App Store or Google Play.</p><p>Why do this and complicate the path for users?</p><p>Because you pay a 15% to 30% commission to Apple and Google on every transaction.</p><ul><li><p>If you have a new app and you earn up to $1 million per year, you will give away 15% (as a member of the Small Business Program).</p></li><li><p>If you exceed this threshold, you will start paying 30%.</p><p>I sincerely wish for you to exceed this threshold as soon as possible.</p></li></ul><p>So, when a user pays not through Apple/Google, but enters their card details and pays via a Payment Gateway (for example, Stripe), the commission in the US is only <strong>2.9% + $0.30</strong>, which is much less than 20-30%. That is exactly why Web2App funnels have acquired such popularity. There are even ready-made funnel builders that allow you to create them without developers. I will review them in detail in a separate article.</p><p>By the way, many beginners think that Web2App is technically difficult. In reality, there is no &#8220;magic&#8221;: the user registers and pays on the mobile site, and then downloads the app and simply logs in with the same email and password. Your database sees the &#8220;Premium&#8221; status and opens access. This is a simple synchronization available to any development team.</p><blockquote><p><strong>Important Note on Payments in the US</strong></p><p>Recently, following the legal battles between Epic Games and Apple, developers in the US were allowed to place links to external payment methods directly inside the app (you might have seen a &#8220;Pay via Credit Card&#8221; button in Tinder).</p><p>Does this solve the problem? No. Apple still charges a commission on these transactions (around 27%), plus it requires complex reporting.</p><p><strong>The Verdict:</strong> For a startup, a Web2App funnel is still the superior strategy. Don&#8217;t try to cheat the system from inside the app; it&#8217;s better to lead the user to the website from the start.</p></blockquote><p></p><h3>ASO and Installation</h3><p>Next, let&#8217;s talk about how the user looks at screenshots and how important they are, as well as the icon and reviews &#8212; nobody reads the app description, so it is important to convey the essence through screenshots and headers. Screenshots and icons are so important that Apple/Google created a mechanism for A/B testing screenshots and icons.</p><p>Then, the user downloads the app.</p><p></p><h3>Verification</h3><p>Next, as a rule, is <strong>SMS verification</strong>. It helps to filter out lazy scammers, serving as a minimum defense. But you must be aware of two critical threats:</p><ol><li><p><strong>SMS Pumping Attacks (Toll Fraud).</strong> This is a nightmare scenario where fraudsters use bots to trigger thousands of SMS verification codes to premium-rate numbers that <em>they</em> control (usually in high-cost regions like Indonesia or parts of Africa). <strong>The math is scary:</strong> You pay Twilio/Telesign $0.10 per SMS. The fraudster gets a kickback of $0.03 from the corrupt telecom provider. They run a bot for one night, sending 100,000 requests. You wake up to a <strong>$10,000 bill</strong>, and they walk away with $3,000 profit. This is a topic for a separate article, but you need to set rate limits immediately.</p></li><li><p><strong>Disposable Phone Numbers.</strong> These are temporary virtual numbers (often VoIP or SIM farms) that anyone can rent for minutes to receive a code and then discard.</p></li></ol><p>This means SMS is <strong>not a 100% protection</strong> against scammers.</p><p><strong>The Next Step &#8212; Get the User&#8217;s Email</strong></p><p>This is critically important because email is our main tool for Retention (returning users to the app).</p><p>How exactly to get it? The classic &#8220;Email + Password&#8221; combo is already outdated and considered unsafe. Users often set weak passwords, making them vulnerable to Account Takeover (ATO) through brute-force attacks.</p><p>Therefore, I strongly recommend using <strong>Email OTP</strong> (One-Time Password). This is a &#8220;passwordless&#8221; method: the user simply enters their email, a 4-digit code is sent to them, they enter it, and they are in. No password needs to be remembered, and it cannot be stolen.</p><p>Also, add Google SSO and Apple SSO. This is even faster for the user, and for you, it is a huge plus that you do not need to verify the email &#8212; Google and Apple have already done this for you; you get a guaranteed valid email.</p><p>Important advice: Do not make a login via Facebook. Trust in it has fallen, and people are afraid to share their data through this social network.</p><p><strong>Date of Birth</strong></p><p>Next, we request the Date of Birth. We categorically must not let in users under 18 years old. However, the strictness of the check directly depends on your niche.</p><ol><li><p><strong>Mainstream Dating Apps (Tinder, Bumble):</strong> For ordinary dating apps hosted in the App Store and Google Play, a standard DOB Picker (selecting the date of birth in the interface) is currently enough. At the moment, this is enough to comply with store policies, although requirements are gradually tightening.</p></li><li><p><strong>Adult Industry:</strong> Such projects are usually banned in mobile stores and live exclusively on the Web. And here, legislation (especially in the US and EU) requires strict <strong>Age Assurance</strong>. You cannot simply trust the entered date &#8212; it is illegal. You are obliged to use advanced mechanisms:</p><ol><li><p>Selfie verification with AI age estimation (liveness check).</p></li><li><p>Full document check (Government ID verification).</p><p>This topic is a legal and technical minefield. In the future, I will make a separate big article about age verification, where we will consider all the pitfalls.</p></li></ol></li></ol><p></p><h3>Filling the Profile: Energy vs. Friction</h3><p>Next, we ask the user to fill out various important fields, for example: Height, Education, Job, Smoking habits, etc.</p><p>By the way, what do you think: if we don&#8217;t make these fields mandatory and request them only after the user has gotten inside the app &#8212; will they fill them out?</p><p>Actually, as my experience and other apps like Tinder, Hinge, and others show &#8212; people willingly fill out mandatory fields during registration that can be entered quickly (dropdown-based). But if you make them optional, people do not fill them out.</p><p><strong>The secret</strong> is that during registration, people are <strong>excited</strong> and they have that <strong>energy</strong> which was created by your marketing and that video banner. And this energy, these expectations, become the fuel that, despite the <strong>friction</strong>, moves the user through the many steps of registration.</p><p>But if you make these fields optional, users get inside the app, and many of them then simply leave and do not return.</p><p>Retention Day 1 after registration for new dating apps is 10-20%, meaning 80-90% of users registered and left. And if they didn&#8217;t fill out the profile, nothing remains of them in your catalog. But if they filled out the profile but churned, then later some other user might write to this user and resurrect them.</p><p>And what do you think, what percentage of people will fill out the &#8220;About Me&#8221; field during registration if it is optional? And is it worth making photos mandatory? How many photos to request? And how does profile completeness and the presence of photos affect the reply rate? I will publish a separate article on all these questions.</p><p></p><h3>The Setup Moment</h3><p>Okay, the user filled out the profile, uploaded a photo, what next? Next, they get inside the app. What do they do? They look around &#8212; look at other people&#8217;s profiles, like others, and so on.</p><p>But do other people see this user? No, because moderators haven&#8217;t checked the profile yet; what if there is nudity in the photo? We cannot show it to other people, and we cannot deliver any types of messages from this user to others until they are approved.</p><p>As a rule, this moment when the user can use the product and has already performed the necessary settings is called the <strong>Setup Moment</strong>. In our case, the user must have a filled profile, they must have at least 1 photo, and they must be <strong>approved by moderators</strong> (meaning a human/system must check their profile data and their photos).</p><p>Sounds expensive? Don&#8217;t be scared. You don&#8217;t need to hire a staff of moderators from the start. In the beginning, you can (and should) do this yourself to feel the audience. And a bit later, plug in AI solutions (like <strong>AWS Rekognition</strong>), which cost pennies and automatically filter 95% of forbidden content. </p><p><strong>Switching Modes: From Funnel to Product</strong></p><p>Our hero has overcome all barriers: downloaded the app, passed SMS verification, completed the profile, and was approved.</p><p>They are inside. Phew.</p><p>This means we have successfully closed two stages at once: <strong>Sign Up Moment</strong> and <strong>Setup Moment</strong> (the user is technically ready to use the product).</p><p>Here we need to pause and change optics.</p><p>Until this moment, we looked at the process through the eyes of a Marketer and a Developer. Now we must put on the glasses of a Product Manager.</p><p>Why? After all, we are talking about money (Number of New Buyers), why not simply ask for payment right now?</p><p>Because in Dating Apps, Money is a consequence of Value. If we try to sell a subscription to a user who simply filled out a profile but hasn&#8217;t yet understood why they are here, we will burn the budget.</p><p>To make our business model work, it remains for us to lead the user through the next two steps:</p><ol><li><p><strong>Aha Moment (First Value).</strong> The moment when the user for the first time gets a real result and thinks: &#8220;Oh, this is what I need!&#8221;. It is exactly this realization that forms their <strong>willingness to pay</strong>.</p></li><li><p><strong>Habit Moment (Habit).</strong> The moment when using the app becomes part of their routine. This guarantees that they will not just make a one-time purchase, but will attach to us and pay again and again while this habit is active.</p></li></ol><p>But to understand when exactly these moments occur, we first need to define the global meaning of our app for the user.</p><p></p><h3>Global Goal (NSM)</h3><p>The ultimate goal of any dating app is to create a happy couple. That is the &#8220;Product Vision.&#8221;</p><p>But as a business, we have a problem: We cannot track happiness. It happens offline, away from our servers.</p><p>To find a metric we <em>can</em> track, we need to <strong>reverse-engineer the &#8220;Happy Path&#8221;</strong> of a user. Let&#8217;s trace the steps backward from the goal:</p><ol><li><p><strong>Happy Couple</strong> (The Goal)</p><ul><li><p><em>Can we measure this?</em> No.</p></li></ul></li><li><p><strong>Offline Dates</strong></p><ul><li><p><em>Can we measure this?</em> Generally, no. We cannot stand next to them with a candle to see if they actually met at Starbucks.</p></li></ul></li><li><p><strong>Exchange of Contacts</strong> (Phone number / Instagram / FaceTime)</p><ul><li><p><em>Can we measure this?</em> <strong>YES.</strong> This is a digital action inside our chat.</p></li></ul></li><li><p><strong>Active Dialogue</strong></p><ul><li><p><em>Can we measure this?</em> <strong>YES.</strong></p></li></ul></li></ol><p><strong>The &#8220;Offline Blindness&#8221; Problem</strong></p><p>Most apps go blind the moment users leave the chat. Exception: Hinge is trying to solve this. They built a feature called &#8220;We Met.&#8221; After an exchange of phone numbers, the app eventually asks: &#8220;Did you go on a date?&#8221;</p><p>If the user clicks &#8220;Yes,&#8221; Hinge asks a follow-up quality question: &#8220;Is she/he the type of person you&#8217;d see again?&#8221;</p><p>It is a brilliant attempt to feed offline data back into their online algorithm.</p><p>However, for most apps, we cannot rely on users to report back. We have to trust the data we have.</p><p>That is why our North Star Metric&#8212;the most reliable &#8220;thermometer&#8221; of success&#8212;is the step just before the offline date:</p><p><strong>NSM = The number of dialogues that result in a Contact Exchange.</strong></p><p></p><h3>The Aha Moment</h3><p>In product analytics, the next big moment after Setup is called the <strong>Aha Moment</strong>. This is the moment when the user experiences the <strong>core value prop</strong> for the first time, meaning in our case, when their first dialog took place.</p><p>In our case with dating, the Aha Moment is when the user has spoken with at least one person within 1 week after registration.</p><p>Examples of Aha Moments for other products:</p><ul><li><p><strong>Airbnb:</strong> Booked night turns out well.</p></li><li><p><strong>Pinterest:</strong> I&#8217;ve found something cool in an interesting feed.</p></li></ul><p></p><h3>The Habit Moment</h3><p>The next important moment is Habit. This is the moment when a habit appears in the user around this core value prop. In our case, this is the dialogs with other users. That is, when a user has spoken with, for example, 10 people within 1 week after registration. This means that the user has developed a habit, and they will remain with us with a very high probability and will use our product further.</p><p>Examples of Habit Moments from other spheres:</p><ul><li><p><strong>Pinterest:</strong> &#8220;I find cool things on Pinterest every week.&#8221;</p></li><li><p><strong>Airbnb:</strong> Booking second stay within one year.</p></li></ul><p></p><h3>The Engagement Moment</h3><p>The next stage is the <strong>Engagement Moment</strong> &#8212; when the user has not just formed a habit, but continues to actively use the app. Moreover, they do not just come to the app, but perform the core action often, which in our case is participation in chats. And we will measure engagement in dating with such metrics:</p><ul><li><p><strong>Daily Active Chatters</strong> / <strong>Weekly Active Chatters</strong>. The meaning of the metric is we want people ideally to come to us every day and talk to at least someone. This is an indicator that measures the frequency of engagement.</p></li></ul><p><em>Examples of how Engagement Frequency is measured for other products:</em></p><ul><li><p><strong>Airbnb:</strong> Frequency - QAG/YAG (Quarterly active guests / Yearly active guests).</p></li><li><p><strong>Pinterest:</strong> Frequency - DAR/WAR (Daily Active Pins/Repins / Weekly Active Pins/Repins).</p></li></ul><p></p><h3>The Finale: Synchronizing Value and Revenue</h3><p>We examined the user&#8217;s value track with you, but where is the Number of New Buyers here? Well, first I wanted to show how the user receives value from dating apps.</p><p>And now that value is received, is it time for us to earn on this?</p><p>Here we approach the main question: how to synchronize <strong>Value</strong> and <strong>Revenue</strong>?</p><p>The main decision that a founder must make: <strong>where exactly to place the Paywall relative to the Aha Moment?</strong></p><p>If you ask for money too early, when there is no trust yet &#8212; the user will leave. If too late &#8212; you will leave money on the table.</p><p>Let&#8217;s compare how market leaders do this.</p><h4><strong>Two Dominant Monetization Models</strong></h4><p><strong>1. The Tinder Model (Freemium)</strong>: Payment as an Accelerator and Competitive Advantage</p><p>In this model, the Aha Moment (dialogue) is technically free. Two users can match and start corresponding without spending a penny.</p><p>Why then do they pay?</p><ul><li><p><strong>They pay for Speed (Tinder Gold):</strong> Swiping at random is work. Guessing &#8220;did they like me or not&#8221; is stress. By buying access to the &#8220;Who Likes You&#8221; list, the user cuts a corner: they immediately see those who have already shown interest. This is the monetization of impatience and curiosity.</p></li><li><p><strong>They pay for Visibility (Tinder Platinum):</strong> The market is oversaturated. Beautiful girls simply do not see the likes of ordinary users in the pile. By buying Platinum, a man pays for his like to be shown first (Priority Likes). This is already the monetization of <strong>competition</strong>.</p></li></ul><p><strong>The essence of the strategy:</strong> Value is available for free, but <em>efficiency</em> costs money.</p><p><strong>2. The Seeking Model (Paywall):</strong> Payment as a Pass</p><p>In niche apps or models with high intention, the Aha Moment is strictly behind a paywall.</p><ul><li><p>You can look at profiles, you can add them to favorites, but you physically cannot enter into a dialogue without payment.</p></li><li><p><strong>The essence of the strategy:</strong> We monetize access. The user <em>cannot</em> experience the Aha Moment (dialogue) until they become a buyer.</p></li><li><p>In this model, <strong>Purchase is a prerequisite</strong> for receiving value.</p></li></ul><p></p><h3>Main Metric: Reg-to-Paid Conversion</h3><p>Regardless of which model you choose, for the variable <strong>Number of New Buyers</strong> in our formula, one metric is critically important: <strong>Registration-to-Purchase Conversion</strong>.</p><p>This is the bridge between the world of product and the world of finance.</p><ul><li><p><strong>User&#8217;s view:</strong> &#8220;I register -&gt; Fill out profile (Setup) -&gt; See value -&gt; Pay&#8221;.</p></li><li><p><strong>Business view:</strong> &#8220;Traffic -&gt; Setup -&gt; <strong>First purchase</strong> -&gt; LTV&#8221;.</p></li></ul><p>To maximize the quantity of new buyers, you must minimize friction at the Setup stage (make entry simple), but maximize motivation before the Paywall (make being in a free status &#8220;painful&#8221; or ineffective).</p><p></p><h3>Summary</h3><p>Let&#8217;s look at our formula one more time:</p><blockquote><p><strong>Expected Income = (Number of New Buyers &#215; LTV) &#8211; Marketing Costs</strong></p></blockquote><p>In this article, we analyzed the first variable &#8212; Number of New Buyers.</p><p>We found out that this is not simply &#8220;buying clicks&#8221; on Facebook. This is a complex chain:</p><ol><li><p><strong>Funnel:</strong> Efficient delivery of the user from advertising to download (preferably via Web2App to save 30%).</p></li><li><p><strong>Setup:</strong> Guiding the user through verification and filling out the profile on the energy created by marketing.</p></li><li><p><strong>Trigger:</strong> Installing the paywall exactly where the user&#8217;s motivation reaches a peak &#8212; whether it is a desire to cut the path (as in Tinder) or get access (as in Seeking).</p></li></ol><p><strong>What&#8217;s Next?</strong> We have already covered <strong>LTV</strong> in Part 1. In the final article of this series, we will tackle the last variable of our equation &#8212; <strong>Marketing Costs</strong>. We will discuss how to lower your CAC (Customer Acquisition Cost), how to test creatives efficiently, and how to scale without burning your budget.</p><p></p><h3><strong>Why Build From Scratch?</strong></h3><p>Setting up <strong>monetization logic</strong>, fighting <strong>SMS fraud</strong>, and optimizing the <strong>onboarding flow</strong> is hard enough without having to code the entire platform yourself.</p><p><strong>This is why we built <a href="https://skadate.com">SkaDate</a>.</strong></p><p>We provide the complete technical engine&#8212;native mobile apps, flexible paywalls, and robust anti-spam tools&#8212;ready from Day 1. Ready to skip the development nightmare?</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://calendly.com/alex-funnelflex/skadate-qa&quot;,&quot;text&quot;:&quot;Discuss Your Project with Me&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://calendly.com/alex-funnelflex/skadate-qa"><span>Discuss Your Project with Me</span></a></p><p>You focus on finding the users; we&#8217;ll make sure the technology keeps them there.</p>]]></content:encoded></item><item><title><![CDATA[The Foundation: The Anatomy of a Dating Product ]]></title><description><![CDATA[Dissecting the ecosystem behind Tinder: From PWA and lifecycle marketing to payments and trust layers.]]></description><link>https://alexsergeev.com/p/the-foundation-the-anatomy-of-a-dating</link><guid isPermaLink="false">https://alexsergeev.com/p/the-foundation-the-anatomy-of-a-dating</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Mon, 15 Dec 2025 22:16:25 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/d4750bce-49ca-413f-8a98-9d4c735fe2e9_1024x565.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I am writing this not as a theorist, but as an operator who has launched dating products from scratch. As a co-founder of Meetville.com, I helped scale the platform to $5M ARR (Annual Recurring Revenue). Later, as Head of Growth at Seeking.com, I drove revenue growth by $20M. I have built dating projects entirely from the ground up and on top of white-label solutions like SkaDate.</p><p>In this article, we are going to dissect a product like Tinder to understand exactly what a modern dating app is made of.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>Imagine Tinder. You&#8217;ve likely used it. Let&#8217;s freeze it in time for a moment. Freeze the product and the traffic&#8212;no new users arriving, no one leaving. Now, let&#8217;s look at it under a microscope to see the infrastructure required to keep it alive.</p><p>We see thousands of users currently active inside the ecosystem. However, we see them accessing the product through different platforms:</p><ul><li><p><strong>Native Mobile Apps:</strong> Android and iPhone apps.</p></li><li><p><strong>Desktop Web:</strong> The browser version on a computer.</p></li><li><p><strong>PWA (Progressive Web App):</strong> The mobile browser experience that behaves like an app.</p></li></ul><p>Let&#8217;s break down why these distinctions matter for a founder.</p><p></p><h3>The Platforms: Native vs. Desktop vs. PWA</h3><p><strong>Native Apps (iOS/Android)</strong></p><p>With native apps, the math is simple: these platforms are much stickier and typically drive <strong>3.5X higher LTV (Lifetime Value)</strong> compared to the mobile web. The primary reason is push notifications. They allow you to activate and retain users effectively&#8212;bringing them back into the app repeatedly. We will discuss the mechanics of this later.</p><p><strong>Desktop Web</strong></p><p>Users open dating sites on desktop when they are in a calmer, more deliberate context: at home, on a laptop, checking email, or clicking a link from a notification. The larger screen fundamentally changes behavior. It facilitates reading profiles, viewing photos in detail, and&#8212;crucially&#8212;typing long-form messages.</p><p>Desktop users swipe less and chat more. This platform isn&#8217;t about rapid discovery; it&#8217;s about deepening interactions. Therefore, a desktop version complements mobile apps by driving up engagement metrics and conversation quality, even if it represents a smaller slice of your total traffic.</p><p><strong>PWA (Progressive Web App)</strong></p><p>A PWA is essentially a website that acts like an app.</p><p>Here is how it works: A user opens your site in a mobile browser (via a link, search, or ad). They register and start using the product. Then, you prompt them to &#8220;Add to Home Screen.&#8221; Once installed, the PWA opens in its own window without the browser interface and, crucially, can receive push notifications.</p><p><strong>The PWA Revolution</strong></p><p>The watershed moment came in 2023 when Apple added support for web push notifications in Safari on iOS. Before this, PWAs were a compromise. Now, they are a legitimate retention channel comparable to native apps. A PWA can live on the user&#8217;s home screen and ping them with &#8220;You have a match&#8221; notifications&#8212;a feature critical for high-frequency apps like dating.</p><p>If you look at the bigger picture, this is part of a platform war. Google has historically bet on the open web, where products reach users directly. Apple acts as a gatekeeper, controlling access via the App Store. Apple&#8217;s support for Safari push notifications wasn&#8217;t altruism; it was a forced move in this competition.</p><p><strong>Why PWA Matters for Niche Founders</strong></p><p>For certain niches, a PWA isn&#8217;t just an alternative&#8212;it&#8217;s the only option. Categories like <strong>Sugar Dating, Adult, or other &#8220;sensitive&#8221; verticals</strong> face constant friction with the App Store and Google Play: rejection during review, inconsistent moderation, and the looming risk of getting de-platformed overnight.</p><p>In these high-risk verticals, a PWA allows you to own your distribution. You exist outside the store ecosystems while retaining a mobile-first experience and the ability to re-engage users via push.</p><p><em>(Note: I will write a separate deep-dive article on the technical implementation of PWAs, including installation prompts and notification logic.)</em></p><p></p><h3>The Traffic: Acquisition vs. Re-engagement</h3><p>Let&#8217;s look at how those users inside our &#8220;frozen&#8221; Tinder got there.</p><p><strong>Acquisition (New Users)</strong></p><p>Some clicked an ad banner on Instagram, downloaded the app, and are currently onboarding. Others searched &#8220;dating apps&#8221; in the App Store&#8212;this is your organic search traffic (ASO).</p><p><strong>Retention (Returning Users)</strong></p><p>But how did the existing users get back into the app right now?</p><ul><li><p>Some received a <strong>transactional push notification</strong>: &#8220;You have a new like&#8221; or &#8220;You have a match.&#8221;</p></li><li><p>Some are replying to an ongoing conversation.</p></li><li><p>Others hadn&#8217;t opened the app in weeks and received a <strong>marketing push</strong> designed to trigger <strong>FOMO</strong> <strong>(Fear Of Missing Out)</strong>, such as:</p><ul><li><p><em>&#8220;Swipe Surge is live. Let others know what you&#8217;re down for. Tap to join now!&#8221;</em></p></li><li><p><em>&#8220;And the award for the most anticipated return to Tinder goes to Alexander.&#8221;</em></p></li><li><p><em>&#8220;We&#8217;ve got new people popping up every day, but it&#8217;s not the same without you...&#8221;</em></p></li></ul></li></ul><p><strong>Email as a Retention Channel</strong></p><p>Email works similarly but serves a different context. The same triggers&#8212;matches, likes, messages&#8212;can be sent via email, specifically targeting users who haven&#8217;t opened the app recently or are desktop-heavy users. Email is often used for &#8220;softer&#8221; re-engagement. It doesn&#8217;t demand immediate attention like a phone vibration, but it gently reminds the user that activity is happening waiting for them.</p><p></p><h3>The Engine: Lifecycle Marketing</h3><p>All notifications in a dating product generally fall into two buckets:</p><ol><li><p><strong>Event-Based (Transactional):</strong> Triggered by a specific product action (a like, a match, a message). Users expect these. They rarely perceive them as spam. These notifications drive the &#8220;Aha-moment&#8221; and facilitate actual dates.</p></li><li><p><strong>Lifecycle (Marketing):</strong> Dependent on the user&#8217;s <em>state</em>, not a specific event. Is the user dormant? Did they stall during registration? Did they stop replying? These are used to resurrect users. They are powerful but dangerous; if you send them too often or without context, you will burn out your audience.</p></li></ol><p>To manage this, you must understand that a user is not static. They move through a <strong>User Lifecycle</strong>:</p><ul><li><p><strong>Onboarding:</strong> Just registered, looking around.</p></li><li><p><strong>Active:</strong> Swiping, chatting daily.</p></li><li><p><strong>Fading:</strong> Hasn&#8217;t opened the app in 3 days.</p></li><li><p><strong>Dormant:</strong> Gone for 30+ days.</p></li></ul><p>A signal that helps a new user (e.g., &#8220;Complete your profile to get 5x more matches&#8221;) is annoying noise to an active user. This is why <strong>Lifecycle Marketing</strong> exists. It determines the right message, channel, and time for every user segment.</p><p><strong>The Tech Stack</strong></p><p>In practice, dating products rely on specific tools to handle this orchestration:</p><ul><li><p><strong>Push Notifications:</strong> <strong>Firebase</strong> or <strong>OneSignal</strong>. They handle the delivery of native, web, and PWA notifications triggered by product events.</p></li><li><p><strong>Transactional Email:</strong> <strong>AWS SES</strong> or <strong>SendGrid</strong>. The priority here is <strong>deliverability</strong>&#8212;ensuring the &#8220;Verify your email&#8221; or &#8220;You have a message&#8221; email actually hits the inbox, not the spam folder.</p></li><li><p><strong>Marketing Email:</strong> <strong>Mailchimp</strong>, <strong>Customer.io</strong>, or <strong>Iterable</strong>. These allow you to build logic chains (e.g., &#8220;If user doesn&#8217;t open app for 7 days -&gt; Send email&#8221;).</p></li><li><p><strong>Orchestration (Enterprise Level):</strong> Mature products use Customer Engagement Platforms like <strong>Braze</strong>, <strong>CleverTap</strong>, or <strong>OneSignal</strong>. These tools unify everything. They allow you to manage push, email, and in-app messages from a single dashboard, segmenting users by behavior without needing constant developer intervention.</p></li></ul><p></p><h3>The Gatekeepers: Moderation and Content Safety</h3><p>Let&#8217;s go back to the user who just finished registration. They can swipe, but we cannot show their profile to others yet. Why? Because they might have uploaded explicit content, hate speech, or solicitation ads in their &#8220;About Me&#8221; section.</p><p><strong>Moderation</strong> is the immune system of any product reliant on User Generated Content (UGC). In dating, UGC includes photos, videos, audio, and free-text bios.</p><p>Historically, we used classic Computer Vision AI to detect nudity in photos (via AWS Rekognition API or other API). Today, thanks to <strong>LLMs (Large Language Models)</strong> like Gemini, ChatGPT, and Claude, we can also automate text moderation with incredible nuance. The machine can now understand <em>intent</em>. It can tell the difference between a romantic poem and a cleverly disguised solicitation for prostitution. Today, content moderation can be almost entirely automated.</p><p></p><h3>The Trust Ladder: Verification</h3><p>Another critical layer is Verification. A &#8220;Verified&#8221; badge is a psychological trigger; it signals safety, which increases the Reply Rate.</p><p>However, verification isn&#8217;t a single feature; it&#8217;s a ladder of friction vs. trust:</p><ol><li><p><strong>Email Verification:</strong> The baseline. Prevents typos, but offers zero protection against scammers. Bots can create thousands of emails instantly.</p></li><li><p><strong>SMS Verification:</strong> Adds cost to the attacker. While disposable numbers exist, they cost money and vary by country. It&#8217;s a barrier, not a wall.</p></li><li><p><strong>Liveness Check:</strong> This is not just asking the user to upload a video, which can easily be faked. It&#8217;s active liveness detection (powered by tools like AWS Rekognition). Here is how it works:</p><ol><li><p><strong>The Challenge:</strong> The user sees a specific prompt on their screen, such as fitting their face into an oval or watching a sequence of flashing colored lights.</p></li><li><p><strong>Real-Time Analysis:</strong> As they react, the AI analyzes the video stream in real-time. It looks for 3D depth and subtle skin reflections that only occur on a live human face.</p></li><li><p><strong>Spoof Detection:</strong> This process instantly detects if someone is holding up a phone with a video playing (a &#8220;replay attack&#8221;), wearing a realistic mask, or using deepfake software.</p></li></ol><p>If the &#8220;live&#8221; person passes this test, we then use Face Matching to confirm they are the same person shown in their static profile photos. </p><p><strong>The best part? It&#8217;s cheap.</strong> The cost of a single liveness check is negligible&#8212;often just pennies. This means we can perform this verification at our own expense. We don&#8217;t need to charge the user or put this behind a paywall;</p></li><li><p><strong>ID Verification:</strong> The user scans a government ID. This is Liveness + Identity Confirmation. It offers high trust but high friction (users are hesitant to share IDs). Often reserved for Premium tiers.</p><p>While market prices for ID verification are dropping, it remains <strong>an order of magnitude more expensive</strong> than a standard Liveness + Face Comparison check. Because of this higher unit cost, you rarely want to run this on every single free user.</p><p>However, it serves a specific purpose that AI cannot fully solve: Age Verification. ID scanning is the <em>only</em> reliable way to validate a user&#8217;s exact age with legal certainty. If your product requires strict age compliance (e.g., ensuring 18+ users), this step is mandatory, regardless of the cost.</p></li><li><p><strong>Background Check:</strong> This involves checking public records for criminal history. Unlike liveness checks (which cost pennies), a background check costs real money&#8212;typically $10&#8211;$30 each. You cannot subsidize this without destroying your unit economics; users usually pay for this themselves before a date.</p><p>Crucially, this is a US-centric feature. In the US, criminal records are public products you can buy via API. In Europe (GDPR), this data is private state property, making commercial background checks legally impossible.</p></li></ol><p><strong>Founder&#8217;s Advice: Don&#8217;t Overbuild Too Early.</strong> Your job is to choose the rung on the ladder that balances safety with growth. But here is a warning: if you are just launching, do not over-engineer this<strong>.</strong> Heavy verification creates friction, and friction kills growth. You need liquidity (users) before you need a fortress.</p><p>Look at Tinder. Even today, with unlimited resources, they do not make email or liveness verification mandatory for new users. They know that every extra step during onboarding drops conversion. Start with low friction to get traction, then tighten the screws as you scale.</p><p></p><h3>The Safety Net: Support</h3><p>Once you are in production, <strong>Customer Support</strong> stops being an option and becomes a system requirement. Users will write in about billing errors, harassment reports, bans, or emotional disputes.</p><p>Do not build this yourself. Use Zendesk or Freshdesk.</p><p>Crucially, do not view Support merely as a &#8220;Cost Center&#8221; (a department that only spends money). In dating, Support is a retention tool. Speed and quality of response define your brand&#8217;s trustworthiness. One mishandled ticket regarding harassment can cost you a user forever&#8212;and potentially trigger a PR crisis.</p><p></p><h3>The Money: Payments Infrastructure</h3><p>Finally, the layer that keeps the lights on.</p><p>Historically, mobile dating apps offloaded this headache to the App Store and Google Play. You paid a &#8220;tax&#8221; (30% commission, or 15% on your first $1M/year), and in exchange, Apple and Google handled the taxes, the refunds, and the fraud.</p><p>The landscape is shifting. In the US, Apple now allows alternative billing systems. This makes third-party processors like Stripe or Adyen attractive.</p><ul><li><p><strong>App Store:</strong> ~30% fee. Handles everything.</p></li><li><p><strong>Stripe:</strong> ~2.9% + $0.30 fee. You handle everything.</p></li></ul><p>The lower fee is tempting, but it comes with Merchant of Record responsibilities. If you use Stripe, <em>you</em> are responsible for refunds, chargebacks (when a user disputes a charge with their bank), and fraud detection. In dating, chargebacks are common&#8212;often due to &#8220;buyer&#8217;s remorse&#8221; or emotional reactions to a bad date. If your chargeback rate gets too high, Visa/Mastercard can blacklist you. Moving off-store saves money, but requires a dedicated team to manage the financial risk.</p><p></p><h3>Conclusion: Don&#8217;t Reinvent the Wheel</h3><p>If there is one takeaway from dissecting the anatomy of a giant like Tinder, it is this: a modern dating product is a complex organism.</p><p>It requires native mobile apps, a PWA for retention, sophisticated lifecycle marketing tools, AI moderation, and a robust payment infrastructure. Building this &#8220;skeleton&#8221; from scratch can take years and hundreds of thousands of dollars.</p><p>This is the trap many founders fall into. They burn their entire budget building the infrastructure&#8212;the login systems, the chat servers, the payment gateways&#8212;and have nothing left for marketing. By the time they launch, they are exhausted and broke.</p><p>This is exactly why we built<strong> <a href="https://skadate.com">SkaDate</a>.</strong></p><p>We have spent years building and refining this anatomy so you don&#8217;t have to.</p><ul><li><p>Need a PWA that supports push notifications on iOS? <strong>We have it.</strong></p></li><li><p>Need native iOS and Android apps? <strong>We have them.</strong></p></li><li><p>Need integrated payment gateways and anti-spam tools? <strong>It&#8217;s already there.</strong></p></li></ul><p>Your job as a founder is to provide the <strong>soul</strong> of the product: the brand, the niche, the marketing, and the community. Let us provide the <strong>body</strong>.</p><p>If you are ready to launch a product that has all these professional layers from Day 1&#8212;without the development nightmare&#8212;let&#8217;s talk<strong>.</strong></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://calendly.com/alex-funnelflex/skadate-qa&quot;,&quot;text&quot;:&quot;Discuss Your Project with Me&quot;,&quot;action&quot;:null,&quot;class&quot;:null}" data-component-name="ButtonCreateButton"><a class="button primary" href="https://calendly.com/alex-funnelflex/skadate-qa"><span>Discuss Your Project with Me</span></a></p><p>You focus on finding the users; we&#8217;ll make sure the technology keeps them there.</p><p></p><p></p>]]></content:encoded></item><item><title><![CDATA[The Unit Economics of Dating Apps (Part 1): How to Grow Your Customer Lifetime Value]]></title><description><![CDATA[The Golden Formula for Scalable Growth.]]></description><link>https://alexsergeev.com/p/the-unit-economics-of-dating-apps</link><guid isPermaLink="false">https://alexsergeev.com/p/the-unit-economics-of-dating-apps</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Fri, 12 Dec 2025 22:12:32 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/dc3895e7-dabc-443c-9efe-5764ac86c33f_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>It is time to dive into the most critical topic for any entrepreneur planning to launch a dating business: <strong>Money.</strong></p><p>It is time to dive into the most critical topic for any entrepreneur planning to launch a dating business. Since many readers of this newsletter are also <strong>Skadate</strong> clients&#8212;who bought our engine and now want to grow their profits&#8212;this article is for you, too.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p>This post will give you a clear formula for growth. It will direct your efforts&#8212;and your hard-earned capital&#8212;toward the specific levers that lead to scalable revenue.</p><p></p><h3>The Golden Formula of the Dating Business</h3><blockquote><p><strong>Expected Income = (Number of New Buyers &#215; LTV) &#8211; Marketing Costs</strong></p></blockquote><p>This formula calculates your expected income per unit of time&#8212;for example, per week. You spend money to acquire users; a percentage of them become buyers; those buyers generate a certain amount of cash over their &#8220;lifetime&#8221; in the app.</p><p>Naturally, we want <strong>Expected Income</strong> to be greater than zero. Otherwise, what is the point of spending more on advertising than you earn?</p><p>Of course, you may have to work &#8220;in the red&#8221; for a while. Uber burned cash for years before generating an operating profit. But if you want to build a scalable business, sooner or later you must reach a positive Expected Income. To scale, you need to increase marketing spend, and how can you increase spend if you have no profit?</p><p>Do not forget: we are talking about <em>dating</em>. The &#8220;virality&#8221; and &#8220;word-of-mouth&#8221; growth that everyone loves doesn&#8217;t work very well here. People rarely brag to their friends about the new dating app they just joined. So, one way or another, you will have to pay for new users. And it is much healthier to pay for them out of profits rather than borrowed funds.</p><p>Sure, there are VC investments, but investors are not fools. They won&#8217;t give money to a business that cannot generate profit. Yes, there are &#8220;Seed&#8221; stage investors when you just have a pile of dreams and maybe no product yet. But you will still have to spend that seed money on turning the startup into a business and getting your <strong>Expected Income</strong> above zero.</p><p>Let&#8217;s look at the formula components closer.</p><p></p><h3>1. Marketing Costs</h3><p>Let&#8217;s take a typical day. You spent <strong>$X</strong> on advertising today&#8212;for example, in Meta Ads (Facebook and Instagram) and Google Ads (Search Ads + Performance Max). As a result, <strong>Y</strong> people clicked on your banner.</p><p>That settles Marketing Costs. In reality, <strong>traffic acquisition is 70% of success</strong>, not 50%, for any dating app. I will dedicate a separate article to this topic later.</p><p></p><h3>2. Number of First Sales</h3><p>Some users will come from the ad to your listing in the App Store/Google Play. Some will download the app, some will finish registration, some will do something important inside (like liking another user or writing a message). And a very small fraction will buy and bring you revenue.</p><p>Essentially, users need to walk a specific &#8220;path of success&#8221; that leads them from registration to purchase. You can imagine this path as a bridge connecting the promises you made to people on the Instagram banner and your actual product, which must fulfill those promises.</p><p>The most important components of this path are <strong>Onboarding</strong> and <strong>Activation</strong>.</p><ul><li><p><strong>Onboarding:</strong> You likely understand this because everyone has flown on a plane. In dating apps, onboarding includes registration, filling out the profile, uploading photos, etc.</p></li><li><p><strong>Activation:</strong> This is a newer concept. It essentially means the user received value from your product for the first time. In the case of a plane, it might be the first successful flight. In the case of Airbnb, the first successful booking.</p></li></ul><p>This topic is critically important because this path leads your users to the purchase.</p><p>The Airline Analogy: In the case of flights, you are unlikely to change your mind about flying after buying the ticket or demand a refund (and as an airline, you basically earned the money the moment you sold the ticket).</p><p>The Dating Reality: In a dating app, users have 1,001 reasons to step off this successful path and never make a purchase.</p><p>And don&#8217;t forget the refund rate. This &#8220;path&#8221; deserves a whole cycle of articles where we will analyze the elements, the metrics we use to measure the stages, and the typical problems that force users to drop out halfway&#8212;or even earlier. Our task is to engineer a path that guides the user from registration to the first purchase, and from the first purchase to the maximum number of repeat purchases. In exchange, we must provide real value and utility to the user.</p><p></p><h3>3. LTV (Lifetime Value)</h3><p>Today, however, we will focus on <strong>LTV</strong>. Let&#8217;s go!</p><p>So, <strong>Y</strong> people clicked, <strong>Z</strong> people downloaded, registered, liked others, and someone got their first match. What happens next depends heavily on your app&#8217;s business model.</p><ul><li><p><strong>Pay-to-communicate:</strong> A requirement to buy a subscription to send an outgoing message.</p></li><li><p><strong>Credits:</strong> Buying packs of credits for specific actions.</p></li><li><p><strong>Freemium:</strong> The model used by all popular apps (Tinder, Hinge, Bumble, etc.).</p></li></ul><p>The essence of the Freemium model is that the most important action&#8212;the ability to communicate with another person&#8212;is free. It&#8217;s true: if you match with someone on Tinder, you can chat for free. But if you are impatient, or a business person who values their time, you will buy a subscription to see <em>who</em> liked you.</p><p><strong>By the way, have you noticed that Tinder doesn&#8217;t immediately show the people who liked you in your card stack?</strong> Do you know why? If not, definitely follow this newsletter&#8212;in the future, I will do a <strong>deconstruction</strong> of popular (and not so popular) dating apps to explain these mechanics.</p><p>Incidentally, apps where you <em>must</em> buy a subscription to start chatting still exist&#8212;for example, <strong>Seeking.com</strong>. And we won&#8217;t overlook the new class of dating apps where people talk to LLM bots, like <strong>EVA AI</strong>.</p><blockquote><p><em>I have analyzed all these Business Models in detail in this article - </em></p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;2d59535a-29fb-4943-a520-af97d57433e7&quot;,&quot;caption&quot;:&quot;I spent some time considering the best starting point for this Substack series. After drafting a few articles, I realized the single most critical topic for anyone planning to launch a dating product is choosing the business model. It&#8217;s the foundation of your entire strategy and, in classic terms, the core of your business plan.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;The Foundation: 5 Core Business Models in Dating&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-11T19:09:39.784Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/5d9f9fcf-045b-4c46-91b5-3da42d0bcb16_1024x572.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/the-foundation-5-core-business-models&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:181353844,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div></blockquote><p>So, a user buys something in your app. Perhaps an impatient user wanted to see who liked them. Another user in a different app wanted to write a message. A third wanted to buy credits to unlock private photos. There is a huge variety of premium features hidden behind a Paywall.</p><p>A joyous event has occurred&#8212;a reward for all your long labor in launching and tuning your dating app: <strong>The user bought.</strong></p><p>Now, a completely new stage in this user&#8217;s life begins. They finally get access to all paid features. By the way, some apps (and this is becoming a trend) are creating multiple subscription tiers: two or even three, like in Tinder (Plus, Gold, Platinum). This helps raise revenue, and we will discuss &#8220;tiers&#8221; in a separate article.</p><p>After the purchase, the user starts using your product to the fullest and extracting the value you built into the subscription.</p><p><strong>The Lifespan Factor</strong></p><p>Don&#8217;t forget that the user came to you with a specific goal. The classic case: a user looks for a partner. Ideally, they will stop using your app as soon as they find one. Therefore, such a user has an average &#8220;lifespan&#8221; in the app. The sum that one such user brings is what we call LTV (Lifetime Value).</p><p>This metric is calculated in dollars. It is one of the most important metrics for <em>any</em> business, online or offline. Imagine the LTV of a car manufacturer whose loyal customers might buy only that brand of car for their entire lives.</p><p>In our case:</p><blockquote><p><strong>LTV = ARPPU (Average Revenue Per Paying User) &#215; Lifespan</strong></p></blockquote><p>This means: how much the user pays us on average per month, multiplied by the number of months until they stop making one-time purchases or cancel their subscription.</p><p><strong>Industry Insight:</strong> In some dating niches, users return to the site to search for partners multiple times&#8212;or let&#8217;s say, much more often than in &#8220;Vanilla dating&#8221; (standard romance apps). This is common on sites like <strong>Seeking.com</strong> (the sugar daddy industry).</p><p>The conclusion is simple: the longer a user remains a paying user, the more you earn. Simple.</p><p></p><h3>4. Why Users Leave (The LTV Killers)</h3><p>It would be great if all users canceled subscriptions only <em>after</em> finding partners. The harsh truth is that there is a huge pile of <em>other</em> reasons why people stop paying you much earlier. We will analyze these reasons in the future, but here are a few examples.</p><p><strong>The Cold Start Problem</strong></p><p>You just launched your dating site, and you have very few users. A subscriber might quickly view all available users in a week and that&#8217;s it&#8212;there is no point in remaining on the site. They cancel.</p><p>Of course, you know where this problem comes from. Any dating app is essentially a marketplace with two sides: Demand and Supply. At launch, the sharpest problem is always the &#8220;Cold Start.&#8221;</p><blockquote><p><em>I wrote a detailed guide on how to solve the Cold Start Problem here - </em></p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;61c3218c-e07e-4a8e-ac41-2b96bf2a7ff0&quot;,&quot;caption&quot;:&quot;It is 2025. Match.com launched nearly thirty years ago. Tinder has been around for over a decade. The market is saturated with massive brands, and the natural first thought for any new founder is usually:&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;The Foundation: How to Find and Validate a Dating Niche&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-12T19:19:35.284Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/952a7be8-a919-42bd-a337-e4c64a001e01_1024x559.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/the-foundation-how-to-find-and-validate&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:181446264,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div></blockquote><p><strong>Scammers</strong></p><p>Another reason why users either don&#8217;t buy at all or cancel immediately is scammers. There are many varieties of scammers in dating (I will write a separate article about them). But today, what matters is that they try to move communication off your site to an external platform (Telegram or WhatsApp) as quickly as possible.</p><ul><li><p><strong>The nuance:</strong> Scammers usually register as women.</p></li><li><p><strong>The behavior:</strong> They usually write the first message.</p></li></ul><p>All of this causes strong suspicion in most users, but unfortunately, some fall for it and become victims.</p><p>How does this affect LTV? Simple. People don&#8217;t trust a site where they meet scammers. They buy less. Also, a user might buy a subscription just to read a message from a girl, only to find out she is a scammer.</p><p><strong>Guess what the user thinks?</strong> I&#8217;ll tell you a secret: users often think the <em>site owners</em> specifically created these profiles to force them to buy subscriptions. However, the harsh truth is that these scammers register themselves. Young sites that haven&#8217;t implemented protection tools like <strong>Photo</strong> or <strong>Liveness verification</strong> are especially vulnerable. I will definitely write a separate article on how to build such protection with minimal resources.</p><p></p><h3>5. Refunds, Chargebacks, and VAMP</h3><p>It is one thing if a user simply cancels. But some people demand a Refund.</p><p>The worst part isn&#8217;t that you lose the revenue&#8212;it&#8217;s that your app can be removed from the App Store. Apple automatically tracks the refund rate for your app, and if it goes over the limits, your app can simply be deleted.</p><p>Then there are payment gateways, which you connect to accept payments bypassing the App Store/Google Play (to lower the commission from 30% to 3-5% via a web app). Here we are talking about Chargeback Rate.</p><p>A chargeback is essentially when your user demands money back through their bank, not directly from you. If you have too many returns and your chargeback rate exceeds the limits, you can be banned from accepting card payments entirely.</p><p><strong>The VAMP Warning</strong></p><p>For example, Visa has a special monitoring program&#8212;VAMP (Visa Acquirer Monitoring Program)&#8212;which sets these limits.</p><ul><li><p>From <strong>June 1, 2025</strong>, Visa began counting both chargebacks and fraud transactions in a single indicator, setting a new risk threshold of <strong>2.2%</strong>.</p></li><li><p>From <strong>April 2026</strong>, they are lowering it to <strong>1.5%</strong>.</p></li></ul><p>Because of this, it is now much easier for dating site owners to fall into the &#8220;risk zone,&#8221; even if their chargebacks are within the normal range. I will write separately about VAMP and the upcoming limit changes in the future.</p><p><strong>Did you know?</strong> Apple recently allowed developers in the US to accept credit cards directly inside apps. You can look at how this is implemented in Tinder, Hinge, and Bumble.</p><p></p><h3>Conclusion</h3><p>We have now dissected the <strong>LTV</strong> component of our core formula. We know how to calculate it, why it matters, and what kills it&#8212;from scammers and the &#8220;Cold Start&#8221; problem to technical threats like chargebacks.</p><p>But a high LTV is meaningless if you have zero users entering the funnel.</p><p>In the next article, we will tackle the second critical variable: <strong>Number of New Buyers</strong>. We will break down the exact path a user takes to become a customer&#8212;starting from your App Store or Google Play listing, moving through the onboarding process, and finally reaching that crucial first purchase.</p><div class="digest-post-embed" data-attrs="{&quot;nodeId&quot;:&quot;47e4e529-07f4-4161-b831-42c2fd97513e&quot;,&quot;caption&quot;:&quot;Let&#8217;s continue studying the core formula of the dating business.&quot;,&quot;cta&quot;:&quot;Read full story&quot;,&quot;showBylines&quot;:true,&quot;showDescription&quot;:true,&quot;showImage&quot;:true,&quot;size&quot;:&quot;sm&quot;,&quot;isEditorNode&quot;:true,&quot;title&quot;:&quot;The Unit Economics of Dating Apps (Part 2)&quot;,&quot;publishedBylines&quot;:[{&quot;id&quot;:6964152,&quot;name&quot;:&quot;@alexsergeev&quot;,&quot;bio&quot;:&quot;Currently doing growth at Blazr.app, a 420-friendly dating app, and leading SkaDate.com, a white-label dating platform. Previously led growth at Seeking.com and DilMil.co. Built Meetville.com and Hygger.io.&quot;,&quot;photo_url&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/6066b180-d60d-485c-a65c-bbc1831b0b78_800x800.png&quot;,&quot;is_guest&quot;:false,&quot;bestseller_tier&quot;:null}],&quot;post_date&quot;:&quot;2025-12-16T04:13:25.538Z&quot;,&quot;cover_image&quot;:&quot;https://substack-post-media.s3.amazonaws.com/public/images/bd1484d2-fcef-412b-8dcb-d1329c3a8ddd_1024x863.jpeg&quot;,&quot;cover_image_alt&quot;:null,&quot;cover_image_crop&quot;:null,&quot;canonical_url&quot;:&quot;https://alexsergeev.com/p/the-unit-economics-of-dating-apps-a01&quot;,&quot;section_name&quot;:null,&quot;video_upload_id&quot;:null,&quot;id&quot;:181752542,&quot;type&quot;:&quot;newsletter&quot;,&quot;reaction_count&quot;:0,&quot;comment_count&quot;:0,&quot;publication_id&quot;:7221428,&quot;publication_name&quot;:&quot;Alex Sergeev&quot;,&quot;publication_logo_url&quot;:&quot;&quot;,&quot;belowTheFold&quot;:true,&quot;youtube_url&quot;:null,&quot;show_links&quot;:null,&quot;feed_url&quot;:null}"></div><p></p><h3>Why Build From Scratch?</h3><p>Maximizing LTV and fighting scammers is hard enough without having to code the entire platform yourself.</p><p><strong>This is why we built <a href="https://skadate.com">Skadate</a>.</strong></p><p>We provide the complete technical engine&#8212;native apps, payments, and monetization&#8212;ready from Day 1. Ready to skip the development nightmare?</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://calendly.com/alex-funnelflex/skadate-qa&quot;,&quot;text&quot;:&quot;Discuss Your Project with Me&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://calendly.com/alex-funnelflex/skadate-qa"><span>Discuss Your Project with Me</span></a></p><p>You focus on finding the users; we&#8217;ll make sure the technology keeps them there.</p>]]></content:encoded></item><item><title><![CDATA[The Foundation: Solving the Cold Start Problem in Dating]]></title><description><![CDATA[Why ads won't save your new app&#8212;and how to build a network from zero.]]></description><link>https://alexsergeev.com/p/the-foundation-solving-the-cold-start</link><guid isPermaLink="false">https://alexsergeev.com/p/the-foundation-solving-the-cold-start</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Fri, 12 Dec 2025 21:32:42 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/0954e898-ca70-4ffb-aee2-1fcde1066515_1024x559.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>Today, we are looking at the single biggest hurdle for any new dating business: <strong>The Cold Start Problem.</strong></p><p>If you have ever built a standard business&#8212;an agency, a SaaS tool, a blog, or a YouTube channel&#8212;you know the typical playbook: start small, buy some Facebook ads, drive traffic, make a sale, get feedback, improve the product, and repeat. It&#8217;s a linear path.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p><strong>In the dating industry, this logic does not work.</strong></p><p>Dating isn&#8217;t just a software product; it is a network connecting people. Until that network exists, the product has zero value. A single user in a dating app gets nothing out of it. Even a hundred users might feel zero value if they are different ages, live in different neighborhoods, or log in at different times.</p><p>This is why every new dating project faces the same enemy: The Cold Start Problem&#8212;the challenge of igniting a network from absolute zero.</p><p></p><h2>Understanding Network Effects (It&#8217;s Not Just Buzzwords)</h2><p>Most founders have heard the phrase &#8220;network effects,&#8221; but few understand that in dating, this isn&#8217;t just a &#8220;nice to have.&#8221; It is the fundamental physics determining whether your startup lives or dies.</p><p><strong>A Network Effect</strong> occurs when a product becomes more valuable to every user as the number of other users increases.</p><ul><li><p><strong>WhatsApp:</strong> If all your friends are there, it&#8217;s essential. If no one is there, it&#8217;s a useless utility.</p></li><li><p><strong>Uber:</strong> More drivers mean faster pickups; more passengers mean higher earnings for drivers. It&#8217;s a flywheel.</p></li><li><p><strong>Airbnb:</strong> More listings mean better choices for guests; more guests mean better occupancy for hosts.</p></li></ul><h3>The &#8220;Double Coincidence of Wants&#8221; in Dating</h3><p>However, dating network effects are significantly harder to achieve than Uber or WhatsApp. In dating, &#8220;more users&#8221; does not automatically equal &#8220;better product.&#8221;</p><p>Value in a dating app only appears when there are specific people who meet a rigorous set of criteria:</p><ol><li><p><strong>Correct Demographics:</strong> The right gender and age preference.</p></li><li><p><strong>Hyper-Local:</strong> They must be in the same specific city or neighborhood.</p></li><li><p><strong>Active:</strong> They must be online recently (ghost profiles kill retention).</p></li><li><p><strong>Mutual Interest:</strong> Crucially&#8212;and this is unique to dating&#8212;<strong>they must also like you back.</strong></p></li></ol><p>Therefore, the dating network effect isn&#8217;t just about <em>volume</em>. It&#8217;s about <strong>Liquidity</strong>&#8212;having enough of the <em>right</em> people active at the <em>same time</em> to create matches.</p><p></p><h2>The &#8220;Just Buy Traffic&#8221; Trap: The Brutal Math</h2><p>I see this constantly at SkaDate. A founder says: <em>&#8220;I&#8217;ll just buy traffic on Facebook, Instagram, or TikTok. We&#8217;ll quickly gather a user base in one city, then expand to the next.&#8221;</em></p><p>It sounds logical until you run the unit economics. Let&#8217;s look at the real numbers for a new dating app launching in the US today.</p><ul><li><p><strong>CPI (Cost Per Install):</strong> ~$4 (up to $8 for niche apps). This is standard for a new app on Meta/Google/TikTok with no brand recognition and no organic lift.</p></li><li><p><strong>Conversion to Subscriber:</strong> ~5%. For new projects, it&#8217;s often lower because the database is small (&#8221;ghost town&#8221; effect), and you likely haven&#8217;t hired a Head of Growth or optimized your lifecycle marketing (emails, pushes) yet.</p></li></ul><h3>The Unit Economics Nightmare</h3><p>Let&#8217;s do the math on your <strong>CAC (Customer Acquisition Cost)</strong>:</p><p>$4&nbsp;(CPI)&#247;0.05&nbsp;(Conversion)=$80</p><p>It costs you <strong>$80</strong> to acquire one paying subscriber via paid ads.</p><p>Now, consider <strong>LTV (Lifetime Value)</strong>. The average subscriber retention in dating is often just <strong>one month</strong>. Why? Because users subscribe, look around, realize the database is small/low quality, get very few matches, and churn immediately.</p><p>If your CAC is $80, you need to charge <strong>$80/month</strong> just to break even.</p><p><strong>The Market Reality:</strong></p><ul><li><p>The average dating subscription is <strong>$20&#8211;$40</strong>.</p></li><li><p>Charging $80 for a brand-new app with no trust is impossible.</p></li><li><p>Even the giants (Tinder, Bumble) charge less because they survive on <strong>scale</strong>, not high margins per user.</p></li></ul><h3>The Verdict on Performance Marketing</h3><p><strong>Performance marketing cannot solve the Cold Start Problem.</strong></p><p>The economy doesn&#8217;t balance. You need a high price to cover ad costs, but you can&#8217;t charge a high price without a high-quality user base, which you don&#8217;t have yet.</p><blockquote><p><strong>Field Note:</strong> Paid ads work <em>after</em> the network is alive&#8212;when organic K-factor kicks in, retention stabilizes, and users are getting matches. Using ads to <em>start</em> the fire is like trying to boil the ocean with a matchstick.</p></blockquote><p></p><h2>Case Study: How Tinder Actually Solved the Cold Start</h2><p>When people talk about Tinder&#8217;s explosion, they usually credit the &#8220;Swipe&#8221; UI.</p><p>Let&#8217;s be clear: The Swipe was a product innovation, not a marketing one. Product alone does not acquire users.</p><p>(Side note: The swipe was vital because it reduced rejection anxiety. Unlike Match.com or POF where you cold-messaged people, the Swipe forced a &#8220;Double Opt-In,&#8221; ensuring that when you messaged someone, you already knew they were interested. That raised reply rates dramatically.)</p><p>But the <strong>marketing breakthrough</strong>&#8212;the way they solved the Cold Start Problem&#8212;was purely offline.</p><h3>The Campus Strategy</h3><p>Tinder didn&#8217;t try to launch &#8220;in the USA.&#8221; They launched <strong>campus by campus</strong>. Universities are the perfect petri dish for dating networks:</p><ul><li><p>High density of young people.</p></li><li><p>High social activity.</p></li><li><p>Shared context (same school, same age).</p></li></ul><p>Tinder realized they didn&#8217;t need to build a new network from scratch; they simply needed to <strong>digitize a network that already existed offline.</strong></p><h3>The &#8220;Gating&#8221; Tactic</h3><p>Tinder didn&#8217;t recruit users one by one. They recruited <strong>clusters</strong>.</p><ol><li><p>They threw parties at USC and other campuses.</p></li><li><p><strong>The Price of Admission:</strong> You had to show the bouncer that you had Tinder downloaded on your phone.</p></li><li><p>Hundreds of students downloaded it simultaneously at the door.</p></li><li><p>When they opened the app inside the party, they saw the faces of the people standing right next to them.</p></li></ol><p>This created instant <strong>density</strong>. Users got matches in the first 10 minutes. The product felt &#8220;alive&#8221; immediately. This is something Facebook Ads can never replicate.</p><h3>Solving the Gender Balance (The Sorority Hack)</h3><p>Every dating app founder fears the &#8220;Sausage Fest&#8221; scenario: 80% men, 20% women.</p><p>Tinder solved this by leveraging the social hierarchy of Greek Life:</p><ol><li><p>They pitched to <strong>Sororities</strong> (female houses) first. They got the key influencers and socialites on the app.</p></li><li><p>Then, they went to the <strong>Fraternities</strong> (male houses).</p></li><li><p>The pitch to the guys was easy: <em>&#8220;All the cute girls from the sororities are already on this app.&#8221;</em></p></li></ol><p>The guys downloaded it en masse. Because the supply (women) was already there, the demand (men) was satisfied, and the ecosystem flourished.</p><p>Tinder conquered one campus, creating a functional mini-network. Then they moved to the next. Eventually, as students visited friends at other colleges, the &#8220;atomic networks&#8221; began to merge, and organic growth took over.</p><p></p><h2>Actionable Advice for Founders</h2><p>If you are launching a dating business today, accept the reality: <strong>You cannot afford to scale with paid ads on Day 1.</strong></p><p>Your Cost Per Subscription will be too high, your conversion too low, and your churn too fast.</p><p><strong>The Solution:</strong></p><p>Stop looking at Facebook Ads Manager. Start looking at Communities.</p><p>You need to replicate the Tinder model of digitizing an existing offline network where trust and connections already exist.</p><p><strong>Where to find your first 1,000 users:</strong></p><ul><li><p><strong>Offline Events:</strong> Parties, mixers, speed dating.</p></li><li><p><strong>Micro-Communities:</strong> Coworking spaces, local running clubs, language schools.</p></li><li><p><strong>Niche Interests:</strong> Conventions, hobby groups, local subreddits.</p></li></ul><p>You need to acquire users in <strong>batches</strong>, not individuals, to ensure that when they open the app, they see people they might actually want to date.</p><h3>What&#8217;s Next?</h3><p>In the next article, I will break down a case study of a dating project that launched in <strong>January 2024</strong> and solved the Cold Start Problem using a completely different channel: <strong>YouTube.</strong></p><p>Stay tuned.</p><h3></h3><h3>Why Build From Scratch?</h3><p>As you just read, solving the <strong>Cold Start Problem</strong> is the hardest battle in the dating industry. It requires 100% of your focus on marketing and community. You cannot win this battle if you are distracted by product development or managing servers.</p><p><strong>That is our territory.</strong></p><p><strong>This is exactly why we built <a href="http://skadate.com/">SkaDate</a>.</strong></p><p>We are the product experts. We provide you with a battle-tested technical engine&#8212;native apps, payments, and monetization&#8212;perfected over years of development.</p><p>You focus on igniting the network; we&#8217;ll provide the professional infrastructure to support it.</p><p>Ready to launch with a pro-level product?</p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://calendly.com/alex-funnelflex/skadate-qa&quot;,&quot;text&quot;:&quot;Discuss Your Project with Me&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://calendly.com/alex-funnelflex/skadate-qa"><span>Discuss Your Project with Me</span></a></p><p>You focus on finding the users; we&#8217;ll make sure the technology keeps them there.</p>]]></content:encoded></item><item><title><![CDATA[The Foundation: How to Find and Validate a Dating Niche]]></title><description><![CDATA[...and stop wasting budget on "Tinder clones" by using a 6-step framework to verify demand and unit economics first.]]></description><link>https://alexsergeev.com/p/the-foundation-how-to-find-and-validate</link><guid isPermaLink="false">https://alexsergeev.com/p/the-foundation-how-to-find-and-validate</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Fri, 12 Dec 2025 19:19:35 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/952a7be8-a919-42bd-a337-e4c64a001e01_1024x559.jpeg" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>It is 2025. Match.com launched nearly thirty years ago. Tinder has been around for over a decade. The market is saturated with massive brands, and the natural first thought for any new founder is usually:</p><p><em>&#8220;What is the point of launching a dating app now? There is already a site for every possible niche.&#8221;</em></p><p>I hear this constantly. It is healthy skepticism, but it is based on a false assumption: that the market is frozen in time. In reality, online dating is one of the most dynamic markets in the digital world. Society changes, relationship norms shift, and new identities emerge. As life scenarios evolve, they create vacuums for new niches and formats.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><p>Here is why new niches are still opening up&#8212;and how to validate them before you burn cash on development.</p><p></p><h2>Why New Niches Keep Appearing</h2><p>In recent years, the landscape of modern relationships has shifted dramatically. Entire groups of people who previously weren&#8217;t visible&#8212;or weren&#8217;t ready to be open about their preferences&#8212;are now looking for specific platforms.</p><p>We are seeing traction in:</p><ul><li><p><strong>Gender identity:</strong> Trans and gender-diverse users who often feel unsafe on mainstream apps.</p></li><li><p><strong>Relationship structures:</strong> Polyamory, Ethical Non-Monogamy (ENM), and open relationships.</p></li><li><p><strong>Lifestyle choices:</strong> Specific dynamics like &#8220;trad wife&#8221; or &#8220;stay-at-home girlfriend&#8221; scenarios.</p></li><li><p><strong>Diaspora communities:</strong> South Asians in the US/UK (what we targeted with <strong>Dil Mil</strong>), Russian speakers in Europe, etc.</p></li><li><p><strong>Hyper-specific interests:</strong> Pickleball is taking over the world right now&#8212;dating apps centered around courts and matches are popping up fast.</p></li></ul><p>But the most significant shift isn&#8217;t demographic&#8212;it&#8217;s technological.</p><h3>The New Frontier: Generative AI</h3><p>We have already seen the rise of&nbsp;<strong>AI Companions</strong>&nbsp;(such as&nbsp;<strong>Replika</strong>&nbsp;and <strong>EVA AI</strong>). These products address loneliness by providing an AI partner available 24/7. While they solve the &#8220;Cold Start&#8221; problem (the AI is always there), they often struggle with long-term retention once the novelty wears off.</p><p>However, the technology is now evolving from <em>companionship</em> to <em>efficiency</em>.</p><p><strong>The Next Wave: AI Agents &amp; RAG (Ditto.ai)</strong></p><p>A new wave of startups, like Ditto.ai, uses Generative AI not to be your date, but to find one for you.</p><p>This relies on a tech stack called RAG (Retrieval-Augmented Generation). Unlike a standard chatbot that just makes things up, RAG gives the AI a &#8220;memory file&#8221; of your specific data.</p><p>Apps like Ditto use this to learn your voice, your schedule, and your specific taste, and then go out and talk to other people&#8217;s AI agents for you. They simulate the &#8220;talking stage&#8221;&#8212;scheduling the date and vetting the match&#8212;so you don&#8217;t have to swipe or chat. You just get a calendar invite.</p><p>This is a massive blue ocean. It solves &#8220;Dating App Fatigue&#8221; by removing the manual labor entirely.</p><p></p><h2>Part 1: How to Analyze an Existing Niche (The Operator&#8217;s Framework)</h2><p>You don&#8217;t need me to list every possible niche for you. You can ask Gemini or ChatGPT, <em>&#8220;What are the current segments in online dating?&#8221;</em> and get a list in seconds.</p><p>The real value I can offer you&#8212;based on my time scaling <strong>Seeking</strong>, <strong>Dil Mil</strong>, and advising founders at <strong>SkaDate</strong>&#8212;is a method to <em>validate</em> those ideas.</p><p>Before you write a line of code or hire a designer, use this 6-step framework to see if the economics actually make sense.</p><p></p><h3>Step 1. Keyword Analysis: What are people actually typing?</h3><p>Surveys lie. Google search bars don&#8217;t. We need to look at two things:</p><ol><li><p><strong>Volume:</strong> How many people are searching for this per month?</p></li><li><p><strong>Keyword Difficulty (KD):</strong> How hard is it to rank for these words?</p></li></ol><p>I use <strong>Google Ads Keyword Planner</strong> to gauge the raw size of the interest.</p><blockquote><p>Resource: Back in 2021, we conducted a massive analysis of 1,855 dating niche keywords. It&#8217;s a map of how users formulate their desires. You can view the raw volume data here:</p><p>&#128073; <a href="https://docs.google.com/spreadsheets/d/1i24sbpnx11yQ9C2R5dFDKdPWYvlRheQcX1-VZ_InAkE/">Dating Niche Keywords Spreadsheet</a></p></blockquote><p></p><h3>Step 2. SEO Competition: Ubersuggest vs. Ahrefs</h3><p>When checking competitors, you need the right tool.</p><ul><li><p><strong>For a quick glance: <a href="https://neilpatel.com/ubersuggest/">Ubersuggest</a>.</strong> It helps answer the simple question: <em>&#8220;Is there any movement here at all?&#8221;</em></p></li><li><p><strong>For a deep dive: <a href="https://ahrefs.com/">Ahrefs</a>.</strong> This is the gold standard because Ahrefs has its own &#8220;crawler&#8221;&#8212;a bot that scans the entire internet just like Google does.</p></li></ul><p><strong>&#9888;&#65039; The &#8220;Global Trap&#8221; (Liquidity Warning)</strong></p><p>Be careful with the numbers. If you see 10,000 searches for &#8220;Knitting Dating,&#8221; that sounds great. But if those searches are spread evenly across the world, you have a problem. Validate the niche locally first, or choose a &#8220;Virtual-Only&#8221; niche.</p><p></p><h3>Step 3. The Money Check: SensorTower</h3><p>A website might look popular, but is it making money?</p><p>For mobile apps, <a href="https://sensortower.com/">SensorTower</a> is my go-to. It models revenue by country and platform.</p><p><strong>Understanding the Metrics:</strong></p><ul><li><p><strong>Downloads:</strong> How many new people install the app.</p></li><li><p><strong>Revenue:</strong> How much money the app makes <em>through the app store</em>.</p></li><li><p><strong>ARPU (Average Revenue Per User):</strong> This is critical. It tells you how much a single user is worth to the business.</p></li></ul><p>Operator&#8217;s Tip: From my experience, SensorTower&#8217;s revenue estimates are often conservative. I usually multiply their revenue number by x2 to get closer to the real picture.</p><p>Why? SensorTower only sees transactions that go through the App Store or Google Play. It misses Stripe/Web payments, which smart founders use to avoid the 30% commission Apple and Google charge.</p><p></p><h3>Step 4. Web Traffic: SimilarWeb</h3><p>Don&#8217;t ignore the web. Even mobile-first products often have significant web traffic for SEO and acquisition. <strong><a href="http://similarweb.com">SimilarWeb</a></strong> will show you:</p><ul><li><p><strong>Traffic Sources:</strong> Are they buying users (Display Ads) or getting them for free (Direct/SEO)?</p></li><li><p><strong>Stability:</strong> If traffic has been steady for years, the niche is healthy.</p></li></ul><p></p><h3>Step 5. Trend Spotting: Google Trends</h3><p>Before falling in love with your idea, check the timeline on <strong><a href="https://trends.google.com/trends/">Google Trends</a></strong>.</p><ul><li><p>Is interest in &#8220;polyamory&#8221; rising or plateauing?</p></li><li><p>Is the &#8220;trad wife&#8221; discourse spiking or dying out?</p></li></ul><p>You want to enter a market where the curve is pointing up or holding a high plateau.</p><p>Recommendation: Subscribe to Global Dating Insights. It&#8217;s the daily digest I read to see where the industry money is moving.</p><p></p><h3>Step 6. Ad Intelligence: Are the Unit Economics Working?</h3><p>This is the most critical step. If competitors are spending money on ads, it is a very good sign. It means their <strong>Unit Economics</strong> are working.</p><p>The &#8220;Niche Pricing&#8221; Rule:</p><p>In a small niche, you cannot charge $5/month. You won&#8217;t have the volume of users to support the business. Successful niche apps usually have a High LTV (Lifetime Value) model&#8212;charging $30, $40, or even $50/month.</p><p>How to spy on competitor ads (Step-by-Step):</p><p>We use the Facebook Ads Library to see exactly how competitors are selling.</p><ol><li><p><strong>Go to:</strong> <a href="https://www.facebook.com/ads/library">Facebook Ads Library</a></p></li><li><p><strong>Select Country:</strong> Choose a specific country (e.g., USA) or &#8220;All&#8221;.</p></li><li><p><strong>Search:</strong> Type the brand or app name (e.g., &#8220;Bumble&#8221;, &#8220;Hinge&#8221;, &#8220;Muzmatch&#8221;, &#8220;Dil Mil&#8221;).</p></li><li><p><strong>Analyze:</strong> Facebook will show you all active campaigns.</p></li></ol><p><em>Look for longevity:</em> If an ad has been running for 3+ months, it means it is profitable. The LTV is covering the ad costs.</p><p></p><h2>Part 2: The Innovator&#8217;s Path (Validating &#8220;Blue Oceans&#8221;)</h2><p>The 6-step framework above is perfect for existing demand (e.g., &#8220;Christian Dating&#8221;). But what if you are building something completely new, like <strong>Ditto.ai</strong>?</p><p>If you type &#8220;AI agent to date for me&#8221; into Google, the volume will be zero. People don&#8217;t search for products they don&#8217;t know exist yet. In this case, standard SEO tools are useless.</p><p>You must validate in two phases: <strong>Qualitative</strong> (talking) and <strong>Quantitative</strong> (testing).</p><p></p><h3>Phase 1: The &#8220;Therapist&#8221; Interviews (Qualitative)</h3><p>Before you spend a dollar on ads, you need to verify the <em>pain point</em>. Find 10-20 singles who are currently using Tinder/Bumble and interview them.</p><ul><li><p><strong>Don&#8217;t ask:</strong> &#8220;Would you use an AI agent?&#8221; (They will politely say yes).</p></li><li><p><strong>Do ask:</strong> &#8220;Tell me about your last month on dating apps.&#8221; &#8220;How do you feel when you open the app?&#8221; &#8220;How much time do you spend swiping vs. actually going on dates?&#8221;</p></li></ul><p>You are looking for <strong>&#8220;Swipe Fatigue&#8221;</strong> and <strong>&#8220;Burnout.&#8221;</strong> If their stories are full of frustration, exhaustion, and &#8220;dating feels like a second job,&#8221; you have found your problem. Innovation solves <em>pain</em>, not just features.</p><p></p><h3>Phase 2: The Smoke Test (Quantitative)</h3><p>Once you have confirmed the pain in interviews, prove it with data.</p><ul><li><p><strong>The Setup:</strong> Spend <strong>$200</strong> on Facebook/TikTok ads targeting that exact pain point (e.g., &#8220;Stop Swiping forever&#8221;).</p></li><li><p><strong>The Destination:</strong> Send them to a simple landing page explaining your new concept.</p></li><li><p><strong>The Metric:</strong> Measure the <strong>Click-Through Rate (CTR)</strong> and <strong>Email Signups</strong>.</p></li></ul><p>If people are clicking and giving you their email for a product that doesn&#8217;t exist yet, that is your validation.</p><p></p><h2>Reality Check: Before You Launch</h2><p>Even if the numbers look good, there are two operational hurdles you must consider in 2025.</p><p><strong>1. Apple is the Gatekeeper</strong></p><p>While Google Play is relatively open, Apple has become extremely strict. They have a specific rule (Guideline 4.3) regarding &#8220;Spam&#8221; and template apps.</p><p>If you build a generic clone that just swaps the logo and color scheme, Apple will likely reject it. Your niche product needs unique functionality or a very distinct UI to pass review.</p><p><strong>2. The Cold Start Problem</strong></p><p>Validating demand is one thing; getting users to actually stay is another.</p><p>If the first 1,000 users sign up but find nobody to talk to, they will leave immediately. It&#8217;s not just about acquisition; it&#8217;s about liquidity&#8212;ensuring that when a user logs in, they see active profiles and get a response.</p><p>I will dedicate a full separate article to solving the &#8220;Cold Start Problem,&#8221; as it deserves its own deep dive.</p><h2>Summary &amp; Next Steps</h2><p>The market isn&#8217;t dead; it&#8217;s just fragmented. To succeed, follow the framework:</p><ul><li><p><strong>Identify a shift</strong> in culture (AI, legal changes, new identities).</p></li><li><p><strong>Verify density</strong> (or use the &#8220;Smoke Test&#8221; method for innovative ideas).</p></li><li><p><strong>Verify money</strong> via SensorTower (remember the x2 rule).</p></li></ul><p><strong>What now?</strong></p><p>The classic mistake is spending $50k and six months coding an MVP just to test these hypotheses. Your goal is to test the market, not your ability to write code.</p><p><strong>This is exactly why we built <a href="https://skadate.com">SkaDate</a>.</strong></p><p>We provide a flexible, launch-ready engine that allows you to enter your niche immediately. Instead of burning your budget on development, you can use it to acquire users and validate your idea.</p><p></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://calendly.com/alex-funnelflex/skadate-qa&quot;,&quot;text&quot;:&quot;Discuss Your Project with Me&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://calendly.com/alex-funnelflex/skadate-qa"><span>Discuss Your Project with Me</span></a></p><p>You focus on capturing the market; we&#8217;ll provide the technology to power it.</p><p><strong>Ready to launch your niche MVP?</strong></p>]]></content:encoded></item><item><title><![CDATA[The Foundation: 5 Core Business Models in Dating]]></title><description><![CDATA[A practical guide to choosing the right monetization strategy for your dating app.]]></description><link>https://alexsergeev.com/p/the-foundation-5-core-business-models</link><guid isPermaLink="false">https://alexsergeev.com/p/the-foundation-5-core-business-models</guid><dc:creator><![CDATA[@alexsergeev]]></dc:creator><pubDate>Thu, 11 Dec 2025 19:09:39 GMT</pubDate><enclosure url="https://substack-post-media.s3.amazonaws.com/public/images/261a97c1-6721-4239-8f8d-e5dd001b171f_1536x1024.png" length="0" type="image/jpeg"/><content:encoded><![CDATA[<p>I spent some time considering the best starting point for this Substack series. After drafting a few articles, I realized the single most critical topic for anyone planning to launch a dating product is choosing the <strong>business model</strong>. It&#8217;s the foundation of your entire strategy and, in classic terms, the core of your business plan.</p><div class="subscription-widget-wrap-editor" data-attrs="{&quot;url&quot;:&quot;https://alexsergeev.com/subscribe?&quot;,&quot;text&quot;:&quot;Subscribe&quot;,&quot;language&quot;:&quot;en&quot;}" data-component-name="SubscribeWidgetToDOM"><div class="subscription-widget show-subscribe"><div class="preamble"><p class="cta-caption">Alex Sergeev is a reader-supported publication. To receive new posts and support my work, consider becoming a free or paid subscriber.</p></div><form class="subscription-widget-subscribe"><input type="email" class="email-input" name="email" placeholder="Type your email&#8230;" tabindex="-1"><input type="submit" class="button primary" value="Subscribe"><div class="fake-input-wrapper"><div class="fake-input"></div><div class="fake-button"></div></div></form></div></div><p></p><h2><strong>What is a Business Model?</strong></h2><p>Simply put, a business model is <em>the way your product makes money</em>. It answers two very straightforward questions:</p><ol><li><p>How do we deliver value to our users?</p></li><li><p>What do those users pay us for?</p></li></ol><p>In the dating industry, the choice of business model dictates everything:</p><ul><li><p>What users can do for <strong>free</strong> inside the app.</p></li><li><p>What they must <strong>pay</strong> for, and the size of your future revenue.</p></li><li><p>The level of <strong>trust</strong> users will have in the platform.</p></li><li><p>The <strong>speed</strong> at which you can launch the product.</p></li><li><p>The business&#8217;s <strong>risks</strong> and its long-term stability.</p></li><li><p>Your <strong>operating costs</strong> and even your company&#8217;s <strong>reputation</strong>.</p></li></ul><p>It even determines whether you can get into the App Store at all. Getting approved by Apple is much harder now; since 2018, they consider the dating category extremely saturated and vet new apps with heavy scrutiny. (I&#8217;ll cover this in a separate post.)</p><p>Today, let&#8217;s break down the <strong>5 primary business models</strong> in modern online dating. Each has its own pros, cons, risks, and ideal use case.</p><p></p><h2><strong>1. The Freemium Model (Tinder, Bumble, Hinge)</strong></h2><p>This model allows 100% of users to use the core product for free. The most critical action in any dating app (after finding someone you like) is exchanging messages to arrange a date and move the interaction offline (IRL).</p><p>In Tinder, if you like someone and they like you back, you have a <strong>Match</strong>, and you can chat for free forever. Liking and matching&#8212;the core value proposition&#8212;is always free for everyone.</p><p>These applications make money on <strong>boosters</strong> and <strong>premium features</strong> that make the online dating process more effective or efficient. The most profitable feature is usually the ability to see <strong>who has already liked you</strong>.</p><p>The apps deliberately hide the faces of people who have liked you. They also don&#8217;t show those profiles at the top of your deck by default. This is strategic: it encourages you to swipe on new profiles, which generates more likes for others, making <em>them</em> want to see who liked them. Imagine the efficiency if you immediately saw your matches and could skip straight to the chat. It saves time but drastically reduces the number of total likes you might send out, which reduces overall engagement. This feature would be especially helpful for women, who typically receive significantly more likes from men.</p><p>Another common booster is <strong>unlimited likes</strong>. Limiting a user to, say, 10 likes per day reduces the number of likes in the system but increases user engagement (they must return daily) and forces more thoughtful profile selection. I&#8217;ll dedicate an entire article to the typical boosters used across the industry.</p><p>The main advantage of the Freemium model is that your active user base grows organically: 100% of users can get real value completely for free.</p><p><strong>Advantages</strong></p><ul><li><p>Ability for organic growth and virality</p></li><li><p>Maximum user trust</p></li><li><p>Minimal risk of Apple/Google blocks</p></li><li><p>Good chance to build a recognizable brand</p><p></p></li></ul><p><strong>Disadvantages</strong></p><ul><li><p>Dependency on the network effect: no users = no value</p></li><li><p>Requires large marketing budgets to scale initially</p></li><li><p>LTV is lower than in more aggressive models</p><p></p></li></ul><h2><strong>2. Subscription for Access to Messaging (Seeking, eHarmony)</strong></h2><p>In this model, the user must buy a subscription to be able to send messages to others. Years ago, Match.com used this, requiring <em>both</em> parties to have an active subscription. Post-Tinder, user expectations changed dramatically, and Match Group eventually removed paid subscriptions from Match.com.</p><h3><strong>Case Study: Seeking.com (Niche Access)</strong></h3><p><strong>Seeking.com</strong> is the leader in the Sugar Daddy niche (which they pioneered in 2006). In their model, the <strong>Sugar Daddies pay</strong>, and the <strong>Sugar Babies use the site for free</strong>.</p><p>Seeking is essentially selling <strong>access to a specific audience</strong>, not just the ability to chat. Users <em>could</em> look for partners on regular (&#8221;vanilla&#8221;) dating apps, but the efficiency would be much lower because they&#8217;d need to first establish their intentions. On Seeking, everyone shares the same dating intention, eliminating the need for the &#8220;are you looking for sugar?&#8221; vetting phase.</p><p>The paywall on Seeking also acts as a <strong>filter and a marker of seriousness</strong>. Not everyone is willing to spend, for example, $375 for a Diamond 30-Day subscription. The pricing is part of the positioning.</p><p>Furthermore, the swiping mechanic itself would be <strong>redundant</strong> on Seeking because, generally speaking, Sugar Babies are open to communicating with most Sugar Daddies and reply readily. Moreover, it is standard practice in this niche for Sugar Babies to message first.</p><p>This behavior contrasts sharply with the mass market. <strong>Bumble</strong> made a strong USP out of a similar idea&#8212;after a match, only the woman could send the first message&#8212;and used it to differentiate its brand from Tinder. This was a powerful move. However, they later abandoned this rule and allowed men to message first. Why? In Western culture, the expectation that the man makes the first move still dominates, and for many women, initiating contact is socially uncomfortable. Consequently, a significant portion of matches on Bumble &#8220;stalled&#8221; without a conversation starting, which <strong>worsened the product&#8217;s economics</strong> (by reducing conversion from match to chat) and eventually led to the abandonment of the rule.</p><blockquote><p><em>I will write a separate deep-dive on the economics of this sugar daddy/sigar baby niche after my time at Seeking.</em></p></blockquote><h3><strong>Case Study: eHarmony (Quality &amp; Intent Filter)</strong></h3><p><strong>eHarmony</strong> is the philosophical opposite of Tinder. The company bets on deep psychological compatibility and long-term relationships. Most people come to eHarmony with serious intent&#8212;to find a spouse.</p><p>The service is based on its own scientifically developed compatibility model, assessing values, communication style, empathy, and stability. After taking a detailed test, the system selects pairs with the highest probability of a successful union. Swiping mechanics are unnecessary here; users don&#8217;t browse hundreds of profiles&#8212;they receive a concierge list of pre-vetted matches.</p><p>In this context, the paywall is not a barrier; it&#8217;s a <strong>filter against non-serious users, spammers, casual chat, and &#8220;just trying it out&#8221; users.</strong></p><p>A crucial insight: This model not only improves the quality of the user base but also strengthens the product itself. When people pay for a serious service, they behave more responsibly and are more invested in the dating process. This creates a completely different atmosphere&#8212;less chaos, fewer random contacts, and more respectful, conscious communication. This is why eHarmony has one of the highest marriage rates in the industry; the product is optimized for <strong>results</strong>, not just <strong>engagement</strong>. (I&#8217;ll touch on the dopamine loops of Tinder in another post.)</p><p><strong>Advantages</strong></p><ul><li><p>High LTV and stable subscription revenue</p></li><li><p>Paywall filters non-serious users and improves user base quality</p></li><li><p>More respectful, conscious communication atmosphere</p></li></ul><p><strong>Disadvantages</strong></p><ul><li><p>High barrier to entry: a portion of users leave before paying</p></li><li><p>Requires strong, niche positioning to justify the cost</p></li><li><p>Lower virality: subscription reduces organic spread</p><p></p></li></ul><h3><strong>3. Credits and Pay-Per-Message (iDates, Dating.com)</strong></h3><p>In this model, users purchase <strong>virtual credits</strong> that are then deducted for sending messages. The chat is not just a communication tool; it becomes the primary revenue stream around which the entire product economy is built.</p><p>In more aggressive implementations, a portion of the female accounts may be supported by chat agents who are paid to stimulate male users to continue the conversation&#8212;and thus buy more credits.</p><p>A notable example of this model&#8217;s philosophy comes from <strong>iDates</strong>, which states clearly in its footer: <em>&#8220;All chat partners are virtual profiles moderated by exciting real people. Real meetings with them are not possible.&#8221;</em> The service openly informs the user that real dates are off the table; the conversation <em>is</em> the product.</p><p>Why does this model work?</p><p>It&#8217;s a misconception that only older users fall for this. Many paying customers know about Tinder but dislike the swipe model: the high competition, low response rate, and emotional uncertainty. In credit models, they receive instant attention, a guaranteed response, and an emotional feeling of involvement&#8212;things often missing in freemium dating. They pay, not out of ignorance, but because these services fulfill their emotional needs faster and easier.</p><p>Psychologically, this model thrives on the <strong>&#8220;small cost&#8221; effect</strong>: each action is inexpensive on its own, and the user doesn&#8217;t immediately grasp the total expenditure, which is what drives very high monetization. One active male user can generate tens or even hundreds of dollars in an evening. These &#8220;whales&#8221; form a disproportionately large part of the total revenue, resulting in an <strong>extremely high LTV</strong> rarely achievable in other models.</p><p>However, high revenue comes with severe downsides. Many users realize too late how much they&#8217;ve spent, feel deceived, and initiate chargebacks. This creates constant tension with payment processors, increases the risk of platform blocking, and requires a heavy operational infrastructure: extensive moderation, anti-fraud measures, operator control, and legal protection. The reputation quickly deteriorates, forcing many companies to change domains and brand names to escape the negative publicity.</p><p><strong>Advantages</strong></p><ul><li><p>Very high LTV and revenue per active user</p><p></p></li></ul><p><strong>Disadvantages</strong></p><ul><li><p>Low user trust, high risk of chargebacks and complaints</p></li><li><p>Poor reputation: low ratings, negative reviews, need to change domains</p></li><li><p>High operational complexity: agents, anti-fraud, legal risks</p></li></ul><p></p><h3><strong>4. AI Partner Dating (Replika, EVA AI)</strong></h3><p>This is the newest, fastest-growing business model, sitting at the intersection of dating, loneliness, and generative AI. In traditional dating, we connect real people; in AI dating, the product <em>is</em> the conversational partner.</p><p>You can easily find these apps in the stores using queries like &#8220;AI girlfriend&#8221; or &#8220;AI friend.</p><p>Though apps like <strong>Replika</strong> or <strong>EVA AI</strong> don&#8217;t always position themselves as dating apps, they compete directly with the industry by offering users a sense of attention, validation, stability, and emotional intimacy. And yes, a major part of the monetization is built around users satisfying their fantasies, which is now supported by LLMs generating high-quality photos and videos upon request.</p><p><strong>Why the recent explosion?</strong></p><ul><li><p><strong>The Rise of Loneliness:</strong> In AI dating, the bot is available 24/7, answers instantly, is always attentive and polite, and never &#8220;ghosts.&#8221; You don&#8217;t compete with hundreds of other users.</p></li><li><p><strong>Zero Fear of Rejection:</strong> It&#8217;s emotionally easier for people to communicate when there&#8217;s no risk of being rejected, mocked, or simply uninteresting.</p></li><li><p><strong>Personalization Effect:</strong> The model adapts to the user&#8217;s personality, remembers details, and reinforces the illusion of &#8220;chemistry,&#8221; creating a feeling of a real relationship.</p></li></ul><p><strong>Monetization is based on &#8220;payment for emotional intimacy&#8221;:</strong></p><ul><li><p>Generating intimate photos and videos on demand.</p></li><li><p>Purchasing a &#8220;premium&#8221; personality (more romantic, caring, or playful versions of the AI).</p></li></ul><p>These apps show high engagement in the first few days but often bore users quickly because the interaction remains predictable and simulated. Users experiment briefly, lose interest, and rarely pay long-term, resulting in low retention and low LTV. Ultimately, it&#8217;s more of an emotional &#8220;casual product&#8221; than a sustainable dating business.</p><p><strong>Advantages</strong></p><ul><li><p>No Cold Start Problem: The AI is always available, no need for a user base.</p></li><li><p>Low operational risk: No moderation of live users, fewer complaints, minimal chargebacks.</p></li><li><p>Scalability: A single AI partner can &#8220;manage&#8221; millions of dialogues.</p></li></ul><p><strong>Disadvantages</strong></p><ul><li><p>High competition (easy to launch because there is no Cold Start problem here)</p></li><li><p>App Store Limitations: Apple and Google strictly regulate 18+ content.</p></li><li><p>Ethical Risks: Addiction, emotional attachment, and regulatory complexity.</p></li></ul><p></p><h2><strong>5. White-Label Dating with Shared Database (HubPeople.ai)</strong></h2><p>This model involves launching your dating site on a single technical platform that shares a common user database. A partner creates a simple landing page and drives traffic to it. Everything else&#8212;the product, the matching, the database&#8212;is handled by the platform. You receive a percentage of all payments made by your users (e.g., 70% to you, 30% to the platform).</p><p>This setup promises fast launch, no need for your own user base (no cold start problem), and seems convenient for partners.</p><p><strong>The Fundamental Flaw:</strong> You own neither the users nor the code nor the product. All user data, all profiles, all messages&#8212;they belong to the platform, not you.</p><p>A key example is <strong>WhiteLabelDating.com</strong>, once a major player. It operated on this model for many years but eventually closed, and thousands of partners lost their sites and the entire business they had built. Because the database was not theirs and the code/infrastructure was platform-controlled, people were simply left with nothing.</p><p><strong>As CEO of SkaDate</strong>, I always advise that white-label is only suitable as a <strong>temporary experiment</strong> to test a niche. It should never be viewed as a strategic product. The WhiteLabelDating history is a stark lesson: without owning the user base and the code, you are not building a business&#8212;you are merely renting it. And the lease can end, leaving you empty-handed.</p><p><strong>Advantages</strong></p><ul><li><p>Fastest launch without development costs</p></li><li><p>No cold start problem (users are immediately available)</p></li></ul><p><strong>Disadvantages</strong></p><ul><li><p>You do not own the database; you lose all users if the platform closes.</p></li><li><p>Impossible to create a unique product: all sites share the same database and mechanics.</p></li><li><p>No code, no infrastructure, no ability to migrate&#8212;your project vanishes with the platform.</p></li></ul><h2><strong>Conclusion: Your Model is Your Foundation</strong></h2><p>In dating, the business model is the foundation that dictates everything: growth rate, user trust, launch complexity, monetization, and even your chance of passing App Store moderation.</p><ul><li><p><strong>Freemium</strong> suits those ready to build a massive product with a long-term horizon and invest heavily in the network effect.</p></li><li><p>The <strong>Subscription for Access</strong> model only works when the audience&#8217;s value is demonstrably higher than average (like on Seeking or eHarmony), and users understand exactly what they are paying for: access to a specific type of person and a higher quality, more serious dating experience.</p></li><li><p><strong>Credit models</strong> offer the highest revenue but come with major reputational risks and severe operational complexity.</p></li><li><p><strong>AI Dating</strong> is an emotional toy that users burn out on quickly, not a sustainable business.</p></li><li><p><strong>White-label platforms</strong> are great for niche testing, but do not create a real product&#8212;without owning the database and code, you are merely renting your business.</p></li></ul><p>The correct business model isn&#8217;t just a way to make money. It is a strategic decision that determines whether your product can grow, retain users, pass moderation, and generate stable profit. Choose your model not by potential earnings, but by the <strong>unique value you are creating</strong>, who it is for, and how truly unique that value proposition is.</p><p></p><h3>Why Build From Scratch?</h3><p>Choosing the right business model is critical, but coding it is a nightmare. Different models require completely different technical architectures&#8212;credit systems, subscription tiers, paywalls, or AI integrations.</p><p><strong>This is exactly why we built <a href="https://skadate.com">SkaDate</a>.</strong></p><p>We don&#8217;t force you into a box. Our engine is flexible enough to power <strong>any</strong> of these models. Whether you need a Freemium Tinder-clone, a high-end Subscription site like Seeking, or a Credit-based niche app, we have the features ready to go.</p><p></p><p class="button-wrapper" data-attrs="{&quot;url&quot;:&quot;https://calendly.com/alex-funnelflex/skadate-qa&quot;,&quot;text&quot;:&quot;Discuss Your Project with Me&quot;,&quot;action&quot;:null,&quot;class&quot;:&quot;button-wrapper&quot;}" data-component-name="ButtonCreateButton"><a class="button primary button-wrapper" href="https://calendly.com/alex-funnelflex/skadate-qa"><span>Discuss Your Project with Me</span></a></p><p>You choose the strategy; we provide the engine to execute it.</p><p></p>]]></content:encoded></item></channel></rss>