Trupeer

@abod_rehman Totally agree.
That’s exactly what pushed us to build this.

@abod_rehman that's why we have created this ;)

@shivali_goyal1 hey there :) Curious how you handle accuracy and edge cases: when a screen recording includes detours, mistakes, or non-linear flows, how does AI Doc Writer decide what becomes part of the final step-by-step doc? Is there a confidence/scoring or review layer to avoid hallucinated or misleading steps? This is a really interesting shift from better editors to no writing at all!

@shivali_goyal1 Congrats on the launch! How does AI Doc Writer integrate with existing workflows—Word, Google Docs, email?

Does AI Doc Writer apply your Brand Kit custom glossary during step generation, or only after? That's the on-brand naming consistency that keeps docs from turning into a cleanup job.

@shivali_goyal1 congrats on the launch. In which format are the docs generated?

@prashastha_jain Thanks, really appreciate it 🙌
We’re trying to make docs feel as easy as hitting record.

@prashastha_jain you bet ;)

Thanks Arun, really appreciate the kind words 🙌
We’ve put a lot of care into making the output feel genuinely “shippable”, not generic.

If you try it, I’d love to know what you’re documenting most often: internal SOPs, product walkthroughs, or customer onboarding?

@a_s_k_af thanks man! Happy to see Trupeer being helpful in your work

@a_s_k_af true!

Thanks @harkirat_singh3777 
That “messy recordings → clean, on-brand docs” line is exactly the goal.

We built Trupeer to work with real-world inputs (Zoom/Meet demos, imperfect walkthroughs), then use vision-based understanding to pick the actions that matter and turn them into a doc that reads like something your team would actually ship.

Curious: where would this help you most, internal SOPs, customer onboarding, or product docs?

@shivali_goyal1  @harkirat_singh3777 thanks buddy! It's so good to see you here

@iamarnob6543 
This means a lot, thank you ❤️

We’ve been obsessed with the nitty-gritty because that’s where documentation usually breaks. People don’t struggle to “explain” something; they struggle to turn that explanation into a doc that’s actually usable and shippable: clean steps, correct screenshots, and the same structure your team expects, without spending hours formatting and rewriting.

That’s why we built Trupeer to work from real recordings (including messy Zoom/Meet demos), use vision-based understanding to detect meaningful actions, and then generate a doc that reads like something a team would confidently send to customers or ship internally.

If you get a chance to try it, I’d love to know what your primary use case is at Olvy: release notes, product docs, onboarding, SOPs, or internal workflows. We’re actively iterating based on feedback, and your perspective would be super valuable

@iamarnob6543 thanks a lot buddy!

@huisong_li thanks!

@huisong_li Really appreciate your support.