# Clark Business Plan Draft ## Executive Summary - Company: CLARK - Mission: Build the leading binational network for precision electronics assembly, firmware-aware manufacturing support, software-enabled factory coordination, and advanced workforce development in North America. - Problem: Customers with small-batch, high-spec electronics needs face fragmented supply, limited trusted capacity, weak firmware-manufacturing coordination, and poor workforce depth. - Solution: A platform company that builds, funds, and coordinates independently operated regional nodes using shared IP, software, training, brand standards, and logistics infrastructure, including Clarkware as the facility-aware operational software layer. - Product priority: Training services led by IPC and Clark Courses first, Clarkware development and testing second, partner-facility assembly and firmware enablement next, and logistics and facility coordination later. - Target market: Industrial-controls OEMs and integrators first, with adjacent rugged-hardware categories later, in the United States and Canada. - Business model: Training-first revenue, followed by node operating revenue, platform fees, minority equity ownership in regional nodes, and later capital recycling. - Why now: Supply-chain regionalization, workforce shortages, firmware-sensitive products, and North American industrial policy create an opening for a coordinated cross-border network. ## Problem North American electronics customers often need more than a conventional contract manufacturer provides. Small-batch and high-mix programs require flexibility, trusted quality systems, firmware-aware production support, and reliable regional turnaround. Existing options are fragmented across specialty shops, offshore vendors, logistics providers, firmware consultancies, and underdeveloped local workforce pipelines. For industrial and defense-adjacent work, this fragmentation increases program risk. Customers absorb longer lead times, supplier coordination overhead, quality inconsistency, and exposure to geopolitical or procurement constraints. At the same time, regional manufacturing growth is constrained by workforce depth and by the lack of coordinated production infrastructure for complex, low-volume work. ## Solution CLARK acts as the platform layer for a network of independently operated electronics assembly nodes. The platform supplies shared intellectual property, process standards, software tools, training curricula, brand architecture, and cross-border logistics coordination. Regional facilities use this system to deliver customer work locally while benefiting from network-level capabilities. The initial node capability set includes: - Small-batch PCB and PCBA assembly delivered through regional specialist facilities - Binary-level firmware optimization delivered through regional specialists and trusted technical partners - IPC-certified workforce training This model lets CLARK standardize quality and operating know-how while preserving local execution agility. Clarkware is intended to become the software layer that records and relays the operating story of each node through workstation-level Integrated Production Environments, evidence capture, messaging, and auditable human-and-AI coordination. ## Network Operating Model ### Calls for Research CLARK identifies capability gaps in the network and commissions nodes to develop solutions through Calls for Research. The platform defines the commercial problem and acceptance criteria, while the node owns the technical execution. Resulting IP is intended to be transferred into the platform for network-wide use, with participation rights for originating nodes where appropriate. ### Calls for Facilities CLARK expands geographically through structured Calls for Facilities that define facility, equipment, certification, workforce, and logistics requirements for new nodes. Selected operators receive access to the platform and may receive seed capital from CLARK in exchange for a minority ownership position. ### Acquisition And Conversion CLARK also expands through acquisition or conversion of existing precision manufacturers. This allows the network to add installed capability, local customer relationships, and experienced operators faster than greenfield buildout alone. ### Node Governance Nodes are expected to remain separately incorporated and operationally autonomous. CLARK's control is exercised through licensing, shared systems, minority investment rights, and protective covenants rather than through day-to-day operating control. ### Division Structure CLARK's internal operating philosophy is divisional. The Training Division is the first working example and is intended to operate with a high degree of self-sufficiency inside CLARK. Future divisions may include Software and Transport, following the same pattern of empowered management teams and reduced dependence on constant C-suite and Board intervention. ## Market ### Ideal Customer Profile - Primary segment: Industrial-controls OEMs and integrators needing low-volume, high-complexity electronics assembly with firmware-sensitive support. - Buyer: Procurement leaders, operations leaders, manufacturing managers, program managers, and technical leadership. - User: Embedded systems teams, hardware engineering teams, and production teams. - Early adopter traits: Urgent turnaround needs, regional sourcing preference, firmware-sensitive products, dissatisfaction with generic EMS options, and need for engineering-adjacent support. ### Market Size - TAM: North American electronics manufacturing services and related support for small-batch and specialty assembly. - SAM: US and Canadian industrial-controls and adjacent rugged-hardware customers requiring trusted regional precision assembly and firmware-aware support. - SOM: Binational corridor demand reachable from Hamilton and Buffalo in the first 24 months, starting with industrial-controls programs that fit CLARK's training-first and firmware-aware operating model. ### Bottom-Up Proof Model This section is a planning model for the first proof case, not an external market-size claim. - Training base case: 22 Year 1 courses at 8 students per class and blended revenue of about CAD 1,200 per student produces about CAD 211,200 gross revenue and about CAD 62,536 of net CLARK contribution after direct instructional costs and Niagara facility participation. - First partner-facility proof case: one paid discovery engagement at about CAD 5,000, one onboarding engagement at about CAD 25,000, and one active recurring node-support relationship at about CAD 3,500 per month produces about CAD 72,000 of node-development and recurring platform revenue contribution in a year. - Early production proof case: 3 anchor industrial-controls accounts with 2 to 4 qualifying programs per year at roughly CAD 25,000 to CAD 75,000 per program creates an initial corridor production-value planning band of about CAD 150,000 to CAD 900,000 before later-scale expansion. The practical investor point is that CLARK does not need to prove a continent-wide market immediately. It needs to prove that one Hamilton training operation, one Clarkware pilot, and one partner-facility onboarding path can compound into repeatable corridor economics. ## Product And Platform Strategy - Version 1 scope: Prove the Hamilton-Buffalo corridor with repeatable operating standards, training-first revenue, Clark Courses launch, shared tooling, customer delivery, and facility-aware software that improves visibility and accountability. - Investor proof ladder: - training revenue proof - Hamilton site activation proof - Niagara Clarkware pilot proof - first partner-facility economics proof - Core shared assets: Process IP, training curricula, software tooling, logistics systems, brand standards, node launch methods, and owner-accessible reporting infrastructure. - Early software focus: Clarkware Integrated Production Environments built on Theia, facility activity logging, role-based reporting, human-and-AI agent audit trails, chat and workflow coordination, firmware development environments, test bench automation, and calibration tooling. - Service-delivery principle: Assembly services and firmware optimization should be delivered primarily by partner facilities and regional specialists, while CLARK supplies the enhanced resources that strengthen execution at the workbench and facility level. - Key differentiators: Binational footprint, firmware-aware manufacturing support, workforce training integration, software-enabled coordination, secure facility-aware reporting, and shared logistics infrastructure. - Defensibility path: Shared know-how, brand trust, software tools embedded in facility operations, IP registry, node network effects, cross-border execution capability, and minority ownership in expanding nodes. ### Product Family Stack CLARK's operating model is easier to understand when the product families are separated clearly. The current priority order is: 1. Training services 2. Clarkware development and testing 3. Assembly services through partner facilities 4. Firmware optimization through partner specialists 5. Logistics and facility coordination services ### Training Services Training services are the first direct revenue line and the first operating proof point. The training-services family currently includes: - IPC certification delivery - train-the-trainer services - Clark Courses professional education - later licensed training-delivery partnerships Clark Courses should be treated as a real revenue-bearing line inside the training-services family, not merely as a supporting curriculum layer. It gives CLARK a standalone education offer that can serve technicians, engineers, managers, career changers, and training-delivery partners even when they are not direct manufacturing customers. ### Clarkware Clarkware is the first major product-development effort, but it should be framed as a development and testing program before it is framed as a scaled software business. The immediate goal is to prove the Niagara pilot, not to overstate platform maturity. ### Partner-Facility Services Assembly services and firmware optimization should be presented as CLARK-enabled services delivered through regional specialists, trusted technical partners, and partner facilities. CLARK strengthens execution through training, standards, software, reporting, and network support rather than by centralizing every service line on its own books. ## Anchor Nodes And Corridor Design ### Niagara Assembly Hamilton is the founding node and primary R&D engine. Its likely role is to lead process development, support firmware-sensitive manufacturing work through partner specialists, and host portions of the platform software and IP portfolio. ### Hamilton Training Facility The earliest commercial model assumes a CLARK-operated IPC training facility in Hamilton within the larger Niagara Assembly footprint. CLARK owns service delivery directly, uses the CLARK brand directly, and contracts instructors as needed in the early phase. The working co-location plan is now more specific. CLARK is expected to co-locate into Niagara Assembly's Hamilton site at the optimal site near Sector A and lead the charge in renovating and activating the front two portions of an initial `4,500 sq ft` launch footprint. The back third of that first-phase area is intended to remain reserved for Niagara Assembly's specialized low-batch testing and flashing hub. A further `5,000 sq ft` on the main level may become available for Niagara Assembly to secure independently, but that additional area should currently be treated as optional expansion capacity rather than part of CLARK's guaranteed launch footprint. The facility is intended to serve as: - CLARK's first direct revenue source - a workforce-development engine for the broader region, with Niagara Assembly as prime beneficiary - a beta model for future training facilities and future training licensing The initial focus is expected to be train-the-trainer depth and strong practical coverage of a specific launch bundle: IPC-A-610 CIS, IPC-A-610 CSE, Hand Soldering Certification, EPTAC Hands-on Cable and Wire Harness Lab, and IPC-A-610 CIT. The CIT path should be aimed particularly at experienced professionals who want to transition into training or add instructional capability to their careers. CLARK should also build a modular layer of Clark Courses around the formal IPC stack. These courses should teach broader manufacturing literacy, inspection logic, qualification concepts, and board-building knowledge in a rigorous format that can stand on its own while also serving as intake and progression support for participants moving toward IPC certification. Clark Courses should also be treated as a separate commercial education offer with multiple delivery paths: - public cohort delivery in Hamilton - private corporate cohorts - partner-venue delivery - later licensed delivery partners and selected online Foundations content ### Commercial Relationship With Niagara Assembly - Niagara Assembly hosts the designated training footprint - CLARK leads renovation and activation of the front two portions of the first-phase optimal site near Sector A co-location footprint - Niagara Assembly retains the back-third testing and flashing hub inside that same first-phase area - Niagara Assembly charges nominal rent and equipment-use fees - The beta-phase model should use fixed fees calibrated to course volume plus a revenue-sharing component calculated after direct instructional costs - CLARK should carry instructor liability - The facility side should carry trainee injury and equipment-damage responsibility - Niagara Assembly should own facility safety and site procedures - CLARK should own instructor and training-process compliance The current working beta economics for Hamilton are: - 1 to 2 delivered courses per month: CAD 1,250 fixed monthly facility fee plus 12% of contribution margin after direct instructional costs - 3 to 4 delivered courses per month: CAD 2,500 fixed monthly facility fee plus 10% of contribution margin after direct instructional costs - 5 or more delivered courses per month: CAD 4,000 fixed monthly facility fee plus 8% of contribution margin after direct instructional costs Direct instructional costs should be limited to instructor compensation, instructor travel and lodging where needed, course-specific consumables and materials, and third-party certification or course-delivery fees directly tied to the class. Broader CLARK overhead should sit outside that calculation. ### Advisory Group During the beta phase, CLARK should coordinate an Advisory Group around the Hamilton training model. This should ideally include: - regional university representatives - EPTAC, if participation is available - additional local ecosystem participants as needed The Advisory Group should function as a working group rather than a formal approval body. It should receive monthly updates and meet quarterly to refine the approach. CLARK should retain control of training standards and operations while using the group for ecosystem fit and model refinement. ### Buffalo Assembly Buffalo is the American anchor for precision assembly and inspection services and may become the first reference point for domestic customer acquisition in the corridor. ### Dunkirk Logistics Option Dunkirk should be treated as a later logistics and warehousing option rather than as part of the current launch footprint. It may become relevant if corridor volume, warehousing needs, and Buffalo-side logistics constraints justify it, but it should not sit inside the core proof case for the current raise story. ## Go-To-Market - Phase 1: Launch IPC certification revenue and train-the-trainer activity enabled through EPTAC in Markham, Ontario, while launching Clark Courses as a standalone professional education offer around the IPC stack. - Phase 2: Use the Hamilton training site and Niagara Assembly co-location model to establish local workforce credibility and early operating rhythm. - Phase 3: Bring Niagara Assembly into contract testing and assembly work, then add platform fees and node operating revenue. - Training-market focus in the first 12 months: - existing regional company employees needing upskilling - nearby university and college students seeking practical capability before graduation - Clark Courses go-to-market paths: - public cohorts for individuals and small employer-sponsored groups - private cohorts for corporate clients - early partner-development conversations with colleges, workforce organizations, and future licensed delivery partners - Credentialing model: market formal IPC outcomes as IPC-certified and position Clark Courses under the Clark Certified label as a separate CLARK-branded achievement layer. CLARK should develop verifiable shareable records for these outcomes by the end of year 1. - Acquisition channels: Direct outreach to target OEMs, industrial networks, procurement relationships, hardware ecosystems, and regional manufacturing stakeholders. - Sales model: Founder-led and node-led enterprise selling with relationship-driven qualification. - Partnerships: Workforce institutions, EPTAC, regional economic development bodies, logistics providers, and applied engineering ecosystems. - Expansion motion: Use corridor credibility to recruit licensed nodes, support selective acquisitions, and extend the network into the Great Lakes region. ## Revenue Model ### Phase 1: Training-First Revenue - IPC certification revenue from direct training delivered through the Hamilton site - Train-the-trainer and related workforce enablement revenue supported by EPTAC partnership activity in Markham, Ontario - Clark Courses revenue from public cohorts, private cohorts, and modular CLARK-branded professional education that complements IPC pathways - Later Clark Courses curriculum licensing and partner-delivery revenue once the first training model is stable - Early CLARK-sponsored training operations as the first cash-generating layer of the model ### Phase 2: Node Operating Revenue As partner facilities such as Niagara Assembly come online for testing and assembly contracts, node operating revenue begins to matter. This provides the first proof that the corridor can convert training-led presence into production-led commercial activity without CLARK needing to centralize all delivery itself. The first investor-safe proof case should assume one paid discovery engagement, one onboarding engagement, and one recurring node-support relationship before assuming broad multi-node scale. ### Phase 3: Platform Fees - Discovery and qualification fees: CAD 2,500 to CAD 7,500 per engagement - Node onboarding fees: CAD 15,000 to CAD 40,000 per node - Recurring enablement and platform participation: CAD 2,000 to CAD 8,000 per month per active node depending on support scope - IP licensing royalties for access to process documentation, firmware methodologies, training materials, and the brand system - Training license fees for later licensed delivery - Clarkware bundled into Assembly Centre / Assembly Center licensing by default - Separate Clarkware or software fees for non-center users seeking partial access to the Clark System - Logistics coordination and infrastructure fees should be treated as later-phase revenue only after real corridor volume exists ### Equity Ownership - Default CLARK ownership target in new Assembly Centres / Assembly Centers: 10% - Likely upper band: 15% to 20% when CLARK contributes more capital or strategic support - Ownership can be sold down over time and recycled into newer centers ### Capital Recycling CLARK may eventually sell down selected equity positions and redeploy proceeds into newer nodes, increasing capital efficiency over the life of the network. ### Innovation Incentives Nodes that originate platform IP may receive defined participation rights tied to the licensing income from that IP, aligning local innovation with network-wide growth. ### Purchasing Leverage Consolidated purchasing across nodes may become an additional source of customer savings, margin improvement, or platform revenue if the network reaches sufficient scale. ## Operations - Founding team roles: Platform strategy, node development, capital formation, industrial sales, software and IP architecture, operational quality oversight, and training partnerships. - Early hires: Network operations lead, customer development lead, training and quality lead, software tools lead, and cross-border logistics coordinator. - Core systems needed: Licensing framework, IP registry, quality documentation, training curriculum, brand standards, CRM, logistics coordination systems, and secure collaboration infrastructure. - Legal and compliance considerations: Cross-border trade, export controls, defense-adjacent procurement requirements, corporate structure, minority investment governance, licensing enforcement, and the Hamilton training / Niagara Assembly co-location structure. ## Financial Model Assumptions - First revenue: IPC training and train-the-trainer revenue should come first, before assembly and platform-fee revenue are meaningful. - Year 1 revenue mix: Weighted toward IPC training, Clark Courses, and early operating services rather than mature platform fees. - Year 2 revenue mix: Increasing contribution from partner-facility assembly services, firmware-sensitive operating support, platform licensing, software, training, logistics fees, and greater node throughput. - Hamilton beta economics: Use a simple facility-cost model with fixed monthly charges by delivered-course band and a modest post-instructional-cost revenue share to Niagara Assembly. - Gross margin: Mixed profile depending on direct training and service revenue versus higher-margin platform revenue streams. - Burn: Front-loaded due to node launch support, software and operating systems, business development, training setup, and logistics setup. - Runway target: Sufficient to prove the training-first launch, corridor economics, and the transition into recurring platform revenue. - Primary first-12-month goal: Replicability of the model matters most, while still producing real training revenue and direct regional upskilling. - Incentive treatment: Canadian and New York incentive programs may help some eligible work, but the current raise story should not depend on project-specific incentive capture. ## Risks | Risk | Why It Matters | Mitigation | | --- | --- | --- | | Customer demand risk | The market may value regional precision capacity but not enough to support the full platform economics. | Validate willingness to pay, buying criteria, and repeat demand through anchor-node contracts. | | Training concentration risk | The first revenue layer may depend too heavily on one geography or one partnership path. | Use the Hamilton site to prove demand quickly, then transition toward more distributed training capability. | | Structure risk | The split of responsibilities between CLARK and Niagara Assembly could create operational ambiguity. | Define the co-location and shared-facility model contractually before launch. | | Execution risk | Coordinating quality, software, training, logistics, and local operators is operationally complex. | Standardize processes early and keep initial expansion narrow. | | Competitive risk | Established EMS providers, specialty shops, or training providers may respond aggressively. | Focus on the integrated three-pillar model and the corridor wedge. | | Capital risk | Node formation and platform buildout may require more capital than expected. | Use phased node launch criteria and structure capital with aligned local operators. | | Evidence risk | Several claims about incentives, corridor advantages, and competitive white space remain under-sourced. | Move factual claims into the research log and validate before using them in fundraising. | | Scope risk | Software tools, logistics infrastructure, and adjacent concepts can expand faster than the core model can support. | Keep Dunkirk as a later option, keep workforce housing out of scope, and prioritize the minimum platform needed to prove the first corridor. | ## Milestones ### Next 90 Days - Validate the first beachhead customer segment. - Build the first bottom-up corridor market map. - Define the Hamilton training-facility agreement with Niagara Assembly covering space, equipment access, revenue sharing, and liability splits. - Secure train-the-trainer or equivalent support path through EPTAC in Markham, Ontario. - Publish the first Clark Courses launch set and pricing approach for early cohorts. - Define the initial ownership, governance, and fee model for Assembly Centres / Assembly Centers. - Form the beta-phase Advisory Group for the Hamilton Training Facility. - Keep Dunkirk out of the core proof case unless warehousing economics become decision-ready. ### Next 12 Months - Launch Hamilton training operations and generate first revenue from IPC certifications and related training activity. - Launch the first Clark Courses public and private cohorts. - Deliver direct upskilling for regional companies and near-graduation students. - Operationalize Niagara Assembly and Buffalo Assembly as reference nodes. - Validate the first production programs that prove the corridor thesis. - Launch the first shared training, software, and logistics systems. - Prove the multi-layer revenue model in practice. - Revisit Dunkirk only if corridor volume justifies a dedicated logistics asset.