Product Development Roadmap
A 12-month timeline for taking a connected product from strategy through commercial launch. Each stage links to in-depth guides from the Connected Product Guidebook.
*Timeline modeled on longest time frame (upper bound duration for each stage). Click any stage to jump to details below.
Strategy Setting
Weeks 1-2Determine whether a connected product aligns with your company's strategy and current constraints. Anchor your case in measurable impact drivers proven across industries and identify the customer problems that connectivity can solve.
Key Activities
- Articulate the problem being solved and who feels it most acutely
- Quantify at least one primary impact driver (downtime, truck rolls, energy, safety)
- Identify decision-makers and build internal champions across the organization
Clear investment decision defined with approval criteria and internal champions identified
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Business Case & Financial Model
Weeks 3-8Translate the strategic opportunity into a structured business case. Combine top-down market sizing with bottom-up operational forecasts, model both Base and High scenarios, and pressure-test assumptions with stakeholders before formal review.
Key Activities
- Quantify the market opportunity and define pricing with compelling customer ROI
- Model revenue, costs, and margin evolution across Base and High scenarios
- Pressure-test the model with Sales, Engineering, Operations, and Finance
Business Case Readiness Checklist complete
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Architecture & Design
Weeks 3-11Design your solution architecture around Blues Notehub as the cloud backbone. Define how data flows from devices to your application, organize projects and fleets for scale, and decide between off-the-shelf Notecarriers and custom PCBs for your hardware integration.
Key Activities
- Define Notehub project structure, fleet organization, and data routing architecture
- Select application cloud platform and configure Notehub routes
- Choose hardware integration path: Notecarrier for prototyping, custom PCB for production
Cloud Architecture Checklist complete
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Prototype & Engineering Validation
Weeks 12-23Build and test early prototypes to validate your highest-risk technical assumptions. Treat Notecard as a durable on-device queue, design for intermittent connectivity from day one, and plan for OTA firmware updates before your first deployment.
Key Activities
- Build working prototype and implement firmware using Notecard's queue-based model
- Design power management and validate power budget with actual measurements
- Test critical edge cases: connectivity loss, power interruption, sensor failures
Prototype "Done" Checklist: 8 yes/no questions all answered "yes"
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Design Validation
Weeks 24-33Validate the near-production design by finalizing antenna selection, PCB layout, and enclosure RF performance. Test in your actual enclosure early because enclosure materials directly affect RF performance. Confirm the design meets reliability and operational requirements.
Key Activities
- Select and test antenna performance in actual enclosure with signal measurements
- Finalize custom PCB design following Notecard integration requirements
- Conduct field testing at representative deployment locations
Antenna Selection Checklist and PCB Design Checklist complete
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Production Validation
Weeks 34-45Validate that your connected product can be manufactured, provisioned, tested, and shipped at scale with consistent quality and cost. Finalize the production BOM, select manufacturing partners, and establish quality control processes.
Key Activities
- Select Notecard SKU and finalize production BOM with second-source strategy
- Select contract manufacturer with relevant IoT or wireless experience
- Define production test procedures including functional and connectivity testing
Production Readiness Checklist complete (7 categories)
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Certification Scoping
Weeks 4-8Identify all certification requirements and surface compliance risks early enough to influence architecture and design decisions. Blues Notecard comes pre-certified for FCC, CE, and many other standards, significantly reducing your certification burden.
Key Activities
- Define target deployment geographies and required certifications
- Review Blues Notecard's existing certifications and identify remaining gaps
- Engage certification labs or consultants for early risk and cost review
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Pre-Compliance & Testing
Weeks 9-20Reduce certification risk by running pre-compliance tests on prototype hardware and resolving major issues while changes are still low cost. A typical certification timeline runs 8-12 weeks, so planning ahead is critical.
Key Activities
- Run pre-compliance tests (EMC, RF, safety) on prototype builds
- Identify failure risks and iterate design to resolve issues early
- Align certification timeline with design freeze and production schedule
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Formal Testing & Approval
Weeks 21-42Submit production-intent units for formal certification testing, compile technical documentation, and secure all approvals required for production. The formal testing process typically covers EMC testing, safety testing, RF exposure, documentation, and labeling.
Key Activities
- Submit production-intent hardware for formal EMC and safety testing
- Compile technical files, declarations, and labeling requirements
- Obtain certifications and confirm production builds remain compliant
All required certifications obtained and documented
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Pilot Planning
Weeks 20-23Design a structured pilot that validates both technical performance and business value with real customers. Define what the pilot must prove, confirm operational readiness, and ensure you have clear success criteria before deploying a single device.
Key Activities
- Define value hypotheses the pilot must validate and baseline success metrics
- Confirm prerequisites: working devices, cloud pipeline, and support model
- Secure pilot customer agreements and prepare installer kits and training
Pre-Pilot Readiness Checklist complete
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Pilot Execution & Monitoring
Weeks 24-33Execute the pilot in real-world conditions and monitor performance against defined success criteria. Deploy in waves, capture structured learnings across technical, operational, and customer dimensions, and use Blues Notehub for remote monitoring and diagnostics.
Key Activities
- Deploy devices in waves, validating each wave before expanding
- Monitor device health and data quality via Notehub dashboards
- Collect structured customer feedback on installation, value, and usability
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Pilot Decision & Scale
Weeks 34-37Make a structured go/no-go decision based on pilot results. Evaluate whether success thresholds are met, the operational motion is viable, and customer value is validated. Three outcomes: scale to production, iterate and re-run, or stop.
Key Activities
- Evaluate pilot results against defined success criteria and thresholds
- Make go/no-go decision: Scale to production, Iterate, or Stop
- Plan transition to production including customer retention strategy
Go/No-Go decision: Scale to production, Iterate, or Stop
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Commercial Readiness
Weeks 38-40Prepare your organization to sell the connected product. Finalize pricing based on full cost structure (hardware, connectivity, cloud, support), build sales enablement assets, and train your sales team on the connected product value narrative.
Key Activities
- Model full cost structure and validate pricing model with pilot customer feedback
- Assess sales readiness and determine sales model for connected products
- Build value narrative deck, ROI framework, and objection handling playbook
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Operational Readiness
Weeks 41-43Ensure your organization can deliver, activate, support, and service the connected product at scale. Set up fleet organization in Notehub, configure monitoring and observability, and define the deployment and distribution model.
Key Activities
- Design fleet structure in Notehub for operational workflows and staged rollouts
- Set up monitoring: inactivity detection, alerts, and health dashboards
- Define provisioning, deployment model, and fulfillment logistics
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices:
Launch & Early Scale
Weeks 44-48Execute a controlled commercial launch and establish stable operations across sales, fulfillment, activation, and support. Design the first customer experience carefully, define support tiers and escalation flows, and use staged firmware rollouts to reduce risk.
Key Activities
- Design and validate the customer onboarding and first-data experience
- Define support tiers, escalation paths, and SLAs with response targets
- Deploy firmware updates using staged rollouts to reduce fleet-wide risk
Go-to-Market Checklist complete (6 categories)
Deep Dive
Read these sections from the Connected Product Guidebook for checklists, examples, and best practices: