One window for the 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.
2,000 most recent · 400/day · 15% holdout. Nothing sends until you approve.
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.
The lifecycle email desk. Every job has one, with its own conversation.
One thread covers all six jobs. You do not have to click around the product to get the work done.
Ask which product events are missing. It writes them in your repo and opens a pull request. You review and merge.
Ask for a welcome, a trial-ending note, a receipt. It drafts in the thread and publishes when you say so.
Audience, angle, holdout. It drafts the campaign in the same window and sends in the mode you set.
Promote a campaign into an always-on automation, or ask it to build the flow from scratch.
Describe who should get the send. It builds the segment from product events. The same segment syncs to Google Ads as a matched audience.
Ask what the spend is doing. It drafts ads and proposes budget, audience, and keyword changes. Spend changes after you approve.
Ask which questions deserve a page. It ranks them from Search Console and drafts the page. You edit it and publish it.
Ask what buyers are asking on Reddit. It finds the thread, scores it, and drafts the reply. You post it from your own account.
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.
| What the scan found | Ranla'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 |
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.
Decisions from last week, proposals waiting, one intake question
Open in your repo · waits for your review
Ramp day 3 of 5 · 400 sends today
Move $40/day to the activation campaign · waits before spend
Copy still describes onboarding from six months ago
Search and AEO · you edit and publish
Shipped checkout redesign · narrowed to 4,000 under weekly cap
Drafted in your voice · posts from your account after you approve
Holdout results for finish-setup campaign · AI answer check for the new page
Scale variant B to the rest of the cohort?
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.
DM Ranla, @mention it in a channel, or run /ranla. It is the same conversation as the product window.
Tell it what to do next. Approve a send, snooze a week, or reject, without leaving Slack.
The dashboard is still there when you want the full picture. Slack is how the team talks to it day to day.
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.
Connect GitHub and pick the repository. That is the only setup step on your side before the scan.
Ranla reads how you sign people up, what you already track, and where the gaps are.
It writes the moments the other jobs need, signup, activation, and billing, using the conventions already in the repo.
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.
signed_upWiredactivatedWiredinvited_teammateRecommendtrial_endingRecommendOpens a PR when the repo is connected
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.
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.
Same agent that drafts and asks. Your other agents talk with it. Send rules still hold.
https://mcp.ranla.ai/mcpRanla is the AI growth engineer. Add it to Cursor, Claude, Grok, or any MCP client and brief it on any of its six jobs.
Questions
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.
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.
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.