--- created: 2026-03-12 source: Rivet tags: [agent-archive, rivet] --- # RateRight Decision Log - 2026-02-15 This document captures all key product decisions made between Michael and Rivet regarding the RateRight platform development. --- ## 1. Onboarding Pack Approach **Decision Made:** Option C (Hybrid Template) selected **Context/Reasoning:** After evaluating three approaches (A: Static PDF, B: Dynamic Web Form, C: Hybrid Template), the hybrid approach was chosen for its balance of professionalism and flexibility. This approach allows for a branded, professional document that can be customized per contractor while maintaining consistency. **Date/Time:** 2026-02-15, Morning session **Implications for Implementation:** - Create modular template system with branded components - Allow contractors to customize sections (logo, colors, specific terms) - Maintain PDF export capability for offline sharing - Build template editor interface for future customization **Follow-up Needed:** - Design template components library - Create contractor customization interface - Test PDF generation and formatting --- ## 2. Data Storage Policy **Decision Made:** RateRight will NOT store sensitive personal information (TFN, bank details) **Context/Reasoning:** To minimize compliance burden and security risk, RateRight will not store Tax File Numbers or bank account details. This decision reduces regulatory requirements and potential liability while maintaining platform functionality. **Date/Time:** 2026-02-15, Morning session **Implications for Implementation:** - Remove TFN/bank fields from database schema - Update forms to exclude sensitive data collection - Create secure document generation that doesn't persist sensitive data - Update privacy policy and terms of service - Implement contractor responsibility for maintaining worker records **Follow-up Needed:** - Audit all forms for sensitive data fields - Update database schema and remove unnecessary tables/columns - Create contractor guidance on record-keeping obligations - Review all third-party integrations for data handling --- ## 3. QR Codes on Onboarding Pack **Decision Made:** QR codes will NOT be included on the onboarding pack **Context/Reasoning:** QR codes were considered for easy access to digital resources, but the decision was made to keep the pack clean and professional. Alternative methods of sharing digital resources will be used. **Date/Time:** 2026-02-15, Morning session **Implications for Implementation:** - Focus on clean, professional document design - Create alternative sharing methods (email links, portal access) - Ensure all digital resources are easily accessible via URL - Consider adding short, memorable URLs instead **Follow-up Needed:** - Design professional pack layout without QR code placeholders - Create email templates for sharing digital resources - Set up contractor portal for resource access --- ## 4. Branding Strategy **Decision Made:** Clickable link in footer with subtle marketing approach **Context/Reasoning:** Rather than aggressive branding throughout documents, a subtle approach was chosen with a simple clickable link in the footer. This maintains professionalism while still providing attribution and potential lead generation. **Date/Time:** 2026-02-15, Morning session **Implications for Implementation:** - Design minimal footer with RateRight branding - Ensure link is clickable in digital formats - Include subtle messaging about the platform - Maintain consistent branding across all templates **Follow-up Needed:** - Create footer design options - Test link functionality across different export formats - Write compelling but subtle marketing copy for footer --- ## 5. Contractor Admin Routing **Decision Made:** Admin email collection during signup for routing purposes **Context/Reasoning:** To properly route contractors to their appropriate admin/support team, admin email addresses will be collected during the signup process. This ensures contractors receive proper support and guidance. **Date/Time:** 2026-02-15, Afternoon session **Implications for Implementation:** - Add admin email field to contractor signup form - Create routing logic based on admin email domain - Build admin dashboard for managing assigned contractors - Implement notifications for admins when new contractors sign up **Follow-up Needed:** - Design signup flow with admin email collection - Create admin routing rules and logic - Build admin notification system - Test routing accuracy --- ## 6. Worker Path Options **Decision Made:** Dual path implementation - ABN vs TFN workers **Context/Reasoning:** To accommodate different worker types in the Australian market, the platform will support both ABN (Australian Business Number) holders and TFN (Tax File Number) workers. This provides flexibility for contractors and workers. **Date/Time:** 2026-02-15, Afternoon session **Implications for Implementation:** - Create separate onboarding flows for ABN vs TFN workers - Implement different document templates for each type - Build validation for ABN numbers - Create different payment tracking for each worker type - Ensure compliance requirements are met for both paths **Follow-up Needed:** - Research ABN validation requirements - Design dual-path onboarding UX - Create separate document templates - Implement ABN lookup/validation service --- ## 7. Pricing Validation **Decision Made:** $50 confirmed as optimal price point **Context/Reasoning:** After market analysis and competitive research, $50 was confirmed as the optimal price for the RateRight service. This price point balances affordability for contractors with sustainable revenue for the platform. **Date/Time:** 2026-02-15, Afternoon session **Implications for Implementation:** - Set pricing at $50 per contractor per month - Implement billing system with $50 base price - Create pricing page and marketing materials - Build subscription management features - Ensure pricing is clearly communicated throughout platform **Follow-up Needed:** - Implement billing system with $50 pricing - Create pricing page on website - Build subscription management dashboard - Test payment processing --- ## 8. Iterative Spec Process **Decision Made:** 4-step process established: Kimi → Rivet → Builder → Final **Context/Reasoning:** To ensure quality and accuracy in specifications, a four-step iterative process was established. Kimi agents handle initial research and drafting, Rivet reviews and refines, Builder implements, and final review ensures everything meets requirements. **Date/Time:** 2026-02-15, Throughout the day **Implications for Implementation:** - Establish clear handoff points between stages - Create templates for Kimi research outputs - Build review checkpoints for Rivet validation - Implement feedback loops for continuous improvement - Document the process for team consistency **Follow-up Needed:** - Create process documentation - Establish templates for each stage - Set up review checkpoints - Train team on new process --- ## 9. Text vs Voice Communication **Decision Made:** Michael prefers text replies (TOOLS.md updated) **Context/Reasoning:** To improve communication efficiency and respect preferences, it was established that Michael prefers text-based responses over voice replies. This was documented in TOOLS.md for all future interactions. **Date/Time:** 2026-02-15, Throughout the day **Implications for Implementation:** - Default to text-based responses - Use TTS only when specifically requested - Update all communication templates - Train voice systems to respect this preference **Follow-up Needed:** - Update all voice system defaults - Review and update communication templates - Ensure team is aware of preference --- ## 10. Payment Model **Decision Made:** RateRight doesn't process payments - contractor pays worker directly **Context/Reasoning:** To simplify the platform and avoid complex payment processing requirements, RateRight will not handle payments between contractors and workers. Contractors will pay workers directly, keeping RateRight focused on compliance and documentation. **Date/Time:** 2026-02-15, Afternoon session **Implications for Implementation:** - Remove payment processing features from roadmap - Focus on payment tracking and documentation - Create guidance for contractors on payment methods - Build invoice generation features (without processing) - Ensure platform doesn't handle financial transactions **Follow-up Needed:** - Update feature roadmap to remove payment processing - Create contractor guidance on payment methods - Build invoice generation system - Update terms of service regarding payments --- ## Summary Today's decisions have established a clear direction for RateRight development, focusing on: - Professional, compliant document generation - Minimal data storage to reduce compliance burden - Flexible pricing and worker management - Clear communication preferences - Streamlined feature set without payment processing These decisions will guide development priorities and ensure the platform meets both user needs and regulatory requirements.