ProgrammableMarketing/ramain.ai (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

  • The brief
  • Start here
  • Idea portfolio
  • Effort vs impact
  • This week · 6
  • This quarter · 10
  • Big bets · 4
  • Wildcards · 2
  • How we can help
Generated Nov 10, 2026 1 view
  1. Programmable
  2. Playbooks
  3. Ramain
Ramain logo

growth playbook · Nov 10, 2026

ramain.ai (opens in a new tab)

Ramain growth playbook

Diagnosis

Ramain (YC W26, a team of 7 in San Francisco) has more to sell than its website shows: a published $1,500-a-month self-serve plan, a developer API and MCP server, 60 connectors, top scores on four public browser-agent benchmarks and eight customer stories with hard numbers ($2.5 billion of loans locked a year, 1,500 pharma contracts a month).

But the pages buyers land on (the homepage, the seven industry pages and the customer stories) still carry an older menu that never links to pricing, developers or connectors, and the sitemap leaves those pages out. Industry pages don't link to their own proof, stories lack quotes and time-to-live, and the "Partner with us" line has no partner page even though the best story is a BPO reselling Ramain's work.

This playbook fixes the paths to pricing and proof first, then adds a fixed-price first workflow, a BPO partner programme, connector pages and signal-based outbound for the new GTM engineer, and finally bets on outcome pricing for mortgage locks and a packaged eligibility worker for healthcare.

Growth Score

6/10

Biggest Opportunity

Turn what already exists (a self-serve plan, developer tools, 60 connectors, strong benchmarks and a BPO that resells the work) into visible, linked paths, and make BPO partners a second sales channel.

Biggest Risk

Browser-agent platforms with free starts (Skyvern, Browser Use) and incumbent automation suites (UiPath and other RPA vendors now selling agents) compete for the same budgets, and a team of 7 can be stretched thin by enterprise builds.

01

Start here

The three moves to make first. Each one is written up in full below.

  1. 1

    Put Pricing, Developers and Connectors in the menu on every page, and in the sitemap, so the $1,500 self-serve plan can be found

    Replace the homepage header with the menu already used on /pricing/.

    High impact First result in 2 weeks
  2. 2

    A fixed-price first workflow, so buyers see their own process run before committing to $1,500 a month

    Write a one-page offer: scope, price, two-week timeline and what the buyer receives.

    High impact First result in 1 month
  3. 3

    Link every industry page to its own customer story and research, starting with mortgage and healthcare

    Add the lock-desk story to the mortgage page.

    Medium impact First result in 2 weeks

02

Your idea portfolio

22 ideas, grouped by when to run them. Open any idea for how to run it: the steps, who to approach, copy you can use, and how to measure it.

  • 7 ideas are marked Unexpected: plays you are unlikely to have tried.

    1 of these are things Programmable can build and run for you.

Every idea placed by the effort it takes against the impact it could have. Quick wins sit top left; select a number to open that idea. The filters below narrow the list by status, timing, category and what Programmable can build.

Effort vs impactEach number is an idea. Select one to open it.
Impact →
Quick wins · 3Big bets · 8Fill-ins · 8Reconsider · 3
Effort →

Showing 22 of 22 ideas

This week 6

Quick wins with a clear first action.

  • 01

    Ramain has published a self-serve Platform plan at $1,500 a month with a "Start building" button, a Developers page with an API and MCP server, and a list of 60 connectors. But the homepage, all seven industry pages and the customer stories still use the older menu (Platform, Industries, Research, Security, Contact, Book a demo), which links to none of them, and the 51-URL sitemap leaves out /pricing/, /developers/, /connectors/ and the docs. A buyer who lands on the homepage or an industry page has one path, "Book a demo", and search engines are not told the pricing page exists.

    High impactLow effort First result in 2 weeks Founding engineer

    First action

    Replace the homepage header with the menu already used on /pricing/.

    How to measure it

    Visitors reaching /pricing/

    Now
    –
    Target
    3x the current weekly number
    By
    30 days

    Steps

    1. 1

      Inventory the menus

      List every page still on the old header and footer: homepage, seven industry pages, customer stories, comparisons and research posts.

      Founding engineer (website) 2 hours

    2. 2

      One shared layout

      Move all pages to the newer header with Developers, Connectors and Pricing.

      Founding engineer (website) 1 day

    3. 3

      Fix the footer

      Add Pricing, Developers and Connectors to the Platform column on every page.

      Founding engineer (website) 1 hour

    4. 4

      Complete the sitemap

      Add /pricing/, /developers/, /connectors/ and the /docs/ pages with lastmod dates; resubmit in Search Console.

      Founding engineer (website) 2 hours

    5. 5

      Add a second CTA

      "See pricing" beside "Book a demo" in the homepage hero and at the end of each industry page.

      Founding GTM Engineer 1 day

    6. 6

      Tag sign-up links

      Separate UTM content per page on every "Start building" link.

      Founding GTM Engineer 2 hours

    7. 7

      Measure

      Weekly: pricing visits, Start building clicks and demo bookings, by entry page.

      Founding GTM Engineer weekly

    First result
    2 weeks
    Cost
    $0, about two days of engineering time
    Owner
    Founding engineer (website)

    Smallest test

    Add Pricing to the homepage header today and compare a week of pricing-page visits with the week before.

    Build the prospect list. The list compiled from public sources, verified, deduplicated and delivered to your CRM. Usually live within days.

    Book a working session

    Why it works

    Move every page onto the newer menu that /pricing/ and /developers/ already use (Platform, Industries, Developers, Connectors, Research, Pricing, Contact, Book a demo) from one shared layout. Add Pricing, Developers and Connectors to the footer's Platform column everywhere. Add /pricing/, /developers/, /connectors/ and the /docs/ pages to sitemap.xml with lastmod dates and resubmit it. Put a secondary "See pricing" link beside "Book a demo" in the homepage hero and at the end of each industry page, and tag each "Start building" link by source page so sign-ups trace back to the page that produced them.

    Operations and finance buyers check price before they agree to a call; publishing a price and then hiding it gives neither the trust benefit nor the self-serve sign-ups. Two different menus also tell search engines and AI assistants that the newer pages matter less than they do.

    Ready to use

    ChecklistFindability fix list

    [ ] Homepage on the new header (Developers, Connectors, Pricing)
    [ ] All 7 industry pages on the new header
    [ ] Customer stories, comparisons and research on the new header
    [ ] Footer Platform column: Platform, Developers, Connectors, Benchmarks, Security, Pricing, Customers
    [ ] sitemap.xml: /pricing/, /developers/, /connectors/, /docs/ pages, with lastmod
    [ ] Resubmit sitemap in Search Console
    [ ] "See pricing" beside "Book a demo" on the homepage and industry pages
    [ ] UTM content per page on "Start building"

    Risks and how to handle them

    • An early price puts off large buyers

      Keep the Enterprise column and "Talk to sales" prominent; Platform anchors the low end, not the ceiling.

    • Self-serve sign-ups stall without help

      Offer each new workspace a 30-minute first-workflow session (idea 2).

    Evidence

    • Your websiteNavigation (checked November 9, 2026): the header on the homepage, the industry pages and /customers/ shows Platform, Industries, Research, Security, Contact and "Book a demo", and the footer's Platform column lists Platform, Benchmarks, Security and Customers; none of these pages link to /pricing/, /developers/ or /connectors/. Only the newer /pricing/ and /developers/ pages carry a menu with Developers, Connectors and Pricing.Source
    • Your websiteSitemap (51 URLs, no lastmod dates, checked November 9, 2026): 18 research posts, 8 customer stories, 7 industry pages, 4 comparison pages and a /compare/ index, /platform/, /benchmarks/ and a /meet/ booking page; /pricing/, /developers/, /connectors/ and the /docs/ pages are not listed, and there is no partner page.Source
    • Your websitePricing page: "Pay for the work, not the seats." Platform is "$1,500/month" with 150,000 credits, then $0.01 per credit (187 Junior, 150 Senior or 125 Veteran agent hours), unlimited team members, "50 active workflows, 5 running at once", and a "Start building" button that goes to the sign-in page of platform.ramain.ai. Agent hours cost $8 (Junior), $10 (Senior, default) or $12 (Veteran). Building and testing in the Workbench uses credits; included credits do not roll over; extra credits "don't add capacity; more requires an Enterprise plan". Enterprise is custom, with automations "built and maintained by Ramain", private deployment, BAA and DPA.Source
    • Your websiteDevelopers page: "Run digital workers from your own code." The quick start is three steps: build and save a workflow in the Workbench, copy its input schema from the app, then launch it from your server. A REST API with five endpoints (launch, status, result, events, recording), an MCP server, a Browser SDK that embeds a live view of a run, and links to /docs/ and /connectors/; the /docs/ site covers quickstarts, building, triggers, inbox, agents, workspace and the API.Source
  • 02

    Ramain has no free tier, building and testing in the Workbench uses credits, and the entry plan is $1,500 a month. Rivals let buyers start for almost nothing: Skyvern offers a 14-day free trial and Browser Use starts with $1 free. Ramain already promises that a demo on "one of your current processes" comes with expected usage and a plan recommendation, but it ends in a sales conversation, not a running worker.

    High impactLow effort First result in 1 month CEO

    First action

    Write a one-page offer: scope, price, two-week timeline and what the buyer receives.

    How to measure it

    First-workflow to paid plan conversion

    Now
    –
    Target
    50%
    By
    90 days

    Steps

    1. 1

      Set scope and price

      One process, up to a set volume, two weeks, fee credited to month one.

      CEO (co-founder) 1 day

    2. 2

      Write the offer page

      A section on /pricing/ and /meet/ with what is included.

      Founding GTM Engineer 2 days

    3. 3

      Template the report

      Hours done, credits used, exceptions handed to people, projected monthly cost.

      CTO (co-founder) 2 days

    4. 4

      Point the CTAs

      Route "Get a workflow assessment" to the offer.

      Founding engineer (website) 1 hour

    5. 5

      Run the first three

      Deliver with founders on the call.

      CEO (co-founder) 4 weeks

    6. 6

      Review conversion

      Which processes convert and at what plan.

      Founding GTM Engineer monthly

    First result
    1 month
    Cost
    Founder and engineering time per pilot, offset by the fee
    Owner
    CEO (co founder)

    Smallest test

    Offer it to the next five demo bookings and count how many say yes.

    Why it works

    Package that demo into a paid, fixed-price "first workflow": Ramain maps one process with the team in a session, builds and runs it for two weeks on their real volume, and hands over a report of hours, credits and exceptions. The fee is credited against the first Platform or Enterprise month. Sell it from the pricing page, the /meet/ page and every "Get a workflow assessment" button.

    It turns a $1,500 monthly commitment into a small, bounded decision with proof on the buyer's own data, and it qualifies buyers better than a free trial would because the team has to bring a real process.

    Risks and how to handle them

    • Pilots eat build capacity

      Cap the number running at once and pick processes that match existing connectors.

    • The fee feels like a barrier

      Credit it in full against the first month.

    Evidence

    • Your websitePricing page: "Pay for the work, not the seats." Platform is "$1,500/month" with 150,000 credits, then $0.01 per credit (187 Junior, 150 Senior or 125 Veteran agent hours), unlimited team members, "50 active workflows, 5 running at once", and a "Start building" button that goes to the sign-in page of platform.ramain.ai. Agent hours cost $8 (Junior), $10 (Senior, default) or $12 (Veteran). Building and testing in the Workbench uses credits; included credits do not roll over; extra credits "don't add capacity; more requires an Enterprise plan". Enterprise is custom, with automations "built and maintained by Ramain", private deployment, BAA and DPA.Source
    • Competitor researchRivals' own homepages: Skyvern, "AI agents to automate workflows on any website", with a 14-day free trial, SOC2 Type II and HIPAA, and "500+ enterprise users"; Browser Use, "Browser agents and cloud browsers", "Start with $1 free" and "$0.006 per task, median"; UiPath, "one platform for business orchestration and automation" where "Agents reason, robots act, and people step in where judgment matters".Source
    • Your websiteBooking page /meet/: "Pick a time to talk. Thirty minutes, one workflow." and "Bring a process your team runs by hand."; the pricing FAQ adds that a demo with one of your current processes includes a walkthrough, expected usage and a plan recommendation.Source
  • 03

    The proof exists but sits one click away in the wrong place. The healthcare page links to no story or research post, although a healthcare billing story and two dental eligibility posts exist. The mortgage page, headed "Built inside a working lock desk.", never links to the lock-desk story ($2.5 billion a year locked). Story pages in turn link only to "Book a demo" and back to /customers/.

    Medium impactLow effort First result in 2 weeks Founding GTM Engineer

    First action

    Add the lock-desk story to the mortgage page.

    How to measure it

    Industry-page demo rate

    Now
    –
    Target
    +20%
    By
    60 days

    Steps

    1. 1

      Map proof to pages

      Each industry page to its stories and research tab posts.

      Founding GTM Engineer 2 hours

    2. 2

      Design the block

      Story card with the number, plus research links.

      Founding engineer (website) 1 day

    3. 3

      Add reverse links

      Stories link to their industry page and to pricing.

      Founding engineer (website) 2 hours

    4. 4

      Fill gaps

      Nearest story for industries without one.

      Founding GTM Engineer 1 hour

    5. 5

      Publish

      All seven pages.

      Founding engineer (website) 1 day

    6. 6

      Track

      Clicks on the block and demo rate per industry page.

      Founding GTM Engineer monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founding GTM Engineer

    Smallest test

    Link the lock-desk story from the mortgage page today.

    Why it works

    Add a "Proof" block to each industry page: the matching story with its headline number, and the two or three research posts from the matching research tab. Add the reverse link on each story ("More for mortgage teams") and a link to pricing. Where an industry has no story yet (logistics, banking), show the closest one and say so.

    A lender reading the mortgage page is most persuaded by another lender's result; linking it there shortens the path from interest to demo and spreads link value to the stories.

    Risks and how to handle them

    • Anonymous stories feel thin

      Pair with idea 4's quotes and time-to-live.

    Evidence

    • Your websiteIndustry pages: the healthcare page ("Payer portal work, done before it holds up a claim.") links to no customer story or research post, although a healthcare billing story and two dental eligibility posts exist; the mortgage page ("Built inside a working lock desk.", "18 investor portals checked every day", maps one workflow in about an hour) names no customer story, although the lock-desk story exists.Source
    • Your websiteCustomer stories: 8 stories, 7 anonymous (a top-10 pharma company, a global online marketplace, US mortgage lenders, an industrial materials platform, a B2B parts sourcing company, a used-car marketplace, a healthcare billing company) and one named, Corgi Insurance. Three give no number (used-car fines, healthcare billing, Corgi). The order-entry story says the work was "automated by the process owner, with no IT project". The lock-desk and Corgi stories carry no customer quote and no time to go live, and story pages link only to "Book a demo" and back to /customers/, not to the industry page or pricing.Source
    • Your websiteResearch: 18 posts, filtered by Benchmarks, Platform, Economics, Mortgage and lending, Healthcare operations and BPO operations; no newsletter signup and no RSS feed; dates appear in two formats ("Sep 24, 2026" and "2026-10-18"); posts have X and LinkedIn share buttons. "The manual dental eligibility cost you are not tracking" says "Count every eligibility touch" but gives no dollar figures.Source
  • 04

    The homepage promises "Most workflows are live in hours", but no story says how long its own workflow took to go live. The lock-desk and Corgi stories have no customer quote, and three of the eight stories (used-car fines, healthcare billing, Corgi) give no number at all.

    Medium impactLow effort First result in 1 month CEO

    First action

    Email the three customers whose stories have no number.

    How to measure it

    Complete stories

    Now
    –
    Target
    8 of 8
    By
    45 days

    Steps

    1. 1

      Pull run data

      First session and first production run dates per customer.

      CTO (co-founder) 1 day

    2. 2

      Ask customers

      One quote and one number each, anonymous by title if needed.

      CEO (co-founder) 2 weeks

    3. 3

      Design the fact box

      Industry, systems, volume, time to live, result.

      Founding engineer (website) 1 day

    4. 4

      Update stories

      All eight pages.

      Founding GTM Engineer 2 days

    5. 5

      Reuse

      Quotes on industry pages and in outbound.

      Founding GTM Engineer 1 day

    6. 6

      Repeat

      Every new customer gets the fact box at launch.

      CEO (co-founder) ongoing

    First result
    1 month
    Cost
    $0
    Owner
    CEO (co founder)

    Smallest test

    Add the time to go live to the lock-desk story this week.

    Why it works

    Go back to each customer for three things: days from first session to first production run, one quote from the process owner (anonymous by title if needed, such as "Head of secondary marketing, independent mortgage bank"), and one before-and-after number. Add a standard fact box to every story: industry, systems, volume, time to live, result.

    Time to value is the question every operations buyer asks after "will it work"; real time-to-live numbers back the homepage promise and pre-empt the IT-project fear.

    Risks and how to handle them

    • Customers will not be quoted

      Offer anonymous attribution by role and company type.

    Evidence

    • Your websiteCustomer stories: 8 stories, 7 anonymous (a top-10 pharma company, a global online marketplace, US mortgage lenders, an industrial materials platform, a B2B parts sourcing company, a used-car marketplace, a healthcare billing company) and one named, Corgi Insurance. Three give no number (used-car fines, healthcare billing, Corgi). The order-entry story says the work was "automated by the process owner, with no IT project". The lock-desk and Corgi stories carry no customer quote and no time to go live, and story pages link only to "Book a demo" and back to /customers/, not to the industry page or pricing.Source
    • Your websiteHomepage (checked November 9, 2026): H1 "Meet Ramain. An AI employee for every process."; CTAs "Book a demo" and "Get a workflow assessment"; FAQ answer "Most workflows are live in hours"; results "1,500 doctor contracts a month", "60% lower cost than manual work", "$2.5B in loans locked a year" and "16 people's worth of work"; SOC 2 Type I, ISO 27001:2022, HIPAA-aligned with a BAA, GDPR with a DPA; work can be requested by email, Slack, text, WhatsApp, schedule or API; no prices on the page.Source
  • 05

    In the lab the homepage scores 99 on mobile, but Google's real-visitor data fails it on one measure: the largest element appears at 2,546 ms for the slowest quarter of visits, just over the 2,500 ms limit. INP and CLS pass and LCP is already 32% faster than before. The gap is mostly the 1,607 ms before the first byte arrives, high for a site served from Amazon S3 through CloudFront, plus 550 ms of render-blocking requests.

    Medium impactLow effort First result in 1 month Founding engineer

    First action

    Look at the cache hit ratio and the cache policy for HTML in CloudFront.

    How to measure it

    Field LCP p75

    Now
    –
    Target
    Under 2,000 ms
    By
    60 days

    Steps

    1. 1

      Check caching

      Cache hit ratio and TTL for HTML pages at CloudFront.

      Founding engineer (website) 2 hours

    2. 2

      Remove redirect hops

      Apex, www and trailing-slash versions resolve in one step.

      Founding engineer (website) 1 hour

    3. 3

      Cache HTML at the edge

      With invalidation on each deploy.

      Founding engineer (website) 1 day

    4. 4

      Unblock rendering

      Inline critical CSS, defer the rest.

      Founding engineer (website) 1 day

    5. 5

      Trim JavaScript and fix accessibility

      Unused bundles; contrast and touch targets.

      Founding engineer (website) 2 days

    6. 6

      Watch field data

      PageSpeed field data over the next 28 days.

      Founding engineer (website) monthly

    First result
    1 month (field data uses a 28-day window)
    Cost
    $0
    Owner
    Founding engineer (website)

    Smallest test

    Cache the homepage HTML at the edge and recheck time to first byte.

    Why it works

    Check CloudFront cache settings so the HTML pages themselves are cached at the edge (not only images and scripts) with a sensible TTL and invalidation on deploy, and check for redirects between the apex and www or trailing-slash versions. Then inline critical CSS to remove the render-blocking requests, trim the 158 KB of unused JavaScript, and fix the two accessibility issues (contrast and touch targets) in the same pass.

    Passing Core Web Vitals is a small ranking factor, but for a company selling speed and reliability, a fast first impression also matches the message; the fix is mostly configuration.

    Risks and how to handle them

    • Stale pages after deploys

      Invalidate the cache automatically on every deploy.

    Evidence

    • PageSpeedGoogle PageSpeed (November 9, 2026): lab score 99 on mobile and 85 on desktop, but real visitors narrowly fail Core Web Vitals on LCP (2,546 ms at the 75th percentile against a 2,500 ms limit), with time to first byte of 1,607 ms; INP (138 ms) and CLS (0) pass, and LCP is 32% faster than in the previous period. The site is served from Amazon S3 through CloudFront. Lab fixes: 550 ms of render-blocking requests and 158 KB of unused JavaScript. The homepage has no social share image, and two accessibility issues remain (colour contrast, touch-target size).Source
  • 06

    Research posts have X and LinkedIn share buttons, and four benchmark posts went out on the same day, but the homepage has no social share image, so links to Ramain show up as plain text in feeds and chat apps where enterprise buyers and investors pass them around.

    Medium impactLow effort First result in 2 weeks Founding GTM Engineer

    First action

    Add a default share image to the homepage.

    How to measure it

    Social referral sessions

    Now
    –
    Target
    +50%
    By
    60 days

    Steps

    1. 1

      Design the template

      Title, one number, logo.

      Founding GTM Engineer 1 day

    2. 2

      Generate per page

      At build time for research, stories and industry pages.

      Founding engineer (website) 1 day

    3. 3

      Set a default

      Homepage and any page without its own.

      Founding engineer (website) 1 hour

    4. 4

      Check previews

      LinkedIn Post Inspector and X.

      Founding GTM Engineer 1 hour

    5. 5

      Reshare top posts

      Benchmarks and the lock-desk story with the new previews.

      CEO (co-founder) 1 week

    6. 6

      Measure

      Social referrals by post.

      Founding GTM Engineer monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founding GTM Engineer

    Smallest test

    Add an image to the benchmark post and reshare it.

    Why it works

    Generate a share image per page from a template: the post title, the key number (99.2% on WebVoyager, $0.21 per task, 40 to 15 minutes per lock) and the Ramain mark. Add a default image for the homepage and industry pages. Check previews in LinkedIn's Post Inspector and on X.

    Posts with a large image get noticeably more clicks in LinkedIn feeds, where B2B links travel; the numbers are already strong enough to sell the click.

    Risks and how to handle them

    • Cached old previews

      Force a re-scrape with each platform's inspector.

    Evidence

    • PageSpeedGoogle PageSpeed (November 9, 2026): lab score 99 on mobile and 85 on desktop, but real visitors narrowly fail Core Web Vitals on LCP (2,546 ms at the 75th percentile against a 2,500 ms limit), with time to first byte of 1,607 ms; INP (138 ms) and CLS (0) pass, and LCP is 32% faster than in the previous period. The site is served from Amazon S3 through CloudFront. Lab fixes: 550 ms of render-blocking requests and 158 KB of unused JavaScript. The homepage has no social share image, and two accessibility issues remain (colour contrast, touch-target size).Source
    • Your websiteResearch: 18 posts, filtered by Benchmarks, Platform, Economics, Mortgage and lending, Healthcare operations and BPO operations; no newsletter signup and no RSS feed; dates appear in two formats ("Sep 24, 2026" and "2026-10-18"); posts have X and LinkedIn share buttons. "The manual dental eligibility cost you are not tracking" says "Count every eligibility touch" but gives no dollar figures.Source
    • Your websiteBenchmarks page: Online-Mind2Web 99.3%, WebVoyager 99.2%, WorkArena L3 89.4% and WebArena-Verified Hard 84.2%, at "$0.21 per task", which the page says is 36% less than browser-use on the same model; all tasks are reported.Source

This quarter 10

The core plays for the next three months.

  • 07

    Ramain's biggest result ($2.5 billion a year in loans locked, 70% lower cost) belongs to a BPO that runs locks for 7 mortgage banks, so a BPO is already reselling Ramain's work to its own clients. Every page's footer invites BPOs, IT services firms and integrators to "Partner with us", and there is a BPO research tab, but there is no partner page and no published terms.

    High impactMedium effort First result in 1 quarter CEO

    First action

    Ask the lock-desk BPO what would make them bring Ramain to more of their clients.

    How to measure it

    Partner-sourced end clients

    Now
    –
    Target
    10
    By
    2 quarters

    Steps

    1. 1

      Interview the BPO

      Why they bought, margin effect, what they need to resell.

      CEO (co-founder) 1 week

    2. 2

      Set terms

      Credit rates by volume, referral or resale model, support split.

      CEO (co-founder) 2 weeks

    3. 3

      Publish the page

      /partners/ with tracks, terms and the lock-desk model; add it to the sitemap and footer link.

      Founding GTM Engineer 1 week

    4. 4

      Build a partner list

      BPOs serving mortgage, healthcare billing and insurance.

      Founding GTM Engineer 2 weeks

    5. 5

      Run joint pilots

      One workflow per partner on a real client process.

      CTO (co-founder) 6 weeks

    6. 6

      Review

      Pipeline and revenue by partner.

      CEO (co-founder) monthly

    First result
    1 quarter
    Cost
    Founder time and partner discounts
    Owner
    CEO (co founder)

    Smallest test

    Publish a one-page partner offer and email it to ten BPOs.

    Why it works

    Publish /partners/ with three tracks (BPOs, IT services, systems integrators): what partners get (volume credit rates, co-branded run reports, a shared pipeline, training), what they commit to, and the lock-desk story as the model. Recruit five BPOs in the verticals Ramain already has proof in (mortgage, healthcare billing, insurance) and give each a partner workspace and a joint first workflow.

    BPOs own the client relationships and the process knowledge; Ramain lets them keep the client and improve margin instead of losing work to automation. One partner brings many end clients, which suits a team of 7.

    Risks and how to handle them

    • Channel conflict with direct deals

      Register partner deals and protect them for a fixed period.

    • Partners need more support than direct customers

      Train partner staff to build workflows themselves.

    Evidence

    • Your websitePartners: every page's footer says "BPO, IT services or systems integrator? Partner with us", but there is no partner page in the sitemap and no published terms; the post "What work can AI agents do that used to go to offshore BPO?" advises "Hand over the browser work first" and ends with "Book a demo".Source
    • Your websiteLock-desk story: the customer is a BPO that runs loan locking for 7 US independent mortgage banks; each lock fell from 40 minutes to 15; "$2.5 billion a year in loans locked autonomously", locks for more than 1,000 homeowners a month and 70% lower cost for the BPO; exceptions such as a pricing conflict are handed to a person on the lock desk.Source
    • Your websiteSitemap (51 URLs, no lastmod dates, checked November 9, 2026): 18 research posts, 8 customer stories, 7 industry pages, 4 comparison pages and a /compare/ index, /platform/, /benchmarks/ and a /meet/ booking page; /pricing/, /developers/, /connectors/ and the /docs/ pages are not listed, and there is no partner page.Source
  • 08

    The connectors page lists 60 systems (SAP, NetSuite, Workday, Coupa, ICE Encompass, Optimal Blue, Applied Epic, EZLynx, Epic, athenahealth, Veeva PromoMats, Adobe Sign, MercuryGate and more), but none has its own page and many cards link nowhere. People search for the system and the chore ("automate NetSuite order entry", "Encompass automation without API"), and Ramain has stories for several of them.

    High impactMedium effort First result in 2 months Founding GTM Engineer

    First action

    Pick the first five systems by story coverage: NetSuite, Adobe Sign, ICE Encompass, SAP and Applied Epic.

    How to measure it

    Connector-page conversions

    Now
    –
    Target
    20 a month
    By
    2 quarters

    Steps

    1. 1

      Rank systems

      By search volume and existing proof.

      Founding GTM Engineer 2 days

    2. 2

      Write a template

      Jobs, how it connects, proof, replay, CTAs.

      Founding GTM Engineer 2 days

    3. 3

      Write the first five

      With a story or replay on each.

      Founding GTM Engineer 2 weeks

    4. 4

      Build the pages

      Link cards on /connectors/ to them; add to the sitemap.

      Founding engineer (website) 1 week

    5. 5

      Add ten more

      Next systems by demand.

      Founding GTM Engineer 1 month

    6. 6

      Measure

      Search impressions and conversions per page.

      Founding GTM Engineer monthly

    First result
    2 months
    Cost
    Staff time
    Owner
    Founding GTM Engineer

    Smallest test

    Publish the NetSuite page and track it for a month.

    Why it works

    Build /connectors/<system>/ pages for the 15 systems with the most buyer intent and existing proof. Each page: the three jobs Ramain does in that system, how it connects (through the screen, no API needed), the matching story (NetSuite order sync, Adobe Sign contracts, Encompass locks), a short run replay and a "Start building" plus "Book a demo" pair. Add them to the sitemap.

    System-plus-task searches are high intent and less contested than generic "AI agent" terms, and each page gives operations buyers a direct answer to "does it work with our system?".

    Risks and how to handle them

    • Trademark use of system names

      Describe compatibility factually and avoid implying partnership.

    Builds on

    Evidence

    • Your websiteConnectors page: 60 connectors in 12 categories, including SAP, Oracle, NetSuite, Workday, Coupa, QuickBooks, Salesforce, ServiceNow, ICE Encompass, Optimal Blue, Applied Epic, EZLynx, Epic, Cerner, athenahealth, Veeva PromoMats, Adobe Sign, SAP TM and MercuryGate; no connector has its own page, and many cards (such as SAP Concur, Zoho Books and Excel) link nowhere.Source
    • Your websiteCustomer stories: 8 stories, 7 anonymous (a top-10 pharma company, a global online marketplace, US mortgage lenders, an industrial materials platform, a B2B parts sourcing company, a used-car marketplace, a healthcare billing company) and one named, Corgi Insurance. Three give no number (used-car fines, healthcare billing, Corgi). The order-entry story says the work was "automated by the process owner, with no IT project". The lock-desk and Corgi stories carry no customer quote and no time to go live, and story pages link only to "Book a demo" and back to /customers/, not to the industry page or pricing.Source
  • 09

    The new Founding GTM Engineer is hired to build automations that detect buying signals and trigger outreach. For Ramain the clearest signal is a company advertising the exact work a digital worker does: lock desk assistants, AP clerks keying invoices into SAP, eligibility verification specialists, order entry clerks. The homepage already lists these tasks.

    High impactMedium effort First result in 1 month Founding GTM Engineer

    First action

    Write the list of 20 title and phrase matches from the homepage task list.

    How to measure it

    Signal-sourced meetings

    Now
    –
    Target
    15 a month
    By
    90 days

    Steps

    1. 1

      Define signals

      Titles, phrases and system names per vertical.

      Founding GTM Engineer 2 days

    2. 2

      Build the scan

      Weekly pull from public job boards into the CRM.

      Founding GTM Engineer 1 week

    3. 3

      Score fit

      Industry, systems, roles open, company size.

      Founding GTM Engineer 3 days

    4. 4

      Write sequences

      One per task, with a replay and the matching story.

      CEO (co-founder) 1 week

    5. 5

      Send and follow up

      Small batches, watching deliverability.

      Founding GTM Engineer weekly

    6. 6

      Learn

      Reply and meeting rates by signal type.

      Founding GTM Engineer monthly

    First result
    1 month
    Cost
    Data and sequencing tools already in the GTM stack
    Owner
    Founding GTM Engineer

    Smallest test

    Find 30 companies hiring lock desk or eligibility roles and email them this week.

    Why it works

    Build a weekly job-board scan for titles and phrases that match Ramain's tasks ("data entry", "portal", "lock desk", "eligibility verification", "order entry", "accounts payable" plus the system names Ramain supports). Score each company by fit (industry, systems named, number of open roles), enrich with the operations leader, and send a short note: "You're hiring for X; here's the same work running in Y minutes", linking a replay and the matching story.

    A job post is a budget already approved for the work, with the systems and volumes spelled out; outreach that names it is relevant by construction.

    Risks and how to handle them

    • Messages read as "replace your new hire"

      Frame it as clearing the backlog so the hire handles exceptions.

    Evidence

    • HiringFounding GTM Engineer (San Francisco, $120K–$180K, 0.30%–1.20% equity): owns top-of-funnel outbound (lead enrichment, best-fit customer profile scoring, AI-personalized sequences, deliverability), builds automations that detect buying signals and trigger outreach, owns the CRM, tests new channels and automates manual GTM work. Careers page: "Own go-to-market with the founders: outbound, the enterprise pipeline, demos and the systems that run them."Source
    • Your websiteHomepage (checked November 9, 2026): H1 "Meet Ramain. An AI employee for every process."; CTAs "Book a demo" and "Get a workflow assessment"; FAQ answer "Most workflows are live in hours"; results "1,500 doctor contracts a month", "60% lower cost than manual work", "$2.5B in loans locked a year" and "16 people's worth of work"; SOC 2 Type I, ISO 27001:2022, HIPAA-aligned with a BAA, GDPR with a DPA; work can be requested by email, Slack, text, WhatsApp, schedule or API; no prices on the page.Source
    • Y CombinatorYC profile: "RamAIn Employees join your team just like a human"; launch post "Teach AI to use your legacy systems, desktop applications and web portals just like a human" and "if you can see it, RamAIn can do it"; target teams include procurement, insurance brokerage, healthcare, revenue cycle management, finance and operations, retail, pharmacy and logistics.Source
  • 10

    Ramain prices by agent hour ($8, $10 or $12) and credits, which is clear to an engineer but abstract to an operations manager who thinks in tasks per month and minutes per task. The lock-desk story shows the math buyers care about: 40 minutes by hand, 15 with Ramain, 70% lower cost.

    Medium impactMedium effort First result in 1 month Founding GTM Engineer

    First action

    Agree the formula and the average agent minutes per task by tier.

    How to measure it

    Pricing-page conversion

    Now
    –
    Target
    +25%
    By
    60 days

    Steps

    1. 1

      Agree the math

      Agent time per task by tier from real runs.

      CTO (co-founder) 2 days

    2. 2

      Design

      Four inputs, one result panel.

      Founding engineer (website) 2 days

    3. 3

      Build

      On /pricing/, with the lock-desk preset.

      Founding engineer (website) 1 week

    4. 4

      Pass inputs

      Prefill the demo form and CRM.

      Founding GTM Engineer 1 day

    5. 5

      Add vertical presets

      Invoices, contracts, eligibility checks.

      Founding GTM Engineer 1 week

    6. 6

      Measure

      Use, demo rate and deal size of calculator users.

      Founding GTM Engineer monthly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Founding GTM Engineer

    Smallest test

    Publish a static table of three example processes with their monthly cost.

    Why it works

    Add a calculator to /pricing/: tasks per month, minutes per task by hand, loaded hourly staff cost and tier. It shows estimated agent hours, monthly credits, whether Platform covers it, the manual cost and the saving, with the lock-desk numbers as the preset example. Pass the inputs to the demo form so the call starts from the buyer's numbers.

    It converts usage pricing into a business case the buyer can forward to finance, and it qualifies leads by volume before the call.

    Risks and how to handle them

    • Estimates set wrong expectations

      Show ranges and confirm in the first-workflow pilot (idea 2).

    Builds on

    Evidence

    • Your websitePricing page: "Pay for the work, not the seats." Platform is "$1,500/month" with 150,000 credits, then $0.01 per credit (187 Junior, 150 Senior or 125 Veteran agent hours), unlimited team members, "50 active workflows, 5 running at once", and a "Start building" button that goes to the sign-in page of platform.ramain.ai. Agent hours cost $8 (Junior), $10 (Senior, default) or $12 (Veteran). Building and testing in the Workbench uses credits; included credits do not roll over; extra credits "don't add capacity; more requires an Enterprise plan". Enterprise is custom, with automations "built and maintained by Ramain", private deployment, BAA and DPA.Source
    • Your websiteLock-desk story: the customer is a BPO that runs loan locking for 7 US independent mortgage banks; each lock fell from 40 minutes to 15; "$2.5 billion a year in loans locked autonomously", locks for more than 1,000 homeowners a month and 70% lower cost for the BPO; exceptions such as a pricing conflict are handed to a person on the lock desk.Source
  • 11

    Ramain publishes steadily (18 posts, with tabs for benchmarks, economics, mortgage, healthcare and BPO operations), but there is no newsletter signup and no RSS feed, so every reader who is not ready for a demo leaves with no way to hear from Ramain again. Dates are also shown in two formats.

    Medium impactLow effort First result in 1 month Founding GTM Engineer

    First action

    Add a signup box to the research index.

    How to measure it

    Subscribers

    Now
    –
    Target
    500
    By
    2 quarters

    Steps

    1. 1

      Pick the tool

      One that syncs to the CRM with industry tags.

      Founding GTM Engineer 1 day

    2. 2

      Add signups

      Research index and the end of each post.

      Founding engineer (website) 1 day

    3. 3

      Publish RSS

      A feed for /research/; fix the date format.

      Founding engineer (website) 1 day

    4. 4

      Write issue one

      New posts and one customer number.

      CEO (co-founder) 1 day

    5. 5

      Send monthly

      Segmented by industry.

      Founding GTM Engineer monthly

    6. 6

      Measure

      Subscribers, clicks, demos from email.

      Founding GTM Engineer monthly

    First result
    1 month
    Cost
    Email tool, under $50 a month
    Owner
    Founding GTM Engineer

    Smallest test

    Add a signup box and count signups for two weeks.

    Why it works

    Add an email signup to the research index and the end of every post ("One email a month: new benchmarks and the economics of manual work"), publish an RSS feed, and send a monthly email with the new posts plus one customer number. Let subscribers choose their industry so mortgage readers get mortgage posts. Fix the date format while there.

    Enterprise deals take months; a monthly touch keeps Ramain in mind until the buyer's process pain peaks, and subscribers become a warm list for the GTM engineer.

    Risks and how to handle them

    • No time to write

      Reuse posts already published; one paragraph per post.

    Evidence

    • Your websiteResearch: 18 posts, filtered by Benchmarks, Platform, Economics, Mortgage and lending, Healthcare operations and BPO operations; no newsletter signup and no RSS feed; dates appear in two formats ("Sep 24, 2026" and "2026-10-18"); posts have X and LinkedIn share buttons. "The manual dental eligibility cost you are not tracking" says "Count every eligibility touch" but gives no dollar figures.Source
    • HiringFounding GTM Engineer (San Francisco, $120K–$180K, 0.30%–1.20% equity): owns top-of-funnel outbound (lead enrichment, best-fit customer profile scoring, AI-personalized sequences, deliverability), builds automations that detect buying signals and trigger outreach, owns the CRM, tests new channels and automates manual GTM work. Careers page: "Own go-to-market with the founders: outbound, the enterprise pipeline, demos and the systems that run them."Source
  • 12

    Ramain's RPA comparison already says a script "breaks until someone rewrites it" and suggests moving the most frequently broken bots first, and the platform has a recovery agent for when "a website changes". But the page ends with a generic "Book a demo" and no offer for the RPA team who arrived searching for an alternative.

    Medium impactLow effort First result in 6 weeks CEO

    First action

    Write the offer and add it to the RPA comparison page.

    How to measure it

    RPA migration requests

    Now
    –
    Target
    5 a month
    By
    90 days

    Steps

    1. 1

      Define the offer

      One bot, two weeks side by side, a report.

      CEO (co-founder) 1 day

    2. 2

      Update the page

      Offer, form, "run both" section.

      Founding GTM Engineer 2 days

    3. 3

      Report template

      Breaks, recoveries, hours, cost.

      CTO (co-founder) 2 days

    4. 4

      Promote

      Outbound to RPA centre-of-excellence leads.

      Founding GTM Engineer 2 weeks

    5. 5

      Deliver

      First three migrations.

      CTO (co-founder) 6 weeks

    6. 6

      Publish results

      Anonymous before-and-after stories.

      Founding GTM Engineer 1 quarter

    First result
    6 weeks
    Cost
    Build time per migration
    Owner
    CEO (co founder)

    Smallest test

    Add the offer line and form to the page and watch submissions for a month.

    Why it works

    Add a concrete offer to /compare/ramain-vs-legacy-rpa/: send the bot that broke most often this quarter, and Ramain rebuilds it as a digital worker and runs it side by side for two weeks, reporting breaks, recoveries and cost against the RPA licence. Add a short "how teams run both" section and a form that asks which RPA tool and how many bots.

    RPA owners already know which bots cost them the most; a named, bounded swap is an easier yes than a platform change, and every win becomes a story.

    Risks and how to handle them

    • Complex bots take too long

      Limit the offer to bots under a set number of steps.

    Evidence

    • Your websiteComparisons: four pages (legacy RPA, building it yourself, coding agents, other browser agents). The legacy RPA page names UiPath, Automation Anywhere, Blue Prism and Power Automate in its title, says an RPA script "breaks until someone rewrites it", suggests moving the most frequently broken bots first, and has no migration offer.Source
    • Your websitePlatform page: build ("Describe the task."), run, watch ("See every run.", with live view and step-by-step replay), recover ("When a website changes, the work carries on."), control and connect; a managed service: "We build it with you, and we keep it running."; CTAs "Book a demo", "Watch it work" and "Read the benchmarks".Source
  • 13

    The developer quick start asks a new user to first build and save a workflow in the Workbench, then copy its input schema, then call the API. That is three steps before the first API call returns anything, and building uses paid credits. Developers evaluating the API and MCP server want a run they can launch in minutes.

    Medium impactMedium effort First result in 1 month CTO

    First action

    Measure today's time from sign-in to first successful API run.

    How to measure it

    Day-one first run rate

    Now
    –
    Target
    60%
    By
    90 days

    Steps

    1. 1

      Measure

      Time and drop-off from sign-in to first API run.

      CTO (co-founder) 2 days

    2. 2

      Build the sample

      A stable public target and a saved workflow.

      CTO (co-founder) 1 week

    3. 3

      Preload it

      In every new workspace, credits waived.

      CTO (co-founder) 3 days

    4. 4

      Write snippets

      API, Python, TypeScript and MCP that work as pasted.

      CTO (co-founder) 3 days

    5. 5

      Update the page

      Quick start leads with the sample.

      Founding engineer (website) 1 day

    6. 6

      Track

      First-run rate and conversion to paid.

      Founding GTM Engineer monthly

    First result
    1 month
    Cost
    Engineering time and a small credit allowance
    Owner
    CTO (co founder)

    Smallest test

    Give the next ten sign-ups a saved sample workflow and compare first-run time.

    Why it works

    Ship a sample workflow in every new workspace (for example, collecting a document from a public demo portal) with its schema prefilled, so the first API call or MCP request works immediately. Add copy-paste snippets for each tab (API, Python, TypeScript, MCP) that launch it, poll status and fetch the recording. Count the sample's credits as free.

    Time to first successful call is the strongest predictor of developer adoption; a working replay of their own first run is also the best demo Ramain has.

    Risks and how to handle them

    • The sample target site changes

      Host a small demo portal Ramain controls.

    Builds on

    Evidence

    • Your websiteDevelopers page: "Run digital workers from your own code." The quick start is three steps: build and save a workflow in the Workbench, copy its input schema from the app, then launch it from your server. A REST API with five endpoints (launch, status, result, events, recording), an MCP server, a Browser SDK that embeds a live view of a run, and links to /docs/ and /connectors/; the /docs/ site covers quickstarts, building, triggers, inbox, agents, workspace and the API.Source
    • Your websitePricing page: "Pay for the work, not the seats." Platform is "$1,500/month" with 150,000 credits, then $0.01 per credit (187 Junior, 150 Senior or 125 Veteran agent hours), unlimited team members, "50 active workflows, 5 running at once", and a "Start building" button that goes to the sign-in page of platform.ramain.ai. Agent hours cost $8 (Junior), $10 (Senior, default) or $12 (Veteran). Building and testing in the Workbench uses credits; included credits do not roll over; extra credits "don't add capacity; more requires an Enterprise plan". Enterprise is custom, with automations "built and maintained by Ramain", private deployment, BAA and DPA.Source
    • Competitor researchRivals' own homepages: Skyvern, "AI agents to automate workflows on any website", with a 14-day free trial, SOC2 Type II and HIPAA, and "500+ enterprise users"; Browser Use, "Browser agents and cloud browsers", "Start with $1 free" and "$0.006 per task, median"; UiPath, "one platform for business orchestration and automation" where "Agents reason, robots act, and people step in where judgment matters".Source
  • 14

    Ramain logs every run with replay and an audit trail, and included credits do not roll over, so customers who use less than their allowance pay for unused work and may question renewal. The value (a lock in 15 minutes instead of 40, 70% lower cost) is in the run data but is not sent to the buyer who signs the renewal.

    High impactMedium effort First result in 1 month CEO

    First action

    Hand-build the report for the three largest workspaces this month.

    How to measure it

    Workspaces using 70%+ of credits

    Now
    –
    Target
    75%
    By
    2 quarters

    Steps

    1. 1

      Define fields

      Tasks, hours saved, credits, exceptions, suggestion.

      CEO (co-founder) 1 day

    2. 2

      Pilot by hand

      Three largest workspaces.

      CEO (co-founder) 1 week

    3. 3

      Automate

      Generate from run logs monthly.

      CTO (co-founder) 2 weeks

    4. 4

      Add the manager

      A second recipient chosen by the customer.

      Founding GTM Engineer 1 day

    5. 5

      Low-usage alerts

      Under 50% of credits triggers a call.

      Founding GTM Engineer 2 days

    6. 6

      Review

      Utilisation, expansion and renewals.

      CEO (co-founder) monthly

    First result
    1 month
    Cost
    Engineering time
    Owner
    CEO (co founder)

    Smallest test

    Send one hand-made report to one customer and ask what they would forward.

    Why it works

    Send each workspace owner and their manager a monthly report: tasks completed per workflow, estimated staff hours saved at the customer's own rate, credits used against the allowance, exceptions handed to people and how fast they were cleared, and one suggestion (a workflow to add, a tier to change). Flag workspaces using under half their credits for a check-in call.

    Making the saving visible each month protects renewals and opens expansion, and low-usage flags catch churn risk early.

    Risks and how to handle them

    • Hours-saved estimates disputed

      Use the customer's own baseline minutes per task.

    Evidence

    • Your websitePricing page: "Pay for the work, not the seats." Platform is "$1,500/month" with 150,000 credits, then $0.01 per credit (187 Junior, 150 Senior or 125 Veteran agent hours), unlimited team members, "50 active workflows, 5 running at once", and a "Start building" button that goes to the sign-in page of platform.ramain.ai. Agent hours cost $8 (Junior), $10 (Senior, default) or $12 (Veteran). Building and testing in the Workbench uses credits; included credits do not roll over; extra credits "don't add capacity; more requires an Enterprise plan". Enterprise is custom, with automations "built and maintained by Ramain", private deployment, BAA and DPA.Source
    • Your websitePlatform page: build ("Describe the task."), run, watch ("See every run.", with live view and step-by-step replay), recover ("When a website changes, the work carries on."), control and connect; a managed service: "We build it with you, and we keep it running."; CTAs "Book a demo", "Watch it work" and "Read the benchmarks".Source
    • Your websiteLock-desk story: the customer is a BPO that runs loan locking for 7 US independent mortgage banks; each lock fell from 40 minutes to 15; "$2.5 billion a year in loans locked autonomously", locks for more than 1,000 homeowners a month and 70% lower cost for the BPO; exceptions such as a pricing conflict are handed to a person on the lock desk.Source
  • 15

    Platform allows "50 active workflows, 5 running at once", and the pricing FAQ says extra credits "don't add capacity; more requires an Enterprise plan". A customer whose volume grows (the platform advertises parallel runs across hundreds of records) hits the five-run ceiling long before using up a large credit budget, and the only way up is a jump to a custom Enterprise negotiation.

    Medium impactLow effort First result in 1 month CEO

    First action

    Count how many workspaces have hit the five-run limit in the last month.

    How to measure it

    Monthly add-on revenue

    Now
    –
    Target
    10% of Platform revenue
    By
    2 quarters

    Steps

    1. 1

      Measure queueing

      Workspaces and hours queued at the limit.

      CTO (co-founder) 2 days

    2. 2

      Price the add-on

      Per block of five runs; a mid-step bundle.

      CEO (co-founder) 1 week

    3. 3

      Show the queue

      In-app notice when runs wait for capacity.

      CTO (co-founder) 1 week

    4. 4

      One-click upgrade

      Add-on purchase inside the workspace.

      CTO (co-founder) 1 week

    5. 5

      Update pricing page

      Add-on line and FAQ answer.

      Founding GTM Engineer 1 day

    6. 6

      Review

      Uptake and effect on Enterprise deals.

      CEO (co-founder) monthly

    First result
    1 month
    Cost
    Engineering time
    Owner
    CEO (co founder)

    Smallest test

    Offer the add-on by email to workspaces that queued last month.

    Why it works

    Add a self-serve concurrency add-on to Platform (for example, +5 concurrent runs for a fixed monthly fee) and a mid-step bundle (more workflows and runs at a stated price) between Platform and Enterprise. Show in the app when runs are queued because of the limit, with a one-click upgrade.

    It captures expansion revenue at the moment of need instead of stalling it behind a sales cycle, and queue visibility makes the value obvious.

    Risks and how to handle them

    • Cannibalises Enterprise

      Cap the add-on; keep build-and-maintain service and private deployment Enterprise-only.

    Evidence

    • Your websitePricing page: "Pay for the work, not the seats." Platform is "$1,500/month" with 150,000 credits, then $0.01 per credit (187 Junior, 150 Senior or 125 Veteran agent hours), unlimited team members, "50 active workflows, 5 running at once", and a "Start building" button that goes to the sign-in page of platform.ramain.ai. Agent hours cost $8 (Junior), $10 (Senior, default) or $12 (Veteran). Building and testing in the Workbench uses credits; included credits do not roll over; extra credits "don't add capacity; more requires an Enterprise plan". Enterprise is custom, with automations "built and maintained by Ramain", private deployment, BAA and DPA.Source
    • Your websitePlatform page: build ("Describe the task."), run, watch ("See every run.", with live view and step-by-step replay), recover ("When a website changes, the work carries on."), control and connect; a managed service: "We build it with you, and we keep it running."; CTAs "Book a demo", "Watch it work" and "Read the benchmarks".Source
  • 16

    The order-entry story says 16 people's worth of work was "automated by the process owner, with no IT project". Unlimited team members and no seat fees mean nothing stops that person bringing in colleagues from the next department. The expansion path runs through process owners, not IT.

    High impactLow effort First result in 1 month CEO

    First action

    List every live customer and the name of the role that owns their first workflow.

    How to measure it

    Multi-workflow accounts

    Now
    –
    Target
    60% of accounts
    By
    2 quarters

    Steps

    1. 1

      List process owners

      One per live customer.

      CEO (co-founder) 1 day

    2. 2

      Write the session guide

      Next three processes, volumes, systems.

      CEO (co-founder) 1 day

    3. 3

      Make the summary

      One-page results for the owner to forward.

      Founding GTM Engineer 2 days

    4. 4

      Run sessions

      Thirty days after go-live.

      CEO (co-founder) ongoing

    5. 5

      Build workflow two

      With the owner, in the same month.

      CTO (co-founder) 2 weeks each

    6. 6

      Track

      Workflows per account and credit growth.

      Founding GTM Engineer monthly

    First result
    1 month
    Cost
    Founder time
    Owner
    CEO (co founder)

    Smallest test

    Run the session with two customers this month.

    Why it works

    Thirty days after a customer's first workflow goes live, run a 30-minute session with its process owner to map the next three manual processes in their own and neighbouring teams, using the homepage task list as prompts. Give the process owner a one-page internal summary of results to share, and offer to build the second workflow with them.

    The person who already saw a worker clear their queue is the most credible internal seller, and each new workflow raises credit use and switching cost.

    Risks and how to handle them

    • Second processes need other systems

      Prefer processes on systems already connected.

    Builds on

    Evidence

    • Your websiteCustomer stories: 8 stories, 7 anonymous (a top-10 pharma company, a global online marketplace, US mortgage lenders, an industrial materials platform, a B2B parts sourcing company, a used-car marketplace, a healthcare billing company) and one named, Corgi Insurance. Three give no number (used-car fines, healthcare billing, Corgi). The order-entry story says the work was "automated by the process owner, with no IT project". The lock-desk and Corgi stories carry no customer quote and no time to go live, and story pages link only to "Book a demo" and back to /customers/, not to the industry page or pricing.Source
    • Your websitePricing page: "Pay for the work, not the seats." Platform is "$1,500/month" with 150,000 credits, then $0.01 per credit (187 Junior, 150 Senior or 125 Veteran agent hours), unlimited team members, "50 active workflows, 5 running at once", and a "Start building" button that goes to the sign-in page of platform.ramain.ai. Agent hours cost $8 (Junior), $10 (Senior, default) or $12 (Veteran). Building and testing in the Workbench uses credits; included credits do not roll over; extra credits "don't add capacity; more requires an Enterprise plan". Enterprise is custom, with automations "built and maintained by Ramain", private deployment, BAA and DPA.Source
    • Your websiteHomepage (checked November 9, 2026): H1 "Meet Ramain. An AI employee for every process."; CTAs "Book a demo" and "Get a workflow assessment"; FAQ answer "Most workflows are live in hours"; results "1,500 doctor contracts a month", "60% lower cost than manual work", "$2.5B in loans locked a year" and "16 people's worth of work"; SOC 2 Type I, ISO 27001:2022, HIPAA-aligned with a BAA, GDPR with a DPA; work can be requested by email, Slack, text, WhatsApp, schedule or API; no prices on the page.Source

Big bets 4

Larger plays that can change the trajectory.

  • 17

    Ramain's strongest proof is in mortgage: a lock desk running for 7 independent mortgage banks, locks cut from 40 minutes to 15, 70% lower cost and $2.5 billion a year locked. The mortgage page says the product was "Built inside a working lock desk" and checks 18 investor portals daily. Lenders think in cost per loan, not agent hours.

    High impactHigh effort First result in 1 quarter CEO

    First action

    Work out the current cost per lock from the BPO's run data.

    How to measure it

    Per-lock customers

    Now
    –
    Target
    10 lenders
    By
    3 quarters

    Steps

    1. 1

      Cost per lock

      Agent hours, exceptions and support per lock today.

      CTO (co-founder) 1 week

    2. 2

      Price it

      Per lock and per rate-sheet pull, with a monthly minimum.

      CEO (co-founder) 2 weeks

    3. 3

      Standardise setup

      Common investor portals preconfigured.

      CTO (co-founder) 1 month

    4. 4

      Write the offer page

      On the mortgage industry page with the story.

      Founding GTM Engineer 1 week

    5. 5

      Sign three lenders

      Direct and via BPO partners.

      CEO (co-founder) 1 quarter

    6. 6

      Review margin

      Per-lock margin and exception rates.

      CEO (co-founder) monthly

    First result
    1 quarter
    Cost
    Two quarters of founder and engineering focus
    Owner
    CEO (co founder)

    Smallest test

    Quote per-lock pricing to the next two mortgage prospects and compare close rates.

    Why it works

    Package a lock-desk service for independent mortgage banks priced per lock (and per rate-sheet pull), covering setup, the investor portal connections, exception hand-off to the lender's staff and the audit trail. Use the existing BPO customer as reference and design partner, and sell it to lenders directly or through BPO partners (idea 7).

    Per-loan pricing matches how lenders budget and makes the saving obvious; one well-proven vertical package can be repeated across hundreds of similar lenders.

    Risks and how to handle them

    • Volume swings with interest rates

      Set a monthly minimum and offer rate-sheet work that runs daily regardless.

    • Margin risk on complex locks

      Price exceptions separately.

    Builds on

    Evidence

    • Your websiteLock-desk story: the customer is a BPO that runs loan locking for 7 US independent mortgage banks; each lock fell from 40 minutes to 15; "$2.5 billion a year in loans locked autonomously", locks for more than 1,000 homeowners a month and 70% lower cost for the BPO; exceptions such as a pricing conflict are handed to a person on the lock desk.Source
    • Your websiteIndustry pages: the healthcare page ("Payer portal work, done before it holds up a claim.") links to no customer story or research post, although a healthcare billing story and two dental eligibility posts exist; the mortgage page ("Built inside a working lock desk.", "18 investor portals checked every day", maps one workflow in about an hour) names no customer story, although the lock-desk story exists.Source
  • 18

    Ramain already writes about healthcare economics (two dental eligibility posts, one arguing to "Count every eligibility touch"), has a healthcare billing customer, connects to Epic, Cerner, athenahealth, Meditech and payer portals, and offers HIPAA-aligned controls with a BAA. But the eligibility post gives no dollar figures and the healthcare page links to none of it.

    High impactHigh effort First result in 1 quarter CEO

    First action

    Get the billing customer's checks per month and minutes per check, before and after.

    How to measure it

    Eligibility package customers

    Now
    –
    Target
    8
    By
    3 quarters

    Steps

    1. 1

      Gather numbers

      Volumes, minutes, error and denial rates from the billing customer.

      CEO (co-founder) 2 weeks

    2. 2

      Rewrite the post

      Add real dollar figures and a calculator.

      Founding GTM Engineer 1 week

    3. 3

      Package the worker

      Preconfigured for the most common payer portals.

      CTO (co-founder) 1 month

    4. 4

      Price per check

      With a monthly minimum.

      CEO (co-founder) 1 week

    5. 5

      Launch the page

      On the healthcare industry page with the story.

      Founding GTM Engineer 1 week

    6. 6

      Sell

      Billing companies and dental groups via outbound and BPO partners.

      Founding GTM Engineer 1 quarter

    First result
    1 quarter
    Cost
    A quarter of engineering focus plus compliance review
    Owner
    CEO (co founder)

    Smallest test

    Publish the eligibility cost model with real numbers and count demo requests.

    Why it works

    Turn this into a named product for billing companies and multi-site dental groups: eligibility checks before each appointment, claim status follow-up and payer portal entry, sold per check with a fixed monthly minimum. Publish the cost model with real numbers from the billing customer, a calculator for checks per month, and a story with time to go live.

    Eligibility checks are high-volume, rule-bound portal work, exactly what Ramain does best, and buyers already measure them per check.

    Risks and how to handle them

    • Payer portals change often

      Use the recovery agent and report fixes in the monthly report.

    • Compliance reviews slow deals

      Lead with the BAA and audit trail in the first call.

    Builds on

    Evidence

    • Your websiteIndustry pages: the healthcare page ("Payer portal work, done before it holds up a claim.") links to no customer story or research post, although a healthcare billing story and two dental eligibility posts exist; the mortgage page ("Built inside a working lock desk.", "18 investor portals checked every day", maps one workflow in about an hour) names no customer story, although the lock-desk story exists.Source
    • Your websiteResearch: 18 posts, filtered by Benchmarks, Platform, Economics, Mortgage and lending, Healthcare operations and BPO operations; no newsletter signup and no RSS feed; dates appear in two formats ("Sep 24, 2026" and "2026-10-18"); posts have X and LinkedIn share buttons. "The manual dental eligibility cost you are not tracking" says "Count every eligibility touch" but gives no dollar figures.Source
    • Your websiteConnectors page: 60 connectors in 12 categories, including SAP, Oracle, NetSuite, Workday, Coupa, QuickBooks, Salesforce, ServiceNow, ICE Encompass, Optimal Blue, Applied Epic, EZLynx, Epic, Cerner, athenahealth, Veeva PromoMats, Adobe Sign, SAP TM and MercuryGate; no connector has its own page, and many cards (such as SAP Concur, Zoho Books and Excel) link nowhere.Source
  • 19

    Ramain leads four public benchmarks (99.3% Online-Mind2Web, 99.2% WebVoyager, 89.4% WorkArena L3, 84.2% WebArena-Verified Hard at $0.21 per task), but most of these test everyday websites, while buyers care about lock desks, payer portals and ERPs. The new research engineer is hired to train and evaluate agents on verification and learning from every run.

    High impactHigh effort First result in 2 quarters Founding AI/ML Research Engin…

    First action

    Draft 50 task definitions from existing customer workflows, anonymised.

    How to measure it

    Benchmark-sourced demos

    Now
    –
    Target
    10 a month
    By
    3 quarters

    Steps

    1. 1

      Define tasks

      50 anonymised tasks from real workflows.

      Founding AI/ML Research Engineer 1 month

    2. 2

      Build sandboxes

      Portal and ERP patterns with changing screens.

      Founding AI/ML Research Engineer 2 months

    3. 3

      Set scoring

      Completion, correctness, cost, recovery.

      Founding AI/ML Research Engineer 2 weeks

    4. 4

      Run and publish

      Results, method and code.

      CTO (co-founder) 1 month

    5. 5

      Invite submissions

      A public leaderboard.

      Founding GTM Engineer ongoing

    6. 6

      Refresh

      New tasks each quarter.

      Founding AI/ML Research Engineer quarterly

    First result
    2 quarters
    Cost
    One researcher for a quarter plus compute
    Owner
    Founding AI/ML Research Engineer

    Smallest test

    Publish 10 tasks and Ramain's results as a research post.

    Why it works

    Build and open-source a benchmark of realistic enterprise back-office tasks on sandboxed copies of common portal and ERP patterns (rate locks, invoice posting, eligibility checks, order entry), scored on completion, correctness, cost and recovery after screen changes. Publish Ramain's results with full method, invite other agents to submit, and update it quarterly.

    Whoever defines the benchmark buyers trust frames the category; it also gives sales a neutral, technical answer to "how do you compare?".

    Risks and how to handle them

    • Seen as self-serving

      Open-source everything and report all tasks, as the current benchmark page does.

    Evidence

    • Your websiteBenchmarks page: Online-Mind2Web 99.3%, WebVoyager 99.2%, WorkArena L3 89.4% and WebArena-Verified Hard 84.2%, at "$0.21 per task", which the page says is 36% less than browser-use on the same model; all tasks are reported.Source
    • HiringFounding AI/ML Research Engineer: "Train and evaluate the agents that do the work: computer use, verification and learning from every run". Ramain is in Y Combinator's W26 batch, founded in 2025, with a team of 7 in San Francisco.Source
  • 20

    Ramain lists 60 systems and has run the same kinds of work repeatedly (invoices into SAP, orders into NetSuite, contracts in Adobe Sign, locks in investor portals), but every new customer starts by teaching a workflow from scratch, and building uses credits. The platform already saves runs as editable workflows and SOPs.

    High impactHigh effort First result in 1 quarter CTO

    First action

    Pick ten workflows that have run for more than one customer.

    How to measure it

    Template-started workflows

    Now
    –
    Target
    40%
    By
    3 quarters

    Steps

    1. 1

      Find repeats

      Workflows built more than once.

      CTO (co-founder) 1 week

    2. 2

      Generalise

      Strip customer data; keep SOP, inputs and approvals.

      CTO (co-founder) 1 month

    3. 3

      Build the clone flow

      Template to workspace in one step.

      CTO (co-founder) 1 month

    4. 4

      Publish the library

      Public pages linked from connectors.

      Founding engineer (website) 2 weeks

    5. 5

      Add monthly

      New templates from customer work.

      CTO (co-founder) monthly

    6. 6

      Measure

      Template use and time to first run.

      Founding GTM Engineer monthly

    First result
    1 quarter
    Cost
    A quarter of engineering
    Owner
    CTO (co founder)

    Smallest test

    Offer three templates privately to new workspaces.

    Why it works

    Turn proven workflows into templates: "Post a supplier invoice to SAP", "Sync orders into NetSuite", "Send a contract in Adobe Sign", "Check claim status in a payer portal". Each template carries its SOP, inputs and approval steps; customers clone it, point it at their login and adjust. Show the library publicly, linked from each connector page.

    Templates cut time to first value and credits spent building, and a public library is searchable proof of depth per system.

    Risks and how to handle them

    • Customer process details leak into templates

      Review each template for customer-specific data before publishing.

    Builds on

    Evidence

    • Your websiteConnectors page: 60 connectors in 12 categories, including SAP, Oracle, NetSuite, Workday, Coupa, QuickBooks, Salesforce, ServiceNow, ICE Encompass, Optimal Blue, Applied Epic, EZLynx, Epic, Cerner, athenahealth, Veeva PromoMats, Adobe Sign, SAP TM and MercuryGate; no connector has its own page, and many cards (such as SAP Concur, Zoho Books and Excel) link nowhere.Source
    • Your websitePlatform page: build ("Describe the task."), run, watch ("See every run.", with live view and step-by-step replay), recover ("When a website changes, the work carries on."), control and connect; a managed service: "We build it with you, and we keep it running."; CTAs "Book a demo", "Watch it work" and "Read the benchmarks".Source
    • Your websitePricing page: "Pay for the work, not the seats." Platform is "$1,500/month" with 150,000 credits, then $0.01 per credit (187 Junior, 150 Senior or 125 Veteran agent hours), unlimited team members, "50 active workflows, 5 running at once", and a "Start building" button that goes to the sign-in page of platform.ramain.ai. Agent hours cost $8 (Junior), $10 (Senior, default) or $12 (Veteran). Building and testing in the Workbench uses credits; included credits do not roll over; extra credits "don't add capacity; more requires an Enterprise plan". Enterprise is custom, with automations "built and maintained by Ramain", private deployment, BAA and DPA.Source

Wildcards 2

Unexpected experiments, each with a cheap way to test it.

  • 21

    Every Ramain run is recorded and replayable step by step, and the platform page invites visitors to "Watch it work", but the proof on the site is numbers and text. Buyers asking "can it really handle our portal?" are told to book a demo to find out.

    Medium impactMedium effort First result in 1 month Founding GTM Engineer

    First action

    Record a rate-sheet pull and a recovery run on demo data.

    How to measure it

    Replay-to-demo rate

    Now
    –
    Target
    2x site average
    By
    90 days

    Steps

    1. 1

      Pick runs

      One per industry, plus recovery and exception runs.

      Founding GTM Engineer 2 days

    2. 2

      Record on demo data

      No customer data or credentials on screen.

      CTO (co-founder) 1 week

    3. 3

      Add time and cost

      Overlay elapsed time and credits used.

      Founding engineer (website) 3 days

    4. 4

      Build the gallery

      Filtered by industry and system.

      Founding engineer (website) 1 week

    5. 5

      Embed

      Homepage, industry and connector pages.

      Founding engineer (website) 2 days

    6. 6

      Measure

      Watch rate and demo rate after watching.

      Founding GTM Engineer monthly

    First result
    1 month
    Cost
    Staff time
    Owner
    Founding GTM Engineer

    Smallest test

    Embed one replay on the mortgage page and compare its demo rate.

    Why it works

    Publish a gallery of 10-15 short, redacted replays of real work on demo data: a rate lock in an investor portal, an invoice posted to an ERP, a payer portal claim check, a recovery after a screen change, an exception handed to a person. Each replay shows elapsed time and cost, and links to the matching story and "Book a demo". Embed the best one on the homepage.

    Seeing a worker recover from a changed screen answers the main objection to UI automation faster than any claim, and replays are shareable in buying committees.

    Risks and how to handle them

    • Sensitive data in recordings

      Use only demo accounts and review every frame.

    Evidence

    • Your websitePlatform page: build ("Describe the task."), run, watch ("See every run.", with live view and step-by-step replay), recover ("When a website changes, the work carries on."), control and connect; a managed service: "We build it with you, and we keep it running."; CTAs "Book a demo", "Watch it work" and "Read the benchmarks".Source
    • Your websiteHomepage (checked November 9, 2026): H1 "Meet Ramain. An AI employee for every process."; CTAs "Book a demo" and "Get a workflow assessment"; FAQ answer "Most workflows are live in hours"; results "1,500 doctor contracts a month", "60% lower cost than manual work", "$2.5B in loans locked a year" and "16 people's worth of work"; SOC 2 Type I, ISO 27001:2022, HIPAA-aligned with a BAA, GDPR with a DPA; work can be requested by email, Slack, text, WhatsApp, schedule or API; no prices on the page.Source
  • 22

    Ramain sells "an AI employee for every process", and its YC profile says Ramain employees "join your team just like a human". Operations managers already think in roles (lock desk assistant, AP clerk, eligibility specialist) and write job descriptions for them, but Ramain's pages are organised by industry and feature.

    Medium impactLow effort First result in 1 month Founding GTM Engineer

    First action

    Write the AI Lock Desk Assistant page from the lock-desk story.

    How to measure it

    Role-page demos

    Now
    –
    Target
    10 a month
    By
    90 days

    Steps

    1. 1

      Choose roles

      Five roles matched to existing stories.

      Founding GTM Engineer 1 day

    2. 2

      Write the template

      Duties, systems, hours, escalations, cost, references.

      Founding GTM Engineer 2 days

    3. 3

      Write five pages

      One per role.

      Founding GTM Engineer 1 week

    4. 4

      Publish

      Under /employees/ and in the sitemap.

      Founding engineer (website) 2 days

    5. 5

      Use in outbound

      Link the matching role in job-post outreach.

      Founding GTM Engineer ongoing

    6. 6

      Measure

      Search entries and demos per role page.

      Founding GTM Engineer monthly

    First result
    1 month
    Cost
    $0
    Owner
    Founding GTM Engineer

    Smallest test

    Publish one role page and use it in 50 outbound emails.

    Why it works

    Create a set of pages written as job descriptions for AI employees: "AI Lock Desk Assistant", "AI Accounts Payable Clerk", "AI Eligibility Verification Specialist", "AI Order Entry Clerk". Each lists responsibilities, systems used, hours worked, what it escalates to a person, cost per month at the agent-hour rate, and "references" (the matching customer story). End with "Hire this employee" leading to the first-workflow offer.

    It matches how buyers frame the problem and how they search when they are about to hire, and it pairs naturally with the job-post outbound in idea 9.

    Risks and how to handle them

    • Reads as replacing staff

      Show the person the AI employee reports to and what stays with people.

    Builds on

    Evidence

    • Your websiteHomepage (checked November 9, 2026): H1 "Meet Ramain. An AI employee for every process."; CTAs "Book a demo" and "Get a workflow assessment"; FAQ answer "Most workflows are live in hours"; results "1,500 doctor contracts a month", "60% lower cost than manual work", "$2.5B in loans locked a year" and "16 people's worth of work"; SOC 2 Type I, ISO 27001:2022, HIPAA-aligned with a BAA, GDPR with a DPA; work can be requested by email, Slack, text, WhatsApp, schedule or API; no prices on the page.Source
    • Y CombinatorYC profile: "RamAIn Employees join your team just like a human"; launch post "Teach AI to use your legacy systems, desktop applications and web portals just like a human" and "if you can see it, RamAIn can do it"; target teams include procurement, insurance brokerage, healthcare, revenue cycle management, finance and operations, retail, pharmacy and logistics.Source
    • HiringFounding GTM Engineer (San Francisco, $120K–$180K, 0.30%–1.20% equity): owns top-of-funnel outbound (lead enrichment, best-fit customer profile scoring, AI-personalized sequences, deliverability), builds automations that detect buying signals and trigger outreach, owns the CRM, tests new channels and automates manual GTM work. Careers page: "Own go-to-market with the founders: outbound, the enterprise pipeline, demos and the systems that run them."Source

03

How Programmable can help

Where an idea in this playbook is something Programmable builds or runs, it's listed here with what we'd do. Everything else is yours to run.

Have it built

ProgrammableAgency

1 of the 22 ideas are things Programmable builds and runs for its customers: pages, outreach, prospect lists, booking flows and monitors. Pick one, or send the whole list.

Prospect lists1The list compiled from public sources, verified, deduplicated and delivered to your CRM.

A 30-minute session with the engineer who would build it, not a sales call. You leave with a plan whether or not you hire us.

Book a working session

Usually live within days.

Tools for the rest

ProgrammableInfo

Turn the research into a list you can act on

These ideas start with finding the right companies. Info finds them and the right person at each, researches every one and drafts the outreach, then asks before it sends.

  • Build this list in Info for idea #1 (opens programmable.info in a new tab)
  • Build this list in Info for idea #9 (opens programmable.info in a new tab)

New accounts: 100,000 free credits with code BETA100K

Find the companies (opens programmable.info in a new tab)
More example playbooks and reviews
ProgrammableDigital

Show Ramain’s product working

Turn screenshots or the website into an animated product demo in its own brand, for the homepage, launch posts and outreach in this playbook.

Make a demo (opens programmable.digital in a new tab)

More growth playbooks

Other companies we have researched, each read from what they are hiring for.

  • CodeBlu Development growth strategyA Cincinnati custom software studio that builds mission-critical web, mobile, AI and integration systems, led by an active…23 growth ideas
  • Finsai Trade growth strategyAn online multi-asset broker offering forex, crypto, stock, metal, commodity, energy and index CFDs on MetaTrader 5, with copy trading and…24 growth ideas
  • Vetcove growth strategyA free purchasing platform where veterinary clinics compare and buy from all their suppliers at once, plus Vetcove Home Delivery (branded…22 growth ideas
  • Take-Two Interactive growth strategyA video game developer and publisher whose labels include Rockstar Games, 2K, Zynga and Ghost Story Games; take2games.com is its…21 growth ideas
  • Matik growth strategyAutomates data-driven presentations, documents and emails: it pulls live data from CRMs, BI tools and warehouses into a company's own…21 growth ideas
  • Faros growth strategyA token engineering platform that connects AI coding spend to shipped outcomes, routes tasks to the best-value models using evals built…20 growth ideas
  • LeaseLeads growth strategyApartment marketing technology: conversion-focused property websites, a video-powered Virtual Leasing Agent with AI chat, TrueRent…21 growth ideas
  • QC Growth growth strategyAn embedded go-to-market agency: a pod of GTM lead, GTM engineer and outbound support that builds the CRM, signal and reporting systems…23 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 10, 2026, and cites them throughout. Ramain did not commission, review or endorse it, and Programmable is not affiliated with Ramain. Company and product names are trademarks of their owners, used only to identify them. The ideas are suggestions and opinion, not professional, legal or financial advice, and not statements about how Ramain runs its business.

Something wrong, or do you represent Ramain? Email [email protected] and we will correct it or take it down.

30/60/90 roadmap

What to focus on in each month, and the ideas that carry it.

  1. Days 1 to 306 ideas

    Make pricing, developers and connectors findable on every page, offer a fixed-price first workflow, link industry pages to their proof, strengthen the stories, fix the real-visitor load time and add share images.

    Programmable can ship 1 of these in days.

  2. Days 31 to 6010 ideas

    Open the BPO partner programme, build connector pages, start job-post signal outbound, add the savings calculator, the research email, the RPA migration offer, a faster developer start, monthly work reports, a concurrency add-on and the second-workflow programme.

  3. Days 61 to 906 ideas

    Commit to the big bets and wildcards: per-lock pricing for lenders, a packaged eligibility worker, an enterprise-portal benchmark, a workflow library, a public replay gallery and AI employee job descriptions.

The research behind the plan

3 research areas, each summarised in a few lines. Open any of them for the full detail.

Customers

What customers say

Customers value work done in the systems they already use, with no API or IT project. The most cited problem: manual re-keying across portals and ERPs.

  • Large, measurable time savings (a lock from 40 minutes to 15)
  • RPA scripts that break when a screen changes
  • In their words: “by hand”

Market

Competitive landscape

4 competitors compared: Skyvern, Browser Use, UiPath and Legacy RPA (Automation Anywhere, Blue Prism, Power Automate).

  • Gap to exploit: Vertical digital workers with industry proof (lock desks, payer portals)
  • Skyvern: Horizontal browser automation, less vertical proof
  • Browser Use: Developer tool, not a managed digital worker for operations teams

Hiring signals

Ramain's two open roles show where a team of 7 is putting its next hires: go-to-market and agent quality.

  • Founding GTM Engineer: Outbound, buying signals, CRM and demos with the founders. Ideas 1, 8, 9, 10, 11, 22.
  • Founding AI/ML Research Engineer: Agent training, verification and learning from every run. Idea 19.

From the team that wrote this playbook

All products
  • ProgrammableAgencyWorking AI systems in days, not quarters (opens programmable.agency in a new tab)
  • ProgrammableInfoAn agent that finds, researches and asks firstNew accounts get 100,000 free enrichment credits with code BETA100K (opens programmable.info in a new tab)
  • ProgrammableDigitalScreenshots in, an animated product demo out (opens programmable.digital in a new tab)
  • ProgrammableWatchKnow the day a supplier falls out of compliance (opens programmable.watch in a new tab)
  • ProgrammableTalkGet registrants for your events, and know who’s coming (opens programmable.talk in a new tab)
  • ProgrammableMediaAn AI note taker, interpreter and webinar host for your calls (opens programmable.media in a new tab)
  • ProgrammablePageText what you need, your customer gets a page that works (opens programmable.page in a new tab)
  • ProgrammableCommunityForums with labelled AI members, never empty (opens programmable.community in a new tab)
ProgrammableMarketing
ExamplesLeaderboardsProductsTermsPrivacyCookiesDPALegalContact

© 2026 AI-Powered Growth Intelligence