What to Prepare Before Asking for a Custom Electronics Quote
A practical checklist for turning a rough hardware idea into a quoteable brief.
TL;DR: A useful electronics brief does not need to be perfect, but it should explain what the device must do, where it will be used, how it is powered, what it connects to, and what outcome is needed.
The short version
You do not need a finished specification before asking for help with custom electronics. What is useful is a clear description of the problem, the environment, the signals or loads involved, the power source, and what a successful result looks like.
Start with the problem, not the solution
A good brief explains what needs to happen in the real world. That might be measuring something, switching a load, controlling a motor, replacing a failed module, logging data, or making existing equipment easier to use.
- Useful: This pump needs to turn on when the tank level is low and report a fault if it does not run.
- Less useful: I need an Arduino board with Wi-Fi and a relay.
Information that helps
- Function: What the device needs to sense, control, display, log, or communicate.
- Power: Battery, plug pack, vehicle supply, solar, mains-derived supply, or existing equipment rail.
- Loads: Motors, solenoids, relays, LEDs, heaters, pumps, or other outputs, including voltage and current if known.
- Signals: Sensors, switches, encoders, serial data, analogue voltages, CAN, RS-485, Wi-Fi, Bluetooth, or other interfaces.
- Environment: Indoor, outdoor, vehicle, workshop, enclosure, vibration, heat, moisture, dust, or chemical exposure.
- Quantity: One-off repair, prototype, small batch, or something intended for repeat production.
- Outcome: What must be demonstrated, fixed, measured, or delivered for the job to be considered successful.
Photos and sketches are valuable
Clear photos, rough sketches, measurements, connector details, and notes from failed attempts are often more useful than a polished document. They help identify physical constraints early, before time is spent designing around the wrong assumptions.
Common missing details
| Missing detail | Why it matters |
|---|---|
| Supply voltage range | Real equipment supplies are often noisy or poorly regulated |
| Load current | Output drivers, connectors, fuses, and copper widths depend on current |
| Cable length | Long wiring can change voltage drop, noise pickup, and protection needs |
| Mounting space | Board and enclosure choices depend on available volume |
| Environment | Heat, moisture, vibration, and dust affect nearly every design choice |
| Quantity | A one-off prototype and a repeatable product are designed differently |
What I usually look for first
The first pass is usually about risk. Power input, load switching, connectors, protection, enclosure space, and firmware complexity can change the shape of the job quickly. Finding those constraints early makes the project easier to quote honestly.
A simple brief format
- What are you trying to make, fix, or improve?
- What does it connect to?
- How is it powered?
- Where will it be used?
- What must it survive?
- How many do you need?
- What would a successful result look like?
Related services
Common questions
Do I need a complete specification before contacting Ryan Dynamics?
No. A rough brief, photos, sketches, measurements, and a clear explanation of the desired outcome are enough to start a useful discussion.
Can you work from an existing broken device or prototype?
Often, yes. Existing hardware, photos, measurements, and notes about what failed can be useful starting points.
Is this only for PCB design?
No. The same information helps with custom PCBs, wiring, embedded firmware, control systems, enclosures, and prototype hardware.