Requirements into circuits
Translate power, sensing, motor control, communications, protection, and user-interface needs into an electrical architecture. Select the key components and establish the BOM and interfaces before routing.
Green Shoe Garage
Electronics design & engineering
Circuits and boards built around what your product needs to do—from a breadboard proof of concept to a documented, testable PCBA.
We connect electrical architecture, mechanical packaging, firmware, and practical testing early, so the board can become part of a working product.
01 / Architecture first
Power rails, grounding, protection, signal paths, interfaces, and control logic determine whether the product can operate reliably.
Translate power, sensing, motor control, communications, protection, and user-interface needs into an electrical architecture. Select the key components and establish the BOM and interfaces before routing.
Consider battery life, power conversion, noise, ADC accuracy, EMI, RF paths, and sensor placement. Account for heat, vibration, grounding, and the effect a metal enclosure can have on wireless performance.
Coordinate PCB shape, connectors, mounting, antenna keep-outs, return paths, and component heights with the mechanical design. Plan firmware hooks and diagnostic access alongside the hardware.
Compare custom circuits, modules, and off-the-shelf parts against your cost and performance targets. Review availability, alternatives, lifecycle, and planned upgrades. Identify specialist requirements before committing to the architecture.
02 / Technical scope
Technology selection follows the requirements. The scope identifies what GSG designs, assembles, and tests and where a manufacturing partner or specialist is needed.
We fabricate suitable small single- and double-sided prototype boards in-house. Multilayer, higher-speed, and more demanding fabrication goes to a PCB manufacturing partner; surface-mount and through-hole assembly and integration can be performed in the shop. Cellular and other network choices are checked for the intended deployment.
13 services
Arduino, Raspberry Pi, BeagleBone, STM32, ATtiny, ESP32, ESP8266, nRF52, and various PLC and FPGA platforms.
Incorporating sensors for data collection, and electronic and mechanical outputs that interact with the user, the environment, or other devices.
Integration of WiFi, Bluetooth, LoRa, Zigbee, RS232 and RS485, and other protocols.
Gateways for managing data from multiple sensors and devices.
Cloud services or edge computing devices for data collection, analysis, and remote monitoring.
Surface-mount and through-hole soldering, plus low-volume manufacturing of assembled prototypes for testing.
Secure, efficient firmware written for the part you are actually shipping.
Companion applications for remote control or device monitoring.
Edge inference with Edge Impulse.
Cyber and physical assessment of embedded and Internet of Things devices. See our security lab for the full practice.
From block diagram through reviewed schematic.
Small single and double-sided boards with low-speed, low-power signals (under 1 GHz, a few amps maximum) fabricated in-house. Larger multilayer and higher-speed boards designed here and manufactured by a PCB partner such as OSH Park or DirtyPCBs. Surface mount and through-hole assembly onto third-party boards done in-house.
The two halves assembled and made to agree with each other.
◫ Try the bench
The same offline-first approach as our field instruments, shrunk to a single task. These run entirely in your browser. Nothing is sent anywhere.
Resistor decoder
4 & 5 band
Ohm's law
V I R P
Voltage divider
Vout
RC filter corner
fc
Need the full versions? The free toolkits carry 171 field instruments like these.
03 / From architecture to hardware
Each stage produces evidence that guides the next design decision. Existing hardware can enter at the appropriate point after review.
Is the architecture viable?
Development boards, evaluation kits, breadboards, an early schematic, or a rapid PCB demonstrate the core sensing, control, power, or communication principle.
Focus: Component selection, power rails, sensor approach, interfaces, and architecture risks.
What you receive: A proof of principle and a record of the remaining technical questions.
Does it work on custom hardware?
An assembled engineering board powers up, responds to peripherals, and performs the core operating modes on the intended hardware.
Focus: Schematic design, layout, bring-up, signal behavior, power stability, and peripheral tests.
What you receive: The prototype PCBA, design files, and bring-up findings.
Does it work as part of the product?
Electronics are integrated with the enclosure, mechanics, firmware, and interfaces for full workflows under controlled, realistic conditions.
Focus: Integration tests, thermal behavior, EMI risks, DFM/DFT updates, BOM refinement, and debugging.
What you receive: Integrated test evidence and changes needed before the next revision.
Can repeated samples be built and tested?
A revised board and defined programming, assembly, power-up, and test workflow prepare the design for a pilot run.
Focus: Manufacturing readiness, production tests, QA workflow, documentation, and supplier transfer.
What you receive: Production files, a refined BOM, flashing procedures, and test instructions.
04 / Bring-up & diagnostics
Test points, programming connectors, debug access, and firmware diagnostics make it easier to separate a hardware problem from a software or integration problem.
Give power rails, RF paths, analog signals, high-current circuits, and critical interfaces extra attention before committing to PCB manufacture.
Inspect parts and assembly, plan safe power-up, flash the agreed firmware, and measure the behavior of rails, sensors, peripherals, controls, and communications.
Verify mechanical fit, power, controls, connectivity, and hardware functionality after installation in the enclosure. Document configurations and conditions so findings can be reproduced.
Use manufacturer constraints to refine fabrication and assembly data, test access, component alternatives, and production checks. Coordinate external tests when the scope calls for them.
Hardware prototypes can include focused diagnostic or demonstration firmware. For complete application behavior, companion apps, cloud connections, or update mechanisms, see Firmware & software.
05 / Your next build
Your agreed deliverables make the design understandable and transferable to the next engineer, assembler, or manufacturing supplier.
Ownership and licensing are defined in the engagement, including third-party components and software. Explore how we scope the work.
Ready when you are
An idea, a drawing, a stubborn problem, or a prototype that needs another set of eyes. Tell us where you are and what you need to learn.
Schedule a consultation