ABOUT THE FOUNDER

I got tired of
remembering everything.

IOOK began with a very human problem: life had become a collection of tabs I was afraid to close.

Flights. Payments. Work. Family. Prices I was waiting on. People I needed to call. Things I had to remember next week, next month, or at exactly the right moment. Every tool wanted me to come back and check it. I wanted the opposite.

I did not want another app to check.
I wanted something that checked for me.

WHY JOB WATCH MATTERS IN INDIA

Your next workplace should be allowed to call you.

For a student or young professional, finding the next job can become a second job by itself. You discover the companies you admire, open their careers pages, check again tomorrow, check again next week, and hope the right opening appears while you happen to be looking.

I do not think that is how opportunity should work. If someone knows the kind of role they want, the qualification they have, the experience they can offer and the salary they need, software should be able to carry the repetitive checking for them.

That is why Job Watch became one of the most important parts of IOOK. Give IOOK a public company careers page, describe the job you are waiting for, and leave. IOOK keeps watching. When a new opening matches, it can call you back inside IOOK and by email.

“Software Engineer” “12th Pass or bachelor's degree” “0–2 years experience” “₹12,000+ per month”

A good opportunity should not be lost because somebody refreshed the careers page one day too late. Sometimes, a young person's next work nest should be the one that calls them.

THE ROAD HERE

Computer science taught me how systems work. Life taught me why most of them do not.

I studied Computer Science at Auburn University in the United States and worked on research with Dr. Peng Li. After graduating, I joined KNAPP as a systems software engineer, working around the kind of automation and logistics systems that quietly keep enormous operations moving.

Later, I moved deeper into manufacturing and business through ORM Engineering, working across supply chain, engineering, customers, factories, logistics and international operations. That meant living inside a constant stream of decisions: quotations, shipments, travel, payments, reminders, people, deadlines and dozens of small things that could become expensive if I noticed them too late.

I had software everywhere. What I did not have was a system that stayed awake when I was not looking at it.

THE MOMENT

There had to be a better way.

The frustration was not that information was unavailable. The frustration was that I had to keep remembering to look for it.

Did the right job finally open? Is the flight cheaper yet? Did that listing finally drop? What bill am I forgetting? What changed while I was busy living?

At some point the thought stopped being “someone should build this.” It became: I have to build this.

THE IDEA

Software should not wait for you to remember it exists.

Most software is reactive. You open it. You search. You refresh. You ask. Then you leave, and the software effectively goes to sleep.

IOOK is being built around a different relationship: tell it what matters once, then let it keep working. It can watch, remember, understand and alert — and over time, with explicit permission and safety controls, help execute the next step too.

OBSERVE→UNDERSTAND→ALERT→EXECUTE

THE PEOPLE BEHIND THE WHY

IOOK is technical.
The reason I care about it is not.

The bigger the product became in my head, the more I realized I was not building it just to save clicks. I was building it to give people more attention back for the people and moments that actually deserve it.

Renuka

My wife, and the first person I think about when I think about what “life admin” steals from us: time, attention and mental space that should belong to real life.

Vanshika

My sister. A reminder that context is personal. People are not records in a database; the details we remember are part of how we show up for each other.

Porus

My son. PORUS — IOOK's permissioned execution and security layer — carries his name. If IOOK is ever trusted to act for someone, I want that trust treated with the seriousness I would demand for my own family.

PORUS

Capability without control is not intelligence.

IOOK's long-term direction is not merely to answer questions. It is to help carry responsibility. PORUS is the layer being designed around permission, approval, safety and execution — so that “AI that does things” never means “AI that does whatever it wants.”

WHY KEEP BUILDING?

I want a future where remembering to check is no longer a job humans have to do.

If IOOK succeeds, the achievement will not be another AI dashboard. It will be the quiet disappearance of thousands of tiny obligations that currently live in people's heads.

That includes the careers page a student is refreshing, the price someone is waiting to fall, the flight someone is waiting to book, and all the other small checks that software can carry instead.

That is the future I am trying to build — one where software notices, remembers and comes back when it matters, so we can spend more of our lives somewhere else.

— Mayur Somani

Building something similar? Found a problem? Want to talk? contact@theiook.com →