ProgrammableMarketing/useiam.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 · 8
  • Big bets · 3
  • Wildcards · 3
Generated Nov 4, 2026
  1. Programmable
  2. Playbooks
  3. iAM
iAM logo

growth playbook · Nov 4, 2026

useiam.ai (opens in a new tab)

iAM growth playbook

Diagnosis

iAM is a private-beta AI concierge with a two-sided plan: consumers ask for outcomes, and businesses claim an @ that is recommended and sold inside the plans.

The product promise is clear on the business page, but the public web barely sees it: robots.txt and the sitemap redirect to sign-in, link previews point to a private preview address, the business page hides at /about, and "See it live" leads to a login.

This playbook fixes those front doors first, adds a waitlist with invites and a better claim flow, then builds density in one city and category, founding-business offers, monthly insight reports and group-plan sharing, and finally opens the @ to other AI agents and to personal recommenders.

Growth Score

5/10

Biggest Opportunity

Turn the @ itself into the acquisition engine: a findable, shareable claim page, a name checker and founding status, with density in one city so the first plans feel complete.

Biggest Risk

Agentic checkout from Stripe, OpenAI, Rye and Firmly lets many assistants sell for businesses, so iAM must win businesses with reach and insight before larger assistants make an extra storefront feel unnecessary.

01

Start here

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

  1. 1

    Make the "Claim your @" page findable and shareable: robots, sitemap and link previews

    Exempt /robots.txt, /sitemap.xml and /og.png from the auth middleware and redeploy.

    High impact First result in 2 weeks
  2. 2

    Make "See it live" show something live: a public sample plan instead of a sign-in page

    Record one real Stage plan from the beta and publish it as a page.

    High impact First result in 2 weeks
  3. 3

    Split the front door: a public homepage for newcomers, the app for beta testers

    Draft the logged-out homepage copy in one paragraph.

    High impact First result in 2 weeks

02

Your idea portfolio

20 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 · 4Big bets · 11Fill-ins · 4Reconsider · 1
Effort →

Showing 20 of 20 ideas

This week 6

Quick wins with a clear first action.

  • 01

    iAM's growth depends on businesses claiming their @, but the page that asks them is hard to reach from outside. robots.txt and sitemap.xml both redirect to the sign-in page, so search engines get a login form instead of a crawl file. Every page's link preview points its image at a Vercel preview address that asks for a Vercel sign-in, so a shared link shows no picture on LinkedIn, Slack or iMessage. And the business page sits at /about with the title "About iAM · iAM" and only the tagline as its description. Each founder post, cold email or partner mention that links to "Claim your @" loses clicks before anyone reads the pitch.

    High impactLow effort First result in 2 weeks Growth lead

    First action

    Exempt /robots.txt, /sitemap.xml and /og.png from the auth middleware and redeploy.

    How to measure it

    Business claims from links and search

    Now
    –
    Target
    +50%
    By
    30 days

    Steps

    1. 1

      Open the public files

      Exempt robots.txt, sitemap.xml, og.png and public pages from the sign-in redirect.

      Founding engineer 2 hours

    2. 2

      Fix the metadata base

      og:url, og:image and twitter:image on useiam.ai.

      Founding engineer 1 hour

    3. 3

      Give the page an address

      /business, with /about redirected to it.

      Founding engineer 2 hours

    4. 4

      Write title and description

      State the offer: free, pay only when you sell.

      Growth lead 1 hour

    5. 5

      Make a preview image

      A business-side image with the @ idea.

      Product designer 1 day

    6. 6

      Check previews

      LinkedIn Post Inspector, Slack and iMessage.

      Growth lead 1 hour

    7. 7

      Submit to search

      Search Console and Bing Webmaster Tools with the new sitemap.

      Growth lead 1 hour

    8. 8

      Tag every link

      UTM tags on founder posts and outreach to see what converts.

      Growth lead 1 day

    First result
    2 weeks
    Cost
    $0
    Owner
    Growth lead

    Smallest test

    Fix the og:image address and post the business page once with and once without a preview to compare clicks.

    Why it works

    Let robots.txt, sitemap.xml, /og.png and the public pages through the sign-in middleware. Serve a real robots file and a sitemap listing /about, /contact, /privacy and /terms. Set the metadata base to https://useiam.ai so og:url and og:image use the live domain. Give the business page its own address (/business, with /about redirecting), a title such as "Claim your @ — let AI sell for your business | iAM", a description that states the free, pay-on-sale offer, and its own preview image. Then check the page in LinkedIn Post Inspector and Google Search Console.

    This is a one-day engineering fix, and it improves every channel a growth hire will use. Links with a preview image get noticeably more clicks than bare links, and the business page can start ranking for searches like "sell on AI assistants" while competitors are still talking to developers.

    Ready to use

    ChecklistPublic-page launch list

    [ ] robots.txt served as text, app routes disallowed
    [ ] sitemap.xml lists /business, /contact, /privacy, /terms
    [ ] og:url and og:image on https://useiam.ai
    [ ] /business title and description
    [ ] Business preview image (1200x630)
    [ ] /about 301 to /business
    [ ] LinkedIn Post Inspector check
    [ ] Search Console sitemap submitted

    Risks and how to handle them

    • Private app pages get indexed

      List only public pages in the sitemap and keep app routes disallowed in robots.txt.

    • The /about link already circulates

      Keep a permanent redirect from /about.

    Evidence

    • Your websitehttps://useiam.ai/robots.txt and https://useiam.ai/sitemap.xml both redirect to the sign-in page (/login?callbackUrl=%2Frobots.txt and /login?callbackUrl=%2Fsitemap.xml), so search engines get an HTML login page instead of a robots file or a sitemap. Google PageSpeed's SEO audit flags "robots.txt is not valid" (SEO score 92).Source
    • Your websiteThe link-preview tags on the homepage, /about and /contact (og:url, og:image and twitter:image) point to a Vercel preview deployment address, not useiam.ai. That address redirects to a Vercel sign-in, so the preview image does not load for anyone outside the team. The same image is public at useiam.ai/og.png.Source
    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source
    • Google PageSpeedMobile performance 100/100 (desktop 100): largest paint 0.8 seconds, 508 KB page, 47 requests, about 107 KB of unused JavaScript. Chrome has no real-visitor speed data for useiam.ai yet, a sign of low public traffic.Source
  • 02

    Every "See it live" link on the business page goes to "/", which for anyone outside the beta is a sign-in page. A business owner who wants proof before claiming an @ hits a wall at the exact moment of interest.

    High impactMedium effort First result in 2 weeks Product designer

    First action

    Record one real Stage plan from the beta and publish it as a page.

    How to measure it

    Visitor-to-claim rate

    Now
    –
    Target
    +30%
    By
    45 days

    Steps

    1. 1

      Pick the request

      One that shows the Stage at its best.

      Founder & CEO 1 day

    2. 2

      Capture the plan

      Real output from the beta, with permission from any business shown.

      Founding engineer 1 day

    3. 3

      Design the page

      Read-only, with the @ highlighted.

      Product designer 3 days

    4. 4

      Build it

      Static page at /demo.

      Founding engineer 2 days

    5. 5

      Repoint links

      All "See it live" links to /demo.

      Founding engineer 1 hour

    6. 6

      Measure

      Clicks from /demo to Claim.

      Growth lead weekly

    First result
    2 weeks
    Cost
    Staff time only
    Owner
    Product designer

    Smallest test

    Repoint "See it live" to a short screen recording for one week.

    Why it works

    Build a public, read-only demo at /demo: one request ("Dinner for 6 on Friday") turned into a full Stage plan with sample businesses, showing where a business's @ appears and how it answers questions. Point every "See it live" link there, with "Claim your @" at the end.

    Owners trust what they can see. A concrete plan makes "placed in plans nobody made yet" believable without opening the beta.

    Risks and how to handle them

    • The demo looks staged

      Use a real beta plan and say so.

    Evidence

    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source
    • Your websiteHomepage (checked November 4, 2026): title "iAM — Say what you want. Get what you mean."; meta description ends "Private beta, open to beta testers only." A logged-out visitor gets the sign-in shell with a chat prompt "Where to today?" and suggestions "Dinner for 6 on Friday", "A gift under $50" and "What can you do?"; the server returns the /login page for "/".Source
    • Your websiteFeatures promised to businesses on /about: "Found by intent", "Placed in plans nobody made yet", "Sells for you, always on", "No lost checkouts", "Know your customers: Every chat shows you what people actually want", "The Stage: One request becomes a complete plan", and group planning: "People plan as a group inside iAM. Your @ joins because you fit what they're building." Onboarding: "Connect your business and iAM turns your products, knowledge, and voice into your @."Source
  • 03

    For logged-out visitors, useiam.ai is a sign-in page with a chat box, and the description says the beta is for testers only. Consumers and businesses arriving from search or a link see no explanation and no way to join.

    High impactMedium effort First result in 2 weeks Growth lead

    First action

    Draft the logged-out homepage copy in one paragraph.

    How to measure it

    Waitlist sign-ups

    Now
    –
    Target
    500 a week
    By
    60 days

    Steps

    1. 1

      Write the page

      One line, three examples, two calls to action.

      Growth lead 1 day

    2. 2

      Design

      Match the app's look.

      Product designer 2 days

    3. 3

      Route by session

      Logged-out sees the page, signed-in sees the app.

      Founding engineer 1 day

    4. 4

      Add the waitlist

      Email plus "what would you ask iAM?".

      Founding engineer 1 day

    5. 5

      Link businesses

      Clear link to /business.

      Founding engineer 1 hour

    6. 6

      Track

      Sign-ups and claims by source.

      Growth lead weekly

    First result
    2 weeks
    Cost
    Staff time only
    Owner
    Growth lead

    Smallest test

    Put a "Join the waitlist" link on the sign-in page today.

    Why it works

    Serve logged-out visitors a short public homepage: what iAM does in one line, the three sample requests as examples, a waitlist form for people and a "For businesses" link to the claim page. Keep the app at the same address for signed-in users.

    A two-sided marketplace needs two clear doors. Today neither side has one, and every visit that bounces is lost.

    Risks and how to handle them

    • Beta testers see the wrong page

      Check the session before rendering.

    Evidence

    • Your websiteHomepage (checked November 4, 2026): title "iAM — Say what you want. Get what you mean."; meta description ends "Private beta, open to beta testers only." A logged-out visitor gets the sign-in shell with a chat prompt "Where to today?" and suggestions "Dinner for 6 on Friday", "A gift under $50" and "What can you do?"; the server returns the /login page for "/".Source
    • Your websiteContact page: "Have a question, want into the private beta, or just want to tell us what you think? Send a message — a real person reads every one." There is no public waitlist or invite form; the logged-in app has Plans, Friends, Notifications, Bag, Create a Post and "Train your Genie".Source
    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source
  • 04

    Getting into the beta today means writing to the contact form, where "a real person reads every one". iAM is already social (Friends, group plans, posts), so invites fit the product.

    High impactLow effort First result in 2 weeks Growth lead

    First action

    Pick a waitlist tool and set the weekly invite size.

    How to measure it

    Invited sign-ups

    Now
    –
    Target
    40% of all sign-ups
    By
    60 days

    Steps

    1. 1

      Choose the tool

      Built-in or a waitlist service.

      Founding engineer 1 day

    2. 2

      Set the rules

      Moves per invite and weekly admits.

      Growth lead 1 day

    3. 3

      Add the question

      "What would you ask iAM first?"

      Growth lead 1 hour

    4. 4

      Launch

      On the new homepage.

      Founding engineer 2 days

    5. 5

      Admit weekly

      Top of the list.

      Founder & CEO weekly

    6. 6

      Read answers

      Group requests by category and city.

      Growth lead weekly

    First result
    2 weeks
    Cost
    Under $100 a month
    Owner
    Growth lead

    Smallest test

    Email the current contact-form requests an invite link and count shares.

    Why it works

    Replace the contact-form route with a waitlist that shows each person their place and a personal invite link. Every friend who joins moves them up; the top of the list gets in each week. Ask each signer what they would ask iAM first, and use the answers to pick launch categories.

    Waitlist referrals give a pre-launch product free reach, and the "first request" answers are market research for seeding supply.

    Risks and how to handle them

    • Fake sign-ups to jump the line

      Count only confirmed emails.

    Evidence

    • Your websiteContact page: "Have a question, want into the private beta, or just want to tell us what you think? Send a message — a real person reads every one." There is no public waitlist or invite form; the logged-in app has Plans, Friends, Notifications, Bag, Create a Post and "Train your Genie".Source
    • Your websiteHomepage (checked November 4, 2026): title "iAM — Say what you want. Get what you mean."; meta description ends "Private beta, open to beta testers only." A logged-out visitor gets the sign-in shell with a chat prompt "Where to today?" and suggestions "Dinner for 6 on Friday", "A gift under $50" and "What can you do?"; the server returns the /login page for "/".Source
    • Your websiteFeatures promised to businesses on /about: "Found by intent", "Placed in plans nobody made yet", "Sells for you, always on", "No lost checkouts", "Know your customers: Every chat shows you what people actually want", "The Stage: One request becomes a complete plan", and group planning: "People plan as a group inside iAM. Your @ joins because you fit what they're building." Onboarding: "Connect your business and iAM turns your products, knowledge, and voice into your @."Source
  • 05

    The claim form asks only for a username and email, and the success message says to check email to set a password and design a storefront. iAM does not learn what the business sells or where, and a claim that never sets a password is a lost business.

    High impactLow effort First result in 2 weeks Growth lead

    First action

    Count how many claims set a password today.

    How to measure it

    Claim-to-storefront rate

    Now
    –
    Target
    50%
    By
    60 days

    Steps

    1. 1

      Add the fields

      Category and city for business claims.

      Founding engineer 2 hours

    2. 2

      Write the emails

      Three, over seven days.

      Growth lead 1 day

    3. 3

      Set up sending

      From a person, not no-reply.

      Growth lead 1 day

    4. 4

      Founder notes

      A personal email per business.

      Founder & CEO daily

    5. 5

      Track the steps

      Claim, password, products, live.

      Founding engineer 1 day

    6. 6

      Review

      Where claims stall.

      Growth lead weekly

    First result
    2 weeks
    Cost
    $0
    Owner
    Growth lead

    Smallest test

    Email the last 20 claims personally and see how many go live.

    Why it works

    Add two fields for businesses: category and city (or "online only"). Send a three-email sequence: set your password, connect your products, see your first sample plan. Have the founder personally write to every business that claims, for now.

    Knowing category and city lets iAM seed supply where demand is, and fast personal follow-up is what turns a held username into a live storefront.

    Risks and how to handle them

    • Longer form lowers claims

      Make the new fields one tap each.

    Evidence

    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source
    • Your websiteFeatures promised to businesses on /about: "Found by intent", "Placed in plans nobody made yet", "Sells for you, always on", "No lost checkouts", "Know your customers: Every chat shows you what people actually want", "The Stage: One request becomes a complete plan", and group planning: "People plan as a group inside iAM. Your @ joins because you fit what they're building." Onboarding: "Connect your business and iAM turns your products, knowledge, and voice into your @."Source
    • Your websiteContact page: "Have a question, want into the private beta, or just want to tell us what you think? Send a message — a real person reads every one." There is no public waitlist or invite form; the logged-in app has Plans, Friends, Notifications, Bag, Create a Post and "Train your Genie".Source
  • 06

    Set-password emails decide whether a claim becomes a storefront. useiam.ai's DMARC policy is "p=none" and SPF ends "~all", which mailbox providers treat as weaker signals for a domain registered less than a year ago.

    Medium impactLow effort First result in 1 month Founding engineer

    First action

    Check last month's DMARC reports for unaligned senders.

    How to measure it

    Inbox placement

    Now
    –
    Target
    95%+
    By
    30 days

    Steps

    1. 1

      Read reports

      List every sender.

      Founding engineer 1 day

    2. 2

      Align senders

      SPF and DKIM for each.

      Founding engineer 1 day

    3. 3

      Split streams

      Transactional on a subdomain.

      Founding engineer 1 day

    4. 4

      Tighten DMARC

      To quarantine.

      Founding engineer 1 hour

    5. 5

      Tighten SPF

      To -all.

      Founding engineer 1 hour

    6. 6

      Monitor

      Weekly report check.

      Founding engineer weekly

    First result
    1 month
    Cost
    $0
    Owner
    Founding engineer

    Smallest test

    Send a test set-password email to Gmail, Outlook and Yahoo and check where it lands.

    Why it works

    Read the DMARC reports, confirm every sender (app email, contact replies, newsletters) is aligned, then move DMARC to "quarantine" and SPF to "-all". Send transactional email from a subdomain so marketing email cannot hurt it.

    A new domain has no sending reputation; strict authentication is the cheapest way to keep set-password emails in the inbox.

    Risks and how to handle them

    • A forgotten sender gets blocked

      Watch reports for two weeks before tightening.

    Evidence

    • Domain recordsuseiam.ai was registered on December 1, 2025. Email: SPF ends "~all" and DMARC is set to "p=none" (monitoring only), with DKIM present.Source
    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source

This quarter 8

The core plays for the next three months.

  • 07

    iAM promises that one request becomes a complete plan "across every business that fits", across travel, dining, products and home services. A marketplace that is thin everywhere gives weak answers everywhere.

    High impactHigh effort First result in 1 quarter Founder & CEO

    First action

    Rank beta requests by city and category.

    How to measure it

    Plans that include a claimed @

    Now
    –
    Target
    60% in the launch slice
    By
    1 quarter

    Steps

    1. 1

      Rank requests

      By city and category.

      Growth lead 1 week

    2. 2

      Pick the slice

      One city, one request type.

      Founder & CEO 1 day

    3. 3

      List businesses

      200 candidates.

      Partnerships lead 1 week

    4. 4

      Sign 50

      In person and by phone.

      Partnerships lead 1 month

    5. 5

      Open the city

      Waitlist admits there first.

      Growth lead 1 week

    6. 6

      Measure

      Plan quality and sales.

      Growth lead weekly

    7. 7

      Decide the next slice

      When the target is met.

      Founder & CEO monthly

    First result
    1 quarter
    Cost
    Founder and partnerships time
    Owner
    Founder & CEO

    Smallest test

    Sign ten restaurants in one neighbourhood and run beta requests against them.

    Why it works

    Pick one city and one request the beta already sees often, such as "Dinner for 6 on Friday". Sign 50 restaurants and venues there by hand, then open the waitlist in that city first. Expand only when most requests in that slice get a plan with real @ businesses in it.

    Density makes the product feel magical and gives businesses real sales to talk about, which is what gets the next city to sign.

    Risks and how to handle them

    • Too narrow to excite investors

      Show depth metrics, then repeat the playbook.

    Evidence

    • Your websiteHomepage (checked November 4, 2026): title "iAM — Say what you want. Get what you mean."; meta description ends "Private beta, open to beta testers only." A logged-out visitor gets the sign-in shell with a chat prompt "Where to today?" and suggestions "Dinner for 6 on Friday", "A gift under $50" and "What can you do?"; the server returns the /login page for "/".Source
    • Your websiteFeatures promised to businesses on /about: "Found by intent", "Placed in plans nobody made yet", "Sells for you, always on", "No lost checkouts", "Know your customers: Every chat shows you what people actually want", "The Stage: One request becomes a complete plan", and group planning: "People plan as a group inside iAM. Your @ joins because you fit what they're building." Onboarding: "Connect your business and iAM turns your products, knowledge, and voice into your @."Source
    • Your websiteTerms of Service (updated June 30, 2026): operated by IntentNet Inc, a Delaware corporation; "an invitation-only, MVP-scoped private beta"; iAM is "a technology platform and intermediary" for flights, accommodation, car rental, experiences, restaurant reservations, products, and professional and home services supplied by third parties.Source
  • 08

    The business page says "stake your place while the shift is still early" and iAM earns only on sales. Early businesses need a concrete reason to set up a storefront before customers arrive.

    High impactMedium effort First result in 1 quarter Partnerships lead

    First action

    Write the founding offer in three lines.

    How to measure it

    Live founding storefronts

    Now
    –
    Target
    100
    By
    1 quarter

    Steps

    1. 1

      Set the terms

      Badge, fee holiday, call.

      Founder & CEO 1 day

    2. 2

      Add to /business

      A counter of places left.

      Founding engineer 1 day

    3. 3

      Run setup calls

      30 minutes each.

      Partnerships lead ongoing

    4. 4

      Collect quotes

      After first sales.

      Growth lead ongoing

    5. 5

      Announce

      Founding list at launch.

      Growth lead 1 week

    6. 6

      Review

      Who sells, who stalls.

      Partnerships lead monthly

    First result
    1 quarter
    Cost
    Forgone commission
    Owner
    Partnerships lead

    Smallest test

    Offer it to the next 20 claims.

    Why it works

    Offer the first 100 businesses a "Founding @" badge, a year without iAM's cut, a setup call and a place in launch announcements. Ask each for feedback and a short quote.

    Scarcity and a named status move early adopters, and the quotes become proof for the next thousand.

    Risks and how to handle them

    • Fee holiday hides real economics

      Track would-be revenue per business.

    Evidence

    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source
    • Your websiteBusiness pricing on /about: "Free. Forever. No setup fee, no monthly bill. We earn only when you make a sale." No commission rate is stated. Footer: "Launching soon · [email protected]".Source
  • 09

    Claiming a username is the hook of the business page. Handles are scarce and personal, and people check whether theirs is taken on every new platform.

    High impactMedium effort First result in 1 month Growth lead

    First action

    Add an availability check to the claim form.

    How to measure it

    Checker-to-claim rate

    Now
    –
    Target
    20%
    By
    2 months

    Steps

    1. 1

      Availability API

      Rate-limited lookup.

      Founding engineer 2 days

    2. 2

      Checker UI

      On /business.

      Product designer 2 days

    3. 3

      Share card

      Claimed @ image.

      Product designer 2 days

    4. 4

      Outreach line

      "@yourname is still free".

      Growth lead 1 day

    5. 5

      Protect names

      Verification for well-known brands.

      Founding engineer 1 week

    6. 6

      Measure

      Checks, claims, shares.

      Growth lead weekly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Growth lead

    Smallest test

    Email 50 local businesses that their @ is free.

    Why it works

    Build a public checker at /business: type a business name, see if the @ is free, claim in one tap. Add a shareable "I claimed @name on iAM" card. Run outreach that tells businesses their @ is still available.

    Fear of losing a name is a strong motivator, and the checker gives outreach a personal, clickable opening.

    Risks and how to handle them

    • Squatters claim famous names

      Hold known brands for verified owners.

    Evidence

    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source
    • Your websitehttps://useiam.ai/robots.txt and https://useiam.ai/sitemap.xml both redirect to the sign-in page (/login?callbackUrl=%2Frobots.txt and /login?callbackUrl=%2Fsitemap.xml), so search engines get an HTML login page instead of a robots file or a sitemap. Google PageSpeed's SEO audit flags "robots.txt is not valid" (SEO score 92).Source
  • 10

    The pricing section says "Free. Forever." and "We earn only when you make a sale", but no rate is given. Business owners compare every channel by its take rate, and an unknown fee is a reason to wait.

    High impactLow effort First result in 1 month Founder & CEO

    First action

    Decide the launch rate for the first category.

    How to measure it

    Visitor-to-claim rate

    Now
    –
    Target
    +15%
    By
    60 days

    Steps

    1. 1

      Set the rate

      By category if needed.

      Founder & CEO 1 week

    2. 2

      Write the terms

      Sales, payouts, refunds.

      Founder & CEO 1 week

    3. 3

      Legal check

      Merchant terms.

      Outside counsel 1 week

    4. 4

      Publish

      On /business pricing.

      Growth lead 1 day

    5. 5

      Add comparison

      Typical channel fees.

      Growth lead 2 days

    6. 6

      Measure

      Claims before and after.

      Growth lead monthly

    First result
    1 month
    Cost
    Legal review
    Owner
    Founder & CEO

    Smallest test

    Show the rate in the setup-call script first.

    Why it works

    Publish the rate (or a simple range by category), what counts as a sale, when payouts happen and who handles refunds. Add a comparison with typical marketplace and delivery-app fees.

    A clear, low number turns a vague promise into a decision, and saves every sales conversation from the same question.

    Risks and how to handle them

    • Locking in a rate too early

      Publish a founding rate with an end date.

    Evidence

    • Your websiteBusiness pricing on /about: "Free. Forever. No setup fee, no monthly bill. We earn only when you make a sale." No commission rate is stated. Footer: "Launching soon · [email protected]".Source
    • Your websiteTerms of Service (updated June 30, 2026): operated by IntentNet Inc, a Delaware corporation; "an invitation-only, MVP-scoped private beta"; iAM is "a technology platform and intermediary" for flights, accommodation, car rental, experiences, restaurant reservations, products, and professional and home services supplied by third parties.Source
    • Your websitePrivacy Policy: "we never sell your personal data, and we never run third-party advertising against it." iAM builds an "Intent Graph", "a per-user model of your taste, history, and preferences"; payments run through Stripe.Source
  • 11

    The business page promises "Every chat shows you what people actually want." Early on, most @s will have few sales, and a business that hears nothing will forget it signed up.

    High impactMedium effort First result in 1 quarter Product manager

    First action

    Draft one sample report for a restaurant.

    How to measure it

    60-day active storefronts

    Now
    –
    Target
    70%
    By
    2 quarters

    Steps

    1. 1

      Define metrics

      Requests, appearances, suggestions.

      Product manager 1 week

    2. 2

      Privacy rules

      Aggregate only, suppress small counts.

      Founder & CEO 1 week

    3. 3

      Build the report

      Automated email.

      Founding engineer 1 month

    4. 4

      Add one tip

      How to appear more.

      Growth lead 1 week

    5. 5

      Send monthly

      All claimed businesses.

      Growth lead monthly

    6. 6

      Measure

      Opens and storefront updates.

      Growth lead monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Product manager

    Smallest test

    Send a hand-made report to ten businesses.

    Why it works

    Email each business a monthly report of anonymous, aggregated requests in its category and city (what people asked, budgets, times), how often its @ appeared in plans, and one suggestion to show up more. Keep individuals out, in line with iAM's privacy promise.

    Insight is value a business gets on day one, which keeps storefronts maintained until sales arrive.

    Risks and how to handle them

    • Thin data in small categories

      Group by wider area until counts are meaningful.

    Evidence

    • Your websiteFeatures promised to businesses on /about: "Found by intent", "Placed in plans nobody made yet", "Sells for you, always on", "No lost checkouts", "Know your customers: Every chat shows you what people actually want", "The Stage: One request becomes a complete plan", and group planning: "People plan as a group inside iAM. Your @ joins because you fit what they're building." Onboarding: "Connect your business and iAM turns your products, knowledge, and voice into your @."Source
    • Your websitePrivacy Policy: "we never sell your personal data, and we never run third-party advertising against it." iAM builds an "Intent Graph", "a per-user model of your taste, history, and preferences"; payments run through Stripe.Source
    • Your websiteBusiness pricing on /about: "Free. Forever. No setup fee, no monthly bill. We earn only when you make a sale." No commission rate is stated. Footer: "Launching soon · [email protected]".Source
  • 12

    iAM lets people "plan as a group" and has Friends and posts. A plan for "Dinner for 6" involves five people who are not users yet.

    High impactMedium effort First result in 1 quarter Product manager

    First action

    Measure how many people outside the beta each plan involves.

    How to measure it

    Sign-ups per shared plan

    Now
    –
    Target
    1.5
    By
    1 quarter

    Steps

    1. 1

      Shareable plan page

      Open without an account.

      Founding engineer 2 weeks

    2. 2

      Voting and comments

      Lightweight, no sign-up.

      Founding engineer 2 weeks

    3. 3

      Join prompt

      At the moment of booking.

      Product designer 1 week

    4. 4

      Track invites

      Plan to sign-up.

      Founding engineer 1 week

    5. 5

      Promote sharing

      After each plan is made.

      Product manager 1 week

    6. 6

      Measure

      Viral coefficient.

      Growth lead weekly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Product manager

    Smallest test

    Let beta testers share one plan by link and count the clicks.

    Why it works

    Let a user share a plan link that friends can open, vote on and comment without an account, then sign up to book or join. Count each new user brought in by a plan.

    Group planning is a built-in viral loop: each plan reaches several new people with a real reason to join.

    Risks and how to handle them

    • Private details exposed

      Share only what the plan owner chooses.

    Evidence

    • Your websiteFeatures promised to businesses on /about: "Found by intent", "Placed in plans nobody made yet", "Sells for you, always on", "No lost checkouts", "Know your customers: Every chat shows you what people actually want", "The Stage: One request becomes a complete plan", and group planning: "People plan as a group inside iAM. Your @ joins because you fit what they're building." Onboarding: "Connect your business and iAM turns your products, knowledge, and voice into your @."Source
    • Your websiteContact page: "Have a question, want into the private beta, or just want to tell us what you think? Send a message — a real person reads every one." There is no public waitlist or invite form; the logged-in app has Plans, Friends, Notifications, Bag, Create a Post and "Train your Genie".Source
    • Your websiteHomepage (checked November 4, 2026): title "iAM — Say what you want. Get what you mean."; meta description ends "Private beta, open to beta testers only." A logged-out visitor gets the sign-in shell with a chat prompt "Where to today?" and suggestions "Dinner for 6 on Friday", "A gift under $50" and "What can you do?"; the server returns the /login page for "/".Source
  • 13

    The business pitch is that "the way people buy is being rebuilt around AI" and businesses inside that AI win. A web search finds no coverage of iAM, and small business owners are searching for help with exactly this shift.

    Medium impactMedium effort First result in 2 months Growth lead

    First action

    Outline the ten-step checklist.

    How to measure it

    Guide-sourced claims

    Now
    –
    Target
    100 a month
    By
    2 quarters

    Steps

    1. 1

      Outline

      Ten steps.

      Growth lead 2 days

    2. 2

      Write

      Guide and checklist.

      Growth lead 1 week

    3. 3

      Design

      Downloadable checklist.

      Product designer 3 days

    4. 4

      Publish

      Indexed, in the sitemap.

      Founding engineer 1 day

    5. 5

      Distribute

      Posts and local groups.

      Growth lead ongoing

    6. 6

      Measure

      Claims from the guide.

      Growth lead monthly

    First result
    2 months
    Cost
    Writing time
    Owner
    Growth lead

    Smallest test

    Post the checklist on LinkedIn and count claims.

    Why it works

    Publish a plain-English guide and checklist on being found by AI assistants (accurate listings, clear product data, reviews, answers to common questions), with "claim your @" as one of the steps. Turn it into short posts and a talk for local business groups.

    Useful advice earns links and trust from the owners iAM needs, and positions iAM as the expert on AI-led buying.

    Risks and how to handle them

    • Reads as a sales pitch

      Make most steps useful without iAM.

    Evidence

    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source
    • Web searchA web search for useiam.ai and iAM's "Claim your @" (November 4, 2026) found no press, reviews or launch posts about the company; results were other "AI concierge" products.Source
    • Your websitehttps://useiam.ai/robots.txt and https://useiam.ai/sitemap.xml both redirect to the sign-in page (/login?callbackUrl=%2Frobots.txt and /login?callbackUrl=%2Fsitemap.xml), so search engines get an HTML login page instead of a robots file or a sitemap. Google PageSpeed's SEO audit flags "robots.txt is not valid" (SEO score 92).Source
  • 14

    Onboarding promises "Connect your business and iAM turns your products, knowledge, and voice into your @." The faster that happens, the more claims become live storefronts.

    High impactHigh effort First result in 1 quarter Founding engineer

    First action

    Ask the first 20 businesses which system holds their products.

    How to measure it

    Median time to live

    Now
    –
    Target
    Under 15 minutes
    By
    1 quarter

    Steps

    1. 1

      Survey systems

      First 20 businesses.

      Partnerships lead 1 week

    2. 2

      Build first import

      The most common one.

      Founding engineer 1 month

    3. 3

      Draft the voice

      From the business's own pages.

      Founding engineer 2 weeks

    4. 4

      Owner review

      Approve before going live.

      Product designer 2 weeks

    5. 5

      Second import

      Next most common.

      Founding engineer 1 month

    6. 6

      Measure

      Time to live and completion.

      Growth lead monthly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Founding engineer

    Smallest test

    Build one storefront by hand from a business's Shopify feed and time it.

    Why it works

    Build imports from the most common systems in the launch slice (for example Shopify product feeds, Square catalogs, Google Business Profile hours and menus), so a storefront is drafted in minutes for the owner to review.

    Setup effort is the biggest reason marketplace sign-ups never go live; imports remove it.

    Risks and how to handle them

    • Wrong product data goes live

      Owner approves every storefront.

    Evidence

    • Your websiteFeatures promised to businesses on /about: "Found by intent", "Placed in plans nobody made yet", "Sells for you, always on", "No lost checkouts", "Know your customers: Every chat shows you what people actually want", "The Stage: One request becomes a complete plan", and group planning: "People plan as a group inside iAM. Your @ joins because you fit what they're building." Onboarding: "Connect your business and iAM turns your products, knowledge, and voice into your @."Source
    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source

Big bets 3

Larger plays that can change the trajectory.

  • 15

    Stripe and OpenAI's Agentic Commerce Protocol, and checkout layers like Rye and Firmly, are making products buyable inside many assistants. iAM already uses Stripe. A business will value its @ more if it sells everywhere, not only inside iAM.

    High impactHigh effort First result in 3 quarters Founder & CEO

    First action

    Read the protocol spec and list the gaps against iAM's storefront data.

    How to measure it

    Share of sales from outside agents

    Now
    –
    Target
    20%
    By
    4 quarters

    Steps

    1. 1

      Study the specs

      ACP and similar.

      Founding engineer 2 weeks

    2. 2

      Map the data

      Catalogue, price, checkout.

      Founding engineer 1 month

    3. 3

      Build a pilot

      One category.

      Founding engineer 1 quarter

    4. 4

      Business controls

      Opt in by channel.

      Product designer 1 month

    5. 5

      Launch

      To founding businesses.

      Partnerships lead 1 month

    6. 6

      Measure

      Sales by channel.

      Growth lead monthly

    First result
    3 quarters
    Cost
    Engineering time
    Owner
    Founder & CEO

    Smallest test

    Make one storefront's products available through one protocol test.

    Why it works

    Expose each storefront's catalogue and checkout through the open protocols, so the @ is a business's AI storefront in iAM and beyond, with iAM as the place to manage it. Keep iAM's own experience as the best one.

    Being the tool that puts a small business into every AI assistant is a far stronger pitch than "be inside one more app", and it answers the "will anyone use iAM" objection.

    Risks and how to handle them

    • Feeding competitors

      Keep the management layer and insights inside iAM.

    Evidence

    • Competitor researchRivals' own homepages: Rye, "Universal agentic checkout" to let users "buy without ever leaving your native AI experience"; Firmly, "The agentic commerce platform" to "Make any digital experience shoppable"; the Agentic Commerce Protocol, "an open standard" for commerce between AI agents and businesses "Developed by Stripe + OpenAI"; Mindtrip, a "Personal Travel Assistant" that helps people "plan and book".Source
    • Your websitePrivacy Policy: "we never sell your personal data, and we never run third-party advertising against it." iAM builds an "Intent Graph", "a per-user model of your taste, history, and preferences"; payments run through Stripe.Source
    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source
  • 16

    iAM needs thousands of businesses before its plans feel complete, and one-by-one claiming is slow. Business associations and local chambers speak to owners every week.

    High impactMedium effort First result in 3 quarters Partnerships lead

    First action

    List five associations in the launch city and category.

    How to measure it

    Partner claims

    Now
    –
    Target
    500
    By
    3 quarters

    Steps

    1. 1

      List partners

      Chambers and associations.

      Partnerships lead 2 weeks

    2. 2

      Design the offer

      Member benefits.

      Founder & CEO 1 week

    3. 3

      Co-branded page

      Tracked claim links.

      Founding engineer 1 week

    4. 4

      Sign two

      One chamber, one association.

      Partnerships lead 1 quarter

    5. 5

      Member sessions

      Live setup workshops.

      Partnerships lead monthly

    6. 6

      Measure

      Claims and live storefronts by partner.

      Growth lead monthly

    First result
    3 quarters
    Cost
    Partner benefits
    Owner
    Partnerships lead

    Smallest test

    Run one setup workshop with a local chamber.

    Why it works

    Offer partner groups a co-branded claim page, member benefits (founding status, a lower rate) and a monthly insights report for their members. Start with one city chamber and one trade association in the launch category.

    Partners bring trust and volume that a small team cannot reach alone.

    Risks and how to handle them

    • Low-effort bulk claims

      Track live storefronts, not claims.

    Evidence

    • Your websiteFeatures promised to businesses on /about: "Found by intent", "Placed in plans nobody made yet", "Sells for you, always on", "No lost checkouts", "Know your customers: Every chat shows you what people actually want", "The Stage: One request becomes a complete plan", and group planning: "People plan as a group inside iAM. Your @ joins because you fit what they're building." Onboarding: "Connect your business and iAM turns your products, knowledge, and voice into your @."Source
    • Your websiteBusiness pricing on /about: "Free. Forever. No setup fee, no monthly bill. We earn only when you make a sale." No commission rate is stated. Footer: "Launching soon · [email protected]".Source
    • Your websiteTerms of Service (updated June 30, 2026): operated by IntentNet Inc, a Delaware corporation; "an invitation-only, MVP-scoped private beta"; iAM is "a technology platform and intermediary" for flights, accommodation, car rental, experiences, restaurant reservations, products, and professional and home services supplied by third parties.Source
  • 17

    The claim form already offers a personal @ ("Me"), and the app has posts and "Train your Genie". People with taste already recommend gifts, restaurants and trips to friends.

    High impactHigh effort First result in 4 quarters Product manager

    First action

    Invite ten beta testers to publish a gift list.

    How to measure it

    Recommendation-driven sales

    Now
    –
    Target
    15% of sales
    By
    4 quarters

    Steps

    1. 1

      Design the share

      Rate and rules.

      Founder & CEO 1 month

    2. 2

      Public lists

      Shareable personal @ pages.

      Founding engineer 1 quarter

    3. 3

      Attribution

      Sales back to the recommender.

      Founding engineer 1 month

    4. 4

      Disclosure

      Clear labels on earning recommendations.

      Outside counsel 2 weeks

    5. 5

      Recruit

      Beta testers with audiences.

      Growth lead 1 quarter

    6. 6

      Measure

      Sales and new users.

      Growth lead monthly

    First result
    4 quarters
    Cost
    Revenue share
    Owner
    Product manager

    Smallest test

    Publish one tester's gift list and count clicks.

    Why it works

    Let personal @s publish recommendations and plans that others can book or buy, and give them a share of iAM's cut on resulting sales. Start with gift lists ("A gift under $50") and local guides.

    Recommenders bring their own audiences, creating demand for businesses without paid ads, which fits iAM's no-ads promise.

    Risks and how to handle them

    • Trust in rankings

      Keep paid shares out of iAM's own ranking and label them.

    Evidence

    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source
    • Your websiteContact page: "Have a question, want into the private beta, or just want to tell us what you think? Send a message — a real person reads every one." There is no public waitlist or invite form; the logged-in app has Plans, Friends, Notifications, Bag, Create a Post and "Train your Genie".Source
    • Your websitePrivacy Policy: "we never sell your personal data, and we never run third-party advertising against it." iAM builds an "Intent Graph", "a per-user model of your taste, history, and preferences"; payments run through Stripe.Source
    • Your websiteHomepage (checked November 4, 2026): title "iAM — Say what you want. Get what you mean."; meta description ends "Private beta, open to beta testers only." A logged-out visitor gets the sign-in shell with a chat prompt "Where to today?" and suggestions "Dinner for 6 on Friday", "A gift under $50" and "What can you do?"; the server returns the /login page for "/".Source

Wildcards 3

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

  • 18

    The business page says businesses appear in plans and "You never paid for it", and the privacy policy promises no third-party advertising. Consumers and businesses will both ask how the AI decides what to show.

    Medium impactLow effort First result in 1 month Founder & CEO

    First action

    Write the five ranking rules.

    How to measure it

    Claims from the rules page

    Now
    –
    Target
    10% of claims
    By
    2 quarters

    Steps

    1. 1

      Draft rules

      Five principles.

      Founder & CEO 2 days

    2. 2

      Check against product

      Match how ranking works.

      Founding engineer 2 days

    3. 3

      Publish

      Linked from /business and app.

      Growth lead 1 day

    4. 4

      Use in outreach

      Fairness line.

      Growth lead ongoing

    5. 5

      Collect questions

      From businesses.

      Partnerships lead ongoing

    6. 6

      Update

      As ranking changes.

      Founder & CEO quarterly

    First result
    1 month
    Cost
    $0
    Owner
    Founder & CEO

    Smallest test

    Add three lines on ranking to the business page.

    Why it works

    Publish short, plain rules: what makes a business show up (fit to the request, availability, reviews, price), what never does (payment for placement), and how businesses can improve their fit.

    Being the AI that cannot be paid for placement is a rare, defensible position against ad-funded assistants, and it gives businesses a fair way to compete.

    Risks and how to handle them

    • Rules limit future revenue

      Separate clearly labelled promotions from ranking if ever added.

    Evidence

    • Your websiteThe business page lives at /about with the title "About iAM · iAM" and only the tagline as its description. Its pitch: "A next-gen AI that understands, recommends, and sells. Your business lives inside iAM as an @." "Claim your @" opens a form (this @ is for "A business" or "Me", a username and an email); the success message says "Your account is made and your username is held. Check your email to set a password — then you can design your storefront." Every "See it live" link goes to "/", the sign-in page.Source
    • Your websitePrivacy Policy: "we never sell your personal data, and we never run third-party advertising against it." iAM builds an "Intent Graph", "a per-user model of your taste, history, and preferences"; payments run through Stripe.Source
    • Competitor researchRivals' own homepages: Rye, "Universal agentic checkout" to let users "buy without ever leaving your native AI experience"; Firmly, "The agentic commerce platform" to "Make any digital experience shoppable"; the Agentic Commerce Protocol, "an open standard" for commerce between AI agents and businesses "Developed by Stripe + OpenAI"; Mindtrip, a "Personal Travel Assistant" that helps people "plan and book".Source
  • 19

    Search engines currently see nothing but a sign-in page. Beta testers are already turning requests like "Dinner for 6 on Friday" into full plans.

    Medium impactLow effort First result in 2 months Growth lead

    First action

    Pick five beta plans and ask for permission to publish.

    How to measure it

    Monthly visits to plan pages

    Now
    –
    Target
    5,000
    By
    2 quarters

    Steps

    1. 1

      Choose plans

      Five strong examples.

      Growth lead 1 week

    2. 2

      Get permission

      From the planner and businesses.

      Growth lead 1 week

    3. 3

      Page template

      Plan, businesses, call to action.

      Product designer 1 week

    4. 4

      Publish

      In the sitemap.

      Founding engineer 2 days

    5. 5

      Notify businesses

      Share-ready link.

      Partnerships lead 1 day

    6. 6

      Measure

      Visits and sign-ups.

      Growth lead monthly

    First result
    2 months
    Cost
    Staff time only
    Owner
    Growth lead

    Smallest test

    Publish one plan page and share it.

    Why it works

    With permission, publish anonymised plans as public pages ("A birthday dinner for 6 in [city]") listing the businesses involved and a "Make your own plan" button. Add them to the sitemap.

    Each page targets a real search, shows the product working, and gives featured businesses a link to share.

    Risks and how to handle them

    • Thin pages

      Only publish complete, useful plans.

    Evidence

    • Your websiteHomepage (checked November 4, 2026): title "iAM — Say what you want. Get what you mean."; meta description ends "Private beta, open to beta testers only." A logged-out visitor gets the sign-in shell with a chat prompt "Where to today?" and suggestions "Dinner for 6 on Friday", "A gift under $50" and "What can you do?"; the server returns the /login page for "/".Source
    • Your websitehttps://useiam.ai/robots.txt and https://useiam.ai/sitemap.xml both redirect to the sign-in page (/login?callbackUrl=%2Frobots.txt and /login?callbackUrl=%2Fsitemap.xml), so search engines get an HTML login page instead of a robots file or a sitemap. Google PageSpeed's SEO audit flags "robots.txt is not valid" (SEO score 92).Source
    • Your websiteFeatures promised to businesses on /about: "Found by intent", "Placed in plans nobody made yet", "Sells for you, always on", "No lost checkouts", "Know your customers: Every chat shows you what people actually want", "The Stage: One request becomes a complete plan", and group planning: "People plan as a group inside iAM. Your @ joins because you fit what they're building." Onboarding: "Connect your business and iAM turns your products, knowledge, and voice into your @."Source
  • 20

    PageSpeed scores useiam.ai 100 on mobile today, but about 107 KB of the 377 KB of JavaScript is unused on first load. Each new app feature (Stage, Friends, Bag, Genie) will add more.

    Medium impactLow effort First result in 2 weeks Founding engineer

    First action

    Add a bundle-size check to the build.

    How to measure it

    Mobile performance

    Now
    –
    Target
    Stay at 95+
    By
    ongoing

    Steps

    1. 1

      Measure bundles

      By route.

      Founding engineer 1 day

    2. 2

      Set budgets

      Per route.

      Founding engineer 1 day

    3. 3

      Split screens

      Load on demand.

      Founding engineer 3 days

    4. 4

      Check releases

      PageSpeed in CI.

      Founding engineer 1 day

    5. 5

      Review monthly

      Budget breaches.

      Founding engineer monthly

    6. 6

      Share results

      With the team.

      Founding engineer monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founding engineer

    Smallest test

    Run a bundle analyser once and remove the biggest unused import.

    Why it works

    Set a JavaScript budget in the build, split the app's heavier screens so the first screen loads only what it needs, and check PageSpeed in each release.

    Speed is a quiet advantage for a chat-first product; keeping it costs little now and a lot later.

    Risks and how to handle them

    • Over-optimising early

      Only set budgets, fix when breached.

    Evidence

    • Google PageSpeedMobile performance 100/100 (desktop 100): largest paint 0.8 seconds, 508 KB page, 47 requests, about 107 KB of unused JavaScript. Chrome has no real-visitor speed data for useiam.ai yet, a sign of low public traffic.Source
    • Your websiteContact page: "Have a question, want into the private beta, or just want to tell us what you think? Send a message — a real person reads every one." There is no public waitlist or invite form; the logged-in app has Plans, Friends, Notifications, Bag, Create a Post and "Train your Genie".Source
More example playbooks and reviews

More growth playbooks

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

  • Clear Street growth strategyA cloud-native brokerage and capital markets infrastructure firm (clearing, custody, financing, execution, Clear Street Studio) for…22 growth ideas
  • Ekimetrics growth strategyA data science and AI consultancy best known for marketing mix modeling and marketing effectiveness, plus customer analytics, commercial…21 growth ideas
  • ElevenLabs growth strategyAI audio research and products: ElevenAgents for voice and chat agents, ElevenCreative for speech, music, image and video creation, and…21 growth ideas
  • OpenSpace growth strategyA Visual Intelligence Platform for construction: 360° camera, smartphone, drone and laser capture mapped automatically to plans, field…22 growth ideas
  • Juno growth strategyA free personal health assistant app for chronic illness: people log symptoms by text or voice, pace their energy, see patterns alongside…23 growth ideas
  • Wave growth strategyMobile money in Africa: free deposits and withdrawals at agents, transfers for 1%, free bill payments and airtime, plus business payments…21 growth ideas
  • refurbed growth strategyA Vienna-based online marketplace for refurbished products (phones, laptops, tablets, household appliances, sport, kids' products and…22 growth ideas
  • General Astronautics growth strategyA Y Combinator (Winter 2026) space robotics startup building autonomous dexterous robotic arms for orbital inspection, repair and…23 growth ideas

See every playbook and website review

Independent research. Programmable wrote this playbook from public sources, as they stood on November 4, 2026, and cites them throughout. iAM did not commission, review or endorse it, and Programmable is not affiliated with iAM. 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 iAM runs its business.

Something wrong, or do you represent iAM? 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 307 ideas

    Public files and previews, a live demo, a public homepage, the invite waitlist, a better claim flow and email authentication; trim JavaScript.

  2. Days 31 to 6010 ideas

    One city and request type, founding businesses, the @ checker, the published rate, monthly insight reports, shareable group plans, the AI-visibility guide, imports; ranking rules and plan pages.

  3. Days 61 to 903 ideas

    Commit to the big bets: open commerce standards, partner bulk sign-ups and personal recommender @s.

The research behind the plan

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

Customers

What customers say

Customers value saying the outcome instead of searching. The most cited problem: too many tabs and checkouts.

  • One place to decide and buy
  • Planning with a group
  • In their words: “say what you want”

Market

Competitive landscape

4 competitors compared: ChatGPT with Agentic Commerce Protocol, Rye, Firmly and Mindtrip.

  • Gap to exploit: An AI storefront small businesses control in their own voice
  • ChatGPT with Agentic Commerce Protocol: Businesses do not control how they appear
  • Rye: Developer tool, not a consumer product

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