Consulting & Teaching

A method your team keeps.

The deliverable is the method, working inside your own team — usually a simple working prototype, often a software tool your engineers keep using.

Areas

Three areas, taken seriously.

Depth in a narrow set of things beats availability in all of them. These are the three where the research background pays.

01

Power electronics & electrification

Topology, magnetics, control and the measurement work in between — from concept to hardware that has been built and measured. Where a design has plateaued on efficiency, size or cost and nobody is quite sure why, this is the work that finds out.

02

Agentic AI workflows

Where agentic AI removes real work in a company — and, just as usefully, where it does not. Design and evaluation of workflows that touch real documents, data and existing systems, with a sober read on what is production-ready today.

03

Teaching & seminars

Professional education for engineering teams and at conferences — including seminars at APEC, the IEEE Applied Power Electronics Conference (2012, 2015 and 2026).

Many projects that start as consulting mandates end up under Technology Development — a working prototype has a way of becoming a product.

Teaching

Hands on the hardware.

Teaching runs from conference seminars for practising engineers down to training on the equipment itself — wiring up a charge controller, measuring what it does, and finding out where the datasheet stops being true.

A group of trainees gathered around a solar charge controller being mounted on a wall
Hands-on training on solar charge controller installation.
The deliverable

A prototype, not a PDF.

A method described in a document is a method nobody can rerun. So the method arrives in the form of a simple working prototype — a model, a script, a test setup, a small piece of hardware — built against your real case and handed over with it.

Often that prototype is worth hardening. When it is, the mandate ends with a software tool your team owns: something that runs on your data, in your process, after we have gone. It is the same work Wattli does under Technology Development, scoped to one company.

How it runs

Three steps, and an exit.

The engagement is designed to end. If your team cannot rerun the method without us, the work was not finished.

  1. Assessment

    A short, paid look at the actual problem, at a fixed fee agreed up front: what is stuck, what has already been tried, and what a good outcome looks like in numbers. Usually a matter of days, and it ends with a straight answer about whether the rest is worth doing — including "it is not".

  2. Method transfer

    The core of the work. The method is built against your real case as a working prototype, with your engineers in the room. Where it makes sense, that prototype becomes a tool they keep.

  3. Implementation support

    Whatever it takes for the method to survive contact with your schedule: review of the first designs done without us, fixes to the tooling, follow-up measurement. Then we are done.

Fit

Worth being direct about.

A good fit

  • A design that has plateaued on efficiency, size or cost.
  • An AI workflow idea that deserves an honest technical read before a budget follows it.
  • A prototype that works on the bench and has to work somewhere considerably less forgiving.

Probably not a fit

  • Extra hands to execute a specification that is already fixed.
  • A one-page opinion to justify a decision that has already been taken.
  • Broad IT or software work outside the areas above — better served elsewhere.
Contact

Tell us what is stuck.

A short description of the problem is enough to start. Write in English or German — whichever you think in. Replies within 24 hours.

info@watt.li