One window for the six jobs

Talk to Ranla in one window about all six jobs.

Each job has its own desk and its own conversation with Ranla. Ask for the email, the ad budget change, the page, the Reddit reply, or the pull request, and the work opens beside the thread where you can edit it. The dashboard is still there when you want it. Sends still wait on your rules. Spend changes and merges wait for you.

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 desk. Every job has one, with its own conversation.

The window

What you can ask for in the window.

One thread covers all six jobs. You do not have to click around the product to get the work done.

Events

Open the events pull request

Ask which product events are missing. It writes them in your repo and opens a pull request. You review and merge.

Templates

Write and publish templates

Ask for a welcome, a trial-ending note, a receipt. It drafts in the thread and publishes when you say so.

Campaigns

Build and schedule campaigns

Audience, angle, holdout. It drafts the campaign in the same window and sends in the mode you set.

Automations

Turn winners into automations

Promote a campaign into an always-on automation, or ask it to build the flow from scratch.

Audiences

Segment without a CSV

Describe who should get the send. It builds the segment from product events. The same segment syncs to Google Ads as a matched audience.

Paid

Propose a Google Ads change

Ask what the spend is doing. It drafts ads and proposes budget, audience, and keyword changes. Spend changes after you approve.

Search and AEO

Draft a page

Ask which questions deserve a page. It ranks them from Search Console and drafts the page. You edit it and publish it.

Social

Draft a Reddit reply

Ask what buyers are asking on Reddit. It finds the thread, scores it, and drafts the reply. You post it from your own account.

Daily scan

Every morning, Ranla scans the six jobs and makes a call on each.

Shipped features, stalled cohorts, missing events, spend that is not earning, threads worth answering, overlaps with automations you already run. Each row gets a call: draft, propose, narrow, hold, decline, or ask you.

This morning, 6:00 AMran automatically
What the scan foundRanla's call
53,000 people signed up and never activated. None of them have ever been emailed.
Wrote the campaign and set a ramp of 400 a day, most engaged first. An audience this size always waits for your approval before it sends.
Drafted
Signup is in the product events. Activation is not.
Opened a pull request that tracks activation where setup completes. It waits for your review. Nothing goes to your default branch.
Pull request
Three user-visible changes shipped since the last product update
12,400 people use the parts that changed, but only 4,000 sends are left under this week’s cap. Going to the best 4,000 now, the rest follow next week, rather than holding the whole thing.
Narrowed
One Google Ads keyword keeps spending with no activation behind it
Proposed pausing the keyword and moving its $40 a day to the activation campaign. Spend changes wait for your approval.
Proposed
Variant B is ready to scale
It earned 2.4× variant A over 900 sends. The remaining 6,700 people are over the 5,000 line, so the rollout waits for your yes.
Needs you
Buyers search how to finish signup. ChatGPT and Perplexity do not cite you on it.
Ranked the question from Search Console and drafted the page from how people use the product. You edit it and publish it.
Drafted
Onboarding drop-off at day three
An automation already covers the onboarding stage. If it is underperforming, the fix is to change that automation, not to stack a one-off campaign on top of it.
Declined
A founder thread on Reddit asks how people get past signup without a discount
Scored the thread and drafted a reply in your voice, with the safety checks passed. You post it from your own Reddit account, and Ranla follows how it does.
Drafted
Re-engagement push to everyone quiet for 60 days
“Launch week recap” reached most of this audience four days ago. Holding a week so nobody hears from us twice.
Held
The plan

Ranla plans the week across the six jobs.

Sends, a pull request, a budget change, a page draft, and a Reddit reply on one calendar. You set how much it can do without asking. Anything past that limit waits for your yes.

What an AI growth operator owns →

This weekAutopilot · approve sends over 2,000
  • Mon
    Monday briefScheduled

    Decisions from last week, proposals waiting, one intake question

  • Mon
    Pull request: track activationNeeds you

    Open in your repo · waits for your review

  • Tue
    Activation campaignSending

    Ramp day 3 of 5 · 400 sends today

  • Tue
    Google Ads budget changeNeeds you

    Move $40/day to the activation campaign · waits before spend

  • Wed
    Welcome automation auditNeeds you

    Copy still describes onboarding from six months ago

  • Wed
    Page draft: why teams switchNeeds you

    Search and AEO · you edit and publish

  • Thu
    Product update emailScheduled

    Shipped checkout redesign · narrowed to 4,000 under weekly cap

  • Thu
    Reddit reply: founder threadNeeds you

    Drafted in your voice · posts from your account after you approve

  • Fri
    Performance reviewScheduled

    Holdout results for finish-setup campaign · AI answer check for the new page

Slack

Ranla sits in Slack like a teammate.

DM it, @mention it in a channel, or use /ranla. Brief it, approve a send, see what it is doing. Open the app when you want the canvas. Slack does not replace the dashboard.

Connect Slack →

Talk where the team already is

DM Ranla, @mention it in a channel, or run /ranla. It is the same conversation as the product window.

Brief, approve, keep going

Tell it what to do next. Approve a send, snooze a week, or reject, without leaving Slack.

Open the app for the canvas

The dashboard is still there when you want the full picture. Slack is how the team talks to it day to day.

Replies

Replies land in the same window.

Replies inbox →

Install

Ranla installs into your app with a pull request.

Connect a GitHub repo. Ranla scans the codebase, adds the product events and conversion tracking the other jobs need, and opens a pull request. You review and merge. It does not push to your default branch.

01

Sync the repo

Connect GitHub and pick the repository. That is the only setup step on your side before the scan.

02

Scan the codebase

Ranla reads how you sign people up, what you already track, and where the gaps are.

03

Add the events

It writes the moments the other jobs need, signup, activation, and billing, using the conventions already in the repo.

04

Open a pull request

You get a PR. Merge it when it looks right. Ranla does not push to your default branch. Pull requests work on Free and use credits.

The growth jobs and the code they need, in one window. Marketing and engineering do not need two tools for that.

Keep wiring

Ranla finds the events you are missing, then writes them.

Missing activation? A trial-ending moment with nothing behind it? Ranla recommends events from the product. With the repo connected, it writes those events and opens a pull request. Campaigns and code changes from the same place.

Analytics connect (PostHog, Amplitude, Mixpanel) is still there if you would rather not change the repo.

Try a public repo →

Modes

Draft, Propose, or Autopilot, inside the limits you set.

Frequency caps, daily send limits, and complaint caps are enforced in the send path. Any audience over 5,000 people waits for your approval in every mode. Ranla can tighten its own limits. Only you can loosen them. Same rules in Slack, in the app, and over MCP.

MCP

MCP and agent clients.

Ranla is the AI growth engineer. Add it to Cursor, Claude, Grok, or any MCP client and brief it on any of its six jobs.

Add Ranla to your agents →

Questions

Agent window questions

What is the Ranla agent window?

The in-product conversation where you brief Ranla on any of its six jobs: templates, campaigns, automations, audiences, a Google Ads change, a page draft, a Reddit reply, or a pull request. The work opens beside the thread. You approve in the app or Slack when your mode asks.

Can Ranla instrument our codebase?

Yes. Connect GitHub. Ranla scans the repo, recommends events, writes them, and opens a pull request. You review and merge. It does not push to your default branch. Pull requests work on Free and use credits.

Does Ranla work in Slack?

Yes. DM it, @mention it, or use /ranla. Brief it, approve a send, see progress. The canvas stays in the app when you want the full picture.