Google-Native AI Wellness Discovery MVP
Publicada el 2026-07-20
Descripción de la oferta
Project Title: Citta Companion — Google-Native AI Wellbeing Discovery MVP Project Overview: Citta India is building Citta Companion, a lean Google-native AI wellbeing discovery MVP for employer-funded organisational wellbeing pilots. It should allow employees to register with consent, receive a personalised chatbot link, complete an AI-assisted wellbeing discovery conversation, be classified into wellbeing/risk categories, trigger admin alerts where needed, and generate de-identified employer reporting. Preferred Stack: Google Forms, Google Sheets, Make.com, Google Apps Script where required, Streamlit, Gemini API, Google Cloud Platform, Gmail API, and simple landing page/payment-readiness sections. Ownership: All assets must be created under, or transferred to, the dedicated Citta India Google account. Citta must own all forms, sheets, prompts, automations, source files, deployment access, API setup, reporting templates, website sections, payment-readiness pages, and data. Commercial Requirement: Citta operates on advance payment. No employer pilot, employee onboarding, AI access, reporting, workshop, retainer service, or individual support pathway should begin until payment is received and confirmed. Full Razorpay live integration is not required now. However, the landing page/website must be Razorpay-ready with pricing, policy, contact, refund/cancellation and payment-placeholder sections so Razorpay can be connected later after banking and KYC/KYB are completed. Not Included: Full CRM, EMR, Eka integration, employer portal, real-time dashboard, mobile app, live Razorpay checkout, recurring billing, Firebase Auth, Supabase, full employee login, complex multilingual support, private therapy funnel, automated diagnostic engine, or large chatbot library. Milestone 1: Google Environment, Employee Registration, Landing Page Structure and Automation Set up the dedicated Citta-owned Google environment, Google Cloud project, Gemini API, billing alerts, Google Form, Google Sheets registry and Make.com workflow. The employee registration form should collect preferred name, personal email, optional work email/phone, organisation, department/work type, sector, language preference, consent, privacy acknowledgement, disclaimer acknowledgement and further wellbeing support opt-in. The Make workflow should generate a unique employee ID, create a personalised chatbot URL using limited parameters such as employee ID, sector and language, email the onboarding link to the employee, notify Citta admin, and maintain registry/activity logs. Also prepare the employer-facing landing/service structure for Citta Companion, including service positioning, advance-payment wording, Pricing and Services, Privacy Policy, Terms of Service, Refund and Cancellation Policy, Contact Us, and future Razorpay payment placeholders. Acceptance: A test employee can complete the form, receive a unique ID and personalised chatbot link, and appear correctly in the registry. Citta admin receives notification. The landing/service structure includes pricing, policy, advance-payment and payment-readiness sections. Citta has admin access to all assets. Milestone 2: AI Companion, Gemini Integration, Risk Classification, Admin Alerts and Reporting Structure Deploy or update the Streamlit chatbot and connect it to Gemini API. The chatbot must read employee ID, sector and language from the URL. The chatbot must state that it is not therapy, diagnosis or an emergency service, and that employers will not receive individual employee responses. The chatbot should conduct structured wellbeing discovery across general wellbeing, stress, burnout, sleep/fatigue, workplace pressure, manager/team stress, coping, emotional regulation, workplace conflict/psychological safety, and request for human support. Create a refined Gemini prompt and structured output including risk level, major themes, human support requested and intake trigger. Risk categories: Green, Yellow, Amber, Red and Crisis. Add deterministic crisis keyword override. If crisis/high-risk terms appear, the system must force Crisis classification, display emergency guidance, trigger admin alert and log the event. Create Google Sheet tabs for employee registry, form responses, chat/session summaries, risk flags, support leads, executive reporting and admin review. Configure admin alerts for new onboarding, support requests, amber/red/crisis risk and further wellbeing support opt-in. Acceptance: Chatbot is live and functional. Gemini responds correctly. Sessions link to employee ID. Risk category and structured summary are captured. Crisis override works. Admin alert triggers for high-risk test. Session summary writes to Sheets. Employer-facing reporting excludes personal identifiers. Milestone 3: Testing, Executive Reporting, Payment Readiness, Documentation and Handover Test normal, stressed, burnout, sarcastic, incomplete, empty, contradictory, crisis and human-support-request scenarios. Refine prompts and validate risk classification, crisis override, Make automation, alerts and partial/duplicate submission handling where practical. Create a de-identified executive reporting sheet showing total participants, department/sector participation where anonymity is protected, risk distribution, key wellbeing themes, burnout indicators, percentage requesting support, suggested interventions and recommended Citta pathways. Employer-facing reports must exclude names, emails, phone numbers, individual answers, chat transcripts, diagnosis, medical history, therapy notes and identifiable risk data. Finalise payment-readiness sections: advance-payment rule, B2B pilot payment structure, retainer structure, future B2C support placeholder, payment success/failure placeholders, refund/cancellation policy, terms/privacy pages and contact page placeholders. Document where future Razorpay payment links, buttons or checkout code should be inserted after Citta completes banking and Razorpay KYC/KYB. Final handover must include access/documentation for Google Forms, Sheets, Make, Streamlit, Gemini API, billing alerts, source files/code where applicable, prompts, risk keyword list, operating guide, data flow, report instructions, Razorpay future notes, policy page locations, limitations and future recommendations. Acceptance: MVP is tested end-to-end. De-identified report works. No personally identifiable information appears in employer reports. Payment-readiness and policy sections are editable. Advance-payment rule is visible. Citta has full admin access. Handover is complete. Citta can operate the MVP without daily developer dependency. Confidentiality: The developer must not copy, reuse, disclose, retain or transfer Citta data, prompts, employee records, chatbot logs, forms, reporting templates, policy drafts, payment structures or automations outside the approved Citta environment. Expected Outcome: Citta receives a working Google-native MVP that can onboard employees, generate unique IDs, send chatbot links, run AI wellbeing discovery, classify risk/need levels, alert Citta for support needs, store structured summaries, produce de-identified employer reporting, identify consent-based support leads, and remain ready for future Razorpay setup and platform expansion.
Skills
Fuente original: freelancer