Skip to content

CodeSlick Beta Tester Manual

Program Duration: November 18 - December 31, 2025 (6 weeks) Beta Spots: 10 teams maximum Beta Offer: 4 weeks FREE + 3 months at 50% off (€49/month instead of €99/month) Total Benefit: ~4 months of discounted/free service Version: 1.1 (CORRECTED) Last Updated: November 12, 2025

🎯 Program Overview

Welcome to the CodeSlick Beta Program! As a beta tester, you're not just getting early access—you're helping shape the future of GitHub security analysis. Your feedback will directly influence our product roadmap, and you'll receive exclusive benefits in return.

What You'll Get: - 4 weeks completely FREE (beta testing period) - Then 50% discount for 3 months (€49/month instead of €99/month) - Total benefit: ~4 months of discounted/free service - Priority support (responses within 24 hours) - Direct input on product roadmap - Early access to new features - Your company featured as "Early Supporter" (with permission) - Lifetime recognition as founding customer

What We Ask: - Use CodeSlick on at least 5 PRs per week - Report bugs and issues promptly - Provide honest feedback (good and bad) - Participate in 2-3 short feedback calls - Be patient with occasional bugs (it's beta!)

📋 Table of Contents

  1. Welcome Message
  2. Getting Started
  3. Requirements Checklist
  4. Feedback & Bug Reporting
  5. Support Channels
  6. Feedback Response Process
  7. Implementation & Updates
  8. Troubleshooting Guide
  9. End of Beta Period
  10. Beta Success Metrics
  11. Legal & Privacy
  12. FAQ

💌 a) Welcome Message

Subject: Welcome to CodeSlick Beta - Let's Make GitHub Security Easy!

Hi [First Name],

Welcome to the CodeSlick Beta Program! 🎉

I'm Vitor, the founder of CodeSlick. Thank you for being one of our first 10 beta testers. Your willingness to try a new product means the world to me, and I'm committed to making this a valuable experience for you.

What CodeSlick Does: CodeSlick automatically analyzes every GitHub pull request for security vulnerabilities (SQL injection, XSS, hardcoded secrets, etc.), dependency vulnerabilities, and API security issues. Results appear as PR comments—making security visible to your entire team.

Your Beta Offer: As a beta tester, you get: - 4 weeks completely FREE (the entire beta testing period - no payment required) - Then 50% off for 3 months (€49/month instead of €99/month) - Total: ~4 months of discounted/free service

The free period covers the beta testing phase (Nov 18 - Dec 31, 2025). After that, if you choose to continue, you'll pay €49/month for 3 months. After those 3 months (around April 2026), pricing returns to €99/month (you can cancel anytime).

What Happens Next: 1. Today: I'll send you installation instructions 2. This Week: You'll install CodeSlick on your GitHub repos 3. Week 1-2: You'll test on 5-10 PRs and share initial feedback 4. Week 3-4: I'll implement your top requested features 5. Week 5-6: Final polish based on your feedback 6. End of Beta: You decide if you want to continue (I hope you do!)

My Commitment to You: - I'll respond to all questions within 24 hours (usually much faster) - I'll fix critical bugs within 48 hours - I'll implement your top feature requests within 2 weeks - I'll never charge you without explicit confirmation

Let's Get Started: Reply to this email with: 1. Your GitHub organization name (the one you'll install CodeSlick on) 2. How many developers on your team? (1-5 for Team plan) 3. What programming languages do you use? (JavaScript, Python, Java, TypeScript) 4. Any specific security concerns? (optional)

I'm here to help. If you have any questions, just reply to this email or message me on [preferred channel - Slack/WhatsApp/etc].

Let's build something great together!

Vitor Lourenço Founder, CodeSlick Email: [your-email] Calendar: [Calendly link for 15-min calls]

P.S. - Your honest feedback is the most valuable thing you can give me. If something doesn't work or feels confusing, tell me immediately. That's how we improve! 🚀

🚀 b) Getting Started - Step-by-Step Instructions

Step 1: Verify Your Beta Status (Founder Task)

Before sending welcome email, you must:

  1. Mark team as beta tester in database: 

    UPDATE teams
SET
  beta_tester = true,
  beta_discount_ends_at = '2026-03-31 23:59:59', -- 3 months after beta end
  beta_discount_rate = 50
WHERE id = '[TEAM_UUID]';

  2. Verify in database: 

    SELECT id, name, beta_tester, beta_discount_ends_at, beta_discount_rate
FROM teams
WHERE id = '[TEAM_UUID]';

  3. Test checkout flow (optional but recommended):

  4. Log in as test user on that team
  5. Go to Settings → Billing
  6. Click "Upgrade to Team Plan"
  7. Verify it shows €49.50/month (not €99)
  8. DO NOT complete checkout (cancel before payment)

Step 2: Beta Tester Creates Account

Instructions for Beta Tester:

  1. Go to: https://codeslick.dev

  2. Click: "Sign In with GitHub" (top right)

  3. Authorize: Allow CodeSlick to access your GitHub account

  4. We only request minimal permissions (read repos, write PR comments)

  5. We never access your code directly (only analyze on-demand)

  6. Select Organization: Choose the GitHub org you want to protect

  7. If you have multiple orgs, pick your most active one

  8. You can add more orgs later

  9. Install GitHub App:

  10. You'll be redirected to GitHub
  11. Review permissions (we explain what each one does)
  12. Click "Install & Authorize"
  13. Select repositories: "All repositories" OR "Only select repositories"

Recommended: Start with 1-2 repositories for testing, expand later

  1. Create Team (automatic):
  2. CodeSlick automatically creates a team for your organization
  3. You're added as the team owner

  4. You can invite colleagues later

  5. Verify Installation:

  6. You should see "GitHub App Installed ✅" on your dashboard
  7. You should see your selected repositories listed
  8. Status should show "Active"

Time to Complete: 5-10 minutes

Step 3: Test Your First PR

Instructions for Beta Tester:

  1. Open any PR in your selected repositories
  2. New PR or existing PR (we analyze on-demand)

  3. Make sure PR has code in JavaScript, Python, Java, or TypeScript

  4. CodeSlick Analyzes Automatically:

  5. Within 5-10 seconds, you'll see a comment from CodeSlick bot

  6. Comment shows all security issues found (or "No issues found ✅")

  7. Review Results:

  8. Issues are grouped by severity (CRITICAL, HIGH, MEDIUM, LOW)
  9. Each issue shows: file name, line number, description, fix suggestion

  10. OWASP Top 10 mapping included

  11. Expected Behavior:

  12. ✅ Comment appears within 10 seconds
  13. ✅ Results are accurate (not too many false positives)
  14. ✅ Formatting is readable and professional

If This Works: You're all set! Continue using CodeSlick on all PRs.

If This Doesn't Work: See Troubleshooting Guide or contact me immediately.

Step 4: Invite Team Members (Optional)

Instructions for Beta Tester:

  1. Go to: Dashboard → Settings → Team Members

  2. Click: "Invite Member"

  3. Enter Email: Colleague's email address

  4. Select Role:

  5. Owner: Full access (billing, settings, members)
  6. Admin: Manage repositories and settings (no billing access)

  7. Member: View results only

  8. Send Invitation: They'll receive email with invitation link

Note: All team members covered under your Team plan (up to 5 members).

Step 5: Upgrade to Paid (When Ready)

Instructions for Beta Tester:

  1. Go to: Dashboard → Settings → Billing

  2. Click: "Upgrade to Team Plan"

  3. Verify Pricing:

  4. You should see €49.50/month (50% beta discount)
  5. Regular price €99/month shown with strikethrough

  6. Discount valid until [DATE]

  7. Enter Payment Info:

  8. Credit card (Stripe secure checkout)

  9. Billing address

  10. Confirm: Click "Subscribe"

  11. Confirmation:

  12. You'll receive email receipt
  13. Dashboard shows "Team Plan - Active"
  14. Unlimited PR analyses enabled

Beta Discount Note: Your 50% discount lasts for 3 months from first payment. After 3 months, you'll be charged €99/month (you can cancel anytime before then).

✅ c) Requirements Checklist

Beta Tester Requirements (Your Responsibility)

Before Starting: - [ ] GitHub organization with repos (not personal account) - [ ] At least 1 repository with active development - [ ] Code in supported languages (JavaScript, Python, Java, TypeScript) - [ ] GitHub admin access (to install GitHub App) - [ ] Credit card for paid upgrade (after testing free features)

During Beta: - [ ] Test CodeSlick on at least 5 PRs per week - [ ] Report any bugs within 24 hours of discovery - [ ] Provide feedback via survey (sent weekly) - [ ] Respond to my emails/messages within 48 hours - [ ] Attend 1-2 short feedback calls (15 minutes each) - [ ] Upgrade to paid within first 2 weeks (to test full flow)

Technical Setup: - [ ] GitHub organization (not personal account) - [ ] Active PRs (at least 2-3 per week) - [ ] Team size: 1-5 developers (Team plan limit) - [ ] Repositories: 1-5 repos (Team plan limit)

Communication: - [ ] Check email daily (my primary communication channel) - [ ] Respond to feedback requests within 48 hours - [ ] Be honest (I need to hear the bad stuff too!)

Founder Requirements (My Responsibility)

Before Onboarding: - [ ] Mark team as beta tester in database - [ ] Verify beta discount applies correctly (€49.50) - [ ] Test GitHub App installation flow - [ ] Prepare welcome email with personalized details - [ ] Create team's dashboard account (auto or manual)

During Beta: - [ ] Respond to all messages within 24 hours (goal: 2-4 hours) - [ ] Fix critical bugs within 48 hours - [ ] Fix high-priority bugs within 1 week - [ ] Implement top feature requests within 2 weeks - [ ] Send weekly check-in email ("How's it going?") - [ ] Schedule 15-min feedback calls (Week 2 and Week 4) - [ ] Monitor usage metrics (are they actually using it?) - [ ] Proactive outreach if usage drops

Support Infrastructure: - [ ] Email support (primary channel) - [ ] Slack/WhatsApp for urgent issues (optional) - [ ] Calendly link for scheduled calls - [ ] Bug tracking system (GitHub Issues or Notion) - [ ] Feedback database (spreadsheet or Notion)

Technical Monitoring: - [ ] Monitor error logs (Sentry or similar) - [ ] Track analysis times (alert if >5s) - [ ] Monitor GitHub webhook deliveries - [ ] Check Stripe subscription status - [ ] Database backup before any schema changes

🐛 d) Feedback & Bug Reporting Process

How Beta Testers Should Report Issues

1. Bug Reports

Use This Template (send via email or GitHub Issue):

**Bug Title**: [Short description]

**Severity**:
- [ ] Critical (can't use product)
- [ ] High (major feature broken)
- [ ] Medium (annoying but workaround exists)
- [ ] Low (minor cosmetic issue)

**What Happened**:
[Describe what went wrong]

**Expected Behavior**:
[What should have happened]

**Steps to Reproduce**:
1. Go to...
2. Click on...
3. See error...

**Screenshots/Logs**:
[Attach screenshots or error messages]

**Environment**:
- Browser: [Chrome/Safari/Firefox]
- Repository: [link to repo if public, or name if private]
- PR: [link to PR if relevant]
- Date/Time: [when did this happen]

**Impact**:
[How is this affecting your team?]

Where to Send: - Email: [your-email] with subject "BUG: [short description]" - GitHub Issues: [link to issues page] (if public repo) - Slack (if urgent): [your Slack channel]

Response Time SLA: - Critical: I'll respond within 2 hours, fix within 24 hours - High: I'll respond within 4 hours, fix within 48 hours - Medium: I'll respond within 24 hours, fix within 1 week - Low: I'll respond within 48 hours, fix when capacity allows

2. Feature Requests / Suggestions

Use This Template:

**Feature Request**: [Short title]

**Problem**:
[What problem does this solve?]

**Proposed Solution**:
[How would you like it to work?]

**Use Case**:
[How would your team use this?]

**Priority** (your perspective):
- [ ] Must-have (blocking our adoption)
- [ ] Should-have (would use daily)
- [ ] Nice-to-have (occasional use)

**Alternatives**:
[Are there workarounds? How do you currently solve this?]

**Willingness to Pay**:
[Would this make you upgrade to Enterprise tier?]

Where to Send: - Email: [your-email] with subject "FEATURE: [short description]" - Feedback Survey: [link to weekly survey]

Response Process: 1. I'll acknowledge within 24 hours 2. I'll ask clarifying questions if needed 3. I'll prioritize (P0/P1/P2/P3) 4. I'll share timeline (this week, next sprint, backlog) 5. I'll update you when implemented

3. General Feedback / UX Improvements

Use This Template:

**Area**: [Dashboard, PR Comments, Settings, etc.]

**What's Confusing/Annoying**:
[Be brutally honest!]

**Suggestion**:
[How would you improve it?]

**Frequency**:
[Does this bother you daily, weekly, or rarely?]

Where to Send: - Weekly Feedback Survey: [link - sent every Friday] - Email: [your-email] with subject "FEEDBACK: [area]" - 15-Min Call: [Calendly link] - let's discuss!

📊 Weekly Feedback Survey

Sent Every Friday at 5 PM

Questions (5 minutes to complete):

  1. How many PRs did you analyze this week? [Number]

  2. Were the results accurate?

  3. Yes, very accurate (few false positives)
  4. Mostly accurate (some false positives)

  5. Too many false positives (annoying)

  6. Analysis speed?

  7. Fast (<5 seconds)
  8. Acceptable (5-10 seconds)

  9. Too slow (>10 seconds)

  10. Did you find any bugs this week?

  11. No bugs
  12. Minor bugs (already reported)

  13. Major bugs (will report separately)

  14. What's the #1 thing that would make CodeSlick more useful? [Open text]

  15. How likely are you to continue using CodeSlick after beta?

  16. Definitely (already getting value)
  17. Probably (needs some improvements)
  18. Maybe (significant concerns)

  19. Unlikely (not meeting needs)

  20. Net Promoter Score: How likely are you to recommend CodeSlick to a colleague? [0-10 scale]

  21. Anything else? [Open text]

💬 e) Response Process (Founder Side)

My Communication Commitments

Response Time SLAs:

Channel First Response Resolution
Critical Bug 2 hours 24 hours
High Bug 4 hours 48 hours
Medium Bug 24 hours 1 week
Low Bug 48 hours Backlog
Feature Request 24 hours 2-4 weeks (if accepted)
General Question 4 hours Same day
Feedback Survey 48 hours N/A

My Availability: - Email: Monday-Friday, 9 AM - 7 PM (Lisbon time) - Emergency Slack: 24/7 (critical bugs only) - Calls: By appointment (Calendly)

Weekends: I'll check email Saturday morning. True emergencies only (production down, security issue, payment problem).

Response Templates (Internal Use)

Template 1: Bug Acknowledged

Hi [Name],

Thanks for reporting this! I've logged it as [BUG-001] and marked it as [severity].

**My Understanding**:
[Paraphrase the issue to confirm I understood correctly]

**Next Steps**:
1. I'll investigate today
2. I'll send you an update by [time/date]
3. Expected fix: [timeline]

**Workaround** (if available):
[Temporary solution if one exists]

If this is blocking your team, let me know and I'll prioritize it higher.

Vitor

Template 2: Feature Request Acknowledged

Hi [Name],

Great suggestion! I really like this idea because [specific reason].

**Priority Assessment**:
- **My Priority**: [P0/P1/P2/P3]
- **Reasoning**: [why this priority]
- **Timeline**: [this week / next sprint / Q1 2026 / backlog]

**Questions**:
[Any clarifying questions]

I'll keep you updated on progress. If I decide not to build this, I'll explain why.

Thanks for the feedback!

Vitor

Template 3: Weekly Check-In

Subject: Week [X] Check-In - How's CodeSlick Working?

Hi [Name],

Quick check-in on your CodeSlick experience this week:

**What I See** (from usage metrics):
- PRs analyzed: [number]
- Issues found: [number]
- Last active: [date]

**Questions**:
1. Is CodeSlick providing value? What's working well?
2. Any frustrations or blockers?
3. Anything I should prioritize?

**This Week's Updates**:
- [New feature or bug fix]
- [Another update]

Let's schedule a quick call if you have 15 minutes: [Calendly link]

Vitor

Template 4: Feature Shipped

Subject: ✅ Your Feature Request is Live!

Hi [Name],

Remember when you suggested [feature]? It's live!

**What Changed**:
[Description of implementation]

**How to Use It**:
1. [Step 1]
2. [Step 2]

**Try It Out**:
[Link or instructions]

Let me know what you think. If it's not quite what you envisioned, I'm happy to iterate.

Thanks for the great idea!

Vitor

🔄 f) Validation & Implementation Process

How I Prioritize Feedback

Priority Framework:

P0 - Critical (Fix Immediately): - Product is broken (can't analyze PRs) - Security vulnerability - Payment processing broken - Data loss or corruption - Timeline: Fix within 24 hours

P1 - High Priority (This Sprint): - Major feature broken (dependency scanning fails) - High user impact (affects daily workflow) - Multiple users report same issue - Blocking beta success - Timeline: Fix within 1 week

P2 - Medium Priority (Next Sprint): - Minor feature broken (export report fails) - Moderate user impact (affects weekly workflow) - One user reports, but valid use case - Quality-of-life improvement - Timeline: Fix within 2-4 weeks

P3 - Low Priority (Backlog): - Cosmetic issue - Edge case (rarely happens) - Nice-to-have, not must-have - Future roadmap item - Timeline: When capacity allows

Feature Request Evaluation

I Will Build It If: - 3+ beta testers request it (high demand) - Solves a real pain point (not just "nice to have") - Aligns with product vision (security focus) - Can be built in <1 week (quick win) - Doesn't add complexity (keeps product simple)

I Won't Build It If: - Only 1 user wants it (too niche) - Doesn't fit product vision (out of scope) - Would take >1 month (post-beta feature) - Adds significant complexity (confuses users) - Better solved with integration (not core feature)

I'll Be Honest: If I decide not to build something, I'll explain why and suggest alternatives.

Implementation Workflow

1. Prioritize (Daily): - Review all feedback from past 24 hours - Categorize: Bug vs Feature vs Feedback - Assign priority: P0/P1/P2/P3 - Add to Notion board or GitHub Issues

2. Plan (Weekly): - Review P0 and P1 items - Estimate effort (S/M/L/XL) - Plan sprint (what can I ship this week?) - Communicate plan to beta testers

3. Build (Daily): - Fix bugs first, features second - Write tests alongside code - Update documentation - Test in production before announcing

4. Ship (When Ready): - Deploy to production - Email beta testers who requested it - Update changelog - Ask for feedback on implementation

5. Follow-Up (Within 48 hours): - Did it solve the problem? - Any issues with the implementation? - What should I improve?

Beta Tester Feedback Loop

Weekly Cycle:

Friday: Send feedback survey Weekend: Review responses, prioritize Monday: Email update: "Here's what I'm working on this week" Tuesday-Thursday: Build and ship Friday: Email update: "Here's what shipped this week"

Bi-Weekly Calls (15 minutes): - Week 2: "How's it going? What should I prioritize?" - Week 4: "What would make this a must-have for you?" - Week 6: "Will you continue after beta? What's missing?"

🆘 g) User Support & Troubleshooting

Common Issues & Solutions

Issue 1: "GitHub App Not Analyzing My PRs"

Symptoms: - Open PR, no comment from CodeSlick - Comment takes >2 minutes - Error message in PR comment

Troubleshooting Steps:

  1. Check GitHub App Installation:
  2. Go to: https://github.com/settings/installations
  3. Find "CodeSlick"
  4. Verify it's installed on the correct organization

  5. Verify repository is included (not excluded)

  6. Check Webhook Delivery:

  7. Go to: GitHub Settings → Webhooks
  8. Find CodeSlick webhook
  9. Check recent deliveries (should see "200 OK")

  10. If "404" or "500", contact me immediately

  11. Check Repository Language:

  12. CodeSlick only supports: JavaScript, TypeScript, Python, Java
  13. Go, Rust, C++, etc. not supported yet

  14. If unsupported language, PR won't be analyzed

  15. Check PR Size:

  16. Very large PRs (>100 files) may timeout

  17. Try smaller PRs first

  18. Still Not Working?:

  19. Email me with PR link
  20. I'll investigate logs and fix

Issue 2: "Too Many False Positives"

Symptoms: - CodeSlick reports issues that aren't real vulnerabilities - Results include noise

Troubleshooting Steps:

  1. Review Reported Issue:
  2. Is it a false positive or a real issue you disagree with?

  3. Example: "SQL injection" flagged but using parameterized queries

  4. Report to Me:

  5. Email with PR link
  6. Explain why it's a false positive

  7. I'll adjust detection rules

  8. Temporary Workaround:

  9. Ignore low-priority issues (focus on CRITICAL/HIGH)
  10. I'll improve accuracy based on your feedback

Issue 3: "Checkout Shows €99 Instead of €49"

Symptoms: - Beta discount not applied - Stripe checkout shows full price

This Is a Critical Bug - Contact Me Immediately: - Email: [your-email] with subject "URGENT: Beta Discount Not Applied" - Include: Team name, screenshot of checkout page - I'll fix within 2 hours

Do NOT complete checkout until I verify discount is applied.

Issue 4: "I Can't Invite Team Members"

Symptoms: - "Invite Member" button not working - Invitation emails not sending

Troubleshooting Steps:

  1. Check Team Plan:
  2. Free plan: No team member invitations (solo only)

  3. Team plan: Up to 5 members

  4. Check Email:

  5. Invitation might be in spam folder

  6. Resend invitation after checking spam

  7. Still Not Working?:

  8. Email me with:
    • Team name
    • Email you're trying to invite
    • Error message (if any)

Issue 5: "Analysis Is Too Slow"

Symptoms: - PR analysis takes >10 seconds - Sometimes times out

Troubleshooting Steps:

  1. Check PR Size:
  2. Large PRs (>50 files) take longer

  3. Expected: 2-5s for small PRs, 10-15s for large PRs

  4. Check Language:

  5. Python analysis slightly slower than JavaScript

  6. Still should be <10s

  7. Report to Me:

  8. If consistently >10s, email me with:
    • PR link (if public)
    • Repository size (number of files)
    • I'll investigate performance

Emergency Support Scenarios

Scenario 1: Production Outage

Definition: CodeSlick is down, no PRs being analyzed

What To Do: 1. Check status page: [link to status page if you have one] 2. Email me: "URGENT: Production Down" 3. I'll respond within 2 hours (24/7)

My Response: - Acknowledge immediately - Investigate and fix within 4 hours - Post-mortem within 24 hours

Scenario 2: Security Vulnerability

Definition: You discover a security issue in CodeSlick

What To Do: 1. Email me: "SECURITY: [brief description]" 2. DO NOT post publicly (GitHub Issues, Twitter, etc.) 3. I'll respond within 2 hours (24/7)

My Response: - Acknowledge immediately - Fix within 24 hours - Credit you in security advisory (if you want)

Scenario 3: Incorrect Charge

Definition: You were charged wrong amount or unexpected charge

What To Do: 1. Email me: "BILLING: [issue]" 2. Include: Charge amount, date, Stripe receipt 3. I'll respond within 4 hours

My Response: - Investigate within 4 hours - Issue refund within 24 hours (if error on my side) - Prevent future occurrences

Proactive Support (My Side)

I Will Reach Out If:

  1. Usage Drops:
  2. You were analyzing 10 PRs/week, now 0

  3. "Hey, I noticed you stopped using CodeSlick. What happened?"

  4. Errors Increase:

  5. Your team is getting errors frequently

  6. "I see errors in your account. Let me investigate."

  7. No Feedback:

  8. You haven't responded to surveys for 2 weeks

  9. "Just checking in - is everything okay?"

  10. Approaching Quota:

  11. Free plan approaching 20 analyses/month
  12. "Heads up - you're close to quota. Want to upgrade?"

I Won't Wait for You to Report Issues - I'll monitor proactively and reach out.

⏰ h) End of Beta Period

Timeline & Transition Plan

Beta Period: November 18 - December 31, 2025 (6 weeks)

Key Dates:

Date Event Action Required
Dec 15 Beta End Notification I'll email: "Beta ends Dec 31"
Dec 20 Pricing Reminder I'll remind you about 50% discount
Dec 25 Final Check-In I'll ask: "Will you continue?"
Dec 31 Beta Ends Your discount continues for 3 months
Jan 1 Public Launch CodeSlick officially launches
Mar 31 Discount Ends Pricing returns to €99/month (you can cancel anytime)

What Happens December 15 (2 Weeks Before Beta Ends)

Email You'll Receive:

Subject: CodeSlick Beta Ending Dec 31 - What's Next?

Hi [Name],

Our 6-week beta ends on December 31. Thank you for being one of our first 10 customers!

**Your Beta Discount**:
Your 50% discount (€49/month) continues for 3 MORE MONTHS after beta ends:
- Jan-Mar 2026: €49/month (50% off)
- Apr 2026 onwards: €99/month (full price)

You can cancel anytime before March 31 with no penalty.

**What Changes on Jan 1**:
- ✅ Nothing! CodeSlick keeps working exactly as before
- ✅ Your discount continues (3 more months)
- ✅ Priority support continues (you're a founding customer)
- ✅ Early access to new features continues

**What I Need From You**:
1. **Continue/Cancel Decision**: Let me know by Dec 20 if you want to continue
2. **Final Feedback**: 30-min call to discuss your experience (I'll buy you coffee ☕)
3. **Testimonial** (optional): If you're happy, I'd love a testimonial

**Will You Continue?**
Reply with:
- [ ] Yes, I'm continuing (very happy!)
- [ ] Yes, but I need [X] feature first
- [ ] Maybe, let's discuss
- [ ] No, here's why: [reason]

Let's schedule a final feedback call: [Calendly link]

Thank you for being an amazing beta tester!

Vitor

What Happens December 31 (Beta End Date)

Email You'll Receive:

Subject: 🎉 Beta Complete - Thank You!

Hi [Name],

Today marks the end of our 6-week beta. Thank you for helping shape CodeSlick!

**Your Status**:
- ✅ Subscription: Active (€49/month)
- ✅ Discount: Valid until March 31, 2026
- ✅ Features: All Team plan features included
- ✅ Support: Priority support (founding customer)

**What Shipped During Beta** (Thanks to Your Feedback):
- [Feature 1 - requested by you]
- [Feature 2 - your suggestion]
- [Bug fix 1]
- [Bug fix 2]

**Beta Stats** (Your Team):
- PRs Analyzed: [number]
- Issues Found: [number]
- Bugs Reported: [number]
- Features Requested: [number]

**What's Next**:

**Jan 1, 2026**: CodeSlick launches publicly
- You'll get a "Founding Customer" badge on your dashboard
- Your company listed as "Early Supporter" (with permission)
- Continued priority support

**Mar 31, 2026**: Your discount expires
- You'll be charged €99/month starting April 1
- You can cancel anytime before then (no questions asked)

**Thank You**:
You're not just a customer - you're a founding member of CodeSlick. Your feedback directly shaped our product.

**Stay in Touch**:
- Email me anytime: [your-email]
- Feature requests: Always welcome
- Bugs: I'll fix them fast (priority support continues)

Let's grab virtual coffee sometime: [Calendly link]

Thank you for believing in CodeSlick!

Vitor

P.S. - If you know a team that needs security analysis, I'd be grateful for a referral. They'll get a special discount too! 🚀

What I Need to Prepare (Founder Checklist)

2 Weeks Before Beta Ends (Dec 15):

  • Send email: "Beta ending Dec 31 - What's next?"
  • Schedule calls: Final feedback calls with all beta testers
  • Prepare survey: "End of Beta Survey" (detailed feedback)
  • Review subscriptions: Verify all beta testers are on paid plan
  • Update dashboard: Add "Founding Customer" badge
  • Prepare testimonials page: Ask for permission to feature them

1 Week Before Beta Ends (Dec 24):

  • Send reminder: "Beta ends in 1 week"
  • Confirm decisions: Who's continuing, who's canceling
  • Fix remaining bugs: Close all P0 and P1 issues
  • Update documentation: Final polish based on beta feedback
  • Prepare thank you gifts (optional): Swag, stickers, discount codes for referrals

Beta End Date (Dec 31):

  • Send thank you email: Celebrate beta completion
  • Update database: Mark beta testers as "Founding Customers"
  • Post on LinkedIn: "CodeSlick beta complete - thank you to our 10 founding customers!"
  • Publish case studies: Success stories from beta (with permission)
  • Prepare for public launch: Jan 1 launch checklist

After Beta (Jan 1+):

  • Public launch: Product Hunt, press releases, social media
  • Continue support: Beta testers still get priority support
  • Monitor churn: Track if any beta testers cancel
  • Quarterly check-ins: "How's CodeSlick working 3 months in?"

Handling Different Outcomes

Outcome 1: Beta Tester Continues (Happy Path) ✅

What I Do: 1. Send thank you email 2. Add "Founding Customer" badge to dashboard 3. Feature their company as "Early Supporter" (with permission) 4. Continue priority support 5. Keep them in beta testers email list (early access to features)

What They Get: - 3 more months of 50% discount - Lifetime priority support - Early access to new features - Recognition as founding customer

Outcome 2: Beta Tester Wants to Continue But Needs Feature X

What I Do: 1. Assess feasibility: Can I build Feature X in 1-2 weeks? 2. If yes: Build it, then they continue 3. If no: Offer to extend their discount until it's ready 4. If they can't wait: Thank them, stay in touch, invite them back when ready

Example Email:

Hi [Name],

I hear you - you'd continue if we had [Feature X].

Good news: I can build this in [timeline]. Here's my proposal:

**Option A**: I build [Feature X] by [date], you continue after it's shipped

**Option B**: I extend your 50% discount for 6 months (instead of 3) while I build [Feature X]

**Option C**: You pause now, I'll email you when [Feature X] is ready (and give you another beta discount)

Which sounds best?

Vitor

Outcome 3: Beta Tester Cancels (But Amicably)

What I Do: 1. Thank them for their time 2. Ask why they're canceling (learn from feedback) 3. Offer to stay in touch ("Can I email you when we add [Feature X]?") 4. Process cancellation immediately (no friction) 5. Send goodbye email

Example Email:

Hi [Name],

I understand you're canceling. Thank you for giving CodeSlick a try!

**Before You Go**:
Can you share why? Your feedback helps me improve:
- [ ] Too expensive
- [ ] Missing features (which ones?)
- [ ] Didn't fit workflow
- [ ] Found alternative (which one?)
- [ ] Other: [reason]

**Stay in Touch**:
- I'll email you quarterly with major updates
- If I add [feature you wanted], I'll give you a special discount to come back
- You can always restart (no hard feelings!)

**Cancellation Confirmed**:
- Last charge: [date]
- Access ends: [date]
- No future charges

Thank you for being a beta tester. You helped shape CodeSlick!

Vitor

P.S. - If you change your mind, just reply to this email. I'll reinstate your 50% discount. 🚀

Outcome 4: Beta Tester Ghosts (No Response)

What I Do:

Day 1 (Dec 31): Send "Beta Complete" email Day 3 (Jan 2): Send follow-up: "Just checking in" Day 7 (Jan 6): Final email: "Last chance to respond" Day 10 (Jan 9): If still no response: - Keep subscription active (they're paying) - Mark as "inactive" in CRM - No more proactive outreach (but still support if they contact me)

📊 i) Beta Success Metrics

What I'm Tracking

Acquisition Metrics: - Beta applications received - Beta testers accepted (target: 10) - Conversion rate (applications → accepted)

Activation Metrics: - GitHub App installs (target: 100%) - First PR analyzed (target: within 48 hours) - Paid upgrade rate (target: 80%+)

Engagement Metrics: - PRs analyzed per week (target: 5+ per team) - Active days per week (target: 3+ days) - Features used (export, invites, etc.)

Retention Metrics: - Weekly active users (WAU) - Response rate to surveys (target: 70%+) - Retention at end of beta (target: 80%+)

Satisfaction Metrics: - Net Promoter Score (target: 40+) - Bug report rate (lower = better) - Feature request rate (higher = engaged)

Business Metrics: - MRR at end of beta (target: €490) - LTV/CAC ratio (target: 3:1) - Payback period (target: <6 months)

Weekly Report (Internal)

Every Monday, I'll Review:

  1. Active Users: Who used CodeSlick this week?
  2. Inactive Users: Who didn't? (reach out proactively)
  3. Bugs Reported: What broke? (fix immediately)
  4. Feature Requests: What do they want? (prioritize)
  5. NPS: Are they happy? (target: 40+)
  6. Churn Risk: Anyone showing signs of leaving?

Terms of Service

Beta testers agree to: - Use CodeSlick on real projects (not test/dummy repos) - Provide honest feedback - Report bugs promptly - Not share access with non-team members - Cancel if not getting value (no hard feelings)

I agree to: - Protect your code (never store, only analyze on-demand) - Protect your data (GDPR compliant) - Respond to support requests within 24 hours - Fix critical bugs within 48 hours - Provide 50% discount for 3 months as promised

Privacy & Data Handling

What I See: - GitHub organization name - Repository names - PR metadata (title, author, files changed) - Analysis results (vulnerabilities found) - Your email and name (from GitHub)

What I DON'T See: - Your source code (we analyze on-demand, never store) - Passwords or credentials - Private customer data - Anything not related to security analysis

Data Storage: - Analysis results: Stored 90 days, then deleted - Usage metrics: Stored indefinitely (anonymized) - Billing info: Stored by Stripe (PCI-compliant)

Data Deletion: - Cancel anytime: All data deleted within 30 days - Request deletion: Email me, I'll delete within 48 hours

NDA (Non-Disclosure Agreement)

Optional: If your company requires an NDA, I'm happy to sign one.

What I'll Keep Confidential: - Your security vulnerabilities - Your codebase details - Your team structure - Your business information

What I Can Share (with permission): - Your company name as beta tester - Anonymized case study - Testimonial (if you provide one)

Request NDA: Email me, I'll send template or sign yours.

❓ k) FAQ

General Questions

Q: How long is the beta period? A: 6 weeks (Nov 18 - Dec 31, 2025). Your 50% discount continues for 3 months after beta ends.

Q: What happens if I cancel during beta? A: No problem! Cancel anytime, no questions asked. Your last charge will be prorated.

Q: Can I invite team members during beta? A: Yes! Team plan includes up to 5 members. All covered under your subscription.

Q: What languages does CodeSlick support? A: JavaScript, TypeScript, Python, and Java. Go, Rust, C++ coming in 2026.

Q: Do you store my code? A: No. We analyze on-demand (when PR opens) and never store your source code.

Q: Can I use CodeSlick on private repositories? A: Yes! Most of our beta testers use private repos.

Q: What if I find a security vulnerability in CodeSlick? A: Email me immediately (subject: "SECURITY"). I'll fix within 24 hours and credit you (if you want).

Pricing Questions

Q: When does my 50% discount start? A: From your first payment. If you upgrade on Nov 20, discount lasts until Feb 28.

Q: What happens after 3 months? A: You'll be charged €99/month starting month 4. You can cancel before then (no penalty).

Q: Can I get a refund if I'm not happy? A: Yes! 30-day money-back guarantee. Email me within 30 days of first charge.

Q: Do you offer annual plans? A: Not during beta. After beta, yes (2 months free on annual plan).

Technical Questions

Q: Does CodeSlick slow down my PRs? A: No. Analysis runs async (in background). Your PR merges normally.

Q: Can I customize severity thresholds? A: Not yet (coming in Q1 2026). For now, you can filter by severity in PR comments.

Q: Can I integrate with Slack? A: Not yet (coming in Q1 2026). You'll get email notifications for now.

Q: Does CodeSlick work with GitHub Enterprise? A: Not yet (on roadmap). Currently only GitHub.com.

📞 Contact Information

Founder: Vitor Lourenço Email: [your-email] Emergency: [your-phone] (critical bugs only) Calendar: [Calendly link] (15-min calls) GitHub: [your-GitHub-profile] LinkedIn: [your-LinkedIn-profile]

Response Times: - Critical bugs: 2 hours (24/7) - General questions: 4 hours (Mon-Fri, 9 AM-7 PM Lisbon time) - Feature requests: 24 hours

✅ Final Checklist (Before Sending to Beta Tester)

Founder Pre-Flight Checklist:

  • Mark team as beta tester in database
  • Verify beta discount applies (€49.50 checkout)
  • Test GitHub App installation flow
  • Prepare personalized welcome email
  • Add to beta testers email list
  • Create folder for their feedback (Notion/Spreadsheet)
  • Set reminder for weekly check-ins
  • Add to calendar: Week 2 call, Week 4 call, Week 6 call

Beta Tester Checklist (Send This):

  • Read this manual (bookmark it!)
  • Install CodeSlick on GitHub repos
  • Test first PR (verify comment appears)
  • Upgrade to paid plan (verify €49.50 pricing)
  • Invite team members (optional)
  • Report first impressions via email
  • Complete Week 1 survey (sent Friday)
  • Schedule 15-min call with Vitor (Week 2)

Thank you for being a CodeSlick beta tester! Let's build something great together. 🚀

Document Version: 1.0 Last Updated: November 11, 2025 Next Update: After Week 1 of beta (based on feedback)