Blog / Devlogs

Devlog #3: Prioritizing Core Features for First User Testing

Jetson Team · · 2 min read

Jetson automatically finds bugs and feature requests hiding in your support inbox.

Try it free

Overview

Jetson is an autopilot for customer feedback that processes Help Scout inboxes, automatically categorizing conversations into bugs, feature requests, and documentation needs, then syncing them to GitHub.

We’re streamlining our MVP before conducting first-user testing on Friday.

This Week’s Focus

With one team member departing for a week, the priority was delivering testable functionality for initial user validation by Friday, deferring non-essential features.

Key Strategic Decisions

Documentation Features Deferred

We disabled documentation and article creation behind a feature flag, reasoning that documentation drafts are public-facing content that requires more polish.

Without bidirectional webhooks, manual edits would create state management complexity.

Simplified GitHub Integration

Rather than implementing full OAuth immediately, the MVP uses a URL-based approach where users paste their repository URL in settings.

Bug reports and feature requests include a button opening GitHub’s issue creation page with prefilled content. Full automation comes post-MVP.

Cron Job Over Webhooks

Initial Help Scout syncing uses a 30-minute cron job instead of webhooks, scanning the past 12 hours after the initial 365-day onboarding scan.

Real-time updates aren’t critical for one test user.

Duplicate Detection Priority

The system will cluster similar customer requests, displaying “25 people have asked for this” rather than creating duplicates—identified as the highest-value feature.

Jetson turns Help Scout conversations into organized GitHub issues automatically.

Learn more

MVP Shipping This Week

  • Bug and feature request creation from Help Scout
  • Duplicate detection and clustering
  • GitHub URL scheme integration
  • Automated cron-based scanning
  • Internal error management with Sentry

Deferred to Next Sprint

  • Help Scout article creation
  • Full GitHub OAuth with automatic issue creation
  • Webhook-based syncing
  • Billing and email notifications
  • Customer-facing error logging

Timeline

  • Wednesday-Thursday: Implementation focus
  • Friday: 30-minute user test preceded by preparation session

Next Steps

Implementation priority:

  1. Feature flag setup
  2. Help Scout cron job with intelligent deduplication
  3. Duplicate detection fixes
  4. GitHub URL scheme integration