ProgrammableMarketing/a0.dev (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 · 12
  • Big bets · 3
  • Wildcards · 1
Generated Nov 10, 2026 2 views
  1. Programmable
  2. Playbooks
  3. a0.dev
a0.dev logo

growth playbook · Nov 10, 2026

a0.dev (opens in a new tab)

a0.dev growth playbook

Diagnosis

a0.dev is a three-person YC W25 company with real reach (it claims 200k+ users and 300k+ apps) and is now hiring its first Growth Lead and Brand and Content Lead to go from hundreds of thousands to tens of millions of users. The product promise is clear: build mobile apps, make money. The storefront around it is not yet doing its job.

The iOS app behind the homepage badge is listed as "a0.dev Analytics" in Education and says it cannot preview apps; the pricing and showcase pages are empty to search engines and AI assistants; four different user numbers appear across the site and job posts; use-case pages promise church or salon apps but show none; and competitors' blogs now write the pages people find when they search "a0 dev pricing" or "a0 dev alternatives".

This playbook fixes those first, then builds proof (real app numbers, example apps per use case), activation (first app on a phone in minutes), and loops (a "Built with a0" credit, creator programme, revenue updates) the new hires can own.

Growth Score

6/10

Biggest Opportunity

a0's users publish apps into the same stores a0 sells in. Turning 300k+ apps, their store listings and their makers' earnings into visible proof and distribution is something no landing page can buy.

Biggest Risk

Rork, Vibecode and Anything make the same "chat to a mobile app, ship and earn" promise, Vibecode's app has thousands of App Store ratings, and credit cost is the recurring complaint about a0; if first builds burn credits before reaching a phone, paid acquisition will leak.

01

Start here

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

  1. 1

    Make the iOS app listing match the homepage: the badge promises "test, edit, and deploy", the listing says "a0.dev Analytics" in Education

    Write the new iOS title, subtitle and first three screenshot captions, using the Google Play title as the starting point.

    High impact First result in 2 weeks
  2. 2

    Put the plans, prices and credit limits in the pricing page itself, not only after scripts run

    Move the plan data from the client fetch into the server-rendered page.

    High impact First result in 2 weeks
  3. 3

    Publish a0's own pricing, alternatives and "a0 vs" pages, before competitors' blogs define them

    List the branded queries in Search Console and pick the four with the most impressions.

    High impact First result in 1 month

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.

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 · 2Big bets · 12Fill-ins · 6Reconsider · 2
Effort →

Showing 22 of 22 ideas

This week 6

Quick wins with a clear first action.

  • 01

    The homepage says the a0.dev mobile app lets you "Test, edit, and deploy your apps from anywhere. Available on Android and iOS." Its App Store badge opens a listing titled "a0.dev Analytics", subtitle "Check your a0 Projects", in the Education category, whose description says "Previewing your a0 app is not supported in this app." It has too few ratings to show a score. The Google Play listing is called "AI App Builder - a0.dev". So iPhone visitors, the core audience of a company that ships iOS apps, are promised one thing on the website and shown another in the store, and the iOS listing doesn't show up for the searches that matter ("AI app builder"). Vibecode, a direct rival, shows a 4.6 rating from 3,324 App Store ratings on its homepage.

    High impactLow effort First result in 2 weeks Founding Growth Lead

    First action

    Write the new iOS title, subtitle and first three screenshot captions, using the Google Play title as the starting point.

    How to measure it

    Weekly iOS installs (App Store Connect, by source)

    Now
    –
    Target
    2x the current weekly rate, and 100+ ratings
    By
    60 days

    Steps

    1. 1

      Decide the app's job

      Companion builder (test, edit, deploy) or analytics only; write it in one sentence used on both the homepage and the listing.

      Founder/CEO 1 day

    2. 2

      Rewrite the listing

      Title and subtitle with 'AI app builder', category Developer Tools or Productivity, description covering chat, preview, publish, payments and stats.

      Founding Growth Lead 2 days

    3. 3

      New screenshots

      Five screens: describe the app, see it build, preview, publish to the stores, watch users and revenue.

      Founding Brand and Content Lead 3 days

    4. 4

      Align the homepage

      Make the 'a0.dev mobile app' section say exactly what the app does, and link each badge to the right store.

      Founding Engineer (Full Stack) 2 hours

    5. 5

      Add a rating prompt

      Ask for a rating after the first successful publish or first revenue notification, never at first launch.

      Founding Engineer (Full Stack) 2 days

    6. 6

      Submit and match Play

      Ship the metadata update and bring the Google Play listing copy into line.

      Founding Growth Lead 1 week

    7. 7

      Measure

      Installs by source, conversion from product page views, ratings count, weekly.

      Founding Growth Lead weekly

    First result
    2 weeks
    Cost
    Staff time only
    Owner
    Founding Growth Lead

    Smallest test

    Change only the title, subtitle and category this week and compare product page conversion over 14 days.

    Why it works

    Decide what the iOS app is for and say it the same way in both places. If it is the companion for testing, editing and deploying, rename the listing to match Google Play ("AI App Builder - a0.dev" or similar), move it to Developer Tools or Productivity, rewrite the subtitle and description around building and shipping apps from the phone, and add screenshots of the chat, a live preview and the publish flow. If it really is analytics only, change the homepage section to say so ("Track your live apps' users and revenue") and give the builder its own listing later. Either way, add an in-app rating prompt after a user's first successful publish or first revenue notification, so the listing builds the ratings that Vibecode already shows off.

    App Store search ranks on title, subtitle and category, and visitors decide from the name and first screenshots. A listing that matches the promise on the site stops the drop-off between badge and install, and the rating prompt timed to a success moment builds social proof in the channel a0's own users publish to.

    Ready to use

    ChecklistiOS listing fix list (if the app is the companion builder)

    [ ] Title: a0.dev - AI App Builder
    [ ] Subtitle: Build, test and ship mobile apps
    [ ] Category: Developer Tools
    [ ] First lines: Describe your app idea and a0 builds it. Test it on your phone, make changes by chatting, and publish to the App Store and Google Play. Track your users, subscriptions and revenue in one place.
    [ ] Screenshots: 1 Describe your app. 2 Watch it build. 3 Test it on your phone. 4 Publish to the stores. 5 See your users and revenue.
    [ ] Homepage 'a0.dev mobile app' text matches the listing
    [ ] Rating prompt after first publish or first revenue notification

    Risks and how to handle them

    • Promising features the iOS app does not have, which App Review can reject

      Describe only what ships today; if preview is missing on iOS, say 'track and publish' until it is added.

    • Rating prompts annoy users

      Use the system prompt once, only after a success moment.

    Evidence

    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source
    • App StoreThe iOS app the homepage App Store badge links to (checked twice, November 9, 2026) is titled "a0.dev Analytics", subtitle "Check your a0 Projects", category "Education"; its description lists "View the stats of your live a0 app" and "Get notifications about your a0 project" and says "Note: Previewing your a0 app is not supported in this app."; ratings: "This app hasn't received enough ratings or reviews to display an overview."Source
    • Google PlayThe Google Play badge on the homepage leads to a listing titled "AI App Builder - a0.dev".Source
    • Competitor researchVibecode's homepage: "Build mobile and web apps with AI"; its mobile app has been on the App Store since June 2025 with a 4.6 out of 5 rating from 3,324 ratings (as of October 2026); its templates are working iPhone apps users remix by chatting.Source
  • 02

    As served, a0.dev/pricing contains only "Choose your plan" and "Pick a plan that best suits you"; the Pro ($20/mo) and Max ($200/mo) plans appear only after scripts load. Search engines and AI assistants that read the page source see no prices, which is why third-party blogs fill the gap with their own estimates (one says plans run up to about $800/month).

    High impactLow effort First result in 2 weeks Founding Engineer

    First action

    Move the plan data from the client fetch into the server-rendered page.

    How to measure it

    Pricing-page visitors who start a paid plan

    Now
    –
    Target
    +15%
    By
    60 days

    Steps

    1. 1

      Server-render the plans

      Same component, data at build or request time.

      Founding Engineer (Full Stack) 1 day

    2. 2

      Explain credits

      One line per plan on what a credit or message buys and the limits.

      Founder/CEO 1 day

    3. 3

      Write the FAQ

      Six questions from support and Discord.

      Founding Growth Lead 1 day

    4. 4

      Add structured data

      Product and Offer markup with prices.

      Founding Engineer (Full Stack) 2 hours

    5. 5

      Title and description

      Include 'from $20/month' and what Pro includes.

      Founding Growth Lead 1 hour

    6. 6

      Check what crawlers see

      Fetch the page without scripts and in Search Console.

      Founding Engineer (Full Stack) 1 hour

    First result
    2 weeks
    Cost
    $0
    Owner
    Founding Engineer (Full Stack)

    Smallest test

    Server-render the two plan cards today and check the page source.

    Why it works

    Render the plan table on the server: plan names, monthly prices, what a credit or message buys, daily and monthly limits, and what happens when they run out. Add a short FAQ ("How many messages does a typical app take?", "Can I publish on Pro?", "Do unused credits roll over?") and Product/Offer structured data. Give the page a real title and meta description with the prices.

    Price is the first question for a $20 tool, and the answer has to be readable by the systems that now answer it for people. First-party numbers replace guesses written by competitors.

    Risks and how to handle them

    • Prices change often

      Read them from one source so the page and checkout always match.

    Evidence

    • Your websitePricing page as served (before scripts run) reads only "Choose your plan", "Pick a plan that best suits you. Upgrade or downgrade any time." and "Need help? Contact us": no plan names, prices, credit limits or FAQ. A browser scan found the plans load later as Pro at $20/mo and Max at $200/mo.Source
    • Search resultsVP0, which sells an iOS app design library, published "a0 dev pricing 2026 explained" (June 2026, updated June 29): it estimates a0 plans from a free tier and Pro at $20/month up to about $800/month for heavy use, says messages per screen drive the real cost, and steers readers to VP0. The same site has "a0 dev vs rork" and "a0 dev alternatives reddit" pages.Source
  • 03

    People searching a0 by name now land on pages written by vendors that sell something else: VP0 has "a0 dev pricing 2026 explained", "a0 dev vs rork" and "a0 dev alternatives reddit"; Banani's "A0.dev Alternatives" (October 2026) puts its own tool first. a0's sitemap has no comparison or alternatives page at all, and the Growth Lead role explicitly owns SEO and AI search visibility.

    High impactMedium effort First result in 1 month Founding Growth Lead

    First action

    List the branded queries in Search Console and pick the four with the most impressions.

    How to measure it

    Search Console clicks on 'a0 vs', 'a0 pricing', 'a0 alternatives'

    Now
    –
    Target
    Rank first for 3 of 4 queries
    By
    90 days

    Steps

    1. 1

      Pick queries

      Branded pricing, alternatives and vs queries by impressions.

      Founding Growth Lead 1 day

    2. 2

      Check rival facts

      Each rival's current homepage and pricing, dated.

      Founding Growth Lead 2 days

    3. 3

      Write the pages

      Fair tables, one worked cost example, honest 'better fit' notes.

      Founding Brand and Content Lead 1 week

    4. 4

      Founder review

      Accuracy on what a0 does and does not do.

      Founder/CTO 1 day

    5. 5

      Publish and link

      Sitemap, footer and pricing page links.

      Founding Engineer (Full Stack) 1 day

    6. 6

      Refresh

      Re-check rival facts every quarter.

      Founding Growth Lead quarterly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Founding Growth Lead

    Smallest test

    Publish 'a0 pricing explained' first and watch its ranking for two weeks.

    Why it works

    Publish four first-party pages: "a0 pricing explained" (with a worked example of what a typical app costs in messages), "a0 vs Rork", "a0 vs Vibecode" and "a0 vs Anything". Each one gives a fair table (platforms, publishing to each store, payments, analytics, code export, pricing) and a 'when the other tool is the better fit' line. Add them to the sitemap and footer.

    Branded comparison searches come from people already deciding. Answering them on a0.dev gives the buyer accurate numbers and gives AI assistants a primary source to quote.

    Risks and how to handle them

    • Claims about rivals go out of date

      Date every table and cite each rival's own page.

    Builds on

    Evidence

    • Search resultsVP0, which sells an iOS app design library, published "a0 dev pricing 2026 explained" (June 2026, updated June 29): it estimates a0 plans from a free tier and Pro at $20/month up to about $800/month for heavy use, says messages per screen drive the real cost, and steers readers to VP0. The same site has "a0 dev vs rork" and "a0 dev alternatives reddit" pages.Source
    • Search resultsBanani, an AI UI prototyping tool, published "A0.dev Alternatives: 9 Best AI Mobile App Builders in 2026" (October 22, 2026), recommending its own tool first and Rork for full-stack publishing.Source
    • Your websiteUse-case pages: the sitemap has 17 URLs, the homepage, /use-cases and 15 use-case pages (church, festival, gym/trainer, restaurant/café, salon/barbershop, youth sports, real estate portal, artist/band, local delivery, HOA, schools/PTA, coaches/consultants, field inspection, Google Sheets to app, passive income), and no blog or showcase URLs. The pages checked each show a headline, a prompt box "Create a mobile app that ..." with "Build it", "130,000+ users", "4.9/5 rating" and "Backed by YC", but no example app, screenshot, template or FAQ.Source
    • HiringFounding Growth Lead (Contract-to-Hire, San Francisco, $140K–$180K, 0.40%–1.00% equity): the post says a0 has helped over 300k people and aims to grow from hundreds of thousands to tens of millions of users; the role owns paid acquisition (Meta, TikTok, Google), SEO and AI search visibility, landing page, signup and onboarding conversion, lifecycle and re-engagement, viral and referral loops, experiments, attribution and dashboards, and works with engineering on the AI's prompts and capabilities.Source
  • 04

    The homepage says 200k+ users and 300k+ apps; all use-case pages say 130,000+ users and a 4.9/5 rating with no source; the YC launch post says 100k+ developers; the job posts say a0 has helped over 300k people. A careful visitor moving from a use-case page to the homepage sees the number change by 70,000, and the rating has no visible source.

    Medium impactLow effort First result in 1 week Founding Brand and Content Le…

    First action

    Pull today's real counts of users, apps created and apps published.

    How to measure it

    Use-case page signup conversion

    Now
    –
    Target
    +10%
    By
    45 days

    Steps

    1. 1

      Pull the counts

      Users, apps created, apps live in each store, as of a date.

      Founder/CTO 1 day

    2. 2

      Source the rating

      Name the source and count, or drop it.

      Founding Brand and Content Lead 1 day

    3. 3

      Build one component

      A shared proof bar used by the homepage and every use-case page.

      Founding Engineer (Full Stack) 2 hours

    4. 4

      Update off-site

      YC profile and job posts.

      Founder/CEO 1 hour

    5. 5

      Schedule refresh

      Update the numbers monthly from the database.

      Founding Engineer (Full Stack) monthly

    6. 6

      Test the lead number

      Apps published vs users as the headline proof.

      Founding Growth Lead 3 weeks

    First result
    1 week
    Cost
    $0
    Owner
    Founding Brand and Content Lead

    Smallest test

    Replace the use-case proof bar with the homepage numbers today.

    Why it works

    Pick one dated, defensible set of numbers (users, apps created, apps published to the stores) and put them in one shared component used on every page. Either source the 4.9/5 rating (where it comes from, how many ratings) or remove it. Update the job posts and YC profile to match.

    Consistent, sourced numbers read as true; numbers that drift read as marketing. This matters more for a young company asking people to trust it with their app and payments.

    Risks and how to handle them

    • The true number is smaller than a current claim

      Lead with apps published, which is the most impressive verifiable count.

    Evidence

    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source
    • Your websiteUse-case pages: the sitemap has 17 URLs, the homepage, /use-cases and 15 use-case pages (church, festival, gym/trainer, restaurant/café, salon/barbershop, youth sports, real estate portal, artist/band, local delivery, HOA, schools/PTA, coaches/consultants, field inspection, Google Sheets to app, passive income), and no blog or showcase URLs. The pages checked each show a headline, a prompt box "Create a mobile app that ..." with "Build it", "130,000+ users", "4.9/5 rating" and "Backed by YC", but no example app, screenshot, template or FAQ.Source
    • Y CombinatorY Combinator profile: Winter 2025 batch, team size 3, San Francisco, "We make mobile apps using AI"; the Phase 1 launch post reported 100k+ developers on the platform.Source
    • HiringFounding Growth Lead (Contract-to-Hire, San Francisco, $140K–$180K, 0.40%–1.00% equity): the post says a0 has helped over 300k people and aims to grow from hundreds of thousands to tens of millions of users; the role owns paid acquisition (Meta, TikTok, Google), SEO and AI search visibility, landing page, signup and onboarding conversion, lifecycle and re-engagement, viral and referral loops, experiments, attribution and dashboards, and works with engineering on the AI's prompts and capabilities.Source
  • 05

    Real visitors fail Core Web Vitals on a0.dev: the main content takes 6.6 s to appear on phones at the 75th percentile and interactions take 516 ms. The homepage downloads 10.2 MB, 6.4 MB of it images, about 6.2 MB from the file host behind the showcase and media, and PageSpeed says better image delivery alone would save 5.9 MB. The audience comes from TikTok, Reels and X, mostly on phones, and the Growth Lead is about to spend on Meta and TikTok traffic.

    High impactMedium effort First result in 1 month Founding Engineer

    First action

    Run the showcase images through the image optimiser and set cache headers.

    How to measure it

    Mobile LCP p75 (CrUX)

    Now
    –
    Target
    Under 2.5 s, INP under 200 ms
    By
    60 days

    Steps

    1. 1

      Optimise images

      Resized modern formats, explicit sizes.

      Founding Engineer (Full Stack) 1 day

    2. 2

      Cache them

      Long cache lifetimes for static media.

      Founding Engineer (Full Stack) 2 hours

    3. 3

      De-duplicate the showcase

      Render each card once; animate with CSS.

      Founding Engineer (Full Stack) 1 day

    4. 4

      Lazy-load below the fold

      Showcase, testimonials and badges.

      Founding Engineer (Full Stack) 1 day

    5. 5

      Defer non-critical tags

      Load tags not needed for the first view after interaction.

      Founding Growth Lead 1 day

    6. 6

      Measure

      PageSpeed weekly; CrUX after 28 days.

      Founding Engineer (Full Stack) weekly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Founding Engineer (Full Stack)

    Smallest test

    Optimise the showcase images alone and re-run PageSpeed.

    Why it works

    Serve showcase images as resized WebP/AVIF through the Next.js image pipeline with long cache lifetimes, lazy-load everything below the prompt box, stop repeating the showcase cards several times in the markup, and render the prompt box (the largest element) without waiting for scripts. Move tags that are not needed for the first paint behind user interaction.

    Paid social clicks bounce fast on slow pages; every second saved before the prompt box appears is more people typing their first idea.

    Risks and how to handle them

    • Ad attribution drops if tags are deferred too far

      Keep the conversion tag immediate; defer only the rest.

    Evidence

    • PageSpeedGoogle PageSpeed (homepage, November 2026): mobile performance 55 (desktop 86); real visitors fail Core Web Vitals (LCP 6.6 s and INP 516 ms at the 75th percentile; CLS 0.05 passes); the page downloads 10.2 MB in 107 requests, 6.4 MB of it images and about 6.2 MB from the Supabase file host; "Improve image delivery" could save 5.9 MB; the largest element is the sample prompt "Build a fun multiplayer app I can play with my friends."; the homepage has no H1 and no page language, and some buttons have no accessible name.Source
    • HiringFounding Growth Lead (Contract-to-Hire, San Francisco, $140K–$180K, 0.40%–1.00% equity): the post says a0 has helped over 300k people and aims to grow from hundreds of thousands to tens of millions of users; the role owns paid acquisition (Meta, TikTok, Google), SEO and AI search visibility, landing page, signup and onboarding conversion, lifecycle and re-engagement, viral and referral loops, experiments, attribution and dashboards, and works with engineering on the AI's prompts and capabilities.Source
  • 06

    PageSpeed finds no H1 and no language attribute on the homepage, and buttons without accessible names; the footer still says "© 2025". The page title says "Ship Mobile Apps to App Store & Google Play with AI", but nothing in the page marks it as the main heading.

    Low impactLow effort First result in 1 week Founding Engineer

    First action

    Add the H1 and lang attribute.

    How to measure it

    Accessibility score (mobile)

    Now
    –
    Target
    95+
    By
    2 weeks

    Steps

    1. 1

      Add H1

      One H1 with the core promise.

      Founding Engineer (Full Stack) 30 minutes

    2. 2

      Set language

      lang="en" on the html element.

      Founding Engineer (Full Stack) 5 minutes

    3. 3

      Name buttons

      aria-labels on icon buttons.

      Founding Engineer (Full Stack) 1 hour

    4. 4

      Fix contrast

      The flagged text colours.

      Founding Brand and Content Lead 1 hour

    5. 5

      Auto year

      Copyright year from the build date.

      Founding Engineer (Full Stack) 5 minutes

    6. 6

      Apply to use-case pages

      Same template fixes.

      Founding Engineer (Full Stack) 1 hour

    First result
    1 week
    Cost
    $0
    Owner
    Founding Engineer (Full Stack)

    Smallest test

    Ship the H1 and lang today.

    Why it works

    Make "Build mobile apps. Make money." (or the title phrase) a real H1, set lang="en", give icon buttons aria-labels, fix the contrast issue and make the copyright year automatic.

    These are the signals search engines, screen readers and AI summarisers use to understand the page; they cost an hour.

    Risks and how to handle them

    • Design changes from a visible H1

      Style the H1 like the current headline.

    Evidence

    • PageSpeedGoogle PageSpeed (homepage, November 2026): mobile performance 55 (desktop 86); real visitors fail Core Web Vitals (LCP 6.6 s and INP 516 ms at the 75th percentile; CLS 0.05 passes); the page downloads 10.2 MB in 107 requests, 6.4 MB of it images and about 6.2 MB from the Supabase file host; "Improve image delivery" could save 5.9 MB; the largest element is the sample prompt "Build a fun multiplayer app I can play with my friends."; the homepage has no H1 and no page language, and some buttons have no accessible name.Source
    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source

This quarter 12

The core plays for the next three months.

  • 07

    The homepage section is called "Real apps, real numbers. All made with a0.", but its seven cards show only an app name and a creator, with no numbers or store links, and the same cards repeat several times. The showcase page as served has no app list at all. Rork's homepage leads with one creator's App Store business; a0, whose tagline is "Make money", shows none.

    High impactMedium effort First result in 1 month Founding Brand and Content Le…

    First action

    Pull the top 30 published apps by users and revenue from a0's analytics.

    How to measure it

    Homepage to first prompt rate

    Now
    –
    Target
    +15%
    By
    60 days

    Steps

    1. 1

      Find the winners

      Top 30 live apps by users and revenue.

      Founder/CTO 1 day

    2. 2

      Ask for consent

      Opt-in to show a number, a screenshot and a store link.

      Founding Brand and Content Lead 1 week

    3. 3

      Write build stories

      One line each: idea, time to publish, result.

      Founding Brand and Content Lead 1 week

    4. 4

      Rebuild the cards

      Number, badge and link; each card once.

      Founding Engineer (Full Stack) 3 days

    5. 5

      Indexable showcase

      Server-rendered /showcase and per-app pages in the sitemap.

      Founding Engineer (Full Stack) 1 week

    6. 6

      Refresh monthly

      Update numbers and rotate in new winners.

      Founding Brand and Content Lead monthly

    First result
    1 month
    Cost
    Staff time; optional small thank-you credits for makers
    Owner
    Founding Brand and Content Lead

    Smallest test

    Add numbers to three cards and A/B the section.

    Why it works

    Ask the makers of the top 30 apps (by users or revenue in a0's own analytics) to opt in to showing a real number: downloads, chart position, monthly revenue or subscribers. Each card gets that number, the store badge, a screenshot and a one-line build story. Make /showcase server-rendered with one page per app (/showcase/<app>) that search engines can index.

    "Make money" is the promise; a verified result from an ordinary maker is the proof. Per-app pages also rank for app names and give makers something to share.

    Risks and how to handle them

    • Revenue claims read as income promises

      Show verified figures with dates and note that results vary.

    • Showcased apps that copy famous titles

      Feature original apps only.

    Builds on

    Evidence

    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source
    • Your websiteShowcase page as served reads "Explore apps. Get inspired." and "From games to productivity tools"; the app list loads only in the browser, so no app names, creators or store links are in the page source.Source
    • Competitor researchRork's homepage: "Create mobile apps by chatting with AI, ship to App Store and start making money", featuring one creator's App Store business as a "journey to a million dollars" and a Rork Max app to "publish iOS apps on the go". Anything's homepage: "Turn your words into mobile apps, sites, tools, and products".Source
  • 08

    a0 has 15 use-case pages (church, salon, gym, HOA, schools/PTA, field inspection and more) promising things like "Sermons, Events, Giving" or "Booking, Reviews, Loyalty". Each page is a headline, a prompt box and a proof bar: no example app, screenshot, template or FAQ. A church administrator or salon owner, who is not a developer, has nothing to picture. Vibecode offers working template apps users remix by chatting.

    High impactMedium effort First result in 1 month Founding Growth Lead

    First action

    Build the church and salon examples first and record them.

    How to measure it

    Use-case visitors who start a build

    Now
    –
    Target
    +30%
    By
    90 days

    Steps

    1. 1

      Rank pages

      Use-case pages by traffic and signups.

      Founding Growth Lead 1 day

    2. 2

      Build examples

      One polished app per page, made in a0.

      Founding Engineer (Full Stack) 3 weeks

    3. 3

      Capture

      Screenshots and a 30-second recording each.

      Founding Brand and Content Lead 1 week

    4. 4

      Remix button

      Open the builder with the example project cloned.

      Founder/CTO 1 week

    5. 5

      Write FAQs

      Five questions each, from real user questions.

      Founding Brand and Content Lead 1 week

    6. 6

      Add FAQ markup

      Structured data for each FAQ.

      Founding Engineer (Full Stack) 1 day

    7. 7

      Measure by page

      Build and publish rates per use case.

      Founding Growth Lead monthly

    First result
    1 month
    Cost
    About 3 weeks of build time plus content
    Owner
    Founding Growth Lead

    Smallest test

    Add one example to the church page and compare its build rate with the restaurant page.

    Why it works

    Build one good example app per use case with a0 itself, publish a screenshot strip and a short screen recording on the page, list the features it includes, and add a 'Remix this app' button that opens the builder with the example loaded. Add a five-question FAQ per page (cost, publishing under your own name, payments or giving, updates, who maintains it).

    Non-technical buyers decide from seeing the finished thing. An example also shortens the first build, so fewer credits are spent before the user sees value.

    Risks and how to handle them

    • Examples go stale as the builder changes

      Rebuild each example quarterly as a regression test.

    Evidence

    • Your websiteUse-case pages: the sitemap has 17 URLs, the homepage, /use-cases and 15 use-case pages (church, festival, gym/trainer, restaurant/café, salon/barbershop, youth sports, real estate portal, artist/band, local delivery, HOA, schools/PTA, coaches/consultants, field inspection, Google Sheets to app, passive income), and no blog or showcase URLs. The pages checked each show a headline, a prompt box "Create a mobile app that ..." with "Build it", "130,000+ users", "4.9/5 rating" and "Backed by YC", but no example app, screenshot, template or FAQ.Source
    • Competitor researchVibecode's homepage: "Build mobile and web apps with AI"; its mobile app has been on the App Store since June 2025 with a 4.6 out of 5 rating from 3,324 ratings (as of October 2026); its templates are working iPhone apps users remix by chatting.Source
  • 09

    Every use-case page ends in the same half-written prompt, "Create a mobile app that ...", and a "Build it" button. The Growth Lead owns signup and onboarding conversion and attribution. If the use case and the visitor's typed idea are not carried through signup into the first chat, the specific intent the page created is lost.

    Medium impactLow effort First result in 3 weeks Founding Growth Lead

    First action

    Check what happens today to a prompt typed before signup.

    How to measure it

    Signup to first preview (use-case traffic)

    Now
    –
    Target
    +20%
    By
    60 days

    Steps

    1. 1

      Audit the hand-off

      Type a prompt, sign up, see what survives.

      Founding Growth Lead 1 hour

    2. 2

      Write prompts

      One editable default prompt per use case.

      Founding Brand and Content Lead 2 days

    3. 3

      Persist the prompt

      Store it through signup and start the build after.

      Founding Engineer (Full Stack) 3 days

    4. 4

      Tag the account

      Use case as a user property for analytics and emails.

      Founding Engineer (Full Stack) 1 day

    5. 5

      Funnel dashboard

      Page view, prompt, signup, preview, publish.

      Founding Growth Lead 2 days

    6. 6

      Test defaults

      Pre-filled vs empty prompt box.

      Founding Growth Lead 3 weeks

    First result
    3 weeks
    Cost
    Engineering time
    Owner
    Founding Growth Lead

    Smallest test

    Pre-fill the prompt on two use-case pages and compare preview rates.

    Why it works

    Pre-fill each page's prompt box with a strong, editable use-case prompt ("Create a salon app with booking, stylist portfolios and a loyalty card"), keep whatever the visitor types through signup, start the build automatically after signup, and tag the account with the use case for onboarding and lifecycle messages.

    Momentum matters most in the first minute: a visitor who sees their own idea building straight after signup is far more likely to reach a working preview.

    Risks and how to handle them

    • Default prompts produce generic apps

      Ask one follow-up question (name, colours) before building.

    Evidence

    • Your websiteUse-case pages: the sitemap has 17 URLs, the homepage, /use-cases and 15 use-case pages (church, festival, gym/trainer, restaurant/café, salon/barbershop, youth sports, real estate portal, artist/band, local delivery, HOA, schools/PTA, coaches/consultants, field inspection, Google Sheets to app, passive income), and no blog or showcase URLs. The pages checked each show a headline, a prompt box "Create a mobile app that ..." with "Build it", "130,000+ users", "4.9/5 rating" and "Backed by YC", but no example app, screenshot, template or FAQ.Source
    • HiringFounding Growth Lead (Contract-to-Hire, San Francisco, $140K–$180K, 0.40%–1.00% equity): the post says a0 has helped over 300k people and aims to grow from hundreds of thousands to tens of millions of users; the role owns paid acquisition (Meta, TikTok, Google), SEO and AI search visibility, landing page, signup and onboarding conversion, lifecycle and re-engagement, viral and referral loops, experiments, attribution and dashboards, and works with engineering on the AI's prompts and capabilities.Source
  • 10

    a0's Phase 1 post promised iOS builds on your phone "in seconds" with a QR install code, and the homepage says you can test from the a0 mobile app. Holding your own app on your own phone is the moment the product feels real, but there is no visible measure of how many new users get there or how fast. The Growth Lead is hired to analyse user behaviour and work with engineering on the AI's capabilities.

    High impactMedium effort First result in 1 month Founder/CTO

    First action

    Instrument the time from signup to first device install.

    How to measure it

    First-session device installs

    Now
    –
    Target
    40% of new signups
    By
    90 days

    Steps

    1. 1

      Define the event

      First install on a real device, Android or iOS.

      Founder/CTO 1 day

    2. 2

      Instrument

      Timestamps for idea, preview, QR shown, install.

      Founding Engineer (Full Stack) 3 days

    3. 3

      Progress bar

      Three steps visible in the first session.

      Founding Engineer (Full Stack) 1 week

    4. 4

      Show QR early

      Offer install the moment a preview exists.

      Founder/CTO 3 days

    5. 5

      Fix the slowest step

      One per sprint, from the funnel data.

      Founder/CTO ongoing

    6. 6

      Weekly report

      Median minutes and install rate.

      Founding Growth Lead weekly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Founder/CTO

    Smallest test

    Show the QR install prompt automatically after the first preview for half of new users.

    Why it works

    Define activation as 'first build installed on the user's device' and instrument the steps to it. Put a progress bar in the first session (idea, preview, on your phone), offer the QR install as soon as a preview exists, and fix the slowest step each sprint. Report median minutes to first install weekly.

    An app on the home screen is something people show friends; a preview in a browser tab is easy to forget. One clear milestone also focuses the small team.

    Risks and how to handle them

    • iOS install needs a developer account

      Lead with the fastest available path per platform and explain the iOS step plainly.

    Evidence

    • Your websiteBlog: a single post, "a0.dev - Phase 1 (WAGMA)" (July 3, 2025), "We Are All Gonna Make Apps": iOS builds on your phone "in seconds" with a QR install code, one-click upload to App Store Connect, an Agent Mode that can "read logs", in-app payments in beta, Stripe for web apps, Convex and two-way GitHub sync. Nothing has been posted since.Source
    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source
    • HiringFounding Growth Lead (Contract-to-Hire, San Francisco, $140K–$180K, 0.40%–1.00% equity): the post says a0 has helped over 300k people and aims to grow from hundreds of thousands to tens of millions of users; the role owns paid acquisition (Meta, TikTok, Google), SEO and AI search visibility, landing page, signup and onboarding conversion, lifecycle and re-engagement, viral and referral loops, experiments, attribution and dashboards, and works with engineering on the AI's prompts and capabilities.Source
  • 11

    a0's journey has clear stages (idea, preview, device install, store account connected, published, earning), and the Growth Lead is hired to build lifecycle and re-engagement programmes. The site has no newsletter or live chat, and Brevo is already set up for email, so the plumbing exists but no stage-based programme is visible.

    High impactMedium effort First result in 1 month Founding Growth Lead

    First action

    Count users stalled at each stage over the last 30 days.

    How to measure it

    30-day publish rate

    Now
    –
    Target
    +25%
    By
    90 days

    Steps

    1. 1

      Map stages

      Six stages as tracked events.

      Founding Growth Lead 2 days

    2. 2

      Size the stalls

      Users stuck at each stage.

      Founding Growth Lead 1 day

    3. 3

      Write messages

      One email and one push per stall, linked to the project.

      Founding Brand and Content Lead 1 week

    4. 4

      Wire triggers

      Events to Brevo with stage timers.

      Founding Engineer (Full Stack) 1 week

    5. 5

      Holdout group

      10% get nothing, to measure lift.

      Founding Growth Lead 1 day

    6. 6

      Iterate

      Rewrite the weakest message each month.

      Founding Growth Lead monthly

    First result
    1 month
    Cost
    Email tool costs plus staff time
    Owner
    Founding Growth Lead

    Smallest test

    Email last month's 'preview but never installed' users the QR link.

    Why it works

    Send one short, useful message at each stall point: a prompt fix and an example for users stuck before preview; the QR install for users with a preview but no device install; a step-by-step store setup for users who have not connected App Store Connect or Google Play; and a payments setup guide for published apps with no paywall. Each message links straight back to the user's project.

    Most drop-off in app builders happens at specific, predictable steps; a nudge that solves the exact step converts far better than a generic newsletter.

    Risks and how to handle them

    • Too many messages

      One message per stage, cap at two a week.

    Builds on

    Evidence

    • HiringFounding Growth Lead (Contract-to-Hire, San Francisco, $140K–$180K, 0.40%–1.00% equity): the post says a0 has helped over 300k people and aims to grow from hundreds of thousands to tens of millions of users; the role owns paid acquisition (Meta, TikTok, Google), SEO and AI search visibility, landing page, signup and onboarding conversion, lifecycle and re-engagement, viral and referral loops, experiments, attribution and dashboards, and works with engineering on the AI's prompts and capabilities.Source
    • Site scanSite scan: Google Tag Manager, a Meta pixel, Stripe and Calendly load on the homepage; Brevo is verified for email; no newsletter signup or live chat was found; the site links to X, Discord and Reddit but not YouTube, TikTok or Instagram; one Hacker News mention (2 points).Source
    • Your websiteBlog: a single post, "a0.dev - Phase 1 (WAGMA)" (July 3, 2025), "We Are All Gonna Make Apps": iOS builds on your phone "in seconds" with a QR install code, one-click upload to App Store Connect, an Agent Mode that can "read logs", in-app payments in beta, Stripe for web apps, Convex and two-way GitHub sync. Nothing has been posted since.Source
  • 12

    a0 says 300k+ apps have been created and deployed to the App Store, Google Play and the web. Each published app has its own users, store page and screenshots, a distribution surface no ad budget can buy, and the Growth Lead is hired to design viral and referral loops. Today nothing on a published app points back to a0.

    High impactMedium effort First result in 2 months Founding Growth Lead

    First action

    Add the credit line to the store description template in the publish flow, opt-out by default for paid plans.

    How to measure it

    Referral signups per month

    Now
    –
    Target
    5% of new signups
    By
    2 quarters

    Steps

    1. 1

      Design the credit

      Small, consistent, on-brand; settings screen and store text.

      Founding Brand and Content Lead 3 days

    2. 2

      Referral codes

      Per-maker links with tracking.

      Founding Engineer (Full Stack) 1 week

    3. 3

      Add to publish flow

      Pre-filled, editable store description line.

      Founding Engineer (Full Stack) 3 days

    4. 4

      Set the reward

      Credits per referred signup and per paid upgrade.

      Founder/CEO 1 day

    5. 5

      Opt-out rules

      Paid plans can remove it; check store guidelines.

      Founder/CTO 2 days

    6. 6

      Measure

      Referral signups and conversion to paid.

      Founding Growth Lead monthly

    First result
    2 months
    Cost
    Engineering time plus referral credits
    Owner
    Founding Growth Lead

    Smallest test

    Add the line to store descriptions for new free-plan publishes for one month.

    Why it works

    Add an optional, tasteful credit: a 'Made with a0' line in the app's settings or about screen, a line in the store description generated by a0's publishing flow, and a link with the maker's referral code. Makers who keep it earn credits for each signup it brings; makers on paid plans can remove it.

    Every app built becomes a small ad seen by exactly the kind of person who might build one: someone using an indie app. Rewarding the maker turns the credit into their choice rather than a tax.

    Risks and how to handle them

    • Makers dislike branding in their app

      Keep it optional, out of the main screens and rewarded.

    Evidence

    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source
    • HiringFounding Growth Lead (Contract-to-Hire, San Francisco, $140K–$180K, 0.40%–1.00% equity): the post says a0 has helped over 300k people and aims to grow from hundreds of thousands to tens of millions of users; the role owns paid acquisition (Meta, TikTok, Google), SEO and AI search visibility, landing page, signup and onboarding conversion, lifecycle and re-engagement, viral and referral loops, experiments, attribution and dashboards, and works with engineering on the AI's prompts and capabilities.Source
  • 13

    a0's homepage testimonials are makers' own X posts: one thanks a0 for getting "another app charting in the app store", another says "my game is blowing up". The Brand and Content Lead is hired to build a UGC and creator programme as a distribution channel and to run TikTok, Reels and YouTube, yet the site links only to X, Discord and Reddit.

    High impactMedium effort First result in 1 month Founding Brand and Content Le…

    First action

    List makers who have posted about a0 and have published apps.

    How to measure it

    Creator-attributed signups

    Now
    –
    Target
    10% of new signups
    By
    2 quarters

    Steps

    1. 1

      Find makers

      Published apps plus an audience on any platform.

      Founding Brand and Content Lead 1 week

    2. 2

      Set the deal

      Fee or revenue share, credits, early access.

      Founder/CEO 3 days

    3. 3

      Brief

      Show the real build, the store listing and the result.

      Founding Brand and Content Lead 2 days

    4. 4

      Open accounts

      a0 on TikTok, Instagram and YouTube to repost.

      Founding Brand and Content Lead 1 day

    5. 5

      Turn into ads

      Best clips as Meta and TikTok creative.

      Founding Growth Lead monthly

    6. 6

      Track

      Signups and paid conversion by creator code.

      Founding Growth Lead monthly

    First result
    1 month
    Cost
    Creator fees and credits, a few thousand dollars a month
    Owner
    Founding Brand and Content Lead

    Smallest test

    Pay five makers for one video each this month.

    Why it works

    Recruit 20 makers with published apps and an audience into a paid programme: a monthly 'build my app' video each on TikTok, Reels or YouTube, early access to features, a referral code with revenue share, and a feature on the showcase. Re-cut the best clips into ads with the Growth Lead.

    A maker showing their own app earning money is the most believable version of 'Build mobile apps. Make money.' and the clips double as tested ad creative.

    Risks and how to handle them

    • Undisclosed sponsorship

      Require clear paid-partnership labels.

    Builds on

    Evidence

    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source
    • HiringFounding Brand and Content Lead (Contract-to-Hire, San Francisco, $140K–$180K): defines voice, positioning and messaging across the website, product and ads; runs organic content on TikTok, Reels, X, LinkedIn and YouTube; ghostwrites founder content; leads launch narratives; builds a UGC and creator program as a distribution channel; makes ad creative with the Growth Lead; turns user conversations into messaging and product input.Source
    • Site scanSite scan: Google Tag Manager, a Meta pixel, Stripe and Calendly load on the homepage; Brevo is verified for email; no newsletter signup or live chat was found; the site links to X, Discord and Reddit but not YouTube, TikTok or Instagram; one Hacker News mention (2 points).Source
  • 14

    The Growth Lead will run Meta, TikTok and Google, and a0 already has 15 use-case pages (church, gym, salon, schools, HOA and more). Sending each audience to its own page, rather than to the general homepage, gives clean read-outs of which verticals convert to paid, but only once those pages carry examples (idea 8) and load fast (idea 5).

    High impactMedium effort First result in 6 weeks Founding Growth Lead

    First action

    Choose five use cases and write one hook each.

    How to measure it

    Paid cost per published app

    Now
    –
    Target
    Find two verticals under the target payback
    By
    90 days

    Steps

    1. 1

      Pick five verticals

      By page traffic and audience clarity.

      Founding Growth Lead 1 day

    2. 2

      Make creative

      Screen recordings of each example app.

      Founding Brand and Content Lead 1 week

    3. 3

      Set tracking

      Signup, preview and publish events back to ad platforms.

      Founding Engineer (Full Stack) 3 days

    4. 4

      Launch

      Equal budgets on Meta and TikTok.

      Founding Growth Lead 1 day

    5. 5

      Read out

      Cost per published app after four weeks.

      Founding Growth Lead 4 weeks

    6. 6

      Scale or stop

      Double winners, cut the rest.

      Founder/CEO 1 day

    First result
    6 weeks
    Cost
    Test budget of a few thousand dollars
    Owner
    Founding Growth Lead

    Smallest test

    Run two verticals for two weeks.

    Why it works

    Run small, equal-budget tests for the five use cases with the clearest audiences, each with creative showing that exact app and landing on its page with the prompt pre-filled. Kill the bottom three after four weeks and scale the winners. Report cost per published app, not just cost per signup.

    Vertical creative and landing pages lift relevance, and measuring to 'published' avoids buying signups that never build.

    Risks and how to handle them

    • Small budgets give noisy results

      Judge on the full funnel and extend promising tests.

    Builds on

    Evidence

    • HiringFounding Growth Lead (Contract-to-Hire, San Francisco, $140K–$180K, 0.40%–1.00% equity): the post says a0 has helped over 300k people and aims to grow from hundreds of thousands to tens of millions of users; the role owns paid acquisition (Meta, TikTok, Google), SEO and AI search visibility, landing page, signup and onboarding conversion, lifecycle and re-engagement, viral and referral loops, experiments, attribution and dashboards, and works with engineering on the AI's prompts and capabilities.Source
    • Your websiteUse-case pages: the sitemap has 17 URLs, the homepage, /use-cases and 15 use-case pages (church, festival, gym/trainer, restaurant/café, salon/barbershop, youth sports, real estate portal, artist/band, local delivery, HOA, schools/PTA, coaches/consultants, field inspection, Google Sheets to app, passive income), and no blog or showcase URLs. The pages checked each show a headline, a prompt box "Create a mobile app that ..." with "Build it", "130,000+ users", "4.9/5 rating" and "Backed by YC", but no example app, screenshot, template or FAQ.Source
  • 15

    a0 already ships an iOS app whose job is to "View the stats of your live a0 app" and "Get notifications about your a0 project", and the homepage sells built-in payments and an analytics dashboard under the tagline "Make money". The moment a maker sees revenue or new users is the strongest reason to keep paying, but today it lives inside a dashboard they have to remember to open.

    High impactMedium effort First result in 1 month Founder/CTO

    First action

    Send a plain weekly stats email to makers with live apps.

    How to measure it

    Month-3 paid retention (live-app makers)

    Now
    –
    Target
    +10 points
    By
    2 quarters

    Steps

    1. 1

      Weekly digest

      Users, revenue and change vs last week.

      Founding Engineer (Full Stack) 1 week

    2. 2

      Suggested fix

      One rule-based recommendation per app.

      Founder/CTO 2 weeks

    3. 3

      One-tap prompt

      Open the project with the fix pre-written.

      Founding Engineer (Full Stack) 1 week

    4. 4

      Milestone cards

      First user, first dollar, 100 users.

      Founding Brand and Content Lead 1 week

    5. 5

      Push in the app

      Same digest in the mobile app.

      Founding Engineer (Full Stack) 1 week

    6. 6

      Measure

      Return sessions and paid retention vs holdout.

      Founding Growth Lead monthly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Founder/CTO

    Smallest test

    Email last week's stats to 500 makers with live apps and compare return visits.

    Why it works

    Send every maker with a live app a weekly push and email: new users, active users, subscription revenue and one suggested improvement ("add a paywall", "your onboarding loses 60% at screen 2: ask a0 to fix it") with a one-tap link that opens the fix as a prompt. Celebrate milestones (first user, first $1, first 100 users) with a shareable card.

    Makers who see progress come back to build more, which keeps them on paid plans; the suggested fix turns analytics into the next session.

    Risks and how to handle them

    • Zero-revenue apps make the digest discouraging

      Lead with the next step and progress, not only revenue.

    Builds on

    Evidence

    • App StoreThe iOS app the homepage App Store badge links to (checked twice, November 9, 2026) is titled "a0.dev Analytics", subtitle "Check your a0 Projects", category "Education"; its description lists "View the stats of your live a0 app" and "Get notifications about your a0 project" and says "Note: Previewing your a0 app is not supported in this app."; ratings: "This app hasn't received enough ratings or reviews to display an overview."Source
    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source
  • 16

    The recurring outside critique of a0 is cost, not capability: a competitor's pricing explainer says messages per screen, not the headline price, drive the real cost, and estimates heavy use at up to about $800/month. a0's pricing page as served explains no limits at all. Unpredictable spend is what pushes a $20 user to try Rork or Vibecode.

    High impactMedium effort First result in 1 month Founder/CEO

    First action

    Measure the median messages to a first published app.

    How to measure it

    Pro to Max or top-up conversion; churn reasons citing cost

    Now
    –
    Target
    +20% upgrades, -30% cost churn
    By
    2 quarters

    Steps

    1. 1

      Measure cost to publish

      Median and 90th percentile messages per published app.

      Founder/CTO 2 days

    2. 2

      Publish the guide

      Typical cost per app type on the pricing page.

      Founding Growth Lead 2 days

    3. 3

      Pre-run estimate

      Show expected cost for large requests.

      Founder/CTO 2 weeks

    4. 4

      Auto-refund failures

      Detect build errors caused by generated code and refund.

      Founder/CTO 2 weeks

    5. 5

      Top-up pack

      One-off credits between Pro and Max.

      Founding Engineer (Full Stack) 1 week

    6. 6

      Track churn reasons

      Cancellation survey with a cost option.

      Founding Growth Lead ongoing

    First result
    1 month
    Cost
    Engineering time plus refunded credits
    Owner
    Founder/CEO

    Smallest test

    Publish the 'typical cost per app' table and survey upgrade intent.

    Why it works

    Show an estimated message or credit cost before larger requests, a running total per project, and a 'typical app costs X messages' guide on the pricing page. When a0's own build or code error causes a failed run, refund it automatically and say so. Offer a one-time top-up pack instead of forcing an upgrade to Max.

    People pay more willingly when they know what they are paying for; refunding a0's own errors removes the most resented charge.

    Risks and how to handle them

    • Refunds get abused

      Refund only system-detected build failures, with a monthly cap.

    Builds on

    Evidence

    • Search resultsVP0, which sells an iOS app design library, published "a0 dev pricing 2026 explained" (June 2026, updated June 29): it estimates a0 plans from a free tier and Pro at $20/month up to about $800/month for heavy use, says messages per screen drive the real cost, and steers readers to VP0. The same site has "a0 dev vs rork" and "a0 dev alternatives reddit" pages.Source
    • Your websitePricing page as served (before scripts run) reads only "Choose your plan", "Pick a plan that best suits you. Upgrade or downgrade any time." and "Need help? Contact us": no plan names, prices, credit limits or FAQ. A browser scan found the plans load later as Pro at $20/mo and Max at $200/mo.Source
    • Competitor researchRork's homepage: "Create mobile apps by chatting with AI, ship to App Store and start making money", featuring one creator's App Store business as a "journey to a million dollars" and a Rork Max app to "publish iOS apps on the go". Anything's homepage: "Turn your words into mobile apps, sites, tools, and products".Source
  • 17

    The homepage promises one codebase shipped to the App Store, Google Play, APK and web, with built-in payments. The docs' Publishing section has one page, "Connect your App Store Connect Account". There is no guide for Google Play, APK, web or setting up payments, which are exactly the steps where makers get stuck and where searchers look for help.

    Medium impactLow effort First result in 1 month Founding Engineer

    First action

    Write the Google Play guide from the current flow.

    How to measure it

    Projects published to Google Play per week

    Now
    –
    Target
    +25%
    By
    90 days

    Steps

    1. 1

      List the gaps

      Every publish and payments step without a doc.

      Founding Engineer (Full Stack) 1 day

    2. 2

      Google Play guide

      Account, signing, listing, review.

      Founding Engineer (Full Stack) 2 days

    3. 3

      APK and web guides

      Share and host.

      Founding Engineer (Full Stack) 2 days

    4. 4

      Payments guides

      In-app subscriptions and Stripe for web.

      Founder/CTO 3 days

    5. 5

      Rejection guide

      Common store rejection reasons and fixes.

      Founding Engineer (Full Stack) 2 days

    6. 6

      Link from the product

      Contextual help links at each step.

      Founding Engineer (Full Stack) 1 day

    First result
    1 month
    Cost
    Staff time only
    Owner
    Founding Engineer (Full Stack)

    Smallest test

    Publish the Google Play guide and link it from the publish screen.

    Why it works

    Add five docs pages: publish to Google Play (developer account, signing, review), share an APK, publish to the web, set up in-app subscriptions, and accept payments with Stripe on web. Each page ends with 'do it in a0' and links back into the project. Add a 'why was my app rejected' page with the common store reasons and fixes.

    Publishing is the hardest step and the one a0 sells hardest. Good guides cut support load, lift the publish rate and rank for 'how to publish an app' searches.

    Risks and how to handle them

    • Store rules change

      Date each guide and review quarterly.

    Evidence

    • Your websiteDocs (docs.a0.dev): Prompting Guide (Quickstart), Agent Guide, Publishing with a single page, "Connect your App Store Connect Account", and Advanced ("Upgrading your Project"); no Google Play, APK, web or payments guide and no plans or credits page.Source
    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source
  • 18

    a0's blog has one post, "Phase 1 (WAGMA)" from July 3, 2025, and the sitemap includes no blog URLs. Since then the product has added Supabase support, Android, analytics and more, but none of it has a dated public record. The Brand and Content Lead is hired to lead launch narratives and ghostwrite founder content.

    Medium impactLow effort First result in 1 month Founding Brand and Content Le…

    First action

    Write the 'Since Phase 1' catch-up post.

    How to measure it

    Monthly blog sessions and signups

    Now
    –
    Target
    1 post a month; 5% of signups from blog
    By
    2 quarters

    Steps

    1. 1

      Catch-up post

      Everything shipped since July 2025.

      Founding Brand and Content Lead 1 week

    2. 2

      Template

      What shipped, clip, maker example.

      Founding Brand and Content Lead 1 day

    3. 3

      Fix the sitemap

      Include blog posts and dates.

      Founding Engineer (Full Stack) 1 hour

    4. 4

      Founder versions

      Ghostwritten X and LinkedIn posts.

      Founding Brand and Content Lead monthly

    5. 5

      Email it

      Monthly update to users.

      Founding Growth Lead monthly

    6. 6

      Review

      Which features drive return visits.

      Founding Growth Lead quarterly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Founding Brand and Content Lead

    Smallest test

    Publish the catch-up post and email it this month.

    Why it works

    Publish a short monthly changelog post (what shipped, a 30-second clip, one maker using it) and a longer launch post for each major feature. Add blog posts to the sitemap, cross-post the founder's version on X and LinkedIn, and send it to users by email.

    A visible pace of shipping is a reason to choose a young tool, and dated posts give search engines and AI assistants current facts about a0.

    Risks and how to handle them

    • Cadence slips

      Keep it short; one post a month is enough.

    Evidence

    • Your websiteBlog: a single post, "a0.dev - Phase 1 (WAGMA)" (July 3, 2025), "We Are All Gonna Make Apps": iOS builds on your phone "in seconds" with a QR install code, one-click upload to App Store Connect, an Agent Mode that can "read logs", in-app payments in beta, Stripe for web apps, Convex and two-way GitHub sync. Nothing has been posted since.Source
    • HiringFounding Brand and Content Lead (Contract-to-Hire, San Francisco, $140K–$180K): defines voice, positioning and messaging across the website, product and ads; runs organic content on TikTok, Reels, X, LinkedIn and YouTube; ghostwrites founder content; leads launch narratives; builds a UGC and creator program as a distribution channel; makes ad creative with the Growth Lead; turns user conversations into messaging and product input.Source
    • Your websiteUse-case pages: the sitemap has 17 URLs, the homepage, /use-cases and 15 use-case pages (church, festival, gym/trainer, restaurant/café, salon/barbershop, youth sports, real estate portal, artist/band, local delivery, HOA, schools/PTA, coaches/consultants, field inspection, Google Sheets to app, passive income), and no blog or showcase URLs. The pages checked each show a headline, a prompt box "Create a mobile app that ..." with "Build it", "130,000+ users", "4.9/5 rating" and "Backed by YC", but no example app, screenshot, template or FAQ.Source

Big bets 3

Larger plays that can change the trajectory.

  • 19

    a0 differs from general AI builders by owning the last mile: building, signing, creating the App Store Connect listing and uploading. Its claims count apps created and users, but the outcome makers pay for is an app that gets approved and goes live. The Growth Lead is hired to analyse behaviour and shape the AI's prompts and capabilities with engineering, and the Founding Engineer to build 'the future of AI-powered mobile app development'.

    High impactHigh effort First result in 1 quarter Founder/CTO

    First action

    Measure the current share of submitted builds approved first time.

    How to measure it

    Builds approved on first submission

    Now
    –
    Target
    +20 points
    By
    2 quarters

    Steps

    1. 1

      Define the funnel

      Created, built, submitted, approved, live.

      Founder/CTO 1 week

    2. 2

      Log rejection reasons

      Structured reasons from each store response.

      Founding Engineer (Full Stack) 2 weeks

    3. 3

      Top ten checks

      Automated checks for the most common failures.

      Founder/CTO 1 month

    4. 4

      Agent fixes

      One-tap fix for each failed check.

      Founder/CTO 1 month

    5. 5

      Dashboard

      Weekly north-star review.

      Founding Growth Lead weekly

    6. 6

      Go public

      Publish the approval rate on the homepage.

      Founding Brand and Content Lead when ready

    First result
    1 quarter
    Cost
    A quarter of engineering focus
    Owner
    Founder/CTO

    Smallest test

    Add the three most common rejection checks to the publish flow.

    Why it works

    Track the share of projects that reach a live store listing, and the reasons the rest don't (build failures, missing metadata, store rejections). Build a pre-submission check that reviews the app against the most common rejection reasons (missing privacy text, broken links, placeholder content, login demo accounts) and fixes them with the agent before upload. Publish the success rate once it is strong.

    A builder that gets apps approved more often is the clearest edge in a crowded 'chat to app' market, and the metric aligns product, growth and support on the outcome users actually want.

    Risks and how to handle them

    • Store rules shift

      Update checks from the logged rejection reasons each month.

    Builds on

    Evidence

    • Your websiteBlog: a single post, "a0.dev - Phase 1 (WAGMA)" (July 3, 2025), "We Are All Gonna Make Apps": iOS builds on your phone "in seconds" with a QR install code, one-click upload to App Store Connect, an Agent Mode that can "read logs", in-app payments in beta, Stripe for web apps, Convex and two-way GitHub sync. Nothing has been posted since.Source
    • HiringFounding Growth Lead (Contract-to-Hire, San Francisco, $140K–$180K, 0.40%–1.00% equity): the post says a0 has helped over 300k people and aims to grow from hundreds of thousands to tens of millions of users; the role owns paid acquisition (Meta, TikTok, Google), SEO and AI search visibility, landing page, signup and onboarding conversion, lifecycle and re-engagement, viral and referral loops, experiments, attribution and dashboards, and works with engineering on the AI's prompts and capabilities.Source
    • HiringCareers page: Founding Engineer [Full Stack], San Francisco, $140K–$240K, "to help us build the future of AI-powered mobile app development".Source
  • 20

    Half of a0's use-case pages target organisations that rarely build their own software: churches, HOAs, schools and PTAs, salons, youth sports clubs, field inspection teams. Many of them want the app, not the building. Meanwhile a0 has 200k+ users, some of whom already ship apps that chart. Nothing connects the two.

    Medium impactHigh effort First result in 1 quarter Founder/CEO

    First action

    Ask Discord which makers already build apps for clients.

    How to measure it

    Marketplace projects live

    Now
    –
    Target
    50
    By
    2 quarters

    Steps

    1. 1

      Recruit makers

      20 makers with published apps, by vertical.

      Founding Brand and Content Lead 3 weeks

    2. 2

      Request form

      On two use-case pages.

      Founding Engineer (Full Stack) 1 week

    3. 3

      Pricing rules

      Fixed-price packages and a0's fee.

      Founder/CEO 1 week

    4. 4

      Route requests

      Three quotes per request within 48 hours.

      Founding Growth Lead ongoing

    5. 5

      Quality checks

      Review delivered apps before launch.

      Founder/CTO ongoing

    6. 6

      Expand

      Add verticals that convert.

      Founder/CEO quarterly

    First result
    1 quarter
    Cost
    Staff time; low cash cost
    Owner
    Founder/CEO

    Smallest test

    Add a request form to the church page and hand-match the first ten requests.

    Why it works

    Add 'Have it built for you' on each use-case page: the organisation describes its needs, and the request goes to vetted a0 makers in that vertical who quote a fixed price. a0 takes a small fee or requires the app to run on a paid a0 plan. Start with two verticals and 20 vetted makers.

    It brings in buyers who would never open a builder, gives makers income (the 'make money' promise) and adds recurring paid projects to a0.

    Risks and how to handle them

    • Poor work damages the brand

      Vet makers and review apps before they ship.

    Builds on

    Evidence

    • Your websiteUse-case pages: the sitemap has 17 URLs, the homepage, /use-cases and 15 use-case pages (church, festival, gym/trainer, restaurant/café, salon/barbershop, youth sports, real estate portal, artist/band, local delivery, HOA, schools/PTA, coaches/consultants, field inspection, Google Sheets to app, passive income), and no blog or showcase URLs. The pages checked each show a headline, a prompt box "Create a mobile app that ..." with "Build it", "130,000+ users", "4.9/5 rating" and "Backed by YC", but no example app, screenshot, template or FAQ.Source
    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source
  • 21

    a0 says 300k+ apps have been created on it and deployed to the stores and web. That is an unusual dataset: what people build, which categories get published, how long it takes, which apps earn. The Brand and Content Lead is hired to lead launch narratives and shape how a0 shows up publicly, and the company has only one Hacker News mention so far.

    Medium impactMedium effort First result in 1 quarter Founding Brand and Content Le…

    First action

    List the ten statistics a0 can compute from its own data.

    How to measure it

    New referring domains from the report

    Now
    –
    Target
    50
    By
    90 days after launch

    Steps

    1. 1

      Pick the stats

      Ten that are interesting and safe to share.

      Founding Brand and Content Lead 1 week

    2. 2

      Compute

      Aggregate, anonymised queries.

      Founder/CTO 2 weeks

    3. 3

      Privacy review

      No user or app can be identified.

      Founder/CEO 3 days

    4. 4

      Design

      Report page and shareable charts.

      Founding Brand and Content Lead 2 weeks

    5. 5

      Launch

      Press, founder thread, Hacker News, Reddit.

      Founding Brand and Content Lead 1 week

    6. 6

      Repeat

      Annual, with a mid-year update.

      Founding Brand and Content Lead yearly

    First result
    1 quarter
    Cost
    Staff time; optional design help
    Owner
    Founding Brand and Content Lead

    Smallest test

    Post three stats as a founder thread and see the response.

    Why it works

    Publish an anonymised, aggregate report: the most-built app categories, median time from idea to store, share of apps with payments, which categories earn, and what changed over the year. Pair it with a press push, a founder thread and a data page that others can cite.

    Original data earns links, press and AI-assistant citations that product pages never get, and it positions a0 as the authority on AI-built mobile apps.

    Risks and how to handle them

    • Revealing too much to competitors

      Share trends and ratios, not funnels or revenue totals.

    Evidence

    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source
    • HiringFounding Brand and Content Lead (Contract-to-Hire, San Francisco, $140K–$180K): defines voice, positioning and messaging across the website, product and ads; runs organic content on TikTok, Reels, X, LinkedIn and YouTube; ghostwrites founder content; leads launch narratives; builds a UGC and creator program as a distribution channel; makes ad creative with the Growth Lead; turns user conversations into messaging and product input.Source
    • Site scanSite scan: Google Tag Manager, a Meta pixel, Stripe and Calendly load on the homepage; Brevo is verified for email; no newsletter signup or live chat was found; the site links to X, Discord and Reddit but not YouTube, TikTok or Instagram; one Hacker News mention (2 points).Source

Wildcards 1

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

  • 22

    a0's whole promise is speed from idea to store, and the Brand and Content Lead will run YouTube, TikTok and X and ghostwrite founder content. A live session where the team builds a viewer's idea and submits it to the store proves the claim in real time, including the messy parts, in a way edited ads can't.

    Medium impactLow effort First result in 2 weeks Founding Brand and Content Le…

    First action

    Ask Discord for this week's idea.

    How to measure it

    Signups per live session

    Now
    –
    Target
    300
    By
    90 days

    Steps

    1. 1

      Collect ideas

      Weekly thread in Discord and on X.

      Founding Brand and Content Lead weekly

    2. 2

      Set up the stream

      YouTube and X, with a phone camera.

      Founding Brand and Content Lead 1 day

    3. 3

      Build live

      One founder, 60 to 90 minutes, to submission.

      Founder/CEO weekly

    4. 4

      Cut clips

      Three shorts per session.

      Founding Brand and Content Lead weekly

    5. 5

      Follow up

      Post when the app is approved.

      Founding Brand and Content Lead weekly

    6. 6

      Track

      Viewers, clip reach and signups.

      Founding Growth Lead weekly

    First result
    2 weeks
    Cost
    Two hours of founder time a week
    Owner
    Founding Brand and Content Lead

    Smallest test

    Run one live build this week and count signups from its link.

    Why it works

    Every week, pick one idea from Discord or X, build it live on YouTube and X with a founder, install it on a phone on camera and submit it to the store before the session ends. Cut three short clips for TikTok and Reels and follow up when the app goes live.

    Live proof builds trust, the idea-giver shares it with their audience, and each stream becomes a week of short-form content.

    Risks and how to handle them

    • A build fails on air

      Show the fix; recovering live is part of the proof.

    Evidence

    • HiringFounding Brand and Content Lead (Contract-to-Hire, San Francisco, $140K–$180K): defines voice, positioning and messaging across the website, product and ads; runs organic content on TikTok, Reels, X, LinkedIn and YouTube; ghostwrites founder content; leads launch narratives; builds a UGC and creator program as a distribution channel; makes ad creative with the Growth Lead; turns user conversations into messaging and product input.Source
    • Your websiteHomepage (checked November 9, 2026): "Build mobile apps. Make money."; "200k+" users and "300k+" apps "deployed to the App Store, Google Play Store, and web"; one-click publishing, built-in payments and an analytics dashboard; the "a0.dev mobile app" section says "Test, edit, and deploy your apps from anywhere. Available on Android and iOS."; a "Real apps, real numbers. All made with a0." section whose seven app cards show only a name and creator, no numbers, repeated several times; testimonials are creators' X posts; footer "© 2025" with Twitter, Discord and Reddit links.Source
More example playbooks and reviews

More growth playbooks

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

  • Lighthouse growth strategyA commercial platform for hotels: market intelligence, AI pricing, business intelligence and benchmarking, direct booking, distribution…21 growth ideas
  • Sensor Tower growth strategyA digital market intelligence platform with data on mobile apps, gaming, digital advertising (Pathmatics), retail media, audiences and…22 growth ideas
  • Kettle & Fire growth strategyShelf-stable bone broths (beef, chicken, flavoured, reduced sodium, regenerative and wild), cooking broths and grass-fed beef tallow, sold…21 growth ideas
  • Alma growth strategyBuy now pay later for European merchants: payment in 2-4 instalments, pay later, longer financing and payment links, online and in store…22 growth ideas
  • ninjoo growth strategyA Dubai-based online concept store for premium active-lifestyle products: Bala, FOLD and FRAME reformers, Hyperice recovery, Modest…20 growth ideas
  • WEKA growth strategyNeuralMesh, a software platform that combines high-performance storage and extended GPU memory (Augmented Memory Grid) for AI training…23 growth ideas
  • RISIS growth strategySingapore heritage brand (since 1976) that encapsulates natural orchids in 24K Swiss gold and makes orchid jewellery, home and lifestyle…20 growth ideas
  • Vector Legal growth strategyAn AI-native law firm (Vector Legal, P.C.) for tech companies and their investors, paired with VectorOS, a legal operating system built by…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. a0.dev did not commission, review or endorse it, and Programmable is not affiliated with a0.dev. 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 a0.dev runs its business.

Something wrong, or do you represent a0.dev? 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

    Fix the iOS listing, put prices in the pricing page, publish first-party pricing and comparison pages, one proof number, homepage speed and basics.

  2. Days 31 to 6011 ideas

    Showcase with real numbers, example apps on use-case pages, prompt hand-off, time to first phone install, lifecycle by build stage, the "Built with a0" credit, creators, paid tests, credit clarity, publishing docs and a shipping log.

  3. Days 61 to 905 ideas

    Bigger bets: the earnings update as a retention product, publish success rate as the north star, a builder marketplace for local organisations, an annual report and a weekly live build.

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 going from an idea to an app in the stores without writing code. The most cited problem: credit and message limits that make costs hard to predict.

  • One codebase for App Store, Google Play, APK and web
  • The hard last mile of publishing: developer accounts, builds, review
  • In their words: “vibe coding”

Market

Competitive landscape

4 competitors compared: Rork, Vibecode, Anything and Design and prototyping tools (VP0, Banani).

  • Gap to exploit: Published, verifiable results per app built with an AI builder
  • Rork: Same promise as a0, little visible differentiation
  • Vibecode: iPhone-first native Swift focus

Hiring signals

a0 is a team of three hiring its first marketers and an engineer, which says growth is now the priority.

  • Founding Growth Lead (Contract-to-Hire): Paid, SEO and AI search, onboarding, lifecycle and referral loops. Ideas 1, 3, 9, 11, 12, 14.
  • Founding Brand and Content Lead (Contract-to-Hire): Positioning, short-form, launches and a creator programme. Ideas 4, 13, 18, 22.
  • Founding Engineer [Full Stack]: Product and site engineering for speed, docs and publishing. Ideas 5, 17, 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 first (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)
  • 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