Shadow 2.0 - The work your meetings create, done before they end

@soni_karan Shadow understands the meeting context and is helpful enough to takeover much of your workload generated from everyday meetings, alongside, it is careful enough to not execute sensitive tasks, and wait for your approval.

Think metrics brought for you instantly during call,
Mails drafted for you during call,
Calendar events scheduled for you during the call
Notion pages published for you during the call.

@soni_karan here’s still a human layer by design.

Shadow can detect the follow-up, prepare the doc/email, or set up the calendar invite in real time - but the user reviews and approves before anything gets sent or scheduled.

We don’t want AI silently acting on your behalf. We want it to remove the busywork while keeping you in control.

Curious - would you be comfortable with auto-send for low-risk follow-ups, or should approval always stay mandatory?

@soni_karan It does both and goes beyond. Shadow creates Notion docs, drafts emails, books follow-ups, all while you're still on the call. Next up: BI tools, Jira, CRMs. The goal is simple: Give people their time back.

@hersh_singh Hersh has been closest to the people we’re building this for, and this pattern kept coming up again and again: the call is not the hard part, the work after the call is.

That’s why we’re building Shadow as a real-time layer that doesn’t just capture context, but helps complete the work while the context is still fresh.

@raghav39 this is exactly the kind of workflow we want Shadow to handle.

Today, Shadow can capture the notes/action items during the call and turn them into docs, follow-ups, or tasks. Productboard isn’t live yet, but converting customer calls into structured user stories inside product tools is very much on the roadmap.

Curious - would you want it to create raw notes in Productboard first, or directly create polished user stories with problem, context, and acceptance criteria?

Hey @nuseir_yassin1 , I have been watching your videos from so many years, & I totally love them, just didn't expect at all that you would comment here.

But yes, that’s a really good suggestion, and I agree - a lot of meetings, have useful insights that usually just disappear after the call.

We’re starting with completing action items during the meeting itself, but turning key moments into reusable content is definitely an interesting direction.

Curious - do you think the real value is in creating content from meetings, or in helping people notice the “content-worthy” moments they would normally miss?

@bengeekly Shadow is built to handle mixed-language conversations by following the actual conversation context, not forcing everything into one language.

So if a call switches between English, Hindi, Spanish, etc., the transcript and action context can still be understood, and the final output can be created in the language that makes sense for the task - for example, an English follow-up email even if parts of the call were in another language.

Curious - when a call switches languages, what matters more to you: accurate transcript in the original language, or clean outputs in one language?

@bengeekly try seeing it in action, even we get surprised how smoothly the transcript switches language.

@peterclaridge this is a very fair point - and probably the biggest thing we need to make clearer.

We don’t think of Shadow as a notetaker. Notetakers capture the meeting, summarize it, and give you action items after.

Shadow is built for what happens during the call: turning those action items into actual work while the context is still live - follow-up emails, docs, scheduling, and eventually CRM/task/tool updates - with the user reviewing and approving before anything goes out.

So the difference we’re betting on is: meetings shouldn’t end with a better to-do list. They should end with the work already done.

Also, +1 on the comparison matrix. That’s a great idea, especially for people already using tools like Granola/Fathom/Otter/Fireflies.

Curious from your marketing lens - which workflow would make this difference most obvious first: follow-up emails, docs, scheduling, or CRM/task updates?

@peterclaridge Totally respect the notetaking tools, they're great at what they do.

But there's a difference between a tool with ears and one with hands and legs.

Notes tell you what happened. Shadow gets the work done. Yours to choose. 😄

@naitik_kapadia exactly - reliability is the whole game here.

The shift only matters if Shadow can understand the right action, prepare it with context, and still keep the user in control before anything is sent, created, or scheduled.

That’s why we’re starting with high-frequency workflows like follow-up emails, docs, and scheduling before expanding deeper into CRM/task updates.

Curious - from a product perspective, what would make you trust execution during the call: approval before every action, clear action previews, undo/edit controls, or better integrations?

@naitik_kapadia Hey Naitik, just imagine, you get off a call with nothing to do. All the major items, already done or drafted!

@philip_kubinski this is not too specific at all - it’s actually a really strong sales use case.

A lot of the best knowledge in a sales team lives inside calls: how someone handled an objection, framed pricing, prepared a proposal, or moved a deal forward. The problem is that it usually stays with that one AE.

This is exactly the kind of direction we want Shadow to move toward: not just completing the task from one call, but helping turn repeated patterns into shared team knowledge.

Curious - would this be more useful as a searchable sales knowledge base, or as proactive suggestions during the next similar call?

@philip_kubinski We hear this pain everyday. Team features are on the roadmap & not just a shared learning platform, but the ability to set playbooks, tweak the answers reps should give, and have Shadow deliver real time guidance on the call.

Gong does this pathetically. The feedback cycle is brutal: listen, analyse, iterate, wait for results. That's a 3 month loop. By the time you have answers, the market has moved.

We will close that loop to zero. Pain well noted, and you'll be hearing from us. 😄

@iamajeets yes - Shadow can generate MoMs/meeting summaries too.

But we think the bigger shift is that MoMs should become more actionable. A summary is helpful, but the real work starts when decisions need owners, follow-ups need to be sent, and next steps need to move into the right tools.

That’s where Shadow is focused: turning the meeting into ready-to-review work before the call ends.

Curious - what would make a MoM truly useful for your team: better decision tracking, owner/deadline detection, automatic follow-ups, or pushing tasks into your existing tools?