Docs | Smarter.Codes - User contributions [en]

Public:Values

2026-07-06T16:04:29Z

Tushar Goswami:

This article is WIP. Please rather refer to the Values we've documented on Notion.so rather - until we clean the following article
----We adhere to the following core values while making any decision in [[About Smarter. Codes|Smarter.Codes]]:

== 1. COLLEAGUE > CUSTOMER ==
Making a customer happy is important. But making a colleague happy and competent is even more important than customers. Because a single happy and competent colleague can result in 1000s of happy customers.

== 2. ALIGN & DELIVER ==

==== A. ‘Why’ is the best question ====
When working on a task these are the questions you ask

* What is the task
* How to do the task
* When to do the task
* Why are you doing the task

Turns out ‘why’ could be one of the most important questions. Because it helps shape the ‘what, how, and when’. Hence in every task you do we would like you to ‘write down the why’. There is even a book on that now – Start with Why!

'''Align the ‘Why’ of Team'''

Whatever ‘why’ your task has, it helps to the ‘why’ of your colleagues and the ‘why’ of Smarter. Codes company.

It can be empowering if the ‘why’ of everyone at Smarter.Codes aligns before the day begins. Afterall, if the purpose remains aligned, we all progress in the right direction, at a quicker pace.

'''Tell your Why in everything you do'''

In your issue tracker (say Gitlab), task list software (say Trello). So that others reading your work can understand why it is important to work on whatever you are working on

==== B. DELIVER, EVERY WEEK ====
Read how to [[Deliver every week]]

== 3. SHOW EVERYTHING. SEE EVERYTHING ==
Whatever you do, Show it to your people.

Promptly. Every hour. Avoid the ‘''I will show once I am done''’ instinct.

Now that everyone is spending time to show ‘their everything’, do take time out of ‘YOUR daily work’ to check and acknowledge what everyone is working on, and how they are doing it.

When you show and see WIP work of yours and others, it helps everyone to give feedback faster, rather than waiting for all the signals to turn green.

'''''A. Show what you are doing'''''

'''''B. Show how you are doing'''''

'''''C. Show why you are doing'''''

Read more : [[:Category:Show Everything. See Everything]]

== 4. EFFICIENCY ==
'''Smarter.Codes is efficient if'''

* We as individuals are efficient
* We as team are efficient

=== A. Biohacking ===
To keep each individual efficient, we employ holistic methods in Biohacking. Just like in the gym you can train your body to perform better physiologically – likewise you can train your brain to perform better cognitively. We are employing holistic biohacking at Smarter.Codes to enable each one of us to contribute one notch above our mental capacities. At Smarter.Codes we should play to our ‘biological advantage’ to ship amazing stuff for our users.

Check out some advice on Biohacking at Smarter.Codes.

=== B. Upskilling ===
To keep each individual efficient, we embrace [[:Category:Upskilling]] among everyone.

== 5. SIMPLIFY ==

=== A. User Experience ===
Users should find the Products we create ‘easy’ and ‘delightful’ when they are using it

=== B. Colleague Experience ===
Users will get ‘easy and delightful’ products, if people at Smarter.Codes make it ‘easy and delightful’ for their colleagues to ‘together build’ the product.

Public:Sequence Diagram

2026-03-23T16:51:35Z

Tushar Goswami:

[[:en:Sequence_diagram|Sequence diagrams]] are often used to illustrate the Actors, and how the actors interact with each other in a sequence.

= See Also =
[https://docs.google.com/document/d/1K6xbZDji_CLyHdHzzLDpOq2zIXIlXfbVoP2rYrsds3c/edit?tab=t.jvvt15lh4dnp#heading=h.rw4jcbe52lho Sequence Diagram excerpt from Productize AI book][[File:Sequence Diagram of HC Inbox.png|thumb|Example Sequence Diagram of [[HC Inbox]]]]

= Tools =
You can use a free style diagramming tool like draw.io or even figma. Some special purpose toosl to
[[Category:Requirements Engineering]]

Public:Task Analysis

2025-09-25T08:45:56Z

Tushar Goswami:

At Smarter.Codes we build AI automation. We automate a task that a human does. [[:en:Task_analysis|Task Analysis]] involves documenting the each and every step that a human performs. Once its documented, we can use this documentation to communicate to customer, and to engineers on what automation would the AI automation cover.

= Example Task Analysis =
[https://dubble.so/library Task Analysis in operating a software]

[https://docs.google.com/document/d/1DDVG6aMnMIudTm7jyhnuqNaPXIaWK1hrHlppYrohQF4/edit?tab=t.0#heading=h.f81a6qr13qnc Task Analysis in Document Writing] - notice how under "Narrative Writing" section in this example we show task analysis done with video recordings

= Template =
Goal of the Task

Steps of the Task (with screenshots)

Who performs what task (with what context and input)
[[Category:Requirements Engineering]]

Public:Training Burden on each layer in Sales AI

2025-07-21T03:17:43Z

Tushar Goswami: Tushar Goswami moved page Training Burden on each layer in Sales AI to Public:Training Burden on each layer in Sales AI

[[Category:Knowing.dev]]

=== Ref doc ===
<nowiki>https://smartercodes-my.sharepoint.com/:t:/g/personal/tushar_smarter_codes/EbkhuloPbwlDgW3veRbJ1yoBL9XSx_cFj839ZqGF2pI1nw?e=3mRmfv</nowiki>

=== About this Document ===
Sales AI is a unique Sales tool powered by AI to assist and guide Sales Persons at every stage of the client handling process. Since this whole process includes guiding the sales person with soft communicational and technical actionables in a LIVE call, the tool is to be trained accordingly. This document depicts the training burden on respective inhouse and client data to complete the aforementioned job.

=== Training Burden with analogies ===
{| class="wikitable"
|'''Level'''
|'''AI VA'''
|'''Human analogy'''
|'''is learning'''
|'''Ex Vocabulary for human'''
|-
|1st
|Talking DB
|High School
|General English terms
|Customer
|-
|2nd
|Sales AI
|Business School
|Sales
|Customer Segmentation
|-
|3rd
|AI consultancy
|Sum of all knowledge across all AI Agencies
|Industry Terms
|Computer Vision
|-
|4th
|Smarter.codes
|Smarter.Codes
|Company terms
|Computer Vision powered by RPA, TalkingDB, Pinecone.io
|}

=== Training burden in Kray.ai ===
{| class="wikitable"
|'''Level'''
|'''Responsible for Training'''
|'''Training Site'''
|'''AI is is learning What?'''
|'''Ex Vocabulary that AI learns'''
|-
|1st
|Talking DB
|High School
|General English terms
|above $100
|-
|2nd
|Kray.ai
|Business School
|Sales
|Comparing between two products
How to refer to Catalogs and answer Q&A
|-
|3rd
|Kray for Smartphones
|GSM Arena
|Industry Terms
|MP (megapixel), Screen size, Snapdragon Processor
|-
|4th
|MobileDukaan
|Mobile Dukaan Sales Team
|Company terms
|'''Series 30 Casters''' for Cemented Floors
|}

=== Explanation ===

* 1st level : Similar to a human learning general English Vocabulary in high school, Talking DB is tasked with supplying the basic communication vocabulary to the tool
* 2nd Level : Akin to learning business terms like Customer segmentation, churn rate etc., which a human would learn in a business school, Sales-AI imparts these skills in the tool
* 3rd Level : When the tool has learned the General English and Business terms, the onus of imparting industry specific terms falls on the client data. For Ex, The tool would be able to guide salespersons in Smarter Codes using SmarterCodes or industry specific terms like Computer Vision, RPA etc only once trained by Smarter Codes specific data
* 4th Level : While after learning Industry terms, the tool is more or less trained; there may be certain company specific terms which are to be trained by company data. For Ex. Computer Vision powered by RPA is a Unique capability pioneered by Smarter Codes and hence this would be trained by company data

Public:Training Burden on each layer in Sales AI

2025-07-18T08:20:34Z

Tushar Goswami:

Public:Video Script

2025-07-11T10:12:40Z

Tushar Goswami:

We've to create videos to educate customers and colleagues. Than shooting a video ad-hoc we plan it out. Much like you write down your plan in [[:en:Screenwriting|screenwriting]], we draft a video script. Think of this as a rough sketch before your final drawing. The video script once drafted must be sent for review to your peers and you ask them to give you feedback. Their feedback saves you time when recording videos because before recording anything you got feedback on what content actually should be sent for recording. Over the internet people every team has made their [[google:video+script|own format of Video scripts]]. Below we've listed some video script formats we use at Smarter.Codes

= Format of Video script =

== Case Study video script format ==
{| class="wikitable"
|+
!Section
!Step
!Time stamp range
!Verbal Script
!On the screen action
|-
|1. Summary of video
|1.1
|0:00 - 0:30
|Hi, in this video we would _____ and _____
|Intro Slide + Moving mouse on Para1, Para2
|-
|2. Problem Statement
|2.1
|0:30 - 0:45
|
|
|-
|
|2.2
|0:45 - 1:00
|
|
|}
Examples

* [https://beta.smarter.codes/our-project/real-estate-rpa-assisting-users-to-fill-out-long-forms/ Real Estate RPA Assisting Users to fill out long forms], and its [https://docs.google.com/document/d/1tIn_fTj9lnHMoxXQXmZMjP4mlvDQ6u-LI2cNk1QYbR4/edit accompanying script]
* [https://docs.google.com/document/d/1DxFfANl0EXODYF3poFGkQ74O00CwBkcNrpmfCLADa5M/edit?tab=t.0 SC Healthcare Clinical Doc Writing : Video Script Draft]

= After Video script =
You do [[Storyboarding]]
[[File:Public:Video-script-vs-storyboarding.png|left|thumb|900x900px|Video script vs Storyboarding]]

= Learning to write Video Script =
[https://www.udemy.com/course/storytelling-in-the-digital-age/ Learn Storytelling in 1hr]

[[Category:Content Writing Templates]]
[[Category:Video Making]]

Public:PoC Phase of AI Projects

2025-07-11T07:53:18Z

Tushar Goswami:

= When =
You need a Proof of Concept phase if what you're building with AI is still magical.<ref>[[:en:AI_effect|AI effect]] - what was magical before, becomes computational today</ref> But if you're building something for which tool stack and data-set stack is already confirmed (with enough proof already existing) you do not need PoC phase. You rather need a fixed price quote in that case<ref>[https://smartercodes-my.sharepoint.com/:v:/g/personal/tushar_smarter_codes/EatbfLioOl1JrE_V6XQhs2cBmM9sFm70uJK4PGjQ8UlXjA?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZy1MaW5rIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXcifX0%3D&e=bgrfwz Fixed Price quotes when Proof of Tools and Datasets are already there]</ref>

= What =
[[File:Human Demo in PoC Sheet.png|thumb|Human Demo column helps explain how a human does a certain task that AI must automate]]
When building an Artificial Intelligence Product, we first look into how Human Intelligence does the same job. AI is basically trying to emulate Human Intelligence. So we put together a spreadsheet called [https://docs.google.com/spreadsheets/d/1VFsd3g_TKa1the5i0Pa2tlX2ybuSBaUtyhAZhHzIA8g/edit#gid=0 Initial Viability + Prototyping of AI products]. Where we..

# Break down the human process into child tasks. Where hopefully each task gives output of an [[Artifact]]
# Against each task we list
## how valuable is that task for the human / automated process
## how much effort would AI team need to put to replicate that human process through AI
# Cherry pick a few human tasks. We sponsor building their AI Proof of Concept.

This process helps us in various ways

* Helps us list down real world Problems and Solutions in [[Lean Business Canvas]]
* Helps stakeholders build faith on what is possible with AI and what is not (based on how well AI was able to mimic human behavior in limited 200hrs of budget)

Learn more about how we do this process from

* [https://smartercodes-my.sharepoint.com/:v:/g/personal/tushar_smarter_codes/EbbyZL-q2oxIi4EZUcweWZsBp4uFUoYVxC3h3ucvP2WFvw?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZy1MaW5rIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXcifX0%3D&e=onfa1M Video about Proof of Concept phase]

* Example Viability phase spreadsheet : [https://docs.google.com/spreadsheets/d/1YCEJ6bNxe5DcQtfet4Yd0vkG54SHJ1JqFbOc13lRDUA/edit#gid=488227659 Initial Viability Of AI Course Writing]

* [https://smartercodes-my.sharepoint.com/:v:/g/personal/tushar_smarter_codes/EaPgN_sBycxIqeH39XSSDLEB6JEN5pgd1sVuJwWk0TKzow?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZy1MaW5rIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXcifX0%3D&e=5NNhIC Feedback on how the Viability Phase spreadsheet can be improved]

= See Also =
[[:en:Technology_readiness_level|Technological Readiness Level]]

[https://www.nature.com/articles/s41467-022-33128-9 Technology readiness levels for machine learning systems]

= References =
[[Category:AI Project Management]]
[[Category:Product Management Artifacts]]
<references />
[[Category:Sales Nurturing]]

Public:PoC Phase of AI Projects

2025-07-11T07:52:24Z

Tushar Goswami:

= When =
You need a Proof of Concept phase if what you're building with AI is still magical.<ref>[[:en:AI_effect|AI effect]] - what was magical before, becomes computational today</ref> But if you're building something for which tool stack and data-set stack is already confirmed (with enough proof already existing) you do not need PoC phase. You rather need a fixed price quote in that case<ref>[https://smartercodes-my.sharepoint.com/:v:/g/personal/tushar_smarter_codes/EatbfLioOl1JrE_V6XQhs2cBmM9sFm70uJK4PGjQ8UlXjA?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZy1MaW5rIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXcifX0%3D&e=bgrfwz Fixed Price quotes when Proof of Tools and Datasets are already there]</ref>

= What =
[[File:Human Demo in PoC Sheet.png|thumb|Human Demo column helps explain how a human does a certain task that AI must automate]]
When building an Artificial Intelligence Product, we first look into how Human Intelligence does the same job. AI is basically trying to emulate Human Intelligence. So we put together a spreadsheet called [https://docs.google.com/spreadsheets/d/1VFsd3g_TKa1the5i0Pa2tlX2ybuSBaUtyhAZhHzIA8g/edit#gid=0 Initial Viability + Prototyping of AI products]. Where we..

# Break down the human process into child tasks. Where hopefully each task gives output of an [[Artifact]]
# Against each task we list
## how valuable is that task for the human / automated process
## how much effort would AI team need to put to replicate that human process through AI
# Cherry pick a few human tasks. We sponsor building their AI Proof of Concept.

This process helps us in various ways

* Helps us list on real world Problems and Solutions in [[Lean Business Canvas]]
* Helps stakeholders build faith on what is possible with AI and what is not (based on how well AI was able to mimic human behavior in limited 200hrs of budget)

Learn more about how we do this process from

* [https://smartercodes-my.sharepoint.com/:v:/g/personal/tushar_smarter_codes/EbbyZL-q2oxIi4EZUcweWZsBp4uFUoYVxC3h3ucvP2WFvw?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZy1MaW5rIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXcifX0%3D&e=onfa1M Video about Proof of Concept phase]

* Example Viability phase spreadsheet : [https://docs.google.com/spreadsheets/d/1YCEJ6bNxe5DcQtfet4Yd0vkG54SHJ1JqFbOc13lRDUA/edit#gid=488227659 Initial Viability Of AI Course Writing]

* [https://smartercodes-my.sharepoint.com/:v:/g/personal/tushar_smarter_codes/EaPgN_sBycxIqeH39XSSDLEB6JEN5pgd1sVuJwWk0TKzow?nav=eyJyZWZlcnJhbEluZm8iOnsicmVmZXJyYWxBcHAiOiJTdHJlYW1XZWJBcHAiLCJyZWZlcnJhbFZpZXciOiJTaGFyZURpYWxvZy1MaW5rIiwicmVmZXJyYWxBcHBQbGF0Zm9ybSI6IldlYiIsInJlZmVycmFsTW9kZSI6InZpZXcifX0%3D&e=5NNhIC Feedback on how the Viability Phase spreadsheet can be improved]

= See Also =
[[:en:Technology_readiness_level|Technological Readiness Level]]

[https://www.nature.com/articles/s41467-022-33128-9 Technology readiness levels for machine learning systems]

= References =
[[Category:AI Project Management]]
[[Category:Product Management Artifacts]]
<references />
[[Category:Sales Nurturing]]