Platform

The platform the AI growth engineer runs.

Ranla is the AI growth engineer. It does six jobs: engineering, lifecycle email, paid advertising, search, AEO, and social. Under them sit automations, audiences, conversion goals, analytics with holdouts, transactional email, a replies inbox, on-site messages, a creative studio, a brand kit, the agent window, MCP, Slack, and integrations. All of it works from product events: signup, activation, and billing.

Six jobs.

Each job has its own page here, its own desk in the app, and its own conversation with Ranla.

Under the jobs

What sits under the six jobs.

Automations

Build automations that react to what people do

One-off campaigns prove what works against a holdout. Winners become always-on automations. Email and SMS through your Twilio account in the same flow.

Automations →
Agent window

One window for the six jobs

Talk to Ranla about the email, the ad budget change, the page, the Reddit reply, or the pull request. The work opens beside the thread. Slack works the same way.

Agent window →
MCP

Add Ranla to Cursor, Claude, or Grok

The hosted MCP server puts Ranla on the agent team you already run. The agents talk to each other. Drafts and memory stay here.

MCP and agent clients →
Audiences

Audiences from real product behavior

Segments update from events. Connect PostHog, Amplitude, or Mixpanel, or merge a GitHub pull request. The same segment syncs to Google Ads as a matched audience.

Audiences →
Conversions

Goals every job aims at

Name activation, paid conversion, or a key action. The primary goal is what campaigns, automations, ads, and pages aim at.

Conversions →
Analytics

Measure lift against people who got nothing

Email campaigns can hold out a slice and measure lift on the goal you named. Not opens.

Analytics →
Revenue

Revenue and conversions by job

Stripe for LTV, Google Ads for CAC, and the conversion goals you named. It reports. It does not send or spend.

Revenue →
Replies

When they write back, Ranla answers

One inbox. It classifies intent, drafts in your voice, and sends only above a confidence threshold. Refunds, churn, and legal always escalate.

Replies →
Transactional

Password resets and receipts on the same stack

One API, official SDKs, and one suppression list shared with lifecycle email. Free includes 3,000 sends a month.

Transactional email →
On-site

Reach visitors before they have an email

Collect email on the banner, or use a link CTA. Optional After submit URL for a thank-you page or download. Same snippet as conversions.

On-site →
Events

Product events, live and in flight

What your product already sends, and the pull requests that add what is missing. This is the engineering job.

Events →
Creative

Images for campaigns and ads

Composed from your brand kit into one library that lifecycle email and paid advertising share.

Creative →
Brand

Your brand kit

Style, voice, profile, and product, seeded from your website. Every draft in every job reads it first.

Brand →
Integrations

What Ranla connects to

GitHub or analytics first. Then Stripe, Google Ads, Search Console, Reddit, Twilio, and Slack.

Integrations →
In the product

What the app looks like.

Morning scan
Updated just now
Found this morning
Read your product· signup, activation, subscription
Previewed segment· 52,917 people
Removed· 4,112 unsubscribed / bounced / recent
Checked sending health· clear to send
Drafted campaign· 3 angles · 1 recommended
Planned the ramp· 400/day · most engaged first
These people signed up and never activated, so a newsletter won't move them. The one email only you can send names the exact setup step they abandoned and removes it, not a discount, and not a feature roundup.I'd start with the 2,000 most recent, 400 a day, and hold the rest until we see what it earns. Want me to send you a test first?
Approval needed
Schedule “Finish their setup”

2,000 most recent · 400/day · 15% holdout. Nothing sends until you approve.

AdjustApprove & schedule
Reply to Ranla…
Campaign draft
Finish their setupGuiltDiscount
FromMaya at Acme <[email protected]>
ToNever activated · 48,805 people
the setup step you got stuck on, already done

Hey. You signed up for Acme back in March and never finished setting up. That's usually our fault, not yours.

So I did the step you stopped at. Your workspace is ready and there is nothing left to configure.

If it's useful, you can pick up where you left off today.

Send testApprove & schedule

The lifecycle email job in the app. Each of the six jobs has a desk like this, with its own conversation. Talk in that window, or in Slack next to your team. Agent window → · MCP and agent clients →

Automations

Campaigns that win become always-on. Email and SMS via your Twilio account.

Audiences

Segments from product events, not a CSV you keep refreshing.

Analytics

Measure lift against people who got nothing, not opens.

Questions

Platform questions

What is the Ranla platform?

Ranla is the AI growth engineer. Six jobs: engineering, lifecycle email, paid advertising, search, AEO, and social. Under them sit automations, audiences, conversion goals, analytics with holdouts, transactional email, a replies inbox, on-site messages, a creative studio, a brand kit, the agent window, MCP, Slack, and integrations. You choose Draft, Propose, or Autopilot.

Is the agent window a separate product?

No. Ranla is the AI growth engineer, and the window is where you talk to it about all six jobs: templates, campaigns, automations, audiences, a Google Ads change, a page draft, a Reddit reply, or a pull request. Sends still wait on your rules.

Where do I start?

Start free at app.ranla.ai. Connect GitHub or analytics so signup, activation, and billing flow in, then let Ranla draft in all six jobs. Or read the page for each job: Events, Lifecycle email, Paid advertising, Search and AEO, and Social.