I’m Chitrakannan (CK). Founder of Wisibl.I build products that make work easier by reducing friction teams have learned to live with.Right now, I’m exploring how AI can help product teams retain context across tools, conversations, and handoffs. Wisibl is my current experiment in solving that problem.Career highlights- Helped scale a company from $10M → $25M by bringing clarity across product, growth, and operations- Early employee at Ondot Systems, leading product and growth initiatives before its acquisition by Fiserv (2021)- Built 5 products from 0→1, several generating $1M+ in revenue- Started my career in QA, which permanently shaped how I think about quality, systems, and edge casesProducts &amp; experiments- ShaRead: A reader-matching engine built before micro-communities became fashionable- RentYourBag: A marketplace that turned unused luggage space into valueIf you want to discuss building, feel free to DM.

Chitrakannan Balasubramanian

How much of your day is spent actually building product? ⠀ 

Not documenting. Not answering "what did we decide about X?" for the fifth time this week. ⠀ 

Not digging through Slack threads and stale wiki pages. ⠀ 
Actually building. ⠀ 

If you are a PM, you would feel this. ⠀ 

PRDs are getting obsolete. Not because they are bad. 

But because by the time you finish writing one, half the decisions have already changed. ⠀ 

The real product knowledge lives in conversations. Sprint planning. Stakeholder reviews. Customer calls. Slack threads. ⠀ 

But none of it is captured. None of it is structured. None of it is searchable. ⠀ 

So you carry it all in your head. Every module. Every tradeoff. Every risk someone flagged three weeks ago. ⠀ 

That is not product management. That is memory management. ⠀ 

In the AI era, product teams should move as fast as they speak. 

Every conversation should compound into knowledge. Not disappear into a transcript nobody reads. ⠀ 

That is what Wisibl does. ⠀ 

Upload your meeting transcripts. Wisibl turns them into structured product knowledge. 

Organized by product area. Always up to date. ⠀ 

PRDs, user stories, context docs? Wisibl generates them from what your team has already discussed. ⠀ 

The beta is live. Watch the demo below. ⠀ 

If you want to integrate your notetakers, PM tools, or documentation tools, DM me :) ⠀ 

#ProductManagement #BuildInPublic #SaaS

Building Wisibl | 5 Products, 0→1 | Ex-Ondot (Acquired by Fiserv)

Sonata Software

Digital Architect

Encore Software Services, Inc.

Lead QA Analyst

Senior QA Analyst

QA Analyst

Shinelogics Infotech

Software Test Engineer

Leadership and Management:
•	Team Leadership: Lead and mentor a team of QA engineers, providing guidance and support.
•	Resource Management: Allocate resources effectively based on project requirements and timelines.
•	Collaboration: Foster collaboration between QA, development, and other cross-functional teams.
Strategy and Planning:
•	Test Strategy: Develop and implement a comprehensive test strategy for API testing.
•	Test Planning: Create detailed test plans outlining the scope, approach, resources, and schedule.
•	Risk Assessment: Identify potential risks and plan mitigation strategies.
Testing Process:
•	Test Case Design: Oversee the creation of detailed and effective test cases for API testing.
•	Automation: Drive the automation strategy for API testing to improve efficiency.
•	Execution and Monitoring: Oversee the execution of test cases and monitor test results.
•	Regression Testing: Ensure robust regression testing processes are in place.
Quality Assurance:
•	Quality Standards: Establish and enforce quality standards for API development and testing.
•	Defect Tracking: Implement effective defect tracking and management processes.
•	Root Cause Analysis: Lead investigations into the root causes of defects and issues.
Continuous Improvement:
•	Process Improvement: Identify areas for process improvement and implement changes.
•	Training and Development: Provide training and development opportunities for the QA team.
•	Best Practices: Promote and enforce best practices in API testing.
Documentation:
•	Documentation Standards: Define and enforce documentation standards for test cases, test plans, and other QA artifacts.
•	Knowledge Sharing: Encourage knowledge sharing within the QA team and with other relevant teams.
Performance Metrics:
•	Metrics Tracking: Define and track key performance metrics for the QA team.
•	Reporting: Generate regular reports on testing progress, defects, and overall product quality.

Very Strong Knowledge of API testing using POSTMAN and API Automation using NodeJS 
Strong Knowledge in Selenium web driver, SELENIUM IDE.
Strong in SDLC, STLC, and Bug Life Cycle.
Knowledge on Test Plan, Traceability Matrix.
Knowledge of writing, reviewing, executing Test Cases.
Very good knowledge on Functional, Integration, and System Testing.
Very good knowledge on Smoke, Regression, Compatibility and various other types of Testing.
Good knowledge in core Java.

taplio

The Battle

Chitrakannan Balasubramanian

Deepak R

Followers

Posts

Engagements

Likes

Performance ScoreChitrakannan Balasubramanian's LinkedIn Performance

Ready to grow your LinkedIn presence?

taplio

The Battle

Chitrakannan Balasubramanian

Deepak R

Followers

Posts

Engagements

Likes

Performance Score.css-goub6s{font-size:var(--chakra-fontSizes-md);font-weight:500;color:var(--chakra-colors-gray-600);display:block;margin-top:var(--chakra-space-1);}Chitrakannan Balasubramanian's LinkedIn Performance

Ready to grow your LinkedIn presence?

Performance ScoreChitrakannan Balasubramanian's LinkedIn Performance