│ Add Marketplace                                │
│                                                │
│ Enter marketplace source:                      │
│ Examples:                                      │
│  · owner/repo (GitHub)                         │
│  · [email protected]:owner/repo.git (SSH)         │
│  · https://example.com/marketplace.json        │
│  · ./path/to/marketplace                       │
│                                                │
│ frobinson47/claude-code-market-feasibility     | Code language: JavaScript (javascript)

─------------------------------------------------------
  Plugins  Discover   Installed   Marketplaces   Errors

  Manage marketplaces

    + Add Marketplace

    ● ✻ claude-plugins-official ✻
      anthropics/claude-plugins-official
      128 available • 4 installed • Updated 4/10/2026

  ❯ ● frobinson47
      frobinson47/claude-code-market-feasibility
      1 available • 1 installed • Updated 4/11/2026

    ● openbrowser-ai
      billy-enrizky/openbrowser-ai
      1 available • 1 installed • Updated 3/9/2026

  Enter to select · u to update · r to remove · Esc to go back

I want to build an app that helps small fleet operators predict vehicle maintenance
needs using telematics data. Is this viable? Run a feasibility study.
Code language: JavaScript (javascript)

Here's my pitch deck at ~/docs/pitch.pdf — run a feasibility study on this idea.

Market Feasibility Report

FleetPulse — Fleet Maintenance Intelligence Platform

Generated: 2026-04-12 This file is a reference example only — it shows Claude Code the expected output format.

---

Executive Summary

FleetPulse is a proposed SaaS platform that uses telematics data and predictive analytics to help small-to-mid fleet operators (10-200 vehicles) schedule preventive maintenance before breakdowns occur. The market opportunity is real: fleet maintenance is a $30B+ US industry, and small operators are underserved by enterprise tools like Fleetio and Samsara. Technical feasibility is strong — the core stack is well-understood (React + Node + PostgreSQL + telematics APIs), though the predictive ML component carries moderate risk. Financial projections show break-even at ~180 customers on a $99/month plan, achievable within 12-18 months in the moderate scenario. The primary risks are competitive response from incumbents and the complexity of telematics integration across dozens of hardware vendors. Overall recommendation: GO WITH CONDITIONS — viable if the founder can validate the ML prediction accuracy with a pilot fleet before committing to full development.

---

Feasibility Scorecard

---

Idea Profile

Assumptions made for this analysis:

1. The founder is a full-stack developer comfortable with React, Node, and PostgreSQL — assumed from stated experience
2. Telematics hardware (OBD-II dongles) is already installed on target fleets — assumed because this is standard in the segment
3. The founder will work on this full-time — assumed from 6-month timeline ambition
4. The ML prediction component can achieve >80% accuracy — NOT validated; flagged as key risk
5. Target market is US-only at launch — assumed for regulatory simplicity

---

Market & Commercial Feasibility

Problem Validation

Is this a real problem? YES — strong signal.

• Reddit r/fleet and r/trucking: 50+ threads in the past year about unexpected breakdown costs
• ATRI (American Transportation Research Institute) 2025 report: vehicle maintenance is the

#3 cost concern for fleet operators after fuel and driver wages

• Hacker News: 3 "Show HN" posts for fleet tools in 2025, all with 100+ comments
• Pain intensity: HIGH — a single roadside breakdown costs $500-$2,000 in towing + lost

productivity, and fleets of 50 vehicles average 15-25 unplanned breakdowns per year

Current solutions:

• Spreadsheets and calendar reminders (most common for <50 vehicles)
• Fleetio ($5/vehicle/month, designed for 200+ vehicles — overkill for small operators)
• Samsara (enterprise, $30+/vehicle/month — priced out of reach)
• LubeLogger (open source, self-hosted — technically capable but no predictive features)

Why haven't existing solutions solved it? Enterprise tools are overbuilt and overpriced for the SMB segment. Spreadsheets work but don't predict failures. There's a clear gap for a purpose-built SMB tool with predictive capabilities at the $99/month price point.

Is the problem growing? YES — last-mile delivery fleets are expanding rapidly (Amazon DSPs, gig delivery, home services), creating new small fleet operators every month.

Market Sizing

SOM is well above the $100K/year viability threshold. Even the conservative scenario ($4.2M at 0.5% capture) supports a sustainable business.

Competitive Landscape

Market saturation: Moderate — established players exist but SMB segment is underserved. Differentiation potential: HIGH — predictive maintenance for SMB at an accessible price is an unoccupied position.

Customer Segments

Persona 1: "Mike the Fleet Manager" (Primary)

• Job: Manage maintenance schedules for 30-80 delivery vehicles
• Current solution: Excel spreadsheet + calendar reminders
• Pain: 1-2 surprise breakdowns per week costing $800-$1,500 each
• Pain intensity: 8/10
• Budget: Company card, $500/month tools budget
• WTP: $79-$149/month — would pay instantly if it demonstrably prevents breakdowns
• Perceived > objective value (breakdowns feel catastrophic in the moment)

Persona 2: "Sarah the Owner-Operator" (Secondary)

• Job: Run a 10-15 vehicle home services fleet (HVAC, plumbing, etc.)
• Current solution: Paper logbooks + mechanic relationship
• Pain: Vehicles down = technicians can't work = lost revenue
• Pain intensity: 7/10
• Budget: Personal business card, price-sensitive
• WTP: $49-$79/month
• Perceived < objective value (doesn't think of maintenance as a "software problem")

Persona 3: "Dave the Amazon DSP Owner" (Growth)

• Job: Manage 20-40 branded delivery vans for Amazon
• Current solution: Amazon provides basic tracking; maintenance is DIY
• Pain: Amazon penalizes DSPs for delivery failures due to vehicle issues
• Pain intensity: 9/10 (business survival at stake)
• Budget: Tight margins but will pay for survival tools
• WTP: $99-$199/month
• Perceived = objective value (directly tied to Amazon performance metrics)

Persona 4: "Enterprise Procurement" (Future)

• Job: Standardize maintenance tools across 200+ vehicles
• WTP: $500+/month or per-vehicle pricing
• Note: Not addressable at launch — requires SOC 2, SSO, SLA. Roadmap for Year 2.

Brand Name Clearance

Overall Assessment: GREEN — Name is largely clear. The .com is held by an inactive blog (potential acquisition for <$1K). FleetPilot in the UK is a different name and market. Recommend securing fleetpulse.io immediately and pursuing .com acquisition.

---

Technical Feasibility

Requirements Analysis

Recommended Stack

Technical Risks

No technical blockers identified. All required technology exists and is proven. The main uncertainty is ML prediction accuracy, which is testable before full commitment.

Build vs. Buy

MVP Definition

Must-have (launch blockers):

• Connect to Geotab API and ingest vehicle telematics data
• Dashboard showing vehicle list, health status, upcoming maintenance
• Rule-based maintenance alerts (mileage-based, time-based)
• Basic reporting (maintenance history, cost tracking)
• Stripe billing integration

Should-have (week 2-4):

• ML-powered predictive alerts (v1 model)
• Email/SMS notifications for upcoming maintenance
• Multi-user access per account

Nice-to-have (roadmap):

• Mobile app
• Additional telematics provider integrations
• Parts ordering integration
• Enterprise features (SSO, audit log, API access)

Explicitly out of scope for MVP:

• Predictive ML (defer to v1.1 — launch with rule-based alerts first)
• Mobile app
• Enterprise tier
• Any telematics provider beyond Geotab

Estimated MVP scope: ~15 screens, ~30 API endpoints, ~15K-20K lines of code.

---

Financial Feasibility

Development Costs

MVP:

v1.0 (with ML predictions):

Operating Costs (Monthly)

Revenue Projections

Assumptions: $99/month ARPU, 5% monthly churn, moderate scenario assumes 15-20 new customers/month after month 3.

Break-Even Analysis

ROI Projections

Funding Assessment

Can this be bootstrapped? YES — with conditions.

• MVP cost is within founder's stated $10K-$50K budget
• Monthly burn is under $1,500 until revenue materializes
• Break-even at just 16 customers is highly achievable
• Founder needs 9-12 months of personal runway (living expenses)

This is a lifestyle/indie business opportunity, not venture-scale. $1M-$5M ARR ceiling is realistic. This is a strength, not a weakness — it means the founder retains full ownership and control.

---

Legal & Regulatory Feasibility

Business Structure & IP

Regulatory Compliance

Legal Risks

Legal Budget

---

Operational Feasibility

Team Assessment

Scalability Concerns

Founder Capacity

• Full-time commitment: YES (stated)
• Financial runway: 12-18 months (stated $10K-$50K budget + savings)
• Burnout risk: MODERATE — solo founder building ML + full-stack + marketing
• Recommendation: defer ML to post-MVP to reduce scope and burnout risk

---

Schedule Feasibility

Project Timeline

Critical Path

PRD (2w) → Design (2w) → MVP Dev (10w) → Alpha (2w) → Beta (4w) → Launch (2w) = 22 weeks

Parallelizable: Legal setup during dev (saves 0 weeks on critical path but reduces post-launch risk). Marketing content creation during beta (saves 0 weeks but improves launch readiness).

Timeline Risks

Schedule Verdict

TIGHT — The 6-month target is achievable but requires disciplined execution. The original 6-month timeline assumed ML in MVP, which is unrealistic. With ML deferred to v1.1, the 5.5-month plan is feasible. Buffer of 2-4 weeks recommended.

Realistic launch: 6-7 months from start.

---

Pricing & Go-to-Market Strategy

Demand Curve Analysis

Revenue-maximizing price band: $79-$99/month

Pricing Model: Freemium Subscription

Rationale: Fleet operators expect subscription pricing (matches Fleetio, Samsara). A generous free tier for 1-3 vehicles captures Sarah-type small operators who may grow. The $99 price point sits comfortably under the $1,000 procurement threshold, enabling credit-card purchases without formal approval.

Tier Structure

Annual pricing: 2 months free (pay for 10).

Launch Pricing Strategy

Marketing Strategy

Channels (in priority order):

1. Content marketing — blog posts on fleet maintenance cost reduction (SEO play)
2. Fleet management forums and communities (Reddit, fleet Facebook groups)
3. Geotab partner marketplace listing
4. Targeted Google Ads: "fleet maintenance software small business"
5. Conference presence at NAFA Fleet Management Association events

Key messaging:

1. "Predict breakdowns before they strand your driver" — speaks to Mike's pain
2. "Enterprise fleet intelligence at small business prices" — positions against Samsara
3. "5 minutes to set up, works with your existing telematics" — reduces switching cost fear

---

Risk Analysis

Consolidated Risk Register

SWOT Analysis

---

Recommendation

Verdict: GO WITH CONDITIONS

FleetPulse addresses a real, growing problem in an underserved market segment. The economics work, the tech is buildable, and the legal landscape is clean. However, the core value proposition — predictive maintenance — depends on ML accuracy that is currently unvalidated.

Conditions

1. Validate ML feasibility first (2-3 weeks): Obtain sample telematics data from

a friendly fleet operator and build a proof-of-concept prediction model. If accuracy is below 70%, launch with rule-based alerts only and position as "smart scheduling" rather than "predictive maintenance."

1. Secure fleetpulse.io domain immediately (before any public branding)
2. Defer ML to v1.1 — launch MVP with rule-based alerts to reduce timeline risk
3. Line up 3-5 beta fleets before starting development

Recommended Next Steps

1. This week: Register fleetpulse.io, create Geotab developer account, reach out to

3 fleet operators for pilot data

1. Week 2-3: Build ML proof-of-concept with sample data; assess prediction accuracy
2. Week 4: If ML validates, start full development. If not, pivot positioning to

"smart maintenance scheduling" (still viable, lower ceiling)

1. Month 1: Form LLC, draft ToS/Privacy Policy from templates
2. Month 2-4: Build MVP (rule-based alerts, dashboard, billing)
3. Month 5: Alpha testing with pilot fleets
4. Month 6-7: Beta launch, collect feedback, iterate
5. Month 7-8: Public launch with early adopter pricing
6. Month 9-10: Add ML predictions as v1.1 (if validated)

---

Davidson Pricing Checklist

• [x] Strategy: mid-market pricing ($99/mo) with free tier for awareness
• [x] Product definition: maintenance intelligence + peace of mind + cost savings
• [x] Fairness: priced at 1/3 of Fleetio on a per-fleet basis for the target segment
• [x] Customer profile: Mike (team budget, card), Sarah (personal, price-sensitive), Dave (business card)
• [x] Competitor reaction: Fleetio unlikely to drop to $99/mo; may add features
• [x] Sales model: self-serve web for Starter/Pro; inbound for Enterprise
• [x] Segmentation: Starter (free) / Professional / Business / Enterprise
• [x] Bundling: future opportunity with telematics hardware partners
• [x] First price set: $99/mo Professional tier
• [ ] Test and adjust: revisit at Month 3 based on conversion data

---

Appendix: Assumptions & Methodology

Data sources:

• Market sizing: ATRI reports, IBISWorld fleet maintenance industry data, Geotab partner statistics
• Competitor pricing: publicly available pricing pages (accessed April 2026)
• Customer personas: based on fleet industry forums, user interviews cited in Fleetio blog posts
• Financial projections: estimated based on comparable SaaS companies in vertical markets

Key assumptions that should be validated:

1. ML prediction accuracy >70% is achievable with OBD-II telematics data alone
2. Geotab API provides sufficient data granularity for predictive maintenance
3. Fleet operators with 10-50 vehicles are willing to adopt SaaS tools (not just spreadsheets)
4. $99/month is within the self-serve purchase threshold for the target segment
5. Content marketing can generate 15-20 qualified leads per month by month 6