Chay Patil C2X ยท Context-to-Execution Let’s talk

Everis

AI Workflow & Growth Consultant, Feb to Sep 2026. Everis buys small SaaS businesses and grows them. I built the AI systems behind their growth, mostly for Prosp and Pebble.

[ Back ]

Hundreds of people raised their hand. Everyone got the same copy-paste.

Prosp grew with “comment AI and I'll send it to you” posts on LinkedIn. Every post pulled hundreds of warm comments. One setter answered them by hand with the same template, with no record of who replied or booked.

Same 10 comments on a “comment AI” post. Two ways to answer them.

By hand00:00

Right now

Waiting for comments

 

    Answered 0 / 10
    AI setter00:00

    Right now

    Waiting for comments

     

      Handled 0 / 10

      Illustrative leads and names. Timings from the real system: about 5 minutes a lead by hand, about 30 seconds with the setter, and a human still sends every message. The clock runs fast.

      Six steps from a comment to a booked call.

      AI does the reading, sorting and first drafts. A person still sends every message, because that's where trust lives.

      1. 01Input

        A post goes live

        A free resource on offer: “comment AI and I'll send it.”

      2. 02Capture

        Every commenter is pulled in

        Name, headline and the exact words of their comment, the signal most tools throw away.

      3. 03AI

        Each lead gets marked

        Claude reads the comment and profile and marks it hot, warm, cold or skip. Spam and vendor pitches get filtered out.

      4. 04AI

        A personal first message

        Written for each lead in the tone its intent deserves, with the resource link inside.

      5. 05Human

        Routed, reviewed, sent

        Matched to the right one of five brand accounts. The setter reads, edits if needed and hits send.

      6. 06Track

        Tracked to the booking

        Sent, replied, qualified, booked. Duplicates caught, so one person on two posts counts once.

      AI does the workA person decidesPlumbing

      5m → 30sHandling time per lead
      1,000+Warm leads processed every month
      5Brand accounts, one operator

      The setter never had to open the spreadsheet.

      Every earlier tracker died because the operator wouldn't use a spreadsheet. So I stopped asking. They kept writing notes in a doc the way they already worked, and the system read the doc and updated the funnel on its own. Most automation dies at adoption. This one didn't.

      1. AHuman

        Notes, as usual

        Free-form, in a doc. No new tool, no new habit.

      2. BAI

        The doc gets read

        A parser turns messy notes into clean funnel stages.

      3. CTrack

        The funnel updates itself

        Leadership sees the numbers. Nobody does data entry.

      • Claude API
      • Prompt caching
      • Google Apps Script
      • Google Sheets
      • LinkedIn comment scraper
      • Doc-to-sheet parser

      Onboarding rebuilt around where people actually got stuck.

      Instead of guessing why new users dropped off, I read through 30+ support conversations, found the real drop-off point, and rebuilt the onboarding emails and in-app tour around it.

      1. 01Input

        30+ support chats

        What new users actually asked, in their own words.

      2. 02Find

        The real drop-off point

        Questions grouped by theme until one step clearly stood out as where people got lost.

      3. 03Ship

        Emails and a product tour

        Onboarding emails and an Intercom tour written around that step, with tracking to measure it.

      614 affiliates. 41 of them drove 80% of the revenue.

      I audited the whole program, split it into groups by behaviour, and found the small set of partners worth all the attention. Then I built tailored pages for key partners and a win-back campaign for the quiet middle.

      Where affiliate revenue really came from

      51%Opens on the win-back email
      8.9%Clicks
      0Spam complaints

      Plus tailored landing pages and blog assets for four partner brands: Demandii, LinkedOtter, FluidCRM and Lars Kruger.

      Prosp's site, redesigned with Claude.

      I redesigned Prosp's website end to end, using Claude to write and build it.

      An AI video pipeline that shipped 20+ pieces a week.

      For Pebble, a language-learning app, I ran short-form video made with AI, and wrote the playbook so anyone on the team could produce on-brand pieces the same way.

      1. 01Brief

        Prompts and scenes

        Each video planned scene by scene against a locked brand kit.

      2. 02AI

        Generated and voiced

        Scenes, voiceover and captions produced with AI tools.

      3. 03Human

        QA and ship

        Every piece reviewed before it went out. 20+ review-ready pieces a week.

      AI hiring that didn't need the company explained every time.

      AI-assisted hiring flows and tests built on Testlify, with one shared source of truth about the company, so every hiring step ran on the same context.

      Leads waiting on a reply?

      [ Let's talk ]