ProgrammableMarketing/lightmeter.io (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 · 3
  • How we can help
Generated Nov 16, 2026
  1. Programmable
  2. Playbooks
  3. Lightmeter
Lightmeter logo

growth playbook · Nov 16, 2026

lightmeter.io (opens in a new tab)

Lightmeter growth playbook

Diagnosis

Lightmeter has built far more than its website shows. The docs describe a full campaign workspace (Beam), a public API, an MCP server for AI agents, three CRM integrations, AI-drafted replies and a pricing model where only positive replies count.

The public site has eight pages, two blog posts in almost three years, a three-link menu, no price, and a closing "Book Call" button that goes nowhere. A team of five sells through one founder's calendar.

This playbook first repairs the path from visitor to call, publishes the price and puts the product on the site, then adds small automations around the work a five-person team cannot do by hand: call preparation, setup follow-up, turning docs into updates, capacity watching and listing corrections. Larger bets use the team's delivery record and reply data as public proof.

Growth Score

6/10

Biggest Opportunity

Show the product that already exists: Beam, pay-for-positive-replies pricing, the CRM integrations and agent access are strong differences from self-serve sending tools, and none of them is on the homepage.

Biggest Risk

Self-serve rivals with public prices and free starts win the buyer before a call is booked, while every lead, setup and launch at Lightmeter depends on a handful of people.

01

Start here

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

  1. 1

    Publish a pricing page that explains "Only positive replies count"

    Copy the "What Counts as a Positive Reply" section from the docs into a draft and rewrite it for buyers.

    High impact First result in 2 weeks
  2. 2

    Fix the closing "Book Call" button that goes nowhere, and put Beam, integrations and pricing in the menu

    Open the homepage, scroll to "Start sending in 7 days." and click "Book Call"; then set its link to the same calendar as the header button.

    High impact First result in 1 week
  3. 3

    A pre-call brief and follow-up for every booking, so one founder's calendar is not the whole sales process

    Add two questions to the booking page: current sending tool and emails per day.

    High impact First result in 3 weeks

02

Your idea portfolio

24 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.

  • 8 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 · 9Fill-ins · 11Reconsider · 2
Effort →

Showing 24 of 24 ideas

This week 6

Quick wins with a clear first action.

  • 01

    The last thing a visitor sees on the homepage is a banner that says "Start sending in 7 days." with a "Book Call" button, and that button links to "#". The same dead button closes both blog posts. The header and hero buttons work, so the readers who scroll the whole page, the most interested ones, are the ones who hit the button that does nothing. The three use-case tabs and ten customer logos are dead links too. Meanwhile the menu has three links (Home, Updates, About), and the pages that explain what Lightmeter sells today, the Close and HubSpot integrations, are not linked from the homepage or the menu at all. Beam, the API and the MCP server appear only in the docs.

    High impactLow effort First result in 1 week CEO

    First action

    Open the homepage, scroll to "Start sending in 7 days." and click "Book Call"; then set its link to the same calendar as the header button.

    How to measure it

    Homepage visit-to-booking rate

    Now
    –
    Target
    +20%
    By
    60 days

    Steps

    1. 1

      Confirm the dead links

      Click every button, tab and logo on the homepage, the About page and both posts; list each link that goes to "#" or to a generic social site.

      Operations 1 hour

    2. 2

      Repair the closing button

      The banner is a shared theme block, so one change should fix the homepage and both posts. Link it to the booking calendar.

      Lead Engineer 1 hour

    3. 3

      Decide the tabs and logos

      Make the three use-case tabs switch content without a link, or link each to its own section; remove the links from logos that have no story to show.

      Lead Engineer half a day

    4. 4

      Write the Product page

      One page on Beam, the reply inbox, AI-drafted replies, the revenue reports and the delivery network, using the docs as the source.

      CEO 2 days

    5. 5

      Widen the menu

      Product, Integrations, Pricing, Updates, About, plus the booking button; repeat the same links in the footer.

      Lead Engineer half a day

    6. 6

      Track each button

      Add an analytics event per booking button position (header, hero, mid-page, closing banner).

      Lead Engineer half a day

    7. 7

      Review after 30 days

      Compare bookings by button position and visits to the new pages; keep or reorder.

      COO monthly

    First result
    1 week
    Cost
    Staff time only: a few hours for the links, about three days for the Product page and menu
    Owner
    CEO

    Smallest test

    Fix only the closing button today and count clicks on it for two weeks.

    Why it works

    Point every closing "Book Call" button at the booking calendar, and make the three use-case tabs and the logo row either real links or plain content. Then widen the menu to Product, Integrations, Pricing, Updates and About. Product can start as one page that describes Beam, the reply inbox, the revenue reports and the delivery network in the words the docs already use; Integrations links the existing pages; Pricing is covered in idea 3. Add event tracking on each booking button so you can see which position on the page produces calls.

    A visitor who reaches the bottom of a long page has read the whole pitch. Giving that reader a working button, and giving every reader a way to see the product before a call, removes two leaks that cost nothing to close. It also lets search engines find the integration pages through internal links.

    Ready to use

    ChecklistHomepage path repair list

    [ ] Closing "Book Call" button opens the booking calendar (homepage and both posts)
    [ ] Use-case tabs switch content or link to sections
    [ ] Customer logos: real links or no links
    [ ] Footer social icons point at the company's own profiles
    [ ] Menu: Product, Integrations, Pricing, Updates, About
    [ ] Product page describing Beam, replies, reports and the network
    [ ] One analytics event per booking button position

    Risks and how to handle them

    • A wider menu distracts visitors from booking

      Keep the booking button in the header on every page and measure bookings before and after.

    • The Product page drifts from the docs

      Link to the docs for detail and review the page whenever the docs change (see idea 6).

    Evidence

    • Your websiteLink check (November 16, 2026): the "Book Call" button in the closing "Start sending in 7 days." banner links to "#" on the homepage and on both blog posts, while the header and hero buttons open a booking calendar. The three use-case tabs (B2B Startups, Marketplaces, GTM Agencies) and the ten customer logos also link to "#", the footer Twitter icon opens twitter.com's front page, and two of the five testimonial cards link to the twitter.com and linkedin.com front pages.Source
    • Your websiteHomepage: H1 "Turn-key Outreach Infrastructure"; the menu has three links (Home, Updates, About) and a "Book Call" button; the closing banner says "Start sending in 7 days." and "Up to 7,500 emails daily with express warmup." The page shows no price and does not mention Beam, the API, the MCP server or the CRM integrations.Source
    • Your websiteSitemap (checked November 16, 2026): 8 pages and 2 posts: home, about-us, request-information, terms, privacy, integrations, integrations/close and integrations/hubspot. There is no pricing page (/pricing/ returns 404) and no product, comparison, case-study or use-case page. The integrations pages are not linked from the homepage or the menu.Source
    • Your docsBeam docs: "Beam is Lightmeter's campaign workspace for growth teams running outbound at startup speed." Setup runs through Slack, Connect CRM, Connect calendar, Company knowledge, Reply settings and AI replies, and "Each step has Skip for now." Each customer gets Slack channels for replies and reports; AI replies are off by default and nothing sends until someone presses Send; a campaign launches only after Lightmeter staff enable it. This one docs page runs to about 143,000 characters.Source
  • 02

    Every working "Book Call" button opens one founder's personal intro-call calendar, and the team is five people. The only other way in is a form that is not linked from the homepage and does not say what happens next. So each new lead costs a founder research time before the call, and a visitor who books but does not show, or fills the form, depends on someone remembering to follow up.

    High impactMedium effort First result in 3 weeks COO

    First action

    Add two questions to the booking page: current sending tool and emails per day.

    How to measure it

    Booked-call to customer rate

    Now
    –
    Target
    +15%
    By
    90 days

    Steps

    1. 1

      Add booking questions

      Company website, current sending tool, emails per day and CRM, as optional questions on the booking page and the form.

      COO 1 hour

    2. 2

      Define the brief

      One page: what the company sells, team size, likely outreach motion, CRM, which Lightmeter use case fits, and three questions to ask.

      CEO half a day

    3. 3

      Build the intake flow

      Inputs are the calendar's new-booking event and the form entry. It reads the prospect's public website, fills the brief template and posts it to the sales channel and the CRM record. It connects the calendar, the form, the chat tool and the CRM.

      Lead Engineer 1 week

    4. 4

      Draft the follow-ups

      After each call slot, draft a follow-up with the matching integration page and proposed start date; for no-shows, draft a rebooking note. Drafts wait in the channel.

      Lead Engineer 3 days

    5. 5

      Keep a person in the loop

      A founder or Operations approves, edits or discards each draft; the automation never sends on its own.

      Operations ongoing

    6. 6

      Route by fit

      Tag each booking as startup, marketplace or agency and flag bookings that look too small, so the team can offer a shorter call or the form path.

      COO 2 days

    7. 7

      Measure

      Track time spent preparing per call, show rate, follow-up sent within a day, and booked-call to customer rate against the previous quarter.

      COO monthly

    First result
    3 weeks
    Cost
    About two weeks of build time plus existing calendar, chat and CRM tools
    Owner
    COO

    Smallest test

    Write the brief by hand for the next five bookings and note whether the calls go better.

    Why it works

    Build a small booking-intake automation. Input: each new calendar booking and each form submission (name, work email, company domain, any answers). It looks up the company's public site, what it sells, likely outreach volume, and which CRM it appears to use (Close, HubSpot or Salesforce map to existing integrations), then writes a one-page brief into the team's chat channel and CRM record before the call. After the call slot it drafts a follow-up email with the right integration page and next step; a person reads and sends it. No-shows and form leads get a drafted rebooking note the same way. Nothing is sent without a person approving it.

    A managed service is sold on expertise, and a call that opens with the prospect's own sending setup shows it in the first minute. Drafted follow-ups mean leads are not dropped when the team is busy with delivery work, and the founder's time goes to the conversation, not the preparation.

    Risks and how to handle them

    • The brief contains a wrong guess about the prospect

      Show the source page beside each line and mark guesses as guesses.

    • Extra booking questions reduce bookings

      Keep them optional and compare booking rate for two weeks.

    Builds on

    Evidence

    • Your websiteBooking path: every working "Book Call" button opens one founder's personal intro-call calendar. The only form, /request-information/, asks for first and last name, email twice and a required phone number, is not linked from the homepage, and does not say what happens after submitting.Source
    • Y Combinator directory"Lightmeter is turn-key email outreach infrastructure for startups, combining network, platform, and expert advice." Winter 2022 batch, team size 5, no open jobs. The homepage says "Lightmeter grew out of a demand from B2B startups in YCombinator", and startups.lightmeter.io now redirects to the homepage.Source
    • Your websiteIntegration pages: Close and HubSpot each have a page headed "From positive reply to Closed Won." The docs also cover Salesforce ("Connect Salesforce to send positive conversations to the rep responsible for follow-up") and Instantly-compatible webhook events for teams "replacing existing Instantly webhook automations", but the site has no Salesforce page and no switching page.Source
  • 03

    The terms say fees follow a schedule "stated on the Lightmeter.io website", but the site has no pricing page and the homepage shows no price. The docs describe something rivals do not offer: performance pricing where "Only positive replies count" and bounces, automated messages and negative replies cost nothing. A third-party directory already tells buyers that Lightmeter does not display pricing. The most persuasive part of the offer is hidden in a setup guide.

    High impactLow effort First result in 2 weeks CEO

    First action

    Copy the "What Counts as a Positive Reply" section from the docs into a draft and rewrite it for buyers.

    How to measure it

    Pricing-page to booking rate

    Now
    –
    Target
    5% of pricing page visitors
    By
    60 days

    Steps

    1. 1

      Decide what to show

      Exact prices, a "from" price, or the structure only; agree what the terms' fee schedule refers to.

      CEO 1 day

    2. 2

      Write the model

      Subscription, performance pricing, what counts as a positive reply and what never counts, in buyer language.

      CEO 1 day

    3. 3

      Add a worked example

      One realistic month for a startup and one for an agency, using the positive reply rate formula from the docs.

      COO half a day

    4. 4

      Add the comparison

      Paying per mailbox or per email against paying per positive reply, without naming rivals' current prices unless checked that day.

      COO half a day

    5. 5

      Build and link the page

      Publish /pricing/, add it to the menu and footer, and link it from the terms' fee clause.

      Lead Engineer 1 day

    6. 6

      Answer the usual questions

      Minimum term, cancelling, corrections and refunds of charged replies, taken from the terms and docs.

      Operations half a day

    7. 7

      Measure

      Visits to the page, bookings that follow, and whether calls spend less time on price.

      COO monthly

    First result
    2 weeks
    Cost
    Staff time only
    Owner
    CEO

    Smallest test

    Publish the page with the structure only and watch bookings from it for a month.

    Why it works

    Create /pricing/ with the model in plain words: what the monthly subscription includes, how performance pricing works, the six kinds of reply that count as positive, what never counts, and how a wrong classification is corrected. Add a worked example (leads contacted, positive reply rate, what the month costs) and a short comparison with paying per mailbox or per email. If the numbers must stay on a call, publish the structure and a "from" figure. Link the page from the menu and from the terms.

    Buyers compare Lightmeter with tools that show a price in the first screen. A page that says you pay for interested replies, not volume, turns the missing price from a reason to leave into the reason to book. It also brings the site in line with what the terms tell customers.

    Ready to use

    CopyPricing page outline

    1. Headline: pay for interested replies, not for volume
    2. What the monthly subscription covers
    3. Performance pricing: what counts as a positive reply (six kinds) and what never counts
    4. A worked month for a startup and for an agency
    5. How corrections and refunds of charged replies work
    6. Per-mailbox pricing compared with per-positive-reply pricing
    7. Questions: term, cancelling, taxes, start time
    8. Book a call

    Risks and how to handle them

    • A public price anchors larger customers too low

      Publish the structure and a starting figure, and keep volume tiers for the call.

    • The page and the terms disagree

      Have the same person update both, and date the page.

    Evidence

    • Your websiteTerms: "You will be subject to monthly subscription fees in accordance with the fee schedule", with rates "stated on the Lightmeter.io website" in US dollars; billing is monthly and can be cancelled at any time; the service is provided "as is" and the provider "does not guarantee that emails will be delivered without delay."Source
    • Your docsBeam docs on performance pricing: "Only positive replies count. Neutral and negative replies, automated messages, bounces, and delivery failures do not." Six reply categories count as positive (for example meeting scheduled or requested proposal), and a correction "updates reporting and can affect performance pricing."Source
    • Your websiteSitemap (checked November 16, 2026): 8 pages and 2 posts: home, about-us, request-information, terms, privacy, integrations, integrations/close and integrations/hubspot. There is no pricing page (/pricing/ returns 404) and no product, comparison, case-study or use-case page. The integrations pages are not linked from the homepage or the menu.Source
    • Directory listingA sales-tools directory lists Lightmeter under "Email Spam Tester", describes it as "Web-based management for mailserver health and delivery" (the older open-source Control Center, not the delivery service) and says "Lightmeter does not display pricing on the website".Source
  • 04

    Beam's setup has six steps (Slack, CRM, calendar, company knowledge, reply settings, AI replies) and the docs say "Each step has Skip for now." A campaign also cannot launch until Lightmeter staff enable it. With performance pricing, a customer who skipped the CRM or never turned on reply handling produces fewer counted positive replies, so a skipped step costs Lightmeter revenue as well as the customer results. Every customer already has a dedicated Slack channel where a reminder would be seen.

    High impactMedium effort First result in 1 month Operations

    First action

    List current workspaces with the setup steps each has not finished.

    How to measure it

    Time to first launch

    Now
    –
    Target
    7 days median
    By
    90 days

    Steps

    1. 1

      Map the steps to data

      For each of the six setup steps and the launch permission, name the API field or report that shows whether it is done.

      Lead Engineer 1 day

    2. 2

      Build the daily check

      A scheduled job reads every workspace's settings, integrations and campaign state and writes one row per workspace: steps open, days since sign-up, ready for launch or not.

      Lead Engineer 3 days

    3. 3

      Write the nudges

      One short message per open step with the exact menu path from the docs, and a rule of at most one message per customer every two working days.

      Operations 1 day

    4. 4

      Add the approval step

      Drafts appear in an internal channel with Approve, Edit and Skip; only approved messages post to the customer's channel.

      Lead Engineer 2 days

    5. 5

      Build the launch queue

      Workspaces with setup complete and a campaign ready are listed for staff to review and enable; staff keep the decision.

      DevOps Engineer 2 days

    6. 6

      Run it on new customers

      Start with customers signed in the last 30 days, then extend to older workspaces with open steps.

      Operations 2 weeks

    7. 7

      Measure

      Days to first launch, share of workspaces with CRM connected by day 14, and positive replies in the first 30 days, before and after.

      COO monthly

    First result
    1 month
    Cost
    About two weeks of build time; no new tools
    Owner
    Operations

    Smallest test

    Send hand-written nudges to five customers with open steps and see how many finish within a week.

    Why it works

    Build an onboarding tracker. Input: each workspace's settings and integration state from the public API (CRM connected or not, calendar, webhooks, team, agreement status) and campaign state. Each morning it works out which setup steps are still open and how many days since sign-up, then drafts one short, specific nudge for the customer's Slack channel ("your CRM is not connected, here is the two-minute path") and puts workspaces that are ready for launch into a review queue for staff. Operations approves each message before it posts and decides every launch permission; the automation only prepares.

    The homepage promises a start in seven days, and that promise depends on customers finishing steps they were allowed to skip. One timely, specific reminder in a channel they already read is easier to act on than a checklist they left behind, and a launch queue stops ready customers waiting on a busy team.

    Risks and how to handle them

    • Customers feel nagged

      Cap the frequency and let Operations skip any message.

    • A nudge is wrong because the data is stale

      Re-check the step at the moment of approval, not only in the morning run.

    Evidence

    • Your docsBeam docs: "Beam is Lightmeter's campaign workspace for growth teams running outbound at startup speed." Setup runs through Slack, Connect CRM, Connect calendar, Company knowledge, Reply settings and AI replies, and "Each step has Skip for now." Each customer gets Slack channels for replies and reports; AI replies are off by default and nothing sends until someone presses Send; a campaign launches only after Lightmeter staff enable it. This one docs page runs to about 143,000 characters.Source
    • Your docsMCP and API docs: a remote MCP server lets AI agents work in a Lightmeter workspace with the user's normal login, with example prompts "Answer today's positive replies", "Find open deals to nudge" and "See which job titles reply positively"; "All actions are tracked (labelled 'MCP') and visible in the Activity Log of your account." The public API covers leads, campaigns, Unibox, analytics, infrastructure, workspace settings, agreements and webhooks.Source
    • Your docsBeam docs on performance pricing: "Only positive replies count. Neutral and negative replies, automated messages, bounces, and delivery failures do not." Six reply categories count as positive (for example meeting scheduled or requested proposal), and a correction "updates reporting and can affect performance pricing."Source
  • 05

    The article "Sales email vs Marketing email: what's the difference?" lives at /3-experiments-to-improve-your-performance-and-kpis-3/, an address left over from a template that has nothing to do with the article. The homepage title is "Home - Lightmeter" and it has no meta description, so search results and link previews show a generic line for a company whose whole pitch is being read.

    Medium impactLow effort First result in 2 weeks Lead Engineer

    First action

    Change the article's address and add the redirect.

    How to measure it

    Search click-through rate

    Now
    –
    Target
    +10%
    By
    60 days

    Steps

    1. 1

      Rename the article address

      Use a short address that matches the headline, such as sales-email-vs-marketing-email.

      Lead Engineer 30 minutes

    2. 2

      Redirect the old address

      Permanent redirect, and update the homepage and blog links that point to it.

      Lead Engineer 30 minutes

    3. 3

      Rewrite the homepage title

      Replace "Home - Lightmeter" with the offer and the brand.

      CEO 1 hour

    4. 4

      Write descriptions

      Homepage, About, integrations and both posts, each about 150 characters with one proof point.

      CEO half a day

    5. 5

      Add a share image

      One branded image for link previews on every page.

      Operations half a day

    6. 6

      Check previews and indexing

      Share each page in a chat tool to see the preview, then watch Search Console for the new address.

      Lead Engineer 2 weeks

    First result
    2 weeks
    Cost
    $0
    Owner
    Lead Engineer

    Smallest test

    Change the homepage title and description today and compare click-through after two weeks.

    Why it works

    Give the article an address that matches its headline and redirect the old one permanently. Set the homepage title to the offer (managed outreach delivery, priced on positive replies) and write a description of about 150 characters. Add a social share image, and do the same check on the About, integrations and blog pages.

    Titles, descriptions and addresses are what a searcher or a person receiving a shared link sees before the page. Fixing them takes hours and applies to every future visit.

    Risks and how to handle them

    • The article loses its existing ranking

      Use a permanent redirect and keep the headline unchanged.

    Evidence

    • Your websiteBlog: two posts in total. "Sales email vs Marketing email: what's the difference?" (February 5, 2024) lives at /3-experiments-to-improve-your-performance-and-kpis-3/ and says Lightmeter averages about 60% open and 5% reply rates for customers with open tracking on. The next post, "Track your outbound pipeline through to revenue", is dated November 7, 2026.Source
    • PageSpeedLab test, November 15, 2026 (no real-visitor data is available for this site): mobile performance 76, desktop 90; main content appears after 5.2 seconds on mobile against 1.5 on desktop; the homepage weighs 2.8 MB, of which 2.4 MB is images, with about 1.9 MB of image savings flagged. Accessibility 80 (unnamed buttons and links, low contrast, small touch targets). SEO 85: no meta description, and the title is "Home - Lightmeter".Source
  • 06

    The blog, labelled "Updates" in the menu, has two posts: one from February 2024 and one from November 2026. In that gap the team shipped a campaign workspace, three CRM integrations, an API, an MCP server and AI replies, and wrote all of it up in the docs; the Beam page alone runs to about 143,000 characters. The writing is being done, but in a place buyers do not read. A visitor who clicks "Updates" sees a product that seems to have gone quiet for almost three years.

    Medium impactMedium effort First result in 3 weeks CEO

    First action

    List the docs sections with no matching post: Beam, the API, the MCP server, Salesforce, AI replies and walk-in tracking.

    How to measure it

    Updates published

    Now
    –
    Target
    4 a month
    By
    60 days

    Steps

    1. 1

      Snapshot the docs

      A daily job saves the text of the three docs pages, split by heading, and compares it with the previous day.

      DevOps Engineer 2 days

    2. 2

      Define an update

      A template: headline, who it helps, what changed, how to switch it on, one screenshot slot, link to the docs section.

      CEO half a day

    3. 3

      Draft from changes

      For each new or changed section the pipeline fills the template and creates an unpublished post in the content system, plus a two-line customer note.

      Lead Engineer 4 days

    4. 4

      Review and publish

      A founder edits the draft, adds a screenshot and publishes; small wording changes in the docs are ignored by rule.

      CEO 20 minutes per update

    5. 5

      Backfill the gap

      Generate drafts for the features already documented and publish the best six over six weeks.

      CEO 6 weeks

    6. 6

      Send it to customers

      Approved two-line notes go to customer channels and a monthly email to customers and past leads.

      Operations monthly

    7. 7

      Measure

      Posts published, search visits to update pages, and bookings that follow a visit to one.

      COO monthly

    First result
    3 weeks
    Cost
    About two weeks of build time, then minutes of editing per update
    Owner
    CEO

    Smallest test

    Write one update by hand from the Salesforce docs section and publish it this week.

    Why it works

    Build a small content pipeline. Input: the three public docs pages, saved daily. When a section is added or changed, the pipeline writes a short draft update (what changed, who it is for, how to turn it on, link to the docs section), a two-line version for the customer Slack channels and a line for a monthly email. Drafts land in the site's content system as unpublished posts. A founder edits and publishes; nothing goes live on its own. Backfill once: draft posts for the features already in the docs that the blog never announced.

    The expensive part, explaining the feature accurately, is already done by the engineers who write the docs. Reusing it gives the site fresh dated pages for search and for buyers checking whether the company is active, at the cost of a few minutes of editing per update.

    Risks and how to handle them

    • Drafts read like documentation

      Lead with the customer problem in the template and keep a person as the editor.

    • A draft announces something not yet released

      Only published docs are read, and a person approves every post.

    Evidence

    • Your websiteBlog: two posts in total. "Sales email vs Marketing email: what's the difference?" (February 5, 2024) lives at /3-experiments-to-improve-your-performance-and-kpis-3/ and says Lightmeter averages about 60% open and 5% reply rates for customers with open tracking on. The next post, "Track your outbound pipeline through to revenue", is dated November 7, 2026.Source
    • Your docsBeam docs: "Beam is Lightmeter's campaign workspace for growth teams running outbound at startup speed." Setup runs through Slack, Connect CRM, Connect calendar, Company knowledge, Reply settings and AI replies, and "Each step has Skip for now." Each customer gets Slack channels for replies and reports; AI replies are off by default and nothing sends until someone presses Send; a campaign launches only after Lightmeter staff enable it. This one docs page runs to about 143,000 characters.Source
    • Your websiteHomepage: H1 "Turn-key Outreach Infrastructure"; the menu has three links (Home, Updates, About) and a "Book Call" button; the closing banner says "Start sending in 7 days." and "Up to 7,500 emails daily with express warmup." The page shows no price and does not mention Beam, the API, the MCP server or the CRM integrations.Source

This quarter 12

The core plays for the next three months.

  • 07

    In Google's lab test the homepage scores 90 on desktop but 76 on mobile, where the main content takes 5.2 seconds to appear. Images make up 2.4 MB of the 2.8 MB page, and the test flags about 1.9 MB of that as avoidable. There is no real-visitor data for the site, so this is a lab result, but the cause is plain and cheap to fix.

    Medium impactLow effort First result in 2 weeks Lead Engineer

    First action

    Export the list of images over 100 KB from the PageSpeed report.

    How to measure it

    Mobile largest contentful paint (lab)

    Now
    –
    Target
    under 2.5 seconds
    By
    30 days

    Steps

    1. 1

      List the heavy images

      From the report, every image over 100 KB with its displayed size.

      Lead Engineer 1 hour

    2. 2

      Convert and resize

      Modern formats at displayed dimensions, with smaller versions for phones.

      Lead Engineer 1 day

    3. 3

      Lazy-load below the fold

      Logos, testimonials, team photo and news images load when scrolled to.

      Lead Engineer half a day

    4. 4

      Defer blocking files

      Load fonts and non-essential scripts after the first paint; the test estimates about 0.7 seconds here.

      Lead Engineer 1 day

    5. 5

      Fix names and contrast

      Accessible names on icon buttons and links, larger touch targets, stronger text contrast, a main landmark.

      Lead Engineer 1 day

    6. 6

      Re-test

      Run the same test on the homepage, About and a post; record before and after.

      DevOps Engineer 1 hour

    First result
    2 weeks
    Cost
    Three to four days of engineering time
    Owner
    Lead Engineer

    Smallest test

    Compress the three largest images and re-run the test.

    Why it works

    Convert the team photo, customer logos, testimonial portraits and screenshots to modern formats at the size they are displayed, lazy-load everything below the first screen, and load the fonts and scripts that block rendering later. While in the template, give the icon-only buttons and links names and fix the low-contrast text the same test reports.

    Founders often open a link from a message on their phone. A page that shows its headline quickly keeps more of them, and the accessibility fixes are the same hour of work.

    Risks and how to handle them

    • Lab gains do not show for real visitors

      Track bounce rate on mobile before and after as the real check.

    Evidence

    • PageSpeedLab test, November 15, 2026 (no real-visitor data is available for this site): mobile performance 76, desktop 90; main content appears after 5.2 seconds on mobile against 1.5 on desktop; the homepage weighs 2.8 MB, of which 2.4 MB is images, with about 1.9 MB of image savings flagged. Accessibility 80 (unnamed buttons and links, low contrast, small touch targets). SEO 85: no meta description, and the title is "Home - Lightmeter".Source
  • 08

    The homepage has real proof: a customer who went from zero replies to about 150 a week, another whose open rates rose from 40% to 85%, and two customers that were later acquired. None of it has a page of its own. Two of the five testimonial cards link to the front pages of twitter.com and linkedin.com, the ten logos link nowhere, and the acquisitions are labelled "Aquired". A buyer who wants to check the claims has nothing to click.

    High impactMedium effort First result in 6 weeks COO

    First action

    Ask the three customers with the strongest numbers for a 20-minute call and permission to publish.

    How to measure it

    Bookings after a case-study view

    Now
    –
    Target
    25% of bookings
    By
    90 days

    Steps

    1. 1

      Pick three stories

      One startup, one marketplace, one agency, matching the three use cases on the homepage.

      COO 1 day

    2. 2

      Get permission and numbers

      A short call and written approval; pull reply and deal figures from the customer's reports with their consent.

      COO 2 weeks

    3. 3

      Write to one template

      Before, change, after, a quote and one chart, about 500 words each.

      CEO 1 week

    4. 4

      Publish and link

      A /customers/ section; link testimonial cards and logos to the stories.

      Lead Engineer 2 days

    5. 5

      Clean the proof section

      Correct "Aquired", fix or remove placeholder social links, and unlink logos without a story.

      Lead Engineer 1 hour

    6. 6

      Use in sales

      Add the matching story to each call follow-up (idea 2).

      CEO ongoing

    First result
    6 weeks
    Cost
    Staff time; optional design help for charts
    Owner
    COO

    Smallest test

    Publish one story and add it to the next ten call follow-ups.

    Why it works

    Write three case studies first, each one page: the sending problem before, what Lightmeter changed, and the numbers after (replies per week, positive reply rate, deals attributed). Link each testimonial card and logo to its story, correct the spelling, and remove or fix the placeholder social links. Use the new revenue reports to show reply-to-deal figures where the customer agrees.

    A managed service asks for more trust than a tool with a free trial. Named stories with before-and-after numbers do that work on the page, in sales follow-ups and in search results for the customer's own sector.

    Risks and how to handle them

    • Customers will not share numbers

      Offer ranges or percentages and let them approve the final text.

    Evidence

    • Your websiteHomepage proof: five named testimonials (one reports going from zero replies to about 150 a week, another open rates rising from 40% to 85%), "Exits powered by lightmeter" with "Aquired by Splashtop" and "Aquired by Roblox" (spelled that way), a Y Combinator badge, and features including "Warmup Warrantee", daily inbox testing, backup domains and address validation. No case-study pages exist.Source
    • Your websiteLink check (November 16, 2026): the "Book Call" button in the closing "Start sending in 7 days." banner links to "#" on the homepage and on both blog posts, while the header and hero buttons open a booking calendar. The three use-case tabs (B2B Startups, Marketplaces, GTM Agencies) and the ten customer logos also link to "#", the footer Twitter icon opens twitter.com's front page, and two of the five testimonial cards link to the twitter.com and linkedin.com front pages.Source
    • Your websiteProduct post (November 7, 2026): commercial reports named Deals Board, Funnel, Flow, Momentum and Revenue plus a Deal Slack Report; conversations are labelled "Hot", "Reply needed", "Cooling" and "Gone cold"; the example funnel runs from 148 positive replies to 22 CRM deals and 5 won.Source
  • 09

    Subscriptions are monthly and can be cancelled at any time, so a customer whose sending drops has usually decided to leave before anyone notices. The opposite signal is also hidden: mailbox capacity is a rolling 24-hour limit, and a customer who hits it every day needs more infrastructure. Both signals already sit in the capacity, volume and reply reports, but a five-person team cannot read every workspace each week.

    High impactMedium effort First result in 6 weeks Operations

    First action

    Pull last month's sending volume per workspace and mark the three that fell most.

    How to measure it

    Net revenue retention

    Now
    –
    Target
    above 100%
    By
    2 quarters

    Steps

    1. 1

      Define the three signals

      Exact thresholds for at capacity, declining and unanswered positive replies, agreed with the people who know the accounts.

      COO 1 day

    2. 2

      Build the weekly pull

      A scheduled job reads volume, capacity, reply and conversation reports per workspace through the API and stores a weekly row.

      DevOps Engineer 1 week

    3. 3

      Score and explain

      Each flagged account gets the signal, the numbers behind it and a suggested action.

      Lead Engineer 3 days

    4. 4

      Draft the customer note

      A short, specific message for the customer's channel, held for approval.

      Lead Engineer 2 days

    5. 5

      Review weekly

      Operations reads the digest on Monday, sends or edits notes and books calls for the top risks.

      Operations 1 hour a week

    6. 6

      Measure

      Cancellations among flagged accounts that were contacted against those that were not; upgrades after a capacity flag.

      COO monthly

    First result
    6 weeks
    Cost
    About three weeks of build time
    Owner
    Operations

    Smallest test

    Do the review by hand in a spreadsheet for four weeks.

    Why it works

    Build a weekly account review. Input: per-workspace volume, capacity use, positive replies and open conversations from the reporting API. It scores each account on three things: at capacity for most of the week (expansion), sending or positive replies falling for two weeks (risk), and positive replies left unanswered (lost value under performance pricing). Output is one internal digest with a suggested action per flagged account and a drafted note for the customer's channel. Operations chooses which notes to send and makes any offer.

    With month-to-month terms, the weeks before a cancellation are the only time to act. The same check surfaces customers ready to grow, which is the cheapest new revenue a managed service has.

    Risks and how to handle them

    • Seasonal dips look like churn

      Compare with the customer's own history and let a person decide.

    • Capacity flags read as upselling

      Lead with the customer's results and what more capacity would add.

    Evidence

    • Your docsBeam docs on capacity and events: mailbox capacity "returns as accepted sends become 24 hours old; it does not reset at midnight"; sharing domains or mailboxes "adds no capacity"; webhooks fire on positive_reply, reply_received and deal_summary; the docs advise direct Slack webhooks because Zapier "often rewrites or flattens the payload"; reports cover domains, mailboxes, capacity, deliverability, volume and revenue.Source
    • Your websiteTerms: "You will be subject to monthly subscription fees in accordance with the fee schedule", with rates "stated on the Lightmeter.io website" in US dollars; billing is monthly and can be cancelled at any time; the service is provided "as is" and the provider "does not guarantee that emails will be delivered without delay."Source
    • Your docsBeam docs on performance pricing: "Only positive replies count. Neutral and negative replies, automated messages, bounces, and delivery failures do not." Six reply categories count as positive (for example meeting scheduled or requested proposal), and a correction "updates reporting and can affect performance pricing."Source
  • 10

    The self-serve tools a prospect is most likely using show a price or a free start on their first screen: plans from $39 a month, mailboxes at a few dollars each, "Join 50,000+ sales teams". Lightmeter's homepage argues that "Self-service tools and DIY Delivery lag behind", but the site has no page that makes the comparison concrete, so a buyer searching for an alternative to their current tool never finds Lightmeter.

    High impactMedium effort First result in 2 months CEO

    First action

    Ask the last ten customers which tool they used before Lightmeter.

    How to measure it

    Comparison-page bookings

    Now
    –
    Target
    10 a month
    By
    90 days

    Steps

    1. 1

      Pick three starting points

      The tools most often named by new customers.

      CEO 1 day

    2. 2

      Check facts on the day

      Each rival's current price and claims from its own site, with the date.

      Operations 1 day

    3. 3

      Write the pages

      Same seven rows on each page, plus a paragraph on who should stay with the other tool.

      CEO 1 week

    4. 4

      Add proof

      One customer quote per page from someone who switched.

      COO 1 week

    5. 5

      Publish and link

      Under /compare/, linked from the footer and the pricing page.

      Lead Engineer 1 day

    6. 6

      Refresh quarterly

      Re-check prices and claims; update the date.

      Operations quarterly

    First result
    2 months
    Cost
    Staff time only
    Owner
    CEO

    Smallest test

    Publish one page for the most common previous tool.

    Why it works

    Write three fair comparison pages, one per common starting point: a self-serve sequencer, an all-in-one outreach suite, and bought-in mailboxes. Each covers who runs deliverability, where mail is sent from, what you pay for (volume, mailboxes or positive replies), what happens when a domain is blocked, CRM and revenue reporting, and time to start. Say plainly when the self-serve tool is the better choice (very small volume, tight budget). Date every page and re-check rivals' claims before publishing.

    Comparison searches come from people with a live problem and a budget. An honest page that names the trade-off wins the buyers Lightmeter is right for and saves calls with those it is not.

    Risks and how to handle them

    • A claim about a rival goes out of date

      Date each page, cite the rival's own site and review quarterly.

    Builds on

    Evidence

    • Competitor researchRivals' own homepages: Instantly ("Find Clients", "Join 50,000+ sales teams", start free with no credit card); Smartlead ("Get More Replies. Build More Pipeline", plans from $39 to $379 a month); Mailforge ("Get Started With Cold Email Infrastructure Ready In Minutes", "$3 to $2 per mailbox per month"). All three are self-serve with a public price or free start.Source
    • Your websiteSitemap (checked November 16, 2026): 8 pages and 2 posts: home, about-us, request-information, terms, privacy, integrations, integrations/close and integrations/hubspot. There is no pricing page (/pricing/ returns 404) and no product, comparison, case-study or use-case page. The integrations pages are not linked from the homepage or the menu.Source
    • Your docsBeam docs on performance pricing: "Only positive replies count. Neutral and negative replies, automated messages, bounces, and delivery failures do not." Six reply categories count as positive (for example meeting scheduled or requested proposal), and a correction "updates reporting and can affect performance pricing."Source
  • 11

    The docs include a section for teams "replacing existing Instantly webhook automations": Beam can emit events in the format those teams' existing automations already expect, so they can move without rebuilding what sits downstream. That is real engineering aimed at one of the largest pools of potential customers, and it is mentioned nowhere on the public site.

    Medium impactLow effort First result in 1 month Lead Engineer

    First action

    List the compatible events from the docs and write one paragraph for each in plain language.

    How to measure it

    Switcher bookings

    Now
    –
    Target
    8 a month
    By
    90 days

    Steps

    1. 1

      List what carries over

      Leads, blocklists, webhook events and CRM links, each with the docs section that covers it.

      Lead Engineer 1 day

    2. 2

      Write the move plan

      Day-by-day for the first week and what the customer needs to provide.

      Operations 1 day

    3. 3

      Write the page

      Carries over, changes, plan, questions; one screen each.

      CEO 2 days

    4. 4

      Add a switching call

      A booking type with questions about current tool, volume and automations.

      COO 1 hour

    5. 5

      Publish and link

      From the comparison pages, the docs section and the footer.

      Lead Engineer 1 day

    6. 6

      Measure

      Bookings from the page and days from agreement to first send for switchers.

      COO monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    Lead Engineer

    Smallest test

    Send the draft page to three recent switchers and ask what is missing.

    Why it works

    Publish a "Switching to Lightmeter" page: what carries over (leads by file import, blocklists, webhook automations through the compatible event format), what changes (who manages deliverability, how you pay), a week-by-week move plan that fits the "Start sending in 7 days" promise, and the questions switchers ask. Offer a switching call in place of the generic intro call.

    The fear in switching outreach tools is breaking the automations behind it. Showing that the compatibility work is done removes the main objection for teams already frustrated with self-managed deliverability.

    Risks and how to handle them

    • The page promises more compatibility than exists

      List only the events the docs name and link to the docs for the current list.

    Evidence

    • Your websiteIntegration pages: Close and HubSpot each have a page headed "From positive reply to Closed Won." The docs also cover Salesforce ("Connect Salesforce to send positive conversations to the rep responsible for follow-up") and Instantly-compatible webhook events for teams "replacing existing Instantly webhook automations", but the site has no Salesforce page and no switching page.Source
    • Your websiteHomepage: H1 "Turn-key Outreach Infrastructure"; the menu has three links (Home, Updates, About) and a "Book Call" button; the closing banner says "Start sending in 7 days." and "Up to 7,500 emails daily with express warmup." The page shows no price and does not mention Beam, the API, the MCP server or the CRM integrations.Source
  • 12

    The integrations section has pages for Close and HubSpot. The docs describe a third integration, Salesforce, which sends positive conversations to the responsible rep and reads opportunities for revenue attribution. Salesforce is the CRM larger sales teams use, and those teams cannot see on the site that it is supported.

    Medium impactLow effort First result in 1 month Lead Engineer

    First action

    Copy the HubSpot page and replace its content from the Salesforce docs section.

    How to measure it

    Salesforce-user bookings

    Now
    –
    Target
    5 a month
    By
    90 days

    Steps

    1. 1

      Draft from the docs

      Follow-up on positive replies, attribution, booked meetings; keep the docs' cautious wording.

      Lead Engineer 1 day

    2. 2

      Write the questions

      Does it create records, does it change opportunities, how are duplicates handled.

      Operations half a day

    3. 3

      Build the page

      Same template as Close and HubSpot, with a link to the setup guide.

      Lead Engineer 1 day

    4. 4

      Update the index

      Three cards on /integrations/ and a title that names all three.

      Lead Engineer 1 hour

    5. 5

      Link from the homepage

      A CRM row on the homepage and the menu link from idea 1.

      Lead Engineer 1 hour

    6. 6

      Measure

      Search visits to the page and bookings that mention Salesforce.

      COO monthly

    First result
    1 month
    Cost
    $0
    Owner
    Lead Engineer

    Smallest test

    Add a Salesforce card to the integrations index that links to the docs section.

    Why it works

    Build /integrations/salesforce/ on the same template as the other two: what syncs, what stays untouched (the docs say records are never reassigned and opportunities are read without changes), how attribution works, a sample follow-up cadence and the usual questions. Add it to the integrations index, link all three from the homepage, and add a line on each page for teams with another CRM pointing to the API and webhooks.

    Integration pages catch buyers searching for their CRM plus outreach, and they answer a qualifying question before the call. The template and the documentation already exist.

    Risks and how to handle them

    • The integration is still limited

      Describe exactly what the docs describe and say what is not yet covered.

    Builds on

    Evidence

    • Your websiteIntegration pages: Close and HubSpot each have a page headed "From positive reply to Closed Won." The docs also cover Salesforce ("Connect Salesforce to send positive conversations to the rep responsible for follow-up") and Instantly-compatible webhook events for teams "replacing existing Instantly webhook automations", but the site has no Salesforce page and no switching page.Source
    • Your websiteSitemap (checked November 16, 2026): 8 pages and 2 posts: home, about-us, request-information, terms, privacy, integrations, integrations/close and integrations/hubspot. There is no pricing page (/pricing/ returns 404) and no product, comparison, case-study or use-case page. The integrations pages are not linked from the homepage or the menu.Source
  • 13

    The docs describe a remote MCP server that lets an AI agent work inside a Lightmeter workspace with the user's normal login, with ready prompts such as "Answer today's positive replies" and "Find open deals to nudge", and state that every action is labelled and visible in the activity log. Founders who already work inside an AI assistant are looking for exactly this, and the homepage does not mention it.

    Medium impactLow effort First result in 1 month CEO

    First action

    Record the "Answer today's positive replies" prompt on a demo workspace.

    How to measure it

    Workspaces with an active agent connection

    Now
    –
    Target
    25% of active workspaces
    By
    2 quarters

    Steps

    1. 1

      Record three prompts

      Positive replies, deals to nudge, job titles that reply; under a minute each on demo data.

      CEO 1 day

    2. 2

      Write the limits

      What needs approval and what stays in the browser, in the docs' own terms.

      Lead Engineer half a day

    3. 3

      Build the page

      Recordings, limits, activity log screenshot, setup link, booking button.

      Lead Engineer 2 days

    4. 4

      Link it

      From the Product page, the homepage AI line and the docs.

      Lead Engineer 1 hour

    5. 5

      Tell customers

      A note in each customer channel with the first prompt to try.

      Operations 1 day

    6. 6

      Measure

      Agent connections, replies answered through agents, and bookings from the page.

      COO monthly

    First result
    1 month
    Cost
    Staff time only
    Owner
    CEO

    Smallest test

    Post one recording on the company's social profile and count replies.

    Why it works

    Publish a page titled around running outbound from your assistant: three short screen recordings of the documented prompts, what the agent can and cannot do (sending needs approval; payments, agreements and credentials stay in the browser), how the activity log records each action, and a link to the setup guide. Add a short version to the Product page and mention it in the hero's "powered by AI" line, which today has nothing behind it.

    Most outreach tools talk about AI writing emails. An audited way for the buyer's own agent to handle replies and follow-ups is a different, more concrete claim, and it suits small teams with no SDR.

    Risks and how to handle them

    • Buyers worry about an agent sending email unsupervised

      Lead with approvals and the activity log, and show a send being approved.

    Builds on

    Evidence

    • Your docsMCP and API docs: a remote MCP server lets AI agents work in a Lightmeter workspace with the user's normal login, with example prompts "Answer today's positive replies", "Find open deals to nudge" and "See which job titles reply positively"; "All actions are tracked (labelled 'MCP') and visible in the Activity Log of your account." The public API covers leads, campaigns, Unibox, analytics, infrastructure, workspace settings, agreements and webhooks.Source
    • Your websiteHomepage: H1 "Turn-key Outreach Infrastructure"; the menu has three links (Home, Updates, About) and a "Book Call" button; the closing banner says "Start sending in 7 days." and "Up to 7,500 emails daily with express warmup." The page shows no price and does not mention Beam, the API, the MCP server or the CRM integrations.Source
  • 14

    A sales-tools directory files Lightmeter under "Email Spam Tester" and describes it as "Web-based management for mailserver health and delivery". That is the old open-source Control Center, not the managed delivery service. Buyers and AI assistants read these listings, and each wrong one sends the wrong audience or hides Lightmeter from the right one. Nobody on a five-person team has time to check dozens of directories by hand.

    Medium impactLow effort First result in 6 weeks Operations

    First action

    Write the approved 50-word description and category for the delivery service.

    How to measure it

    Accurate listings

    Now
    –
    Target
    90%
    By
    90 days

    Steps

    1. 1

      Write the approved profile

      Description, category, features, pricing line, logo and link.

      CEO half a day

    2. 2

      Build the listing list

      Search for pages that list Lightmeter; record the address and how each accepts corrections.

      Operations 1 day

    3. 3

      Build the monthly check

      A scheduled job reads each public listing and scores it against the approved profile on product, category, price and link.

      Lead Engineer 4 days

    4. 4

      Draft the corrections

      For each wrong listing, a short request with the corrected text, saved to a review sheet.

      Lead Engineer 2 days

    5. 5

      Review and send

      Operations approves each request and submits it through the directory's own route.

      Operations 2 hours a month

    6. 6

      Measure

      Accurate listings as a share of all, and referral visits from directories.

      COO monthly

    First result
    6 weeks
    Cost
    About a week of build time, then two hours a month
    Owner
    Operations

    Smallest test

    Correct the one listing found here by hand and note how long it takes to change.

    Why it works

    Build a monthly listings check. Input: a list of directory, review and comparison pages that mention Lightmeter, plus one approved description, category, feature list and pricing line. The automation reads each listing, compares it with the approved text, and reports which are wrong (old product, wrong category, wrong price, missing link) with a drafted correction request for each site's edit or contact route. Operations reviews the report and sends the requests; the automation does not contact anyone. New mentions found by search are added to the list for review.

    Listings are read by people comparing options and are a source for AI-generated answers. Correcting them is repetitive work that suits automation, and the approved description doubles as the standard wording for the site.

    Risks and how to handle them

    • Directories ignore requests

      Claim profiles where the directory allows it and prioritise the ones that send visits.

    • Some sites block automated readers

      Check those by hand and leave them off the automated list.

    Builds on

    Evidence

    • Directory listingA sales-tools directory lists Lightmeter under "Email Spam Tester", describes it as "Web-based management for mailserver health and delivery" (the older open-source Control Center, not the delivery service) and says "Lightmeter does not display pricing on the website".Source
    • Control Center site"Smart Postfix Monitoring", version 1.9.1, footer "Copyright 2022", newsletter and contact forms showing as unrendered shortcodes, and no link to lightmeter.io. The lightmeter/controlcenter Docker image has 75,672 pulls.Source
    • Y Combinator directory"Lightmeter is turn-key email outreach infrastructure for startups, combining network, platform, and expert advice." Winter 2022 batch, team size 5, no open jobs. The homepage says "Lightmeter grew out of a demand from B2B startups in YCombinator", and startups.lightmeter.io now redirects to the homepage.Source
  • 15

    Lightmeter now knows when its outreach produced revenue: the reports follow a positive reply through to a deal marked Won, and a deal summary event can be sent to Slack. The company grew through founders telling other founders in one startup network. The best moment to ask for an introduction is the day a customer closes a deal that started with a Lightmeter email, and today that moment passes unnoticed.

    Medium impactLow effort First result in 1 quarter COO

    First action

    List the deals marked Won in the last 90 days and which customers they belong to.

    How to measure it

    Referral introductions

    Now
    –
    Target
    10 a quarter
    By
    2 quarters

    Steps

    1. 1

      Set the reward and rules

      What the referrer gets, one ask per customer per quarter, and who is excluded.

      COO 1 day

    2. 2

      Listen for Won deals

      Subscribe an internal endpoint to the deal events for all workspaces and filter for attributed deals marked Won.

      Lead Engineer 2 days

    3. 3

      Draft the message

      Congratulation with the reply-to-won dates and one clear ask, written to a template.

      CEO half a day

    4. 4

      Add approval

      Drafts appear internally; a founder approves, edits or skips before anything posts.

      Lead Engineer 1 day

    5. 5

      Track introductions

      A referral source field on the booking form and in the CRM.

      Operations half a day

    6. 6

      Measure

      Asks sent, introductions, bookings and customers won, each quarter.

      COO quarterly

    First result
    1 quarter
    Cost
    About a week of build time plus the reward
    Owner
    COO

    Smallest test

    Send three hand-written asks to customers with a recent Won deal.

    Why it works

    Build a small trigger. Input: the deal summary and Won events per workspace. When a customer's attributed deal is marked Won, the automation drafts a short congratulation for the customer's channel that states the path (first email date, reply date, won date) and asks for one introduction to a founder with the same problem, with a referral reward the team decides. It is limited to one ask per customer per quarter. A founder approves each message; a monthly internal summary lists asks, introductions and bookings.

    A referral request tied to a specific result the customer just saw is far easier to say yes to than a generic programme, and it reminds the customer what the service earned them in the same message.

    Risks and how to handle them

    • Customers without a connected CRM never trigger it

      Use the manual Won mark in the Deals Board as a second trigger.

    • The ask feels automated

      A founder edits and sends each one.

    Evidence

    • Your websiteProduct post (November 7, 2026): commercial reports named Deals Board, Funnel, Flow, Momentum and Revenue plus a Deal Slack Report; conversations are labelled "Hot", "Reply needed", "Cooling" and "Gone cold"; the example funnel runs from 148 positive replies to 22 CRM deals and 5 won.Source
    • Your docsBeam docs on capacity and events: mailbox capacity "returns as accepted sends become 24 hours old; it does not reset at midnight"; sharing domains or mailboxes "adds no capacity"; webhooks fire on positive_reply, reply_received and deal_summary; the docs advise direct Slack webhooks because Zapier "often rewrites or flattens the payload"; reports cover domains, mailboxes, capacity, deliverability, volume and revenue.Source
    • Y Combinator directory"Lightmeter is turn-key email outreach infrastructure for startups, combining network, platform, and expert advice." Winter 2022 batch, team size 5, no open jobs. The homepage says "Lightmeter grew out of a demand from B2B startups in YCombinator", and startups.lightmeter.io now redirects to the homepage.Source
  • 16

    "GTM Agencies" is one of three audiences on the homepage, promised "predictable performance and costs", but its tab is a dead link and there is no agency page. The product already has what agencies need: separate workspaces, cross-workspace reports and an API. One agency that standardises on Lightmeter brings every client it runs outreach for.

    High impactMedium effort First result in 1 quarter COO

    First action

    Count current customers that are agencies and how many client workspaces each runs.

    How to measure it

    Partner-sourced workspaces

    Now
    –
    Target
    15
    By
    2 quarters

    Steps

    1. 1

      Interview current agencies

      What they need for client reporting, billing and onboarding.

      COO 2 weeks

    2. 2

      Set partner terms

      Margin or per-client rate, and who signs the agreement.

      CEO 1 week

    3. 3

      Write the agency page

      Multi-client view, reporting, billing, what Lightmeter owns.

      CEO 3 days

    4. 4

      Fix the homepage tab

      Link "GTM Agencies" to the new page.

      Lead Engineer 1 hour

    5. 5

      Create a fast path for later clients

      A template workspace and checklist so an agency's next client starts in days.

      Operations 1 week

    6. 6

      Recruit five partners

      Existing agency customers first, then agencies named by customers.

      COO 1 quarter

    7. 7

      Measure

      Workspaces per partner and retention of partner-sourced clients.

      COO quarterly

    First result
    1 quarter
    Cost
    Staff time plus partner margin
    Owner
    COO

    Smallest test

    Offer partner terms to one existing agency customer for its next two clients.

    Why it works

    Publish an agency page: one login across client workspaces, per-client reporting to show clients their replies and attributed deals, how billing works when clients pay or when the agency does, and what Lightmeter handles so the agency does not own deliverability failures. Add partner terms (a margin or a per-client rate) and a short onboarding path for the agency's second and later clients. Start with the agencies already among customers.

    Agencies are measured by clients on replies and meetings, which is what Lightmeter measures and bills on. A partner with ten clients is ten customers acquired with one sale.

    Risks and how to handle them

    • Agency clients with poor lists hurt shared reputation

      Keep staff launch approval for every client workspace.

    Builds on

    Evidence

    • Your websiteLink check (November 16, 2026): the "Book Call" button in the closing "Start sending in 7 days." banner links to "#" on the homepage and on both blog posts, while the header and hero buttons open a booking calendar. The three use-case tabs (B2B Startups, Marketplaces, GTM Agencies) and the ten customer logos also link to "#", the footer Twitter icon opens twitter.com's front page, and two of the five testimonial cards link to the twitter.com and linkedin.com front pages.Source
    • Your docsMCP and API docs: a remote MCP server lets AI agents work in a Lightmeter workspace with the user's normal login, with example prompts "Answer today's positive replies", "Find open deals to nudge" and "See which job titles reply positively"; "All actions are tracked (labelled 'MCP') and visible in the Activity Log of your account." The public API covers leads, campaigns, Unibox, analytics, infrastructure, workspace settings, agreements and webhooks.Source
  • 17

    Lightmeter says it "grew out of a demand from B2B startups in YCombinator", carries the badge on its homepage and lists two customers that were later acquired. There was once a dedicated startups address; it now redirects to the generic homepage. The audience that started the company has no page written for it.

    Medium impactLow effort First result in 1 month CEO

    First action

    Point the old startups address at a new /startups/ draft page.

    How to measure it

    Startup-page bookings

    Now
    –
    Target
    12 a month
    By
    90 days

    Steps

    1. 1

      Define the founder offer

      A simple first-month package and what it includes.

      CEO 2 days

    2. 2

      Write the page

      First campaign, seven-day start, pricing on positive replies, founder quotes, the two exits.

      CEO 2 days

    3. 3

      Build and redirect

      Publish /startups/ and point the old address to it.

      Lead Engineer 1 day

    4. 4

      Fix the homepage tab

      Link "B2B Startups" to the page.

      Lead Engineer 1 hour

    5. 5

      List the offer

      In the startup network's deals listing and founder communities where vendors are welcome.

      COO 1 week

    6. 6

      Measure

      Bookings by source and conversion of the founder offer to ongoing customers.

      COO monthly

    First result
    1 month
    Cost
    Staff time plus the cost of the founder offer
    Owner
    CEO

    Smallest test

    Publish the page and share it with the last five founder customers for feedback and forwarding.

    Why it works

    Rebuild the startups page for founders doing their own outbound: what a first campaign looks like, the seven-day start, pricing that follows positive replies so an early-stage team is not paying for volume, the two acquisition stories and the testimonials from founders. Add a founder offer (for example a fixed first-month package) and post it where batch founders look for vendor deals. Point the old address at the new page.

    Founders buy from companies that other founders in their network used. A page that speaks to a team with no SDR and no deliverability knowledge converts that word of mouth better than a general homepage.

    Risks and how to handle them

    • Very early teams have no list or offer to send

      Qualify on the booking form and point the earliest teams to a guide first.

    Builds on

    Evidence

    • Y Combinator directory"Lightmeter is turn-key email outreach infrastructure for startups, combining network, platform, and expert advice." Winter 2022 batch, team size 5, no open jobs. The homepage says "Lightmeter grew out of a demand from B2B startups in YCombinator", and startups.lightmeter.io now redirects to the homepage.Source
    • Your websiteHomepage proof: five named testimonials (one reports going from zero replies to about 150 a week, another open rates rising from 40% to 85%), "Exits powered by lightmeter" with "Aquired by Splashtop" and "Aquired by Roblox" (spelled that way), a Y Combinator badge, and features including "Warmup Warrantee", daily inbox testing, backup domains and address validation. No case-study pages exist.Source
  • 18

    The only route for a visitor who is interested but not ready for a call is a form that the homepage does not link to. It asks for the email address twice and a required phone number, shows a consent line about text messages, and does not say what happens after submitting. Visitors in other time zones, or anyone who prefers to read first, have no easy option.

    Medium impactLow effort First result in 2 weeks Operations

    First action

    Remove the second email field and make the phone number optional.

    How to measure it

    Form leads that book a call

    Now
    –
    Target
    30% within 30 days
    By
    90 days

    Steps

    1. 1

      Cut the fields

      Work email, company website, current tool; phone optional; one consent line that matches what you will send.

      Operations 1 hour

    2. 2

      Write the confirmation

      What they will receive and by when.

      Operations 1 hour

    3. 3

      Write the reply email

      Pricing, the right integration page, one case study, booking link.

      CEO half a day

    4. 4

      Link it

      A second link beside each booking button and in the footer.

      Lead Engineer half a day

    5. 5

      Connect to follow-up

      Form entries create a CRM record and enter the brief flow.

      Lead Engineer 1 day

    6. 6

      Measure

      Submissions, reply-email opens and bookings from form leads.

      COO monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Operations

    Smallest test

    Link the existing form from the homepage for two weeks and count submissions.

    Why it works

    Rework the form into "Get the details by email": work email, company website and current sending tool, with phone optional. On submit, show a confirmation that says what arrives and when, and send a short email with the pricing page, the matching integration page and a booking link. Link the form beside every "Book Call" button as the second option. Form leads feed the same brief and follow-up flow as bookings (idea 2).

    A second, lower-commitment step catches the visitors the single booking button loses, and asking for less raises completion. A stated next step makes the form trustworthy.

    Risks and how to handle them

    • The form draws low-quality leads

      Require a work email and company website.

    Builds on

    Evidence

    • Your websiteBooking path: every working "Book Call" button opens one founder's personal intro-call calendar. The only form, /request-information/, asks for first and last name, email twice and a required phone number, is not linked from the homepage, and does not say what happens after submitting.Source
    • Your websiteLink check (November 16, 2026): the "Book Call" button in the closing "Start sending in 7 days." banner links to "#" on the homepage and on both blog posts, while the header and hero buttons open a booking calendar. The three use-case tabs (B2B Startups, Marketplaces, GTM Agencies) and the ten customer logos also link to "#", the footer Twitter icon opens twitter.com's front page, and two of the five testimonial cards link to the twitter.com and linkedin.com front pages.Source

Big bets 3

Larger plays that can change the trajectory.

  • 19

    The About page says the team has delivered over 80 billion emails in about a decade. The 2024 article quotes house averages of about 60% opens and 5% replies, and the product classifies every reply into positive, neutral and negative categories. Most published outreach benchmarks come from tools that count sends and opens. Lightmeter can publish what share of outreach gets an interested reply, by sector, title and step, which almost nobody else measures in the same way.

    High impactHigh effort First result in 1 quarter CEO

    First action

    Check what the terms and privacy policy allow for aggregated reporting, and add an opt-in if needed.

    How to measure it

    Referring sites to the benchmark

    Now
    –
    Target
    50
    By
    2 quarters after launch

    Steps

    1. 1

      Confirm permission

      Review terms and privacy wording for aggregated use; add consent where needed.

      COO 2 weeks

    2. 2

      Choose ten questions

      The questions a founder would ask about outreach, each answerable from reply and campaign data.

      CEO 1 week

    3. 3

      Build the dataset

      Aggregate by sector, title, step and month with minimum group sizes so no customer can be identified.

      Lead Engineer 3 weeks

    4. 4

      Write and chart

      One chart and one paragraph per question, with the method stated.

      CEO 3 weeks

    5. 5

      Publish

      A page, a PDF, and single-chart posts over five weeks.

      Lead Engineer 1 week

    6. 6

      Pitch it

      To newsletters and communities for founders and sales leaders, with one exclusive chart each.

      COO 1 month

    7. 7

      Repeat yearly

      Same questions each year so trends can be shown.

      CEO yearly

    First result
    1 quarter
    Cost
    About two months of part-time work across three people; optional design help
    Owner
    CEO

    Smallest test

    Publish one chart, positive reply rate by job title, and see who shares it.

    Why it works

    Publish a yearly report built from aggregated, anonymised campaign data: positive reply rate by industry and job title, which step in a sequence earns the reply, how long from positive reply to deal, and how bounce rates relate to list source. State the method and sample sizes, exclude anything that could identify a customer, and get customer consent in the terms or by opt-in. Release it as a page with charts, a short PDF and five single-chart posts, and offer the data to newsletters that write for founders and sales leaders.

    Original numbers earn links, citations in AI answers and press that a five-person team cannot buy. It also teaches the market to measure outreach by positive replies, the unit Lightmeter prices on.

    Risks and how to handle them

    • Customers object to their data being used

      Aggregate only, set minimum group sizes and offer an opt-out.

    • The sample is too small in some sectors

      Publish only groups above a stated size.

    Evidence

    • Your websiteAbout page: the team has run email delivery for about a decade and delivered over 80 billion emails; the founders grew the open-source project phpList to 80,000 users and then built Lightmeter Control Center. Roles shown: CEO, COO, Lead Engineer, Accounting, DevOps Engineer and Operations. "Join our team" is an email link, not a job board.Source
    • Your websiteBlog: two posts in total. "Sales email vs Marketing email: what's the difference?" (February 5, 2024) lives at /3-experiments-to-improve-your-performance-and-kpis-3/ and says Lightmeter averages about 60% open and 5% reply rates for customers with open tracking on. The next post, "Track your outbound pipeline through to revenue", is dated November 7, 2026.Source
    • Your docsBeam docs on performance pricing: "Only positive replies count. Neutral and negative replies, automated messages, bounces, and delivery failures do not." Six reply categories count as positive (for example meeting scheduled or requested proposal), and a correction "updates reporting and can affect performance pricing."Source
  • 20

    Rivals let a buyer start in minutes with a card: a free start, plans from $39 a month, mailboxes at a few dollars each. Lightmeter's only entry is a call with a founder, which caps new customers at the hours a founder can spend on calls. The API docs already list agreement acceptance, billing state and checkout among the things the platform handles, so much of the machinery for a guided self-start exists.

    High impactHigh effort First result in 1 quarter CEO

    First action

    Count how many of the last 50 calls were small senders who could have started without a call.

    How to measure it

    Self-started customers

    Now
    –
    Target
    30% of new customers
    By
    3 quarters

    Steps

    1. 1

      Size the segment

      Share of recent calls and customers below a volume threshold.

      COO 1 week

    2. 2

      Define the starter package

      Volume, mailboxes, price and what is included, with performance pricing explained.

      CEO 2 weeks

    3. 3

      Connect agreement and payment

      A web flow from package choice to accepted agreement and paid checkout, using the existing agreement and billing functions.

      Lead Engineer 1 month

    4. 4

      Keep the launch review

      Staff review the first campaign and enable launch; publish the review time.

      Operations ongoing

    5. 5

      Cap and pilot

      A weekly limit on sign-ups for the first two months.

      COO 2 months

    6. 6

      Compare cohorts

      Time to first positive reply, support load and retention for self-started against call-started customers.

      COO quarterly

    First result
    1 quarter
    Cost
    One to two months of engineering time plus support capacity
    Owner
    CEO

    Smallest test

    Offer the next ten small prospects a pay-and-start link in place of a call.

    Why it works

    Design a starter path for small teams: choose a package on the pricing page, accept the agreement and pay online, then follow the existing setup steps with the chaser from idea 4. Keep what makes the service managed: staff still review and enable the first launch, and warmup follows the usual schedule. Calls remain for larger senders and agencies. Test with one package and a capped number of sign-ups per week so the delivery team is not overloaded.

    It removes the founder's calendar as the limit on growth for the smallest customers while keeping staff approval where it protects sending reputation. It also answers the first question a comparison shopper asks: can I start now?

    Risks and how to handle them

    • Self-started customers send poor lists

      Keep staff launch approval and address validation before the first send.

    • Support load grows faster than revenue

      Cap weekly sign-ups and price the package to cover onboarding.

    Builds on

    Evidence

    • Competitor researchRivals' own homepages: Instantly ("Find Clients", "Join 50,000+ sales teams", start free with no credit card); Smartlead ("Get More Replies. Build More Pipeline", plans from $39 to $379 a month); Mailforge ("Get Started With Cold Email Infrastructure Ready In Minutes", "$3 to $2 per mailbox per month"). All three are self-serve with a public price or free start.Source
    • Your docsMCP and API docs: a remote MCP server lets AI agents work in a Lightmeter workspace with the user's normal login, with example prompts "Answer today's positive replies", "Find open deals to nudge" and "See which job titles reply positively"; "All actions are tracked (labelled 'MCP') and visible in the Activity Log of your account." The public API covers leads, campaigns, Unibox, analytics, infrastructure, workspace settings, agreements and webhooks.Source
    • Your websiteBooking path: every working "Book Call" button opens one founder's personal intro-call calendar. The only form, /request-information/, asks for first and last name, email twice and a required phone number, is not linked from the homepage, and does not say what happens after submitting.Source
  • 21

    Lightmeter's features include daily inbox testing, address validation and backup domains, run by people who describe themselves as the biggest email nerds in the room. Prospects, though, can only experience that expertise after a call. Teams whose outreach has stopped landing search for a way to find out why, and that search is the moment they are open to a managed service.

    High impactHigh effort First result in 1 quarter Lead Engineer

    First action

    List the ten checks the team runs by hand when a prospect says their email is going to spam.

    How to measure it

    Readiness checks that book a call

    Now
    –
    Target
    10%
    By
    2 quarters

    Steps

    1. 1

      Choose the checks

      Five to eight public checks that most often explain poor delivery.

      DevOps Engineer 1 week

    2. 2

      Write the explanations

      What each result means and what to do, in language for a founder.

      CEO 1 week

    3. 3

      Build the check

      A form, the lookups, a scored report page and an emailed copy.

      Lead Engineer 1 month

    4. 4

      Limit abuse

      Work email required, rate limits, and checks only on the domain entered.

      DevOps Engineer 1 week

    5. 5

      Connect to sales

      Each report creates a lead with its findings attached for the call brief.

      Lead Engineer 3 days

    6. 6

      Promote and measure

      Link from the homepage, comparison pages and posts; track checks, bookings and customers.

      COO monthly

    First result
    1 quarter
    Cost
    Six to eight weeks of engineering time
    Owner
    Lead Engineer

    Smallest test

    Offer the check by hand: a form, and a person emails the report within a day, for the first 20 requests.

    Why it works

    Offer a free check on the site: the visitor enters a sending domain and work email, and receives a short report on the public signs of sending readiness, a plain-language explanation of each finding and what Lightmeter would do about it. Deeper checks (inbox placement across providers, list quality) are offered on a call. The report is emailed, so every check is a lead with context for the brief in idea 2. Use only public records and the visitor's own input.

    A diagnostic gives value before asking for anything and shows the team's expertise on the prospect's own domain. It also creates a reason to return, and pages that rank for the problems buyers search for.

    Risks and how to handle them

    • Free checks already exist elsewhere

      Differentiate on the explanation and the specific fix, not on the raw result.

    • Visitors fix the problem themselves and leave

      That builds goodwill; show which problems cannot be fixed without different infrastructure.

    Builds on

    Evidence

    • Your websiteHomepage proof: five named testimonials (one reports going from zero replies to about 150 a week, another open rates rising from 40% to 85%), "Exits powered by lightmeter" with "Aquired by Splashtop" and "Aquired by Roblox" (spelled that way), a Y Combinator badge, and features including "Warmup Warrantee", daily inbox testing, backup domains and address validation. No case-study pages exist.Source
    • Your websiteAbout page: the team has run email delivery for about a decade and delivered over 80 billion emails; the founders grew the open-source project phpList to 80,000 users and then built Lightmeter Control Center. Roles shown: CEO, COO, Lead Engineer, Accounting, DevOps Engineer and Operations. "Join our team" is an email link, not a job board.Source

Wildcards 3

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

  • 22

    Before the delivery service, the team built Lightmeter Control Center, an open-source mail server monitor whose container image has been pulled more than 75,000 times. Its website still stands, with a 2022 copyright line, forms that show as raw placeholder text, and no link to lightmeter.io. People who run their own mail servers work at companies that send sales email, and they already trust the name.

    Medium impactLow effort First result in 1 quarter DevOps Engineer

    First action

    Add a banner on the Control Center homepage linking to lightmeter.io.

    How to measure it

    Referred bookings from the open-source site

    Now
    –
    Target
    5 a quarter
    By
    2 quarters

    Steps

    1. 1

      Decide the project's status

      Maintained, community-maintained or archived; say so on the site.

      CEO 1 day

    2. 2

      Add the banner and page

      A short page explaining the delivery service for a technical reader.

      DevOps Engineer 1 day

    3. 3

      Repair the forms

      Replace the placeholder text with a working sign-up or remove it.

      DevOps Engineer half a day

    4. 4

      Update readme and image text

      One line and a link where developers find the project.

      DevOps Engineer 1 hour

    5. 5

      Tell the story on About

      The open-source history with a link to the project.

      CEO half a day

    6. 6

      Measure

      Tagged links; referred visits and bookings per quarter.

      COO quarterly

    First result
    1 quarter
    Cost
    $0
    Owner
    DevOps Engineer

    Smallest test

    Add the banner with a tagged link and count clicks for a month.

    Why it works

    Add a clear banner and a page on the Control Center site: "From the team behind Control Center: managed delivery for sales email", with a link to the delivery service and an honest note on the project's maintenance status. Fix or remove the broken forms. Add the same line to the project's readme and container description. On lightmeter.io, tell the open-source story on the About page as proof of depth, and link back.

    It reuses an audience and a reputation that were expensive to build, for the cost of a banner. Technical staff are often the ones asked whether sales email will harm the company domain, and they can recommend a provider they know.

    Risks and how to handle them

    • The open-source community dislikes a sales message

      Keep it to one honest banner and be clear about the project's status.

    Evidence

    • Control Center site"Smart Postfix Monitoring", version 1.9.1, footer "Copyright 2022", newsletter and contact forms showing as unrendered shortcodes, and no link to lightmeter.io. The lightmeter/controlcenter Docker image has 75,672 pulls.Source
    • Your websiteAbout page: the team has run email delivery for about a decade and delivered over 80 billion emails; the founders grew the open-source project phpList to 80,000 users and then built Lightmeter Control Center. Roles shown: CEO, COO, Lead Engineer, Accounting, DevOps Engineer and Operations. "Join our team" is an email link, not a job board.Source
  • 23

    The homepage lists a "Warmup Warrantee" as a feature. The terms page describes the service as provided "as is" and says delivery without delay is not guaranteed, and the fetched pages do not say what the warranty covers. A named guarantee that a buyer cannot read is a missed chance: self-serve tools leave warmup risk with the customer, and a clear promise here is something they cannot match.

    Medium impactLow effort First result in 1 quarter CEO

    First action

    Write down what the team already does today when a customer's warmup goes wrong.

    How to measure it

    Call-to-customer rate

    Now
    –
    Target
    +10%
    By
    2 quarters

    Steps

    1. 1

      Record current practice

      What is replaced or credited today when warmup fails.

      Operations 2 days

    2. 2

      Draft the promise

      Commitment, conditions and exclusions in under 300 words.

      CEO 2 days

    3. 3

      Legal review

      Check the wording against the terms and adjust both.

      COO 2 weeks

    4. 4

      Publish and link

      A page linked from the homepage feature, pricing and terms; correct the spelling to "Warranty" if intended.

      Lead Engineer 1 day

    5. 5

      Brief the team

      How to handle a claim and where to record it.

      Operations 1 day

    6. 6

      Measure

      Claims made, cost of claims and close rate before and after.

      COO quarterly

    First result
    1 quarter
    Cost
    Legal review plus the cost of claims
    Owner
    CEO

    Smallest test

    Add one sentence under the homepage feature saying what the warranty covers.

    Why it works

    Define the warranty in a short public page: what Lightmeter commits to during warmup (for example, replacing a domain or mailbox that fails warmup at no charge and extending the start date), what the customer must do, and what is excluded. Link it from the homepage feature and the pricing page, and make sure the terms refer to it so the two do not contradict each other. Have the wording reviewed by a lawyer before publishing.

    A specific, readable guarantee lowers the risk of choosing a managed service over a cheaper tool, and paired with paying only for positive replies it makes a strong, simple offer.

    Risks and how to handle them

    • Claims cost more than expected

      Tie the promise to conditions the team controls and review after one quarter.

    Builds on

    Evidence

    • Your websiteHomepage proof: five named testimonials (one reports going from zero replies to about 150 a week, another open rates rising from 40% to 85%), "Exits powered by lightmeter" with "Aquired by Splashtop" and "Aquired by Roblox" (spelled that way), a Y Combinator badge, and features including "Warmup Warrantee", daily inbox testing, backup domains and address validation. No case-study pages exist.Source
    • Your websiteTerms: "You will be subject to monthly subscription fees in accordance with the fee schedule", with rates "stated on the Lightmeter.io website" in US dollars; billing is monthly and can be cancelled at any time; the service is provided "as is" and the provider "does not guarantee that emails will be delivered without delay."Source
  • 24

    One of the documented agent prompts is "See which job titles reply positively". That answer exists in every workspace, but only for customers who think to ask. Sent to each customer monthly it becomes a reason to keep sending and to adjust targeting; added up across customers, with names removed, it becomes a public index of which roles answer cold outreach, which is a question every founder has.

    Medium impactMedium effort First result in 2 months Lead Engineer

    First action

    Run the job-title prompt on three consenting customers' workspaces and check the answers are useful.

    How to measure it

    Average positive reply rate across customers

    Now
    –
    Target
    +10% relative
    By
    2 quarters

    Steps

    1. 1

      Define the digest

      Four numbers and one suggestion; agree the wording with two customers.

      COO 1 week

    2. 2

      Build the monthly job

      Reads campaign and reply analytics per workspace through the API, groups by title and step, and writes the digest draft.

      Lead Engineer 2 weeks

    3. 3

      Review and post

      Operations checks each digest and posts it to the customer's channel; nothing posts unreviewed.

      Operations 2 hours a month

    4. 4

      Aggregate safely

      Totals by title and sector with minimum group sizes and no names; confirm consent in the terms.

      Lead Engineer 1 week

    5. 5

      Publish the index

      A page with the monthly table and a short commentary, approved by a founder.

      CEO monthly

    6. 6

      Measure

      Targeting changes after digests, positive reply rate trend, and visits and links to the index.

      COO monthly

    First result
    2 months
    Cost
    About a month of part-time engineering
    Owner
    Lead Engineer

    Smallest test

    Write the digest by hand for five customers this month.

    Why it works

    Build a monthly digest job. Input: each workspace's campaign and reply analytics. For each customer it produces a one-screen summary: positive reply rate by job title and by sequence step, the three best and worst segments, and one suggested change for next month. Operations reviews the batch and posts each digest to the customer's channel. Separately, the job writes aggregated totals (minimum group sizes, no customer or lead names) to a table that feeds a public "reply index" page, updated monthly once a founder approves the numbers.

    Customers who see what is working send more and stay longer, and each improvement raises the positive replies Lightmeter is paid on. The public index is a recurring, citable page that costs nothing extra once the digest exists.

    Risks and how to handle them

    • Small samples give misleading advice

      Show counts beside rates and suppress groups below a minimum size.

    • Customers object to aggregated publication

      Publish only totals, with consent, and offer an opt-out.

    Evidence

    • Your docsMCP and API docs: a remote MCP server lets AI agents work in a Lightmeter workspace with the user's normal login, with example prompts "Answer today's positive replies", "Find open deals to nudge" and "See which job titles reply positively"; "All actions are tracked (labelled 'MCP') and visible in the Activity Log of your account." The public API covers leads, campaigns, Unibox, analytics, infrastructure, workspace settings, agreements and webhooks.Source
    • Your websiteProduct post (November 7, 2026): commercial reports named Deals Board, Funnel, Flow, Momentum and Revenue plus a Deal Slack Report; conversations are labelled "Hot", "Reply needed", "Cooling" and "Gone cold"; the example funnel runs from 148 positive replies to 22 CRM deals and 5 won.Source
    • Your docsBeam docs on performance pricing: "Only positive replies count. Neutral and negative replies, automated messages, bounces, and delivery failures do not." Six reply categories count as positive (for example meeting scheduled or requested proposal), and a correction "updates reporting and can affect performance pricing."Source

03

How Programmable can help

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

ProgrammableInfo

Turn the research into a list you can act on

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

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

New accounts: 100,000 free credits with code BETA100K

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

More growth playbooks

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

  • LushUs Hair growth strategyHandcrafted, plant-derived scalp and hair care built on Caribbean fruits and botanicals: shampoos, conditioners, scalp elixirs and…22 growth ideas
  • Aistetic growth strategyAn Oxford University AI spinout whose ListingFlow turns product photos into marketplace-ready listings (titles, descriptions, prices) and…22 growth ideas
  • Scout growth strategyAn AI-native student information system (Scout SIS) with agents for enrollment, compliance, state reporting and student success, plus a…22 growth ideas
  • Trainline growth strategyEurope's leading independent rail and coach ticketing platform: an app and website that search and sell tickets from hundreds of…21 growth ideas
  • Quintagroup growth strategyA Python and JavaScript software development company from Lviv, Ukraine, known for e-procurement and auction systems (the OpenProcurement…23 growth ideas
  • Next Big Innovation Labs growth strategyA Bengaluru deep-tech company that designs and builds Trivima research bioprinters (Mini, Basic, Advanced, Pro, the non-planar NP and the…21 growth ideas
  • Bosant growth strategyA Norwegian brand selling bedding in bamboo viscose and Tencel blend: duvet covers, sheets, pillowcases, pyjamas, sleep masks and wool…20 growth ideas
  • Alpen Labs growth strategyBuilds Alpen, a Bitcoin zero-knowledge rollup and financial infrastructure for vaults, BTC-backed credit, yield and stablecoins (including…21 growth ideas

See every playbook and website review

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

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

    Repair the booking path, publish the price, fix the page basics, and start the three small automations: call briefs, setup follow-up and docs-to-updates.

  2. Days 31 to 6012 ideas

    Speed, proof pages, comparison and switching pages, Salesforce and agent pages, capacity watching, listings, referrals, agencies, the startup page and a no-call path.

  3. Days 61 to 906 ideas

    Commit to the bigger bets: the benchmark report, a self-serve start and a free readiness check; test the Control Center bridge, the written warranty and the reply index.

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 replies and open rates that recover after self-managed sending failed. The most cited problem: outreach landing in spam or promotions.

  • Experts who own deliverability instead of a tool to configure
  • Domains and mailboxes burning out with self-service tools
  • In their words: “positive replies”

Market

Competitive landscape

3 competitors compared: Instantly, Smartlead and Mailforge.

  • Gap to exploit: Outreach priced on positive replies rather than mailboxes or volume
  • Instantly: The customer manages deliverability themselves
  • Smartlead: Pay for sending volume, not for results

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