01
AI Consulting & Engineering Automation
Workflow automation and pragmatic AI tool adoption for engineering teams — automated verification pipelines, scripted tooling, and structured processes that remove manual bottlenecks from development.
AI Consulting & Engineering Automation · Zurich, Switzerland
AI-driven automation for teams shipping hardware.
Workflow automation and AI-assisted tooling, backed by deep embedded hardware, firmware, and PCB expertise for IoT teams, hardware startups, and product engineers — delivered remotely.
Independent AI & engineering automation practice
AI ConsultingEngineering AutomationEmbedded SystemsRemote Support
When to engage
Engineering friction that slows teams down
Perri Engineering steps in when manual workflows or embedded complexity block product development. These are the problems that cost the most to leave unsolved.
Engineering workflows slowing iteration
Manual test processes, missing CI for firmware, or qualification pipelines that take days instead of hours. Automation and AI-assisted tooling can close these loops faster.
Unclear where AI actually fits
Interest in AI tooling without a clear picture of which parts of an engineering workflow it can safely improve — and which parts it should stay out of.
Embedded systems misbehaving
Prototypes that will not come up, intermittent firmware faults, or PCB issues surfaced after fabrication — problems where debug time gets expensive fast.
No embedded engineer in-house
Architecture decisions stalled, or a subsystem that needs specialist review before committing to fabrication, tooling, or production.
What we deliver
Engineering Services
AI-driven automation as the primary practice, backed by general embedded engineering consulting.
02
Embedded Engineering Consulting
General embedded consulting across hardware, firmware, and PCB work — board bring-up, bare-metal C/C++ and RTOS development, schematic and layout review, and structured root-cause analysis when systems misbehave.
In practice
What this looks like day to day
Four everyday situations where automation and AI tooling replace manual engineering overhead.
The Friday report nobody wants to write
- Today
- Someone exports measurement logs, pastes them into a spreadsheet, and rebuilds the same status report by hand every week.
- Automated
- Collection and formatting run as a scripted step, so the report is an artifact the pipeline produces rather than an afternoon of someone’s week.
Test runs that only happen when someone remembers
- Today
- A change lands and the full suite is run manually, days later, if at all. Breakages surface long after the work that caused them.
- Automated
- The suite runs automatically on every change, so a regression is tied to the commit that introduced it instead of turning up weeks later.
Issue reports that arrive without enough detail
- Today
- Field reports and internal tickets come in unstructured. An engineer spends the first hour working out what was actually observed.
- Automated
- A triage step summarizes each report, groups related ones, and attaches the relevant logs before an engineer picks it up.
Knowledge that lives in one person’s inbox
- Today
- Decisions, measurements, and the reasoning behind them sit in chat threads and personal folders. The next engineer re-derives what was already solved.
- Automated
- Structured, searchable documentation is written as work happens, so context survives handovers and staff changes.
How it works
From problem to resolution
A straightforward engagement process designed to get to root cause quickly and deliver documented results.
Describe the problem
Brief written summary or short call. What system, what's failing, what you've already tried. No preparation required.
Structured review
Hardware, firmware, schematic, or workflow — examined from first principles, including where automation or AI tooling fits. Root cause identified, not just symptoms treated.
Implement and test
Fixes, new firmware, layout corrections, or workflow tooling — delivered and verified. Lab measurements and test results included.
Handoff and support
Written findings, reproducible results, and documentation your team can build on. Follow-up support as the next steps progress.
Start the conversation
Ready to unblock your engineering team?
Describe the AI, automation, or hardware challenge you’re facing. Most engagements start with a brief diagnostic discussion — no commitment required.
