🚀 We made it into the Top 150 of BITSoM Vertex Builders’ Pitch Fest 2026!
@hack2skill@bitsom_edu@RishAiLabs
2,300+ registrations → Top 150 → Top 6%
Next: 🏗️ Sept 26 — BUILD
🎤 Sept 27 — PITCH
Only 25 startups make it into the BITSoM Vertex AI Incubator.
Time to build. 🔥
#BITSoMVertex #BuildersPitchFest2026 #Hack2skill #AIStartups
A tool without an owner becomes decoration.
It sits in the sidebar.
It works on easy days.
It is skipped on busy days.
Busy days are the only days that matter.
Give those days a name and a queue.
“The AI failed” is not a root cause.
Was it
the scan
the wrong record in the CRM
the missing amendment
the tool the agent should not have called
the person who sent without reading
Name the step.
Then assign the step.
Put failures in a queue. Do not hide them in chat history.
Queue fields I want:
- time
- input file or lead
- what the system said
- what the human changed
- why
That queue is how the product learns.
A chat thread is how the mistake disappears.
Three seats on an industry AI rollout:
Ops — knows the messy file
IT — knows where identity and data live
The closer — owns anything that leaves the building
If only the founder of the AI tool is on the call, you are still in a pitch.
You are not in a rollout.
Every GenAI tool needs an owner when it is wrong.
Not a Slack channel.
A name.
If the extraction is off, who fixes the field.
If the lead is scored cold and it was hot, who catches it.
If nobody owns that, the tool will be blamed and then ignored.
Another rejection today.
This time, from @speedrun . 🚫
They said they’re only able to select a small number of teams each cycle, and encouraged us to keep building and apply again.
Honestly, rejection never feels great. But it’s becoming part of the founder journey.
YC rejected us. Speedrun rejected us. We’re still building. 🚀
Every “no” gives us another reason to keep going.
Back to building Rish AI Labs.
We’ll be back.
#BuildInPublic #Startups #FounderJourney #AI #RishAILabs #Entrepreneurship
I would rather plug into one messy CRM than ship five new screens.
The customer already has a habit.
Your job is to sit inside that habit.
Industry GenAI that ignores the habit is a tour, not a tool.
WhatsApp is not a feature.
It is the front door for a lot of brokers and operators.
Treat it like intake:
capture
score
log
human sends
Treat it like a chat toy and you will send the wrong text from the wrong number.
Duplicate leads kill more AI CRM projects than bad prompts.
Same person.
New spelling.
Old record.
Agent creates a second card.
Sales calls them twice.
Match the record before you generate the message.
A useful agent has three doors.
In: the channel the customer already uses
Through: extract, score, refuse
Out: the system of record the team already opens tomorrow morning
If “out” is only your dashboard, the team will copy-paste and then stop using you.
Integration order I use:
1. Inbox / WhatsApp — where the lead arrives
2. Drive / PDF folder — where the file sits
3. CRM — where the name already exists
4. Your UI — last
Most teams build 4 first.
Then they wonder why nobody opens it.
Your user does not live in your app.
They live in
WhatsApp
email
CRM
the shared drive
If the AI cannot read from those and write back to those, it is a side window.
Side windows get ignored.