ProgrammableMarketing/thirdlayer.inc (opens in a new tab)
PDF

Views

  • Plan
  • Roadmap
  • Research

On this page

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

growth playbook · Nov 10, 2026

thirdlayer.inc (opens in a new tab)

Thirdlayer growth playbook

Diagnosis

Thirdlayer (YC W25) has unusual technical credibility for a team its size: an open-source AutoAgent repository with 4.6k stars and first-place benchmark results, a Dex product with paying tiers and a Chrome extension, and a homepage logo strip of well-known tech teams. But thirdlayer.inc does little with any of that.

Both buttons are mailto links, the social links are placeholders, two of the three research posts are password-locked, there is no sitemap or favicon, and no customer outcome is told anywhere. The company also describes itself four different ways on four surfaces.

This playbook first turns the site into a working enterprise funnel: booked demos, open research, a repository that points home, one message and the basics. It then adds proof, an evaluation-led wedge for teams that already run agents, a bridge from Dex users to team deals, and published engagement terms. The bigger bets are an open company-eval template, partner delivery capacity and outcome-based pricing.

Growth Score

6/10

Biggest Opportunity

Turn the attention AutoAgent and Dex already earn (thousands of developers and operators) into qualified enterprise conversations, starting with teams that already run agents in production and need evals.

Biggest Risk

Deep forward-deployed delivery limits how many customers a small team can serve. Meanwhile Glean, Dust and Distyl win deals with public proof (named outcomes, thousands of organisations) that Thirdlayer's site does not yet show.

01

Start here

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

  1. 1

    Replace the two mailto buttons with a booked demo, and fix the dead LinkedIn and X links

    Create the booking page with the three questions and swap the two button links.

    High impact First result in 2 weeks
  2. 2

    Open the two password-locked research posts, or publish a public summary of each

    Decide per post what can be public and what stays for the call.

    Medium impact First result in 2 weeks
  3. 3

    Point AutoAgent's 4.6k-star README at the evaluation product, not only at a hiring email

    Add the evaluation block and a tagged link to the README.

    High impact First result in 2 weeks

02

Your idea portfolio

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

  • 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 · 3Big bets · 8Fill-ins · 8Reconsider · 3
Effort →

Showing 22 of 22 ideas

This week 7

Quick wins with a clear first action.

  • 01

    On thirdlayer.inc, every buying action ends in an email client. "Get Started" and "Request Demo" both open mailto:[email protected], and the footer LinkedIn and X links point to "#". An operations or AI lead who reaches the bottom of a strong page (15 well-known logos, four use cases, a dedicated AI FDE, on-prem deployment) has no way to book a time, no form to fill in, and no social profile to check. The company already books Dex onboarding and private-cloud calls through cal.com on joindex.com, so the tool is in place. It just isn't used on the enterprise site.

    High impactLow effort First result in 2 weeks Founder & CEO

    First action

    Create the booking page with the three questions and swap the two button links.

    How to measure it

    Booked enterprise demos per month

    Now
    –
    Target
    2x the current monthly count of demo emails
    By
    60 days

    Steps

    1. 1

      Count the baseline

      Demo requests that reached hello@ in the last 90 days, and how many became calls.

      Founder & CEO 1 hour

    2. 2

      Build the booking page

      Use the cal.com setup already used for Dex onboarding, with three qualifying questions.

      Product Engineer half a day

    3. 3

      Swap the buttons

      Get Started and Request Demo go to the booking page; hello@ stays as a text link.

      Product Engineer 1 hour

    4. 4

      Fix the social links

      Point LinkedIn and X to the real profiles or remove the icons.

      Product Engineer 15 minutes

    5. 5

      Write the confirmation page

      The use case they picked, the AutoAgent post and what the first call covers.

      Founder & CEO 2 hours

    6. 6

      Tag sources

      UTM tags on links from the blog, the repository and Dex.

      Product Engineer 1 hour

    7. 7

      Review monthly

      Bookings by use case and source; adjust the questions.

      Founder & CEO monthly

    First result
    2 weeks
    Cost
    $0 to $15 a month for the booking tool, plus a day of work
    Owner
    Founder & CEO

    Smallest test

    Point only Request Demo to the booking page for two weeks and compare with the emails from Get Started.

    Why it works

    Point both buttons to a booking page with three short questions: team and size, which of the four use cases applies (customer operations, revenue operations, product and engineering, agent evaluation), and whether the deployment must stay inside their boundary. Send a confirmation page with the AutoAgent post and the matching use case to read before the call. Keep hello@ as a small text link for people who prefer email. Point the footer icons to the real LinkedIn and X profiles, or remove them. Tag every booking by source so the team can see which page, post or repository produced each conversation.

    Enterprise buyers expect to pick a time. A mailto link breaks in browsers with no mail client, gives no tracking, and makes the next step a blank email to write. Three answers before the call let the founder or FDE arrive with the right example, and the booking data shows which use case pulls the most interest.

    Ready to use

    ChecklistFront-door checklist

    [ ] Request Demo -> booking page (30 min)
    [ ] Get Started -> same page, or a short form
    [ ] Q1: team and size
    [ ] Q2: use case (customer ops / revenue ops / product & engineering / agent evaluation)
    [ ] Q3: must data stay inside your boundary? (yes / no / not sure)
    [ ] Confirmation page with the matching use case and the AutoAgent post
    [ ] hello@ kept as a text link
    [ ] LinkedIn and X icons go to real profiles
    [ ] UTM tags on blog, GitHub and Dex links

    Risks and how to handle them

    • Fewer, less casual enquiries

      Keep the email link visible for people who don't want to book.

    • Calls from teams that don't fit

      Use the size and deployment answers to send smaller teams to Dex Teams instead.

    Evidence

    • Your websiteHomepage (checked November 10, 2026): eyebrow "Your internal agent factory", H1 "Own the intelligence behind your operations"; both "Get Started" and "Request Demo" are mailto links to [email protected]; the footer LinkedIn and X links point to "#" placeholders; no pricing, testimonial, case study or customer quote anywhere on the page.Source
    • Your websiteHomepage: a logo strip headed "Deploying with teams at the frontier" with 15 logos (among them Vercel, Cursor, Stripe, Ramp, Figma, Notion, Shopify, GitHub and Databricks); four use cases (customer operations, revenue operations, product and engineering, and agent evaluation with "replayed environments, rubrics, and regression suites"); "A dedicated AI FDE rethinks the operation with your team and launches the first production system on Dex"; security claims: deploy inside your boundary, deterministic controls, trace every participant.Source
    • Dex siteDex site (footer "ThirdLayer, Inc."): "The self-driving workspace for operators"; sign-up through the Chrome extension, with onboarding and private-cloud calls booked through cal.com; testimonials from a PE partner, founders, a Head of BD, a VC and a Series B fintech COO; claims operators at large companies "and 10,000+ more".Source
  • 02

    The homepage's research section shows three posts. Two of them, "Let Agents Build the Company Ontology" and "Agents that improve with every trace", ask for a password. These are the posts about the context layer and learning from traces, which is exactly what the homepage sells. The only open post, AutoAgent, is the one that already brought in thousands of developers.

    Medium impactLow effort First result in 2 weeks Research Scientist

    First action

    Decide per post what can be public and what stays for the call.

    How to measure it

    Demo bookings attributed to research posts

    Now
    –
    Target
    5 a month
    By
    90 days

    Steps

    1. 1

      Review content

      Mark anything customer-specific or unreleased.

      Research Scientist 1 day

    2. 2

      Write open versions

      Method, a worked example and results.

      Research Scientist 3 days

    3. 3

      Add the next step

      Link to the matching use case and the booking page.

      Product Engineer 1 hour

    4. 4

      Publish

      Remove the password and add dates.

      Product Engineer 1 hour

    5. 5

      Share

      Post on X and LinkedIn and link from the AutoAgent README.

      Founder & CEO 1 day

    6. 6

      Measure

      Readers, time on page and bookings per post.

      Founder & CEO monthly

    First result
    2 weeks
    Cost
    Researcher time only
    Owner
    Research Scientist

    Smallest test

    Open one post and compare its readership with AutoAgent's first week.

    Why it works

    Publish both posts, or an open version of each with the method, one worked example and a results chart, keeping customer-specific detail out. Offer the full version through the booking page as a reason to talk. Link each post to the matching use case and the demo booking.

    Technical buyers judge an agent vendor by its method. Locked posts in the main research section look unfinished, while open ones earn links, shares and search traffic the way AutoAgent did.

    Risks and how to handle them

    • Giving away the method

      Publish the idea and results; keep the implementation and customer data private.

    Evidence

    • Your websiteResearch page: three posts; "AutoAgent: Autonomous Harness Engineering" (April 2, 2026) is open, while "Let Agents Build the Company Ontology" and "Agents that improve with every trace" are marked "Password required", although they are the posts about the context layer and learning from traces that the homepage sells.Source
    • GitHubAutoAgent repository: 4.6k stars, 493 forks, MIT licence, on a founder's personal account; the README logo links to thirdlayer.inc and says "We're hiring engineers. If this work interests you, reach out to [email protected]."; it does not mention Dex or Thirdlayer's evaluation product.Source
  • 03

    AutoAgent has 4.6k stars and 493 forks, and its README links to thirdlayer.inc only through the logo, plus a "We're hiring engineers" line. Its readers are engineers who run agents and care about harnesses and evals, the same people as the homepage's "agent evaluation" use case. The AutoAgent post ends with an email address rather than a link to the product, and the blog index doesn't link to the repository.

    High impactLow effort First result in 2 weeks Founder & CEO

    First action

    Add the evaluation block and a tagged link to the README.

    How to measure it

    Demo bookings with GitHub as source

    Now
    –
    Target
    4 a month
    By
    60 days

    Steps

    1. 1

      Write the block

      Two sentences and one link for teams running agents.

      Founder & CEO 1 hour

    2. 2

      Update the README

      Evaluation block and a careers link.

      Research Engineer 30 minutes

    3. 3

      Update the post

      Replace the closing email with the product link and booking.

      Product Engineer 30 minutes

    4. 4

      Link back

      Repository link on the blog and research pages.

      Product Engineer 30 minutes

    5. 5

      Consider an org

      Move or mirror the repository under a Thirdlayer GitHub organisation.

      Research Engineer 1 day

    6. 6

      Track

      Referrals from github.com and tagged bookings.

      Founder & CEO monthly

    First result
    2 weeks
    Cost
    $0
    Owner
    Founder & CEO

    Smallest test

    Add the tagged link to the README and count clicks for two weeks.

    Why it works

    Add a short section to the README: "Running agents in production? Thirdlayer builds company-specific evals and regression suites from your own traces", with a tagged link to a page for agent-evaluation buyers. Add the same block at the end of the AutoAgent post, and link the repository from the blog and research pages. Keep the hiring line, but link it to /careers.

    The repository is the company's largest audience and already self-selects for technical buyers. One tagged link turns that audience into measurable pipeline at no cost.

    Risks and how to handle them

    • Open-source users dislike sales copy

      Keep it to one factual section below the usage docs.

    Builds on

    Evidence

    • GitHubAutoAgent repository: 4.6k stars, 493 forks, MIT licence, on a founder's personal account; the README logo links to thirdlayer.inc and says "We're hiring engineers. If this work interests you, reach out to [email protected]."; it does not mention Dex or Thirdlayer's evaluation product.Source
    • Your websiteAutoAgent post (April 2, 2026): an open-source system in which a meta-agent improves an agent harness overnight; it reports 96.5% on SpreadsheetBench and 55.1% on TerminalBench, first on both leaderboards; lessons include that trajectories, not just scores, matter and that optimisers overfit; the post ends with an email address, not a link to Dex, the evaluation product or a demo.Source
    • Your websiteBlog index: 8 posts, the newest dated August 10, 2026; five are Dex release notes or productivity posts from February to April 2026 (such as "Meet TaskOS" and "The Zeigarnik Effect: Why Unfinished Work Hijacks your Mind"); the blog does not link to the AutoAgent repository.Source
  • 04

    A buyer who checks Thirdlayer meets four pitches. The homepage says "Your internal agent factory"; the Y Combinator profile says "the learning and alignment layer for enterprise AI"; joindex.com says "The self-driving workspace for operators"; the Chrome listing says "The AI copilot for your browser". The blog adds consumer productivity posts. Each may be true for its audience, but nothing explains how Dex and the enterprise offer fit together.

    Medium impactLow effort First result in 1 month Founder & CEO

    First action

    Write the three sentences and agree them among the founders.

    How to measure it

    Profiles using the agreed description

    Now
    –
    Target
    8 of 8
    By
    30 days

    Steps

    1. 1

      List surfaces

      Homepage, joindex.com, YC, Chrome, Product Hunt, LinkedIn, X, GitHub.

      Founder & CEO 1 hour

    2. 2

      Write the lines

      Company, Dex, enterprise and how they connect.

      Founder & CEO half a day

    3. 3

      Update profiles

      YC, Chrome, Product Hunt and social bios.

      Founder & CEO 1 day

    4. 4

      Cross-link

      "For teams" from joindex.com and "For individuals" from thirdlayer.inc.

      Product Engineer 2 hours

    5. 5

      Update meta tags

      Homepage title and description to the new line.

      Product Engineer 30 minutes

    6. 6

      Recheck quarterly

      Make sure all surfaces still match.

      Founder & CEO quarterly

    First result
    1 month
    Cost
    $0
    Owner
    Founder & CEO

    Smallest test

    Update the YC profile and Chrome listing this week.

    Why it works

    Write one sentence for the company and one for each product, plus a line that connects them (for example: Dex for individual operators; Thirdlayer builds the same system for whole teams with an FDE). Update the YC profile, Chrome listing, Product Hunt page, both site footers and the social bios to match. Add a short "Dex for teams" link from joindex.com to thirdlayer.inc and back.

    Investors, candidates and buyers compare these surfaces. A consistent story makes the company look bigger and clearer, and helps search engines and AI assistants describe it correctly.

    Risks and how to handle them

    • Confusing current Dex users

      Keep Dex's own pitch and only add the link to teams.

    Evidence

    • Y CombinatorY Combinator profile: Winter 2025 batch, San Francisco, describing the company as "the learning and alignment layer for enterprise AI".Source
    • Chrome Web StoreChrome Web Store listing for Dex (checked November 10, 2026): 2,000 users, 4.2 stars from 36 ratings, version 3.81 updated October 21, 2026, developer site joindex.com, described as "The AI copilot for your browser".Source
    • Dex siteDex site (footer "ThirdLayer, Inc."): "The self-driving workspace for operators"; sign-up through the Chrome extension, with onboarding and private-cloud calls booked through cal.com; testimonials from a PE partner, founders, a Head of BD, a VC and a Series B fintech COO; claims operators at large companies "and 10,000+ more".Source
    • Your websiteHomepage (checked November 10, 2026): eyebrow "Your internal agent factory", H1 "Own the intelligence behind your operations"; both "Get Started" and "Request Demo" are mailto links to [email protected]; the footer LinkedIn and X links point to "#" placeholders; no pricing, testimonial, case study or customer quote anywhere on the page.Source
  • 05

    thirdlayer.inc has no sitemap.xml and no robots.txt (both return 404), no favicon and no social share image. When the homepage or the AutoAgent post is shared in Slack, on X or LinkedIn, the preview has no image, and search engines have no list of pages to crawl. Speed is not the problem: real visitors pass Core Web Vitals.

    Medium impactLow effort First result in 2 weeks Product Engineer

    First action

    Add the favicon and homepage share image.

    How to measure it

    Pages indexed in Search Console

    Now
    –
    Target
    All sitemap URLs
    By
    30 days

    Steps

    1. 1

      Make images

      Favicon, a homepage card and one card per research post.

      Product Engineer half a day

    2. 2

      Add tags

      og:image, og:title, twitter:card on every page.

      Product Engineer 2 hours

    3. 3

      Generate the sitemap

      From the site's routes, including blog and careers.

      Product Engineer 2 hours

    4. 4

      Add robots.txt

      Allow crawling and point to the sitemap.

      Product Engineer 15 minutes

    5. 5

      Submit

      Search Console for both thirdlayer.inc and joindex.com.

      Founder & CEO 30 minutes

    6. 6

      Check previews

      Slack, X and LinkedIn previews.

      Product Engineer 30 minutes

    First result
    2 weeks
    Cost
    $0
    Owner
    Product Engineer

    Smallest test

    Add the homepage share image today and post the link.

    Why it works

    Generate a sitemap of the homepage, research, blog posts and careers pages, and add a robots.txt that points to it. Add a favicon and a 1200x630 share image for the homepage, plus one per research post, showing the headline result (for example AutoAgent's benchmark scores). Submit the sitemap in Search Console.

    Research posts travel by sharing. A card with an image and a clear title gets more clicks than a bare link, and a sitemap helps new posts get indexed quickly.

    Risks and how to handle them

    • Locked pages appear in the sitemap

      Leave out password-protected posts until they are opened.

    Evidence

    • Your websiteSite basics (checked November 10, 2026): the homepage has no social share image and no favicon; /sitemap.xml and /robots.txt both return 404; the domain was registered in May 2025.Source
    • PageSpeedReal visitors (Chrome UX Report, 75th percentile): LCP 766 ms, INP 82 ms, CLS 0, so the homepage passes Core Web Vitals; LCP is 77% slower than in the previous period.Source
  • 06

    joindex.com says operators at large companies use Dex "and 10,000+ more". The Chrome Web Store, where most new users arrive, shows 2,000 users and 4.2 stars from only 36 ratings. The extension was updated on October 21, 2026, so the product is active, but a careful buyer who checks both numbers sees a gap, and 36 ratings is a thin base for a product with paid plans up to $199 a month.

    Medium impactLow effort First result in 1 month Product Engineer

    First action

    Decide exactly what the 10,000+ figure counts and edit the line to say so.

    How to measure it

    Chrome Web Store ratings

    Now
    –
    Target
    100+ ratings at 4.5 or higher
    By
    90 days

    Steps

    1. 1

      Define the number

      What 10,000+ counts and from which data.

      Founder & CEO 1 hour

    2. 2

      Edit the claim

      Wording on joindex.com to match.

      Product Engineer 30 minutes

    3. 3

      Pick the moment

      After a user's third successful automation.

      Product Engineer 1 day

    4. 4

      Build the prompt

      One-click link to the store reviews; feedback form for unhappy users.

      Product Engineer 2 days

    5. 5

      Refresh the listing

      Screenshots and a description that match the current product.

      Product Engineer 1 day

    6. 6

      Watch weekly

      Ratings, average and users.

      Founder & CEO weekly

    First result
    1 month
    Cost
    $0
    Owner
    Product Engineer

    Smallest test

    Email the 50 most active users a direct review link.

    Why it works

    State what the 10,000+ counts (for example operators across the extension, iMessage and Slack, or sign-ups to date) and match the wording on the site. Then add an in-product review prompt for users who have completed several automations, and link to the Chrome listing from the Dex onboarding email. Refresh the store screenshots to show automations and agents.

    Store ratings and user counts are the first trust check for a browser extension that reads web activity. Clear numbers prevent doubt, and a review prompt timed after a success raises both the count and the average.

    Risks and how to handle them

    • Prompting annoys users

      Ask once, only after a success, and never again after a dismissal.

    Evidence

    • Chrome Web StoreChrome Web Store listing for Dex (checked November 10, 2026): 2,000 users, 4.2 stars from 36 ratings, version 3.81 updated October 21, 2026, developer site joindex.com, described as "The AI copilot for your browser".Source
    • Dex siteDex site (footer "ThirdLayer, Inc."): "The self-driving workspace for operators"; sign-up through the Chrome extension, with onboarding and private-cloud calls booked through cal.com; testimonials from a PE partner, founders, a Head of BD, a VC and a Series B fintech COO; claims operators at large companies "and 10,000+ more".Source
    • Dex siteDex pricing: Core $49/month (3 integrations), Max $99/month ("Most popular", 5 integrations), Ultra $199/month (15 integrations, dedicated account manager), Full Service (custom, "Built and managed like a team of EAs") and Teams & Enterprise ("Flat rate pricing (no seat gates)", shared context, private cloud, "Book a call"); no free tier or trial is mentioned.Source
  • 07

    Thirdlayer is hiring for seven roles in San Francisco, and its customer delivery depends on one of them, the Forward Deployed Engineer. The careers page lists the roles with one line of company text: "We keep an eye out for exceptional people regardless of what is posted." The strongest recruiting material (AutoAgent's results and 4.6k stars, the team's backgrounds, the thesis that "AI models are generic, but people's work and processes are specific") is spread across other pages.

    Medium impactLow effort First result in 1 month Founder & CEO

    First action

    Write the five-sentence intro and add it above the job list.

    How to measure it

    Applications that reach a first interview

    Now
    –
    Target
    +50%
    By
    60 days

    Steps

    1. 1

      Write the intro

      Thesis, shipped work and team backgrounds.

      Founder & CEO 2 hours

    2. 2

      Add proof

      AutoAgent results and Dex in two lines.

      Founder & CEO 1 hour

    3. 3

      Explain the FDE role

      A day in a customer deployment.

      Forward Deployed Engineer 2 hours

    4. 4

      Publish

      Above the role list.

      Product Engineer 1 hour

    5. 5

      Relink

      README hiring line and YC jobs to /careers.

      Research Engineer 30 minutes

    6. 6

      Track

      Applications by source and stage.

      Founder & CEO monthly

    First result
    1 month
    Cost
    $0
    Owner
    Founder & CEO

    Smallest test

    Add the intro and compare applications in the next month.

    Why it works

    Add a short top section: the thesis, what the team has shipped (AutoAgent and its benchmarks, Dex), where the team comes from (already on the homepage), how an FDE engagement works, and the YC backing. Link the AutoAgent README's hiring line here instead of to an email address.

    Hiring FDEs and researchers is the company's capacity limit. Strong candidates choose on the problem and the team, and the evidence already exists.

    Risks and how to handle them

    • Overselling stage or size

      Stick to shipped facts and public results.

    Evidence

    • HiringCareers page: seven openings, all in San Francisco: Platform Engineer, Forward Deployed Engineer, Product Engineer, Software Engineer (Intern), Research Scientist, Research Engineer and a General Application; the only company text is "We keep an eye out for exceptional people regardless of what is posted."Source
    • HiringForward Deployed Engineer: deploys the platform "into live customer environments", builds ETL pipelines and connectors for company-specific data, owns work from scoping through production and turns customer patterns into product features; the post's thesis: "AI models are generic, but people's work and processes are specific."Source
    • GitHubAutoAgent repository: 4.6k stars, 493 forks, MIT licence, on a founder's personal account; the README logo links to thirdlayer.inc and says "We're hiring engineers. If this work interests you, reach out to [email protected]."; it does not mention Dex or Thirdlayer's evaluation product.Source

This quarter 11

The core plays for the next three months.

  • 08

    The homepage shows 15 well-known logos under "Deploying with teams at the frontier" but no testimonial, case study or number. Rivals sell with outcomes: Glean shows Zillow's "1.5+ hours saved weekly per user" and TIME's "3 weeks to go-live", Dust shows case studies with hours reclaimed and adoption rates. Thirdlayer's own eval dashboard already measures pass rates and regression tests, so the numbers exist inside each deployment.

    High impactMedium effort First result in 6 weeks Forward Deployed Engineer

    First action

    Ask the two happiest deployment teams for permission to publish their results.

    How to measure it

    Use cases with a published outcome

    Now
    –
    Target
    4 of 4
    By
    90 days

    Steps

    1. 1

      Pick candidates

      One deployment per use case with a clear result.

      Forward Deployed Engineer 1 day

    2. 2

      Ask permission

      Named or anonymised, with approval rights.

      Founder & CEO 1 week

    3. 3

      Pull the numbers

      Pass rates, regressions caught, time saved, from the eval data.

      Forward Deployed Engineer 2 days

    4. 4

      Write

      Before, system, evals, outcome, in 300 words.

      Founder & CEO 1 week

    5. 5

      Approve

      Customer sign-off on every number.

      Founder & CEO 2 weeks

    6. 6

      Publish

      Under each use case and in sales follow-ups.

      Product Engineer 1 day

    First result
    6 weeks
    Cost
    Staff time only
    Owner
    Forward Deployed Engineer

    Smallest test

    Publish one anonymised story on the agent-evaluation use case.

    Why it works

    For each use case (customer operations, revenue operations, product and engineering, agent evaluation), write one short story with an approved customer: the operation before, the system built on Dex, the eval results and the outcome (tickets resolved without escalation, hours saved, regressions caught). Where a customer can't be named, publish it anonymised by industry and size. Place each story under its use case on the homepage.

    A logo shows that someone tried the product; a number shows that it worked. Buyers comparing Thirdlayer with Glean or Dust need a result they can repeat to their boss.

    Risks and how to handle them

    • Customers decline to be named

      Offer anonymised stories with industry and size.

    Evidence

    • Your websiteHomepage: a logo strip headed "Deploying with teams at the frontier" with 15 logos (among them Vercel, Cursor, Stripe, Ramp, Figma, Notion, Shopify, GitHub and Databricks); four use cases (customer operations, revenue operations, product and engineering, and agent evaluation with "replayed environments, rubrics, and regression suites"); "A dedicated AI FDE rethinks the operation with your team and launches the first production system on Dex"; security claims: deploy inside your boundary, deterministic controls, trace every participant.Source
    • Competitor researchRivals' own homepages: Glean leads with named outcomes (Zillow "1.5+ hours saved weekly per user" and "3.4k+ agents"; TIME "3 weeks to go-live") and a "Get a demo" page; Dust shows "3,000+ global organizations", "300,000+ agents deployed", a free trial and case studies with numbers; Distyl calls itself "an AI-native operations company" with "50+" enterprise deployments.Source
    • Your websiteHomepage (checked November 10, 2026): eyebrow "Your internal agent factory", H1 "Own the intelligence behind your operations"; both "Get Started" and "Request Demo" are mailto links to [email protected]; the footer LinkedIn and X links point to "#" placeholders; no pricing, testimonial, case study or customer quote anywhere on the page.Source
  • 09

    "Agent evaluation" is one of the four homepage use cases: replayed environments, rubrics and regression suites for agents already in production. AutoAgent showed the method publicly, reporting first place on two benchmarks and finding that trajectories matter more than scores and that optimisers overfit. Teams with a production agent have a budget, a measurable problem and a much shorter path to yes than a full operations rebuild.

    High impactMedium effort First result in 6 weeks Research Engineer

    First action

    Write a one-page pilot scope with deliverables, timeline and price.

    How to measure it

    Eval pilots signed

    Now
    –
    Target
    4
    By
    1 quarter

    Steps

    1. 1

      Define scope

      Inputs, deliverables, four-week timeline and price.

      Research Engineer 2 days

    2. 2

      Build the report template

      Pass rates, failure clusters, regressions and recommended fixes.

      Research Engineer 1 week

    3. 3

      Write the page

      Agent-evaluation landing page with the pilot offer.

      Founder & CEO 2 days

    4. 4

      Promote

      AutoAgent README, research posts and founder posts.

      Founder & CEO ongoing

    5. 5

      Run the first pilot

      One design partner at a reduced price.

      Forward Deployed Engineer 4 weeks

    6. 6

      Convert

      Proposal to keep the suite running on Dex.

      Founder & CEO 1 week

    First result
    6 weeks
    Cost
    Staff time; priced to cover delivery
    Owner
    Research Engineer

    Smallest test

    Offer the pilot to five teams that starred or forked AutoAgent and work at companies with production agents.

    Why it works

    Package a four-week pilot with a fixed price: Thirdlayer replays the customer's traces, builds a company-specific eval suite, runs a harness optimisation pass and delivers a report on pass rates, failure clusters and regressions. The pilot ends with a proposal to keep the suite running on Dex. Market it to AutoAgent's GitHub audience and on the agent-evaluation use-case page.

    A small, measurable first deal is easier to sign than an open-ended transformation. It also creates the eval data and trust that lead to the larger FDE engagement.

    Risks and how to handle them

    • Pilots stay pilots

      Agree the conversion criteria and price before the pilot starts.

    Builds on

    Evidence

    • Your websiteAutoAgent post (April 2, 2026): an open-source system in which a meta-agent improves an agent harness overnight; it reports 96.5% on SpreadsheetBench and 55.1% on TerminalBench, first on both leaderboards; lessons include that trajectories, not just scores, matter and that optimisers overfit; the post ends with an email address, not a link to Dex, the evaluation product or a demo.Source
    • Your websiteHomepage: a logo strip headed "Deploying with teams at the frontier" with 15 logos (among them Vercel, Cursor, Stripe, Ramp, Figma, Notion, Shopify, GitHub and Databricks); four use cases (customer operations, revenue operations, product and engineering, and agent evaluation with "replayed environments, rubrics, and regression suites"); "A dedicated AI FDE rethinks the operation with your team and launches the first production system on Dex"; security claims: deploy inside your boundary, deterministic controls, trace every participant.Source
    • HiringPlatform Engineer: owns the context capture and learning pipeline with customers, and builds "evaluation and reliability tooling" that decides when agents act on their own and when they check in.Source
  • 10

    Dex sells to individuals at $49 to $199 a month and has a Teams & Enterprise plan with "Flat rate pricing (no seat gates)", shared context and private cloud. Its testimonials come from operators at funds and startups. When three or more people at one company pay for Dex separately, that company has already shown demand for shared context, but nothing on either site connects the two offers.

    High impactMedium effort First result in 1 month Founder & CEO

    First action

    Run the domain grouping on current paying accounts.

    How to measure it

    Team plans signed from Dex domains

    Now
    –
    Target
    5
    By
    2 quarters

    Steps

    1. 1

      Group accounts

      Paying users by work email domain.

      Platform Engineer 1 day

    2. 2

      Set triggers

      Three paying users or one Ultra user per domain.

      Founder & CEO 1 hour

    3. 3

      Write the offer

      Flat price replacing individual plans, plus a first system.

      Founder & CEO 1 day

    4. 4

      Add the in-app prompt

      "Using Dex with your team?" for matched domains.

      Product Engineer 3 days

    5. 5

      Reach out

      To the most active user at each domain.

      Founder & CEO weekly

    6. 6

      Hand over

      Signed teams go to an FDE for the first system.

      Forward Deployed Engineer ongoing

    First result
    1 month
    Cost
    Staff time only
    Owner
    Founder & CEO

    Smallest test

    List the top 10 domains by paying users and contact the top three.

    Why it works

    Group Dex accounts by work email domain each week. When a domain reaches three paying users, or one Ultra user, reach out with a team proposal: shared context across their tools, one flat price that replaces the individual subscriptions, and an FDE-built first system. Add a "Using Dex with your team?" prompt inside the product that leads to the same offer.

    Bottom-up usage is the cheapest enterprise pipeline: the buyer already trusts the product, and the team plan solves a problem individual plans can't (shared context).

    Risks and how to handle them

    • Users feel watched

      Use only paying-account domains and reach out as an offer, not a notice.

    Builds on

    Evidence

    • Dex siteDex pricing: Core $49/month (3 integrations), Max $99/month ("Most popular", 5 integrations), Ultra $199/month (15 integrations, dedicated account manager), Full Service (custom, "Built and managed like a team of EAs") and Teams & Enterprise ("Flat rate pricing (no seat gates)", shared context, private cloud, "Book a call"); no free tier or trial is mentioned.Source
    • Dex siteDex site (footer "ThirdLayer, Inc."): "The self-driving workspace for operators"; sign-up through the Chrome extension, with onboarding and private-cloud calls booked through cal.com; testimonials from a PE partner, founders, a Head of BD, a VC and a Series B fintech COO; claims operators at large companies "and 10,000+ more".Source
    • HiringProduct Engineer: ships features across "the browser extension, web surfaces, and platform", defines how users interact with agents, and builds integrations and data pipelines.Source
  • 11

    The homepage promises "A dedicated AI FDE" who "launches the first production system on Dex", but gives no timeline, deliverables or price. Dex publishes prices up to $199 a month and a custom Full Service tier, while the enterprise offer has none. Buyers have to ask before they know whether Thirdlayer is in their budget.

    Medium impactLow effort First result in 1 month Founder & CEO

    First action

    Write the five-step engagement timeline from the last two deployments.

    How to measure it

    Call-to-proposal rate

    Now
    –
    Target
    +25%
    By
    90 days

    Steps

    1. 1

      Map past deployments

      Real timelines and deliverables.

      Forward Deployed Engineer 1 day

    2. 2

      Set a price anchor

      "From" price or range for the first system.

      Founder & CEO 1 day

    3. 3

      Write the page

      Timeline, deliverables, customer inputs, price.

      Founder & CEO 2 days

    4. 4

      Add an FAQ

      Data access, security, ownership of evals and data.

      Platform Engineer 1 day

    5. 5

      Publish

      Linked from the FDE section and the booking page.

      Product Engineer 1 day

    6. 6

      Measure

      Proposal rate before and after.

      Founder & CEO monthly

    First result
    1 month
    Cost
    $0
    Owner
    Founder & CEO

    Smallest test

    Add the five-step timeline to the homepage FDE section without a price.

    Why it works

    Add an "Engagement" section or page: week 1 map the operation, weeks 2 to 4 build and evaluate, week 5 deploy with approvals, then ongoing improvement. List what the customer receives (agents, workflows, eval suite, dashboard), what the customer provides (data access, a process owner), and a "from" price or price range.

    A visible process and a price anchor qualify buyers before the call and shorten the sales cycle. Buyers who book have already accepted the shape of the deal.

    Risks and how to handle them

    • Price scares off some buyers

      Show a range and what changes the price.

    Builds on

    Evidence

    • Your websiteHomepage: a logo strip headed "Deploying with teams at the frontier" with 15 logos (among them Vercel, Cursor, Stripe, Ramp, Figma, Notion, Shopify, GitHub and Databricks); four use cases (customer operations, revenue operations, product and engineering, and agent evaluation with "replayed environments, rubrics, and regression suites"); "A dedicated AI FDE rethinks the operation with your team and launches the first production system on Dex"; security claims: deploy inside your boundary, deterministic controls, trace every participant.Source
    • Dex siteDex pricing: Core $49/month (3 integrations), Max $99/month ("Most popular", 5 integrations), Ultra $199/month (15 integrations, dedicated account manager), Full Service (custom, "Built and managed like a team of EAs") and Teams & Enterprise ("Flat rate pricing (no seat gates)", shared context, private cloud, "Book a call"); no free tier or trial is mentioned.Source
    • HiringForward Deployed Engineer: deploys the platform "into live customer environments", builds ETL pipelines and connectors for company-specific data, owns work from scoping through production and turns customer patterns into product features; the post's thesis: "AI models are generic, but people's work and processes are specific."Source
  • 12

    The homepage makes three strong security promises: deploy inside your boundary (on-premises or zero data access), deterministic permission and approval controls, and tracing of every action. The product reads email, Slack, CRM and browser activity. But there is no trust or security page, no architecture diagram and no questionnaire pack, so every deal waits on the customer's security review.

    High impactMedium effort First result in 1 quarter Platform Engineer

    First action

    Collect the questions from the last three security reviews.

    How to measure it

    Median days in security review

    Now
    –
    Target
    -30%
    By
    2 quarters

    Steps

    1. 1

      Collect questions

      From past security reviews.

      Platform Engineer 1 day

    2. 2

      Draw diagrams

      One per deployment mode.

      Platform Engineer 3 days

    3. 3

      Write the page

      Data flow, access, retention, sub-processors.

      Platform Engineer 1 week

    4. 4

      Prepare the pack

      Pre-filled standard questionnaire.

      Platform Engineer 1 week

    5. 5

      Legal review

      Check every claim against contracts.

      Founder & CEO 1 week

    6. 6

      Publish and link

      From the security section and the booking page.

      Product Engineer 1 day

    First result
    1 quarter
    Cost
    Staff time; audit costs only if pursued
    Owner
    Platform Engineer

    Smallest test

    Send the pre-filled questionnaire to the next prospect before they ask.

    Why it works

    Publish a security page with a deployment diagram for each mode (cloud, private cloud, on-prem), the data flow from each connector, how approvals and role-based access work, retention and deletion, sub-processors, and the status of any audit or certification. Offer a pre-filled security questionnaire on request through the booking page.

    Security review is often the longest step for an agent that touches company data. Answering the common questions up front shortens deals and lets the buyer's champion argue internally.

    Risks and how to handle them

    • Claims that outrun the product

      Publish only what is in place today, with dates.

    Evidence

    • Your websiteHomepage: a logo strip headed "Deploying with teams at the frontier" with 15 logos (among them Vercel, Cursor, Stripe, Ramp, Figma, Notion, Shopify, GitHub and Databricks); four use cases (customer operations, revenue operations, product and engineering, and agent evaluation with "replayed environments, rubrics, and regression suites"); "A dedicated AI FDE rethinks the operation with your team and launches the first production system on Dex"; security claims: deploy inside your boundary, deterministic controls, trace every participant.Source
    • HiringPlatform Engineer: owns the context capture and learning pipeline with customers, and builds "evaluation and reliability tooling" that decides when agents act on their own and when they check in.Source
    • Your websiteHomepage (checked November 10, 2026): eyebrow "Your internal agent factory", H1 "Own the intelligence behind your operations"; both "Get Started" and "Request Demo" are mailto links to [email protected]; the footer LinkedIn and X links point to "#" placeholders; no pricing, testimonial, case study or customer quote anywhere on the page.Source
  • 13

    The Forward Deployed Engineer role is to deploy into "live customer environments", build ETL and connectors, and turn customer patterns into product features. Dex already has a library of 32 use cases tagged by role. If each FDE deployment ends as a one-off, delivery capacity grows only with headcount.

    High impactMedium effort First result in 1 quarter Forward Deployed Engineer

    First action

    Write the starter template from the most recent deployment.

    How to measure it

    Median days to first production system

    Now
    –
    Target
    -30%
    By
    2 quarters

    Steps

    1. 1

      Define the template

      Connectors, workflow map, eval rubric, checklist.

      Forward Deployed Engineer 2 days

    2. 2

      Back-fill

      From the last three deployments.

      Forward Deployed Engineer 2 weeks

    3. 3

      Strip data

      Remove anything customer-specific.

      Platform Engineer 2 days

    4. 4

      Make it loadable

      One command to start a new workspace from a starter.

      Product Engineer 2 weeks

    5. 5

      Make it a rule

      Every deployment ends with a starter.

      Founder & CEO ongoing

    6. 6

      Measure

      Days to first system, with and without a starter.

      Forward Deployed Engineer quarterly

    First result
    1 quarter
    Cost
    Engineering time
    Owner
    Forward Deployed Engineer

    Smallest test

    Start the next customer-operations deployment from a starter and time it.

    Why it works

    After every deployment, the FDE saves a starter system: the connector set, the workflow map, a starter eval rubric and a first-week checklist, with customer data removed. Group starters by the four homepage use cases. New customers in the same use case begin from the starter, and the best ones appear (described generically) on the use-case pages.

    Reuse shortens time to first production system, which is the number buyers care about and the one that limits how many customers a small team can serve.

    Risks and how to handle them

    • Starters leak customer detail

      Review by a second engineer before saving.

    Evidence

    • HiringForward Deployed Engineer: deploys the platform "into live customer environments", builds ETL pipelines and connectors for company-specific data, owns work from scoping through production and turns customer patterns into product features; the post's thesis: "AI models are generic, but people's work and processes are specific."Source
    • Dex siteDex use case library: 32 use cases in eight categories (CRM, Operations, Inbox, Recruiting, GTM & Sales, Support, Research, Knowledge), each tagged with a role such as Account Executive, Support Lead or Chief of Staff; no customer stories or numbers.Source
  • 14

    thirdlayer.inc is a single page with four use cases in short paragraphs, and it has no sitemap. Dex has a 32-item use-case library on joindex.com, but it is aimed at individuals. A head of support or revenue operations searching for agents for their function finds no Thirdlayer page that speaks to them.

    Medium impactMedium effort First result in 2 months Founder & CEO

    First action

    Write the agent-evaluation page first, since it ties to AutoAgent.

    How to measure it

    Bookings from use-case pages

    Now
    –
    Target
    6 a month
    By
    2 quarters

    Steps

    1. 1

      Outline

      Shared structure for all four pages.

      Founder & CEO 1 day

    2. 2

      Write the first

      Agent evaluation.

      Research Engineer 3 days

    3. 3

      Write the rest

      Customer ops, revenue ops, product and engineering.

      Forward Deployed Engineer 2 weeks

    4. 4

      Add examples

      One sample approval flow per page.

      Product Engineer 1 week

    5. 5

      Publish

      Add to the sitemap and the homepage use-case cards.

      Product Engineer 1 day

    6. 6

      Measure

      Visits and bookings per page.

      Founder & CEO monthly

    First result
    2 months
    Cost
    Staff time only
    Owner
    Founder & CEO

    Smallest test

    Publish the agent-evaluation page and link it from the README.

    Why it works

    Build four pages (customer operations, revenue operations, product and engineering, agent evaluation). Each covers the problem, the system Thirdlayer builds, the connectors involved, the eval approach, a sample approval flow like the homepage CRM example, the outcome story when available, and the booking link pre-set to that use case.

    Function-specific pages match how buyers search and how they pass links internally, and they give each outcome story a home.

    Risks and how to handle them

    • Thin pages without proof

      Launch with the sample flows and add stories as they are approved.

    Builds on

    Evidence

    • Your websiteHomepage: a logo strip headed "Deploying with teams at the frontier" with 15 logos (among them Vercel, Cursor, Stripe, Ramp, Figma, Notion, Shopify, GitHub and Databricks); four use cases (customer operations, revenue operations, product and engineering, and agent evaluation with "replayed environments, rubrics, and regression suites"); "A dedicated AI FDE rethinks the operation with your team and launches the first production system on Dex"; security claims: deploy inside your boundary, deterministic controls, trace every participant.Source
    • Dex siteDex use case library: 32 use cases in eight categories (CRM, Operations, Inbox, Recruiting, GTM & Sales, Support, Research, Knowledge), each tagged with a role such as Account Executive, Support Lead or Chief of Staff; no customer stories or numbers.Source
    • Your websiteSite basics (checked November 10, 2026): the homepage has no social share image and no favicon; /sitemap.xml and /robots.txt both return 404; the domain was registered in May 2025.Source
  • 15

    AutoAgent's post shared lessons that agent teams struggle with: separating the meta-agent from the task agent, optimisers overfitting, and trajectories mattering more than scores. The repository has 493 forks, so hundreds of engineers have tried the method. Thirdlayer's own research roles treat "evals as a research problem in their own right".

    Medium impactLow effort First result in 1 month Research Engineer

    First action

    Announce the first session in the README and on X.

    How to measure it

    Qualified attendees per session

    Now
    –
    Target
    25
    By
    1 quarter

    Steps

    1. 1

      Pick the topic

      One lesson from the AutoAgent work.

      Research Engineer 1 day

    2. 2

      Set up registration

      Name, company and whether they run agents in production.

      Product Engineer 2 hours

    3. 3

      Promote

      README, X, LinkedIn and the blog.

      Founder & CEO 1 week

    4. 4

      Run it

      Talk plus two live reviews.

      Research Engineer 45 minutes

    5. 5

      Publish the recording

      With clips for social.

      Product Engineer 1 day

    6. 6

      Follow up

      Offer the eval pilot to qualified attendees.

      Founder & CEO 1 week

    First result
    1 month
    Cost
    $0
    Owner
    Research Engineer

    Smallest test

    Run one session and count qualified attendees.

    Why it works

    Run a monthly 45-minute live session: a short talk on one lesson (for example, catching overfitting in harness optimisation), then live review of two attendee harnesses or eval suites, volunteered in advance. Record it, post clips, and follow up with attendees from companies that run production agents.

    Practical help builds trust with the exact engineers who later champion an eval or agent platform, at almost no cost.

    Risks and how to handle them

    • Draws hobbyists, not buyers

      Prioritise live reviews for production teams.

    Builds on

    Evidence

    • Your websiteAutoAgent post (April 2, 2026): an open-source system in which a meta-agent improves an agent harness overnight; it reports 96.5% on SpreadsheetBench and 55.1% on TerminalBench, first on both leaderboards; lessons include that trajectories, not just scores, matter and that optimisers overfit; the post ends with an email address, not a link to Dex, the evaluation product or a demo.Source
    • GitHubAutoAgent repository: 4.6k stars, 493 forks, MIT licence, on a founder's personal account; the README logo links to thirdlayer.inc and says "We're hiring engineers. If this work interests you, reach out to [email protected]."; it does not mention Dex or Thirdlayer's evaluation product.Source
    • HiringResearch Scientist: post-trains models on tasks and environments built from production data, treats "evals as a research problem in their own right" and builds pipelines that "turn messy production traces into training signal".Source
  • 16

    Buyers of enterprise agents compare a few clear options. Glean sells enterprise context and agents with named outcomes; Dust sells multiplayer agents with a free trial and "3,000+ global organizations"; Distyl is "an AI-native operations company" for the Fortune 500; many teams build their own. Thirdlayer's mix (FDE-led building, company-specific evals, deployment inside the customer's boundary) is distinct, but no page explains where it fits.

    Medium impactMedium effort First result in 2 months Founder & CEO

    First action

    Write the in-house vs Thirdlayer page from questions asked on recent calls.

    How to measure it

    Comparison-page bookings

    Now
    –
    Target
    4 a month
    By
    2 quarters

    Steps

    1. 1

      List objections

      From recent sales calls.

      Founder & CEO 1 day

    2. 2

      Write in-house page

      Build vs buy, with an honest cost view.

      Founder & CEO 3 days

    3. 3

      Check rivals

      Current claims from their own pages.

      Founder & CEO 2 days

    4. 4

      Write comparisons

      Glean, Dust, Distyl.

      Founder & CEO 1 week

    5. 5

      Legal check

      Trademark and claim review.

      Founder & CEO 3 days

    6. 6

      Refresh

      Every quarter.

      Founder & CEO quarterly

    First result
    2 months
    Cost
    Staff time only
    Owner
    Founder & CEO

    Smallest test

    Publish only the in-house comparison.

    Why it works

    Write a guide to building in-house versus with Thirdlayer, then three fair comparison pages: who each option suits, how agents get built, how they are evaluated and improved, deployment options and the kind of help provided. Date each page and cite rivals' own pages.

    Comparison searches are late-stage and high-intent, and the pages help the internal champion explain the choice.

    Risks and how to handle them

    • Outdated claims about rivals

      Date each page and cite sources.

    Builds on

    Evidence

    • Competitor researchRivals' own homepages: Glean leads with named outcomes (Zillow "1.5+ hours saved weekly per user" and "3.4k+ agents"; TIME "3 weeks to go-live") and a "Get a demo" page; Dust shows "3,000+ global organizations", "300,000+ agents deployed", a free trial and case studies with numbers; Distyl calls itself "an AI-native operations company" with "50+" enterprise deployments.Source
    • Your websiteHomepage: a logo strip headed "Deploying with teams at the frontier" with 15 logos (among them Vercel, Cursor, Stripe, Ramp, Figma, Notion, Shopify, GitHub and Databricks); four use cases (customer operations, revenue operations, product and engineering, and agent evaluation with "replayed environments, rubrics, and regression suites"); "A dedicated AI FDE rethinks the operation with your team and launches the first production system on Dex"; security claims: deploy inside your boundary, deterministic controls, trace every participant.Source
  • 17

    Dex's testimonials come from a PE partner, a VC, founders and a Series B COO. These are people who advise many companies on operations. The Product Hunt launch (234 upvotes, fifth of the day) shows early community support. There is no referral or introduction offer on either site.

    Medium impactLow effort First result in 1 month Founder & CEO

    First action

    Write the forwardable blurb and send it to the five most active investor users.

    How to measure it

    Warm introductions per month

    Now
    –
    Target
    8
    By
    90 days

    Steps

    1. 1

      Pick the users

      Investors and founders with active Dex accounts.

      Founder & CEO 1 day

    2. 2

      Write the blurb

      Problem, what Thirdlayer builds, booking link.

      Founder & CEO 2 hours

    3. 3

      Set the reward

      Free Dex months or a referral fee.

      Founder & CEO 1 hour

    4. 4

      Ask personally

      A short note from the founder.

      Founder & CEO 1 week

    5. 5

      Track

      Tagged booking links per referrer.

      Product Engineer 1 day

    6. 6

      Thank and report

      Tell referrers what happened.

      Founder & CEO monthly

    First result
    1 month
    Cost
    Rewards only on signed deals
    Owner
    Founder & CEO

    Smallest test

    Ask three testimonial authors for one introduction each.

    Why it works

    Offer Dex users who invest in or advise companies a simple introduction programme: a one-paragraph blurb and a booking link they can forward, with a reward such as free months of Dex or a fee per signed team. Start with the users quoted in testimonials.

    Investors and operators make warm introductions all the time. A ready-made blurb makes it easy, and a warm intro converts far better than outbound.

    Risks and how to handle them

    • Referrers feel used

      Ask only users who already praised Dex, and keep it optional.

    Builds on

    Evidence

    • Dex siteDex site (footer "ThirdLayer, Inc."): "The self-driving workspace for operators"; sign-up through the Chrome extension, with onboarding and private-cloud calls booked through cal.com; testimonials from a PE partner, founders, a Head of BD, a VC and a Series B fintech COO; claims operators at large companies "and 10,000+ more".Source
    • Product HuntDex launched on Product Hunt on December 11, 2025 as "Turn tabs into automated workflows and tasks": 234 upvotes, fifth product of the day.Source
  • 18

    The homepage's sample dashboard tracks regression tests ("842", "+18 this week"), pass rate ("94%", "+3 pts"), new failures and approvals, and traces failures to context, skills, workflows, harness or model. That is the proof of improvement buyers pay for, but it lives in a dashboard the executive sponsor may never open.

    High impactLow effort First result in 1 month Forward Deployed Engineer

    First action

    Draft the report from one customer's current dashboard.

    How to measure it

    Customers expanding to a second system

    Now
    –
    Target
    40%
    By
    2 quarters

    Steps

    1. 1

      Pick the numbers

      Pass rate, regressions, fixes, approvals, time saved.

      Forward Deployed Engineer 1 day

    2. 2

      Draft

      One customer, sent by hand.

      Forward Deployed Engineer 2 hours

    3. 3

      Get feedback

      Ask the sponsor what they'd add.

      Founder & CEO 1 week

    4. 4

      Automate

      Generate it from the eval data.

      Platform Engineer 1 week

    5. 5

      Roll out

      All customers.

      Forward Deployed Engineer 1 week

    6. 6

      Use in reviews

      Quarterly business reviews and renewals.

      Founder & CEO quarterly

    First result
    1 month
    Cost
    Engineering time
    Owner
    Forward Deployed Engineer

    Smallest test

    Send one hand-made report to one sponsor this week.

    Why it works

    Send an automatic weekly email to each customer's sponsor: pass rate and change, new regression tests, failures fixed and where they came from, approvals handled, and estimated time saved. Add one line from the FDE on what changes next week. Use the same numbers in quarterly reviews and renewals.

    Sponsors renew what they can see improving. A weekly number keeps the value visible between meetings and sets up expansion to the next operation.

    Risks and how to handle them

    • Bad weeks look bad

      Show trend lines and what was learned from new failures.

    Evidence

    • Your websiteHomepage: a logo strip headed "Deploying with teams at the frontier" with 15 logos (among them Vercel, Cursor, Stripe, Ramp, Figma, Notion, Shopify, GitHub and Databricks); four use cases (customer operations, revenue operations, product and engineering, and agent evaluation with "replayed environments, rubrics, and regression suites"); "A dedicated AI FDE rethinks the operation with your team and launches the first production system on Dex"; security claims: deploy inside your boundary, deterministic controls, trace every participant.Source
    • HiringPlatform Engineer: owns the context capture and learning pipeline with customers, and builds "evaluation and reliability tooling" that decides when agents act on their own and when they check in.Source

Big bets 3

Larger plays that can change the trajectory.

  • 19

    AutoAgent shows that open releases spread for Thirdlayer: 4.6k stars and 493 forks for an overnight harness optimiser. The company's real product is the next step: company-specific evals rebuilt from policies, human decisions and outcomes, which its research roles treat as "a research problem in their own right". Most teams have no way to start building such evals.

    High impactHigh effort First result in 2 quarters Research Scientist

    First action

    Choose which parts of the internal eval tooling can be released.

    How to measure it

    Teams using the kit that book a call

    Now
    –
    Target
    30
    By
    2 quarters after release

    Steps

    1. 1

      Scope

      What is released and what stays in the product.

      Research Scientist 1 week

    2. 2

      Build the schema

      Traces and decisions to test cases.

      Research Engineer 1 month

    3. 3

      Write rubrics

      Support and revenue operations templates.

      Forward Deployed Engineer 2 weeks

    4. 4

      Write the guide

      From zero to a first regression suite.

      Research Scientist 2 weeks

    5. 5

      Launch

      Post, README, office hours and Product Hunt.

      Founder & CEO 1 week

    6. 6

      Convert

      Offer the eval pilot to active adopters.

      Founder & CEO ongoing

    First result
    2 quarters
    Cost
    Two engineers for about a quarter
    Owner
    Research Scientist

    Smallest test

    Release the rubric templates alone as a blog post with a repository.

    Why it works

    Open-source a starter kit for building a company eval: a schema for turning traces and human decisions into test cases, rubric templates for support and revenue operations, a regression-suite runner, and a guide. Thirdlayer's paid product becomes the managed, continuously updated version, with FDEs and private deployment.

    An open standard makes Thirdlayer the reference point in the category it sells, and every team that adopts the kit is a qualified lead for the managed version.

    Risks and how to handle them

    • Competitors adopt it

      Keep the managed service, private deployment and trace learning in the product.

    Builds on

    Evidence

    • GitHubAutoAgent repository: 4.6k stars, 493 forks, MIT licence, on a founder's personal account; the README logo links to thirdlayer.inc and says "We're hiring engineers. If this work interests you, reach out to [email protected]."; it does not mention Dex or Thirdlayer's evaluation product.Source
    • HiringResearch Scientist: post-trains models on tasks and environments built from production data, treats "evals as a research problem in their own right" and builds pipelines that "turn messy production traces into training signal".Source
    • Your websiteHomepage: a logo strip headed "Deploying with teams at the frontier" with 15 logos (among them Vercel, Cursor, Stripe, Ramp, Figma, Notion, Shopify, GitHub and Databricks); four use cases (customer operations, revenue operations, product and engineering, and agent evaluation with "replayed environments, rubrics, and regression suites"); "A dedicated AI FDE rethinks the operation with your team and launches the first production system on Dex"; security claims: deploy inside your boundary, deterministic controls, trace every participant.Source
  • 20

    Every enterprise deal starts with "A dedicated AI FDE", and Thirdlayer is hiring one Forward Deployed Engineer in San Francisco. Distyl shows the scale of the service-heavy model with "50+" enterprise deployments. With FDE time as the bottleneck, demand from the ideas above could exceed what the team can deliver.

    High impactHigh effort First result in 2 quarters Founder & CEO

    First action

    List five firms already building agents for mid-size companies.

    How to measure it

    Partner-delivered production systems

    Now
    –
    Target
    5
    By
    3 quarters

    Steps

    1. 1

      Shortlist

      Five firms with agent delivery experience.

      Founder & CEO 2 weeks

    2. 2

      Write the standard

      Certification checklist from the starter systems.

      Forward Deployed Engineer 2 weeks

    3. 3

      Train one partner

      Shadow one deployment.

      Forward Deployed Engineer 1 month

    4. 4

      Agree terms

      Referral, resale or service split.

      Founder & CEO 2 weeks

    5. 5

      Run a pilot

      One partner-led deployment with Thirdlayer review.

      Forward Deployed Engineer 6 weeks

    6. 6

      Compare

      Time to production and eval results against in-house.

      Founder & CEO 1 week

    First result
    2 quarters
    Cost
    FDE time for training; margin shared with partners
    Owner
    Founder & CEO

    Smallest test

    Let one partner shadow a full deployment.

    Why it works

    Certify two or three small AI implementation firms on Dex using the starter systems. Thirdlayer keeps the platform, evals and the first architecture review; partners handle connectors and rollout under Thirdlayer's checklist. Start with one partner on one use case and compare outcomes with in-house deployments.

    Partners add delivery capacity without headcount and bring their own client relationships, while the platform and eval data stay with Thirdlayer.

    Risks and how to handle them

    • Quality drops

      Thirdlayer signs off architecture and evals before go-live.

    Builds on

    Evidence

    • HiringForward Deployed Engineer: deploys the platform "into live customer environments", builds ETL pipelines and connectors for company-specific data, owns work from scoping through production and turns customer patterns into product features; the post's thesis: "AI models are generic, but people's work and processes are specific."Source
    • Competitor researchRivals' own homepages: Glean leads with named outcomes (Zillow "1.5+ hours saved weekly per user" and "3.4k+ agents"; TIME "3 weeks to go-live") and a "Get a demo" page; Dust shows "3,000+ global organizations", "300,000+ agents deployed", a free trial and case studies with numbers; Distyl calls itself "an AI-native operations company" with "50+" enterprise deployments.Source
    • HiringCareers page: seven openings, all in San Francisco: Platform Engineer, Forward Deployed Engineer, Product Engineer, Software Engineer (Intern), Research Scientist, Research Engineer and a General Application; the only company text is "We keep an eye out for exceptional people regardless of what is posted."Source
  • 21

    Thirdlayer measures its own work in numbers: regression tests, pass rates and failures routed, all shown on the homepage dashboard. Dex already breaks from the norm with flat team pricing ("no seat gates"). Rivals sell seats or services. A vendor whose product is built around evals can price on the outcome those evals measure.

    High impactMedium effort First result in 2 quarters Founder & CEO

    First action

    Pick one use case and define the outcome metric and its measurement.

    How to measure it

    Proposal win rate

    Now
    –
    Target
    +20 points versus standard pricing
    By
    3 quarters

    Steps

    1. 1

      Choose the use case

      Customer operations, where outcomes are clearest.

      Founder & CEO 1 day

    2. 2

      Define the metric

      Outcome, eval and measurement window.

      Research Engineer 1 week

    3. 3

      Model the economics

      Base and success fee from past deployments.

      Founder & CEO 1 week

    4. 4

      Draft contract terms

      Measurement, disputes and caps.

      Founder & CEO 2 weeks

    5. 5

      Offer to two prospects

      Alongside standard pricing.

      Founder & CEO 1 quarter

    6. 6

      Review

      Win rate, margin and delivery effort.

      Founder & CEO 1 week

    First result
    2 quarters
    Cost
    Revenue risk on the success fee
    Owner
    Founder & CEO

    Smallest test

    Offer a small success bonus on one deal.

    Why it works

    Offer the first system with part of the fee tied to an agreed target, for example a share of L1-L2 tickets resolved without escalation at a set pass rate, or CRM fields kept current, measured by the eval suite both sides agree in week one. A base fee covers delivery; a success fee is paid when the target is met for a month.

    It lowers the buyer's risk at the hardest step, the first system, and turns Thirdlayer's eval strength into a commercial edge rivals can't easily copy.

    Risks and how to handle them

    • Disputes about measurement

      Agree the eval suite and baseline in writing in week one.

    Builds on

    Evidence

    • Your websiteHomepage: a logo strip headed "Deploying with teams at the frontier" with 15 logos (among them Vercel, Cursor, Stripe, Ramp, Figma, Notion, Shopify, GitHub and Databricks); four use cases (customer operations, revenue operations, product and engineering, and agent evaluation with "replayed environments, rubrics, and regression suites"); "A dedicated AI FDE rethinks the operation with your team and launches the first production system on Dex"; security claims: deploy inside your boundary, deterministic controls, trace every participant.Source
    • Dex siteDex pricing: Core $49/month (3 integrations), Max $99/month ("Most popular", 5 integrations), Ultra $199/month (15 integrations, dedicated account manager), Full Service (custom, "Built and managed like a team of EAs") and Teams & Enterprise ("Flat rate pricing (no seat gates)", shared context, private cloud, "Book a call"); no free tier or trial is mentioned.Source
    • Competitor researchRivals' own homepages: Glean leads with named outcomes (Zillow "1.5+ hours saved weekly per user" and "3.4k+ agents"; TIME "3 weeks to go-live") and a "Get a demo" page; Dust shows "3,000+ global organizations", "300,000+ agents deployed", a free trial and case studies with numbers; Distyl calls itself "an AI-native operations company" with "50+" enterprise deployments.Source

Wildcards 1

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

  • 22

    AutoAgent reported first place on SpreadsheetBench (96.5%) and TerminalBench (55.1%), and 493 people have forked it. Those forks are running their own optimisation experiments, but there is nowhere to share results, so the community, and Thirdlayer's view of who is serious about agents, stays scattered.

    Medium impactMedium effort First result in 2 months Research Engineer

    First action

    Pick three open tasks and a submission format.

    How to measure it

    Leaderboard submissions

    Now
    –
    Target
    30 a month
    By
    2 quarters

    Steps

    1. 1

      Pick tasks

      Three open, cheap-to-run tasks.

      Research Engineer 1 week

    2. 2

      Define submissions

      Harness files, logs and a reproducible score.

      Research Engineer 1 week

    3. 3

      Build the page

      Static leaderboard on thirdlayer.inc.

      Product Engineer 1 week

    4. 4

      Verify scores

      Re-run top submissions.

      Research Engineer monthly

    5. 5

      Feature winners

      Monthly write-up and office-hours invite.

      Founder & CEO monthly

    6. 6

      Follow up

      Recruiting and sales follow-up with strong entrants.

      Founder & CEO monthly

    First result
    2 months
    Cost
    Compute for re-runs and a week of engineering
    Owner
    Research Engineer

    Smallest test

    Open a GitHub discussion asking forkers to post their results.

    Why it works

    Host a simple leaderboard page on thirdlayer.inc where AutoAgent users submit optimised harnesses and scores on a few open tasks. Feature the best submission each month in a short write-up and invite its author to office hours. Use submissions to spot strong engineering candidates and companies building agents seriously.

    A leaderboard gives an open-source project a reason to come back, earns links and posts, and surfaces both hires and buyers.

    Risks and how to handle them

    • Gamed scores

      Re-run every featured submission and use held-out tasks.

    Builds on

    Evidence

    • Your websiteAutoAgent post (April 2, 2026): an open-source system in which a meta-agent improves an agent harness overnight; it reports 96.5% on SpreadsheetBench and 55.1% on TerminalBench, first on both leaderboards; lessons include that trajectories, not just scores, matter and that optimisers overfit; the post ends with an email address, not a link to Dex, the evaluation product or a demo.Source
    • GitHubAutoAgent repository: 4.6k stars, 493 forks, MIT licence, on a founder's personal account; the README logo links to thirdlayer.inc and says "We're hiring engineers. If this work interests you, reach out to [email protected]."; it does not mention Dex or Thirdlayer's evaluation product.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 #3 (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)
ProgrammableTalk

Fill the events in this plan

These ideas are events. Talk gets registrants for them and tells you who's coming and what their company does before the day.

Plan an event (opens programmable.talk 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.

  • Robin Radar Systems growth strategyA Dutch maker of 3D radar systems that detect and classify small flying objects: IRIS for drone detection (counter-UAS) and MAX for bird…22 growth ideas
  • Grafana Labs growth strategyOpen source and cloud observability: Grafana, Loki, Mimir, Tempo, Pyroscope, Alloy, Beyla and k6, delivered as Grafana Cloud (with AI…22 growth ideas
  • Rent the Runway growth strategyDesigner clothing rental: subscriptions of five items per shipment, one-time rentals for events, and resale of pre-loved pieces, from…22 growth ideas
  • Udundi growth strategyA boutique Shopify Plus agency in Austin, Texas, founded in 2012: custom Shopify development, migrations, UX/UI design, CRO and A/B…21 growth ideas
  • 404 Parts growth strategyAn online store for Genuine OEM GM parts and accessories (Cadillac, Chevrolet, GMC), wireless charging and CUE retrofit kits, GM upfitter…23 growth ideas
  • ALX Africa growth strategyOnline and hub-based tech, AI, creative and entrepreneurship training for young Africans, with an All Access subscription for every…22 growth ideas
  • PrescriberPoint growth strategyAn AI-powered point-of-care platform for U.S. healthcare professionals: FDA label information, comparisons, coverage and savings look-ups…21 growth ideas
  • OP Labs growth strategyThe team behind Optimism's technology: it develops the OP Stack, ships upgrades every OP Stack chain inherits, and delivers OP Enterprise…20 growth ideas

See every playbook and website review

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

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

30/60/90 roadmap

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

  1. Days 1 to 307 ideas

    Fix the front door: booked demos, open research, a repository that points home, one message, site basics, Dex listing numbers and a careers page that sells the mission.

  2. Days 31 to 6011 ideas

    Proof and pipeline: outcome stories, the eval pilot, Dex-to-team signals, an engagement page, trust page, FDE templates, use-case pages, office hours, comparisons, referrals and the sponsor report.

  3. Days 61 to 904 ideas

    Commit to the big bets: the open company-eval template, partner delivery, outcome-based pricing and the harness leaderboard.

The research behind the plan

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

Customers

What customers say

Customers value context that builds up across tools instead of starting from zero each time. The most cited problem: operations scattered across Gmail, Slack, Notion and the CRM.

  • Hours saved on routine work such as meeting prep and CRM updates
  • Generic AI that does not know the company's own processes
  • In their words: “agent-native”

Market

Competitive landscape

4 competitors compared: Glean, Dust, Distyl and In-house agent teams.

  • Gap to exploit: Company-specific evals for agents already in production
  • Glean: Search-first heritage; less hands-on building per customer
  • Dust: Customers build their own agents; little forward-deployed help

Hiring signals

Thirdlayer is hiring seven roles, all in San Francisco, and they show where the company is going: a Forward Deployed Engineer to deliver the FDE-led enterprise offer and turn deployments into product (ideas 7, 11, 13…

  • Forward Deployed Engineer: FDE-led delivery into live customer environments. Ideas 11, 13, 20.
  • Platform Engineer: Context capture, learning pipeline and evaluation tooling. Ideas 9, 12, 18.
  • Product Engineer: Browser extension, web surfaces and integrations. Ideas 6, 10.

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