# CLARK Product Roadmap ## Purpose This roadmap defines the order in which CLARK's product families should be built, tested, and operationalized. The near-term priority is not to launch every product line at once. It is to prove the training-first commercial wedge and the Clarkware development and testing path that strengthens the network at the workstation and facility level. ## Roadmap Priorities 1. Training services 2. Clarkware development and testing 3. Assembly services through partner facilities 4. Firmware optimization through partner facilities 5. Logistics and facility coordination services ## Product Family Roles ### Training Services Training services are the first direct revenue layer. They include: - IPC certification delivery - train-the-trainer services - Clark Courses wraparound curriculum - later licensed training-center models Training services should establish CLARK's first cash flow, workforce credibility, and operating discipline inside the Niagara Assembly relationship. The training-services family now includes both IPC-centered delivery and Clark Courses as a standalone professional education line with future licensing potential. ### Clarkware Clarkware is the first core product-development effort. It should begin as a development and testing program tied to real station activity, evidence capture, messaging, reporting, and auditable human-and-AI coordination. Early success depends on proving the Niagara pilot honestly before broadening the software story. ### Assembly Services Assembly services should be framed as partner-facility-delivered services, not as CLARK trying to become a centralized contract manufacturer. Regional specialist facilities carry out the work. CLARK improves their ability to win and deliver work through: - training and workforce development - software and workstation tooling - process standards and documentation - quality and reporting systems - customer coordination and network credibility - selective capital and launch support ### Firmware Optimization Firmware optimization should also be framed as a network-enabled service carried out through regional specialists and trusted technical partners. CLARK's role is to create the shared environment, documentation, workflow support, and coordination layer that helps firmware-sensitive manufacturing work happen more effectively inside the network. ### Logistics And Facility Coordination These services may become highly valuable, but they should follow after the first training and Clarkware proof points. The likely scope includes: - cross-border shipment coordination - warehousing and routing support - customs and handoff coordination - facility-to-facility scheduling and escalation support - shared operating visibility across nodes where justified ## Phased Roadmap ### Phase 1: Training-First Launch Primary focus: - launch Hamilton training operations - generate early IPC and train-the-trainer revenue - refine Clark Courses and Clark Certified structure - launch the first Clark Courses public and private cohort model - document repeatable training operations Why first: - fastest path to early revenue - strongest immediate proof of market demand - strongest path to workforce credibility and regional trust ### Phase 2: Clarkware Development And Testing Primary focus: - stand up the Niagara Clarkware pilot - prove workstation-level IPE use in real work - prove evidence capture, messaging, and reporting - validate auditable human-and-AI participation - document repeatable pilot and rollout patterns Why second: - Clarkware is a major long-term differentiator - it strengthens both training and partner-facility service delivery - it should be tested in real operating conditions before being scaled as a platform promise ### Phase 3: Partner-Facility Assembly Service Enablement Primary focus: - recruit or formalize partner-facility participation - document CLARK's assembly enablement model - support quality, workflow, and reporting improvements - use Clarkware and training to strengthen partner execution Why third: - CLARK should enable regional specialists rather than replace them - this phase turns the platform story into practical network service delivery ### Phase 4: Partner-Facility Firmware Optimization Enablement Primary focus: - define the firmware-support offer inside the network - support partner specialists with shared tooling and workflow coordination - tie firmware-sensitive work more tightly to evidence capture and production context Why fourth: - strategically important, but dependent on the network and software environment being credible first - best positioned as a specialist network capability, not an abstract promise ### Phase 5: Logistics And Facility Coordination Expansion Primary focus: - build out cross-border routing and warehousing support - define facility coordination services - support multi-node scheduling, handoffs, and escalation - selectively monetize logistics and coordination where the network has real leverage Why later: - potentially high value, but easier to sequence after training, software, and partner-service execution are already proven ## Near-Term Build Sequence ### Next 6 Months - prioritize training-service readiness and Hamilton operating launch - prioritize Clarkware pilot build, development, and testing - document the assembly-service and firmware-optimization enablement models ### 6 To 12 Months - prove repeatable training delivery - prove Clarkware pilot truthfully in live work - begin structured onboarding of partner-facility assembly and firmware capabilities ### 12 To 24 Months - expand Clarkware beyond the first pilot station and node - scale training services into a more repeatable network offer - deepen assembly and firmware enablement across partner facilities - begin selective logistics and facility-coordination services where justified ## Discipline Rule CLARK should avoid presenting later-phase logistics and coordination services as mature operating products before the training and Clarkware proof points are real.