# How we work — SyntaForge Canonical: https://syntaforge.com/en/process/ Language: en > This is a text rendering of the same public webpage. Use the canonical URL for citation. Private inquiry records and administrator data are never included. How we work # Start from where you are. Creators, founders and enterprise teams can start with an idea, a prototype or an existing product. [Let’s find your starting point.](https://syntaforge.com/en/contact/) A light worktable with product sketches, a T9 sample and a screenless band during a product discussion. ### I have an idea. We define the product together. ### I have a prototype. We work through the gaps. ### I have an existing product. We plan the next version or production step. ## Agree the work before we build. Creators, founders and enterprise teams can start with an idea, a prototype or an existing product. We agree what each stage should prove, then move from samples and small pilot runs to feedback, revised batches and repeat production. - 01 ### Discovery and architecture What are we building, and what needs proving first? - 02 ### Functional prototypes Does the core product work as intended? - 03 ### Validation and pilot Is the design ready for its intended use and production? - 04 ### Batch delivery and repeat production Can the agreed product be built and checked consistently? 1 ## Discovery and architecture We work on We define the user, task, wearing form and key functions together. Electronics, mechanics and software are considered early, alongside component choices, manufacturing questions and initial cost assumptions. You review Agree the first build and the questions it needs to answer. ### Stage outputs Product brief and system architecture Initial BOM cost model and design risks Scoped development plan and review milestones A light worktable with product sketches, a T9 sample and a screenless band during a product discussion. Illustrative scene 2 ## Functional prototypes We work on We bring up the electronics, integrate the display or sensors and assemble working units. The prototypes let us review software, data connections, controls and the wearing experience together. You review Review the core functions before committing to the next design stage. ### Stage outputs Working hardware and software samples Integration and functional review records Prioritized issues for the next revision A T9 terminal with two right-side buttons resting on its strap beside a development laptop. Illustrative scene 3 ## Validation and pilot We work on The test plan follows the product requirements and operating conditions. We review reliability, fitting and use, and run a small pilot batch. Feedback from users and assembly helps us refine the design and confirm the next version. You review Review the trial feedback, close the important issues and agree the next production version. ### Stage outputs Test records and design corrections Pilot build results and inspection criteria An agreed release or further-revision decision A T9 sample and strap being considered at a mechanical design worktable. Illustrative scene 4 ## Batch delivery and repeat production We work on We prepare tooling and production tests, control the released hardware and software versions, and review batches against agreed acceptance criteria. Deliveries and repeat orders follow the launch or deployment plan. We review demand, component changes and product revisions before increasing production. You review Review the batch, confirm the next order and decide when to increase production. ### Stage outputs Released production and test documentation Batch deliveries and quality records A repeat-order plan, with component and version changes recorded Four matching T9 samples in a foam tray supported by gloved hands. Illustrative scene ## Clear decisions at each stage. Scope, quantities and timing are agreed for each project after the requirements and main risks are understood. [Discuss your starting point](https://syntaforge.com/en/contact/) ## Clear agreements keep the work moving. These decisions belong in the project from the beginning. ### Component continuity Review component availability, alternative options and the way changes will be communicated. Any inventory or supply commitment is agreed for the project. ### Software and data Agree the application interfaces, device permissions and update responsibilities, including where data is sent and who operates each system. ### Quality records Define acceptance criteria and the records needed to relate a delivery batch to its hardware, software and inspection results. ### Tooling and intellectual property Record the ownership and handover terms for tooling, custom work and source materials. Identify existing technology and third-party components separately. ### Reviews and inspections Agree what the team needs to inspect, the evidence to provide and how any project or production review will be arranged.