Cross-sell & upsell
Ranla is the AI growth engineer. It reads product and billing events, so it sees when someone hits a plan limit, adopts a power feature, or pays but never invites the team. It drafts the expansion message for that moment and measures upgrades against people who got nothing. The same events drive its six jobs: engineering, lifecycle email, paid advertising, search, AEO, and social.
Campaigns and automations from signup, activation, and billing events.
Product events and conversion tracking as a pull request you review.
Tracks whether ChatGPT, Perplexity, and Google AI Overviews cite you.
Adds the events behind an upgrade: plan limit reached, power feature used, teammate invited, from your billing events.
Product events →Drafts the upgrade email for the moment someone hits a limit, measured against a holdout on paid conversion.
Lifecycle email →Syncs your best-fit accounts to Google Ads as a matched audience for an upgrade campaign, created paused.
Paid advertising →Drafts pages that answer what buyers search before they upgrade: pricing, limits, comparisons. You edit and publish them.
Search →Checks whether AI answer engines describe your paid plans correctly, and drafts the corrections.
Search and AEO →Near a plan limit, used feature X but not Y, paid but never invited a teammate. Segments come from events you already track, or from events Ranla adds to your repo as a pull request.
Expansion campaigns can hold out a slice of the segment. Lift is read on paid conversion and revenue from your billing events, not on opens.
Start in Draft. Move to Propose when you want to approve each send in the app or Slack. Hand it Autopilot with caps when you are busy. Audiences over 5,000 always need approval.
Events · Conversions · Automations · Audiences · Analytics · Transactional · Paid advertising · Search & AEO · Social · MCP · Docs · All solutions · Pricing
Questions
Ranla is the AI growth engineer. It reads product and billing events, so it sees when someone hits a plan limit, adopts a power feature, or pays but never invites the team. It drafts the expansion message for that moment and measures upgrades against people who got nothing. The same events drive its six jobs: engineering, lifecycle email, paid advertising, search, AEO, and social.
Segments from usage and plan limits. Near a plan limit, used feature X but not Y, paid but never invited a teammate. Segments come from events you already track, or from events Ranla adds to your repo as a pull request.
Ranla does six jobs on one platform: engineering, lifecycle email, paid advertising, search, AEO, and social. Transactional email runs on the same sending stack. SMS uses your Twilio account; Google bills ad spend to you.