Hi Friends,

Even as I launch this today ( my 80th Birthday ), I realize that there is yet so much to say and do. There is just no time to look back, no time to wonder,"Will anyone read these pages?"

With regards,
Hemen Parekh
27 June 2013

Now as I approach my 90th birthday ( 27 June 2023 ) , I invite you to visit my Digital Avatar ( www.hemenparekh.ai ) – and continue chatting with me , even when I am no more here physically

Thursday, 22 October 2026

RE: Feedback Needed - Blog Genie Skills

 Kishan ,

 

I could not fully appreciate these templates but my feedback is as follows :

 

Ø   In “ Thought Leadership “ template , reduce the text to , under 600 words ( after looking at how this appears, we may increase it slightly ) . “ Synopsis “ can be another 100 words max

Ø  Following IDENTICAL paragraph headings in all blogs , look very “ Boring / laboured / Straight jacket / AI give away “ :

 

         #  What Happened

        #  Why this matters

         #  What this means for ………….

         #  What to do now

         #  The Bigger Picture

         #  Questions readers will ask

 

          These IDENTICAL headings make the blogs to appear to be tumbling out on a “ Mass Production Assembly Line “   !

 

This ( feeling ) must be avoided

 

Somehow , we must make each blog to appear UNIQUE ( designer ? )

 

Only such VARIETY / NOVELTY , can make readers to read the NEXT blog

 

How would it come out if :

 

Ø   We avoid the para-titles , altogether ?  OR

Ø   From one blog to another , both the no of “ Paras  with Titles “ AND

“ Title Descriptions “ , change – thereby ensuring  UNIQUENESS

 

Phone me around 5 pm with your views

 

With regards,

 

Hemen Parekh 

 

From: Kishan Kokal [mailto:kokalkishan.official@gmail.com]
Sent: 21 October 2026 18:57
To: Hemen Parekh <hcp@recruitguru.com>
Cc: Vishesh Parekh <vishesh@incomegroup.in>
Subject: Feedback Needed - Blog Genie Skills

 

Please find the attached skills for your review. Kindly share your feedback.

Warm regards,

FW: AI got cheaper. Did your workload?

 With regards,

 

Hemen Parekh 

 

From: Joe Stolte [mailto:joe@joestolte.com]
Sent: 21 October 2026 20:31
To: hcp@recruitguru.com
Subject: AI got cheaper. Did your workload?

 

Smarter AI. Same business bottlenecks.  ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏ ͏­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­­

Hi there,

Last week, four AI agents beat Minecraft together.

They split the work, shared what they learned, and kept going until they won.

No human help.

Now compare that to what's happening in your business.

A qualified lead hits your inbox…

Does someone follow up?

How fast?

Or does everything stop until you weigh in?

For a lot of entrepreneurs I talk to, it’s a full stop.

Last week I said most businesses aren't ready to hand work to AI.

This week that gap got a lot harder to ignore.

Because AI got better AND cheaper this month.

Yet most businesses still aren't seeing the payoff.

The tools can do the work. So what's holding up the results?

Spoiler: It's not the AI.

This week I'm going to explain why most business automations keep failing and exactly what to do instead.

Welcome back to Way Forward Wednesday.

My take on three developments in AI and tech… and what they mean for YOUR business.

Let's get into it.

Update #1: Agents can now split the work and keep going.

Google dropped four Gemini 4 Argon agents into a fresh Minecraft world with one goal:

Beat the Ender Dragon.

No assigned roles to follow and no detailed playbook to follow.

They got a basic bot library, shared notes, and a group chat.

The agent team wrote 2,783 programs.

Picked up each other's lost items.

And won in just over 27 hours.

No human stepped in.

Oh… they also died 605 times.

In a game? That's cute.

In YOUR business? That's 605 pissed off clients and maybe a lawsuit.

But here's what made it work:

→ A clear goal

→ Shared information

→ Tools they could actually use

→ A way to check progress

That's your checklist.

If you want AI to do more work with less babysitting...

You need ALL four of those things locked in.

But before you hand over the work…

You need to make two more decisions.

1) Set limits and approval rules.

As agents get more capable, big firms are drawing hard lines.

Schwab is blocking outside agents from moving customer money.

JPMorgan's doing the same thing.

They'll let AI research a customer.

But making promises TO that customer? No way.

Your business needs the same rules.

What can an agent do on its own?

When does it need approval?

Who steps in when things go sideways?

Figure that out before you flip the switch.

Not after you accidentally refund someone $10K.

2) Decide what stays human.

Some work should stay with people.

Some can go to AI.

Some needs both.

The key is knowing which is which...

And when AI should hand the work BACK to a person.

Last week I shared my favorite framework for this: Find, Filter, Free.

As promised, I recorded the full walkthrough.

It includes how we helped a CEO get two full days back each week...

Without hiring anyone.

Watch: Before You Hire Another Employee, Do This ​

And NOW is a very good time to put it to work.

Because AI just got cheaper. Again.

Update #2: High-volume AI work costs a lot less.

Earlier this month, Anthropic launched Claude Haiku 5.5.

For prompts up to 100,000 tokens, input and output prices are 90% lower than Haiku 4.5.

Anthropic estimates average running costs dropped about 75%.

Forget the model names for a sec.

Think about the WORK:

·         Pulling key facts from documents

·         Sorting incoming requests

·         First-pass research

·         Turning long notes into usable summaries

All 75% cheaper now.

Lower prices make these tasks cheaper to TEST.

And running them across your whole business starts to look realistic.

But here's the thing...

Cheap output can still create expensive work.

If someone spends 20 minutes fixing a summary that used to take 10 minutes to write by hand…

You didn't save time. You added work.

You want to count the human checks, fixes, and the back-and-forth.

Measure the cost of a USABLE result. Not just the cost of an AI response.

Before any automation goes live, I run it through The 3S Test.

I'll break that down in this week's Friday Field Notes.

But here's the million dollar question...

If AI is doing MORE and costing LESS...

Why are most businesses still not getting much out of it?

Update #3: The value gap hasn't closed.

​Gartner just dropped some research.

They surveyed 2,000+ tech leaders.

Only 13% said their business had gained major or game-changing value from AI.

13%.

​Bain studied 951 companies and found them realizing about 38% of AI's expected value.

Two studies.

Different yardsticks.

Same finding: Most businesses are getting a FRACTION of what they expected.

My take?

It’s easy to get excited about what an AI tool can do.

But before buying it, there’s a question worth answering:

What’s ACTUALLY broken in the business?

If that’s unclear, you can spend a lot of time automating work that wasn’t the problem.

Too many businesses are generating offers faster…

While qualified leads still wait a day for a reply.

You're summarizing every meeting…

While nobody owns the next steps.

You made a task faster. Did you make the business better?

Let's look at one place your business is probably losing money...

While everyone waits on you.

Here's what I'd do.

Say you run a consulting business.

Someone fills out your inquiry form.

Your assistant reads it. Asks you if they're a fit. And waits.

Eventually someone follows up.

Sometimes that's the next day. (Whoops.)

Find the constraint.

Why does every inquiry come to YOU?

Usually because nobody else knows your qualification rules.

Or your form doesn't collect what's needed to decide.

Write the rules down.

Then measure two things:

• How long leads wait for a reply

• How much time your team spends on each one

Now you have a clearly defined problem to fix.

Filter the work.

Give AI one small piece.

It reads the inquiry. Gathers key details. Drafts a reply based on YOUR rules.

It flags missing info and suggests a next step.

A person checks before anything goes out.

AI cannot invent an offer. It cannot approve a discount. It cannot promise a result.

One Lead. Two Paths. Where The Work Stalls.

You don't need to script every click.

You need a clear goal, the right information, and firm limits.

The Minecraft agents had the first two.

For your business, make the limits just as clear.

Free the people. Then prove it.

Run it for two weeks.

Are leads getting useful replies sooner?

Is your team spending less time checking and fixing them?

Are more qualified prospects booking calls?

If yes, expand.

If no, find out WHY before you add another agent.

Maybe key details are missing.

Maybe the rules need work.

Maybe you fixed a delay that wasn't the main problem.

Find out first before you change anything else.

Your next move

Don’t try to automate everything at once.

Pick ONE process that's killing time.

The one where work keeps waiting on you as the leader.

Map it. Measure it. Hand ONE piece to AI.

Then see if your business actually works better.

Check the time saved, the corrections needed, and the result.

Do this once a week for 90 days…

And your business won't look the same when you’re done.

This is the way forward.

Onwards 🚀

Joe

P.S. Whenever you're ready, here's 3 ways I can help you grow your business with AI:

1. Binge my best training on using AI to grow revenue without hiring more people on YouTube.

2. I've installed AI in 400+ businesses. This video breaks down what I learned about why most people get stuck and how to actually save time and drive revenue.

3. Want me to install AI agents in your business and train your team to run them? Click here to learn more. ​

​Unsubscribe | Update your profile | 600 1st Ave, Ste 330 PMB 92768, Seattle, WA 98104-2246

Wednesday, 21 October 2026

Blog Genie 3.0

 Kishan ,

 

Even as I look forward to today’s demo , I think you may want to glance through my following chat with CLAUDE yesterday

 

Hcp

 

https://claude.ai/artifact/662N2zpMX9gabVNd9mJqEE#bd1b9427-43c5.my4wg8jeamr.5782

 

 

 

I asked :

 

“ Hey Bro, thanks for valuable inputs. Talking of totally " new " news reports, my feelings on reading these, decide how I " feel " and motivate me or discourage me , to write a blog. These feelings could be treated as " lenses " like ) surprise , anger , disdain , frustration , hope, distress etc . Can Blog Genie use these lenses ? “

 

CLAUDE replied :

 

“ Yes, Bhai, and I think this is the missing piece. Topic lenses tell Genie what a story is about. Feeling lenses tell it whether you’d be moved to write, and what kind of post you’d write. Your best posts don’t start from a topic; they start from a reaction.

One honest caveat: Genie can’t feel anything. What it can do is predict how you would feel. Your archive is full of examples, because each feeling has left a clear pattern in what you wrote.

Each feeling has a trigger and produces a typical post:

Feeling

What in the news triggers it

The post you usually write

Example from your blog

Surprise

Something you proposed years ago suddenly happens

Vindication post with the prior-art trail

“Drone Brigade? Just as predicted”

Hope

A minister or agency takes a step in the right direction

Congratulations, plus “here’s the next step”

“Thank You, Nilekaniji”, “Congratulations, Shri Mandaviyaji”

Frustration

An old problem recurs and your solution is still ignored

Reminder letter: “I have been crying wolf since…”

“Wolf at our Door?”

Anger

Injustice to the powerless; a system crushing an individual

Open letter demanding a fix

“When Algorithms Silence Dignity” (the cab driver’s 99-year ban)

Disdain

Hypocrisy, empty announcements, ego

Satire

Your satirical open letter on detention centres

Distress

Human tragedy: a suicide, an accident, a disaster

A gentle, solution-focused post

The IIT Bombay student posts

Curiosity / wonder

A scientific or technological breakthrough

“What could this mean for India?”

“Nature’s Dusk: A Million Wings”

How Genie would use them:

  1. Learn your reactions. Genie labels about 100 of your past posts with the feeling behind each one, and you correct its labels. That becomes its model of how you react.
  2. Read each morning’s news through your eyes. For every story it predicts a feeling and an intensity from 1 to 5, with a one-line reason. For example: “Hope, 4: the government proposes BS-VII, but it still only tests vehicles at the factory, which ROTE would fix.”
  3. Write only when you’d be moved. If the intensity is 3 or above, write. If it’s below, skip. This filter alone would cut volume and raise quality.
  4. Let the feeling set the format and tone. Hope produces a congratulatory letter; frustration produces a reminder with dates; disdain produces satire.
  5. Learn from your agree/disagree taps. On the approval dashboard you tap “Yes, that’s how I feel” or “No, I’d feel X.” Every tap improves the next morning’s guesses.

Run on your five test stories, Genie would probably guess:

  • Musk: surprise and hope
  • Temple ruling: curiosity
  • MeitY–Meta: frustration (one-off advisories, not a standing framework)
  • BS-VII: hope mixed with frustration
  • Smart classrooms: low intensity, since you’ve already said it

That’s a good check on whether this works.

Three guardrails I’d insist on:

  • Every feeling must end in a proposal. This is your signature: even your angriest posts offer a solution. A post that is only anger or disdain shouldn’t go out.
  • Anger and disdain always need your approval, especially when a named person is involved. And once the avatar is writing on its own, I’d remove those two lenses entirely. Satire or anger attributed to you, about events you never saw, is the riskiest thing an avatar could publish in your name. Hope, surprise, curiosity and constructive frustration are safe to carry forward.
  • Don’t fake the feeling. Genie shouldn’t write “I was shocked to read…” unless you approved it. In avatar mode it should say “Hemen would likely have…”. Readers will trust the avatar more for being honest.

Want me to write this up as a “Feeling Lenses” section for Kishan’s spec? Or I could label your last 30 posts by feeling, so you can see whether Genie reads you correctly.

 

I’ve written up the feeling lenses as a spec for Kishan, ready to share. It covers the seven lenses, a pipeline diagram, the data model and dashboard changes, the guardrails, and a phased rollout.

Two parts need your input:

  • Acceptance test table: I’ve filled in Genie’s expected answers for your five test stories. Your own column is left blank for you to fill in before Kishan runs the test.
  • Open questions at the end:
    • whether 3 is the right threshold for when Genie writes
    • whether to cap it at 3 posts a day
    • whether to add lenses like pride or nostalgia

 

Blog Genie 3.0 — Feeling Lenses Spec

Oct 20, 2026 · @Hemen Parekh · For: Kishan

Purpose

Add a second filter to Genie 3.0's selection step: write only when a story would move Hemen to write, and let the feeling it stirs set the post's format and tone.

Today's selection asks one question: what is this story about? It answers with topic lenses — similarity to the 6,800+ post archive, plus Hemen's recurring themes (zero human intervention, AI regulation, employment, ROTE). That finds stories Hemen could write about. It does not tell us whether he would.

Hemen's real trigger is his reaction on reading the news: surprise, hope, frustration, anger. So each candidate story gets two scores:

Lens

Question it answers

Decides

Topic lens

Has Hemen written on this, or does one of his themes apply?

Whether there is something to say, and which earlier posts to cite

Feeling lens

How would Hemen feel reading this, and how strongly?

Whether to write at all, and what kind of post

A story goes forward only if it passes both. Genie cannot feel; it predicts Hemen's feeling from patterns in what he has written, and his daily agree/disagree taps keep correcting it.

The seven feeling lenses

Each lens pairs a trigger pattern in the news with the kind of post Hemen writes when he feels it. Treat this table as configuration: Hemen can add, rename or retire lenses from the dashboard.

Lens

Trigger signals in the news

Post format

Tone

Example post

Surprise

Something Hemen proposed years ago is now announced or adopted

Vindication post: news hook, dated prior-art trail, comparison table

Matter-of-fact, "just as predicted"

Drone Brigade? Just as predicted

Hope

A minister, agency or company takes a step in the right direction

Congratulations letter, plus "here is the next step"

Warm, respectful

Thank You, Nilekaniji

Frustration

An old problem recurs; Hemen's earlier proposal still not acted on

Reminder letter with the dated trail of earlier posts

Firm, persistent

Wolf at our Door? Invisible too?

Anger

Injustice to the powerless; a system crushing an individual

Open letter demanding a specific fix

Direct, but courteous

When Algorithms Silence Dignity

Disdain

Hypocrisy, empty announcements, ego in public life

Satire or open letter

Ironic

Hemen's satirical open letter to the West Bengal CM on detention centres

Distress

Human tragedy: a suicide, an accident, a disaster

Gentle, solution-focused post

Compassionate, never sensational

The IIT Bombay student posts (Jul and Sep 2026)

Curiosity

A scientific or technological breakthrough

"What could this mean for India?"

Exploratory

Nature's Dusk: A Million Wings

One story can trigger two lenses (for example, hope mixed with frustration). Genie records both, and the stronger one sets the format.

Intensity scale (1–5): 1 = Hemen would scroll past; 3 = he would write a short post; 5 = he would drop everything and write to the minister. Default write threshold: 3.

Pipeline changes

The feeling lens slots in after the topic lens and before drafting; it decides whether to write, and its lens picks the format.

[embed: node/078d5f11-f970]

  1. Label the archive (one-time). Genie labels about 100 recent posts with lens and intensity; Hemen corrects them. These labels are the training examples for step 3.
  2. Topic lens (unchanged). Match each morning story to the archive and Hemen's themes; attach the earlier posts to cite.
  3. Feeling lens. Predict primary and secondary lens, intensity 1–5, and a one-line reason. Use an LLM call with the labelled examples in the prompt; no separate model to train.
  4. Decide. Write if intensity is at least the lens's threshold and the repeat check passes; otherwise list under Skipped today.
  5. Route by lens. The lens selects the post template and tone from lens_config.
  6. Guardrails and approval. Run the checks in Guardrails; sensitive lenses and topics wait for Hemen.
  7. Learn. Every approve, reject, disagree tap and rescue is stored and added to the examples for the next morning.

Data model and dashboard

Three new records and four dashboard changes; everything else in the Genie 3.0 blueprint stays as it is.

New records

Record

Key fields

Filled by

lens_config

lens name, trigger description, post format, tone, example post URLs, write threshold, needs_approval (yes/no), allowed_in_avatar_mode (yes/no)

Hemen, via dashboard

archive_feeling_label

post URL, date, primary lens, secondary lens, intensity 1–5, labelled_by (genie / hemen)

Genie proposes, Hemen corrects

story_score

story URL, date, topic-lens match + cited posts, predicted primary/secondary lens, intensity, one-line reason, decision (write / skip), Hemen's tap (agree / disagree + correct lens), reason if he disagrees

Genie each morning; Hemen's taps

Dashboard changes

  • Each shortlisted story shows Genie's guess in one line: "Frustration, 4 — MeitY issued a one-off advisory; Hemen proposed a standing certification framework in 2023."
  • Two buttons per story: That's how I feel / No, I'd feel… (pick a lens, set intensity, optional reason).
  • A Skipped today list with the reason for each skip, so Hemen can rescue a story Genie dropped. A rescue counts as a disagreement.
  • A weekly agreement score: share of stories where Hemen's tap matched Genie's lens, overall and per lens.

Guardrails

These rules are hard-coded, not configurable from the dashboard.

  1. Every post ends in a proposal. Hemen's posts always offer a fix, however strong the feeling. A draft with no concrete suggestion is rejected before it reaches the approval queue.
  2. Anger and disdain always need Hemen's approval. Same for any post that names or criticises a specific person, and any story about religion, courts or protests. These never auto-publish, even after the autonomy phase.
  3. Avatar mode drops anger and disdain. When Genie publishes without Hemen's review, only surprise, hope, frustration, curiosity and distress are allowed. Anger or satire attributed to Hemen about events he never saw is the riskiest output an avatar can produce.
  4. No faked feelings. In approved posts Genie may write "I was surprised…" only if Hemen ticked that lens. In avatar mode it writes "Hemen would likely have…", and the sign-off reads Written by Hemen Parekh's Digital Avatar, from his writings.
  5. No invented memories. Every personal anecdote or "as I wrote in…" must link to a real archive post. If Genie can't find the source, the line is cut.
  6. Distress posts follow safe-messaging practice. For suicide or self-harm stories: no method or location detail, no sensational headline, and a helpline line at the end (for India, Tele-MANAS 14416). Always held for approval.
  7. Repeat check. Skip a story if Hemen published on the same argument in the last 30 days, whatever the feeling score. Offer a two-line social post linking the earlier post instead.

Rollout, acceptance tests and open questions

Feeling lenses run in shadow mode first: they score and explain, but don't decide, until they match Hemen often enough.

Phases

  1. Label the archive. Genie labels about 100 recent posts with lens and intensity; Hemen corrects them. Target: Hemen agrees with at least 70% of Genie's labels before moving on.
  2. Shadow mode, 2–3 weeks. Each morning Genie shows its feeling guesses beside the topic-lens shortlist; Hemen taps agree/disagree. Selection still follows the existing Genie 3.0 rules.
  3. Feeling lenses decide. Once the weekly agreement score reaches 80% for two weeks running, the intensity threshold gates what gets written. Approval rules in Guardrails still apply.

Acceptance test: Hemen's five test stories (Claude's dry run, 20 Oct 2026; Hemen to fill in his own column)

#

Story

Expected lens

Expected intensity

Expected decision

Hemen's answer

1

Musk vows a SpaceX share for every US child

Surprise + hope

4

Write

2

SC: temple property can't be taken over by government

Curiosity

4

Write, hold for approval

3

Smart classrooms need the human touch

Hope

2

Skip (repeat of 7 Oct post)

4

MeitY asks Meta to review recommendation algorithm

Frustration

4

Write, hold for approval

5

What Bharat Stage VII norms mean

Hope + frustration

4

Write

Genie passes if its lens and decision match Hemen's on at least 4 of the 5.

Open questions for Hemen

  • Is 3 the right write threshold, or should Genie start stricter (4) and loosen later?
  • Should there be a daily cap regardless of scores (suggested: 3 posts a day)?
  • Any lens missing from the seven, such as pride (an Indian achievement) or nostalgia (L&T memories)?