Customer Success Team Requirements
FINVU_PRODUCT_PRINCIPLES
LOW_LATENCY = response time optimization across all touchpoints
LOW_COST = pricing efficiency (sales/negotiation dependent)
HIGH_SUCCESS_RATE = core differentiator (reliability focus)
SUCCESS_RATE_CONTRIBUTING_FACTORS
UX_QUALITY_IMPACT
CO_BUILT_JOURNEYS = custom client-specific user flows
SWEECAR_UI = finvu branded interface
MOBILE_SDKS = native app integration
JS_SDKS = web integration
POSTHOG_INTEGRATION = user journey tracking (recently deployed, testing phase)
FUTURE_ENHANCEMENT = otpless service integration (reduce friction)
API_AVAILABILITY_IMPACT
FINVU_UPTIME = 99.99% availability target
DISASTER_RECOVERY = GCP + OnPrem switching capability
MAINTENANCE_WINDOWS = planned downtime management
FIP_HEALTH_IMPACT
PRIMARY_SUCCESS_RATE_DRIVER = FIP functional uptime
CHALLENGE = FIPs not highly functionally available
MEASUREMENT_NEED = FIP-specific performance tracking
BUSINESS_JUSTIFICATION = success rate attribution to FIP vs AA issues
FUNNEL_HIERARCHY_MAPPING
OVERVIEW_FUNNEL (5_STAGE)
CI = Consents Initiated
CA = Consents Approved
CF = Consents Fulfilled (1st Successful Data Fetch)
DRI = Data Fetch Request Initiated
DRF = Data Fetch Request Fulfilled
DETAILED_FUNNEL (8_STAGE)
AA_client_Initialization → OTP_Based_Sign_in_Sign_up → View_Consent_Details → Discovery → Linking → Approved_Consent_Requests → Rejected_Consent_Requests → FIP_Accepted_Consent_Artefacts → FIP_Rejected_Consent_Artefacts → Data_Fetch_Success → Data_Fetch_Failed → Data_Fetch_Not_Attempted
MULTI_DIMENSIONAL_ANALYSIS_REQUIREMENTS
TSP_WISE = technical service provider segmentation
PURPOSE_CODE_WISE = 101,102,103,104,105 breakdown
FI_TYPE_WISE = deposit, mutual fund, insurance, etc breakdown
LICENSE_TYPE_WISE = SEBI, RBI, other regulatory categorization
FIU_WISE = client-specific performance
UNREGULATED_ENTITY_WISE = LSP (Loan Service Provider) tracking
USER_SEGMENTATION = new vs existing user performance comparison
USER_CLASSIFICATION_LOGIC
NEW_USERS = users with finvu handle created BUT no bank accounts linked (face full funnel)
EXISTING_USERS = users with at least one account already linked on finvu (abbreviated funnel)
CURRENT_UNIQUE_DEFINITION = unique mobile@finvu handle (acknowledged as imperfect)
ENHANCEMENT_REQUEST = both unique + non-unique user tracking capability
DRILL_DOWN_ANALYSIS_PATTERN
LEVEL_1_OVERVIEW_FUNNEL
TRIGGER = drop detected between CI & CA stages
ACTION = drill down to detailed 8-stage funnel
LEVEL_2_DETAILED_FUNNEL
TRIGGER = drop detected at specific stage (e.g., account discovery)
ACTION = drill down to standard categorization
LEVEL_3_CATEGORIZATION
CLASSIFICATION = [NO-RECORDS-FOUND | FAILED | SUCCESSFUL]
TRIGGER = high FAILED percentage
ACTION = drill down to API level analysis
LEVEL_4_API_LEVEL
ANALYSIS_UNIT = eventName (reference to event_pro documentation)
METRICS = HTTP response code distribution
TRIGGER = specific error patterns
ACTION = drill down to logs
LEVEL_5_LOG_ANALYSIS
GRANULARITY = individual failed transaction logs
PURPOSE = root cause identification + hypothesis creation
OUTCOME = actionable insights for FIP/FIU/internal fixes
DATA_ARCHITECTURE_CONSIDERATIONS
CUSTOMER_IDENTITY_ENHANCEMENT
MASKED_ACCOUNT_NUMBERS = available but not currently extracted/stored
COMPLIANCE_STATUS = data blind company requirement maintained
DEDUPLICATION_OPPORTUNITY = use masked account numbers for better unique user identification
UX_TRACKING_ARCHITECTURE
CURRENT_SETUP = PostHog for user journey tracking (SDKs integration)
OPEN_QUESTION = ClickHouse for server events vs PostHog for user journey separation
INTEGRATION_REQUIREMENT = easy navigation between server events + user journey data
DASHBOARD_STATUS = PostHog dashboards still being built/tested
ANALYTICAL_PRIORITIES
DROP_OFF_REDUCTION = primary focus for customer success
FIP_PERFORMANCE_ATTRIBUTION = separate FIP issues from AA issues
ROOT_CAUSE_ANALYSIS = systematic drill-down from high-level metrics to specific logs
HYPOTHESIS_GENERATION = data-driven insights for operational improvements