About

Technology has to reach the market, not just work

My name is Przemysław Wilde. I run technology products and make sure they reach the market polished, not merely finished. I bring the same reflex to artificial intelligence. Engineering sits in the background, and it makes sure every promise can be backed with numbers.

  • 8+years in product
  • 50+products on the market
  • 300+partners trained
  • 126blog posts
Przemysław Wilde
Product manager · AI and new technology · electrical engineer

For the past eight years, I have been working at the intersection of product, technology, and business in building automation and IoT. I am responsible for developing the product portfolio, setting its direction, and turning market needs into clear business decisions. I introduce new solutions to the offer, develop existing product groups, and prepare sales teams for successful product launches.

An electrical engineering degree (Silesian University of Technology) taught me one thing: before you recommend or deploy anything, do the maths and check it. That turned out to matter more than the rest of the syllabus. It lets me talk to engineers without an interpreter, and it stops me making promises I cannot back with data.

Outside work I am drawn to artificial intelligence and what it really changes in day-to-day work. We all hear the announcements; I care about what is left after a month of use. I live in Jastrzębie-Zdrój, and off the clock I am a husband and a father. This blog is where I test things on my own and write down how they turned out. I run my services — consulting, installations and training — under a separate brand, TECH.WILDE.

  • Artificial intelligence and new tools in daily work, not in slide decks
  • Eight years in technology products, mostly building automation and IoT
  • I build small tools after hours and write down how they turned out
  • Electrical engineering in the background, so I talk to engineers without an interpreter
  • Motto: technology has to reach the market, not just work
My path

From wiring diagrams to product decisions

  1. Foundation

    Electrical engineering at the Silesian University of Technology. It left me with a reflex I still cannot switch off: do the maths before you say anything.

  2. From engineering to the offer

    Building automation, IoT and energy, first from the technical side. Then I started deciding which of those solutions made it into the range at all, and why that one.

  3. Product and market

    Product groups that grow with the market, in Poland and abroad. Hundreds of conversations with partners along the way, and plenty of training rooms. Trade fairs still teach me the most: two minutes there and you can see whether someone understands what the product is for.

  4. Today — 126 posts and a bit more

    I have been writing the blog since 2020. Artificial intelligence took over enough of my daily work to become the main subject of these pages. After hours I also build small tools you can open and try right here.

How I work

Four rules you can see on the blog

Plain language, no jargon

Technology should serve people, not intimidate them. I explain things so anyone can follow, even when the subject is hard.

The technical language trap

One product, four perspectives

The same feature means something different to an installer, an end customer, a salesperson and an architect. Miss that and you sell a spec sheet instead of a solution.

The same feature, four different questions

I measure before I advise

Measurements and numbers first, conclusions after. Also when the numbers spoil a nice story.

The role of data in decision making

AI on purpose, not on hype

I show real uses of AI and the hygiene of working with it — no hedging and no magic.

Prompting and digital hygiene
Experience

What working with products taught me

The best lessons come from talking outside the office

A salesperson, an installer and an architect will tell you three different things about the same feature. Only together do they add up to a picture of the product. That is why I spend far less time over a datasheet than with the people who work with the product afterwards.

Market first, roadmap second

I take the direction from wherever the gap shows: customers, competitors, complaints. The best things came out when someone noticed a problem everyone else walked around.

People build reach

A company grows where it has partners, at home and abroad. A catalogue opens the conversation, but after that it comes down to trust and to whether the person on the other side knows what to do with it.

Visibility is part of the product

Trade fairs, partner training, content and search rankings. I take them as seriously as the spec, because the market will not find out on its own about a product nobody has heard of.

The tools I reach for and the training I have done are collected in the toolkit. The full career path — on LinkedIn.

Testimonials

What colleagues say

Recommendations from LinkedIn — the full text and the authors are behind the link next to each one.

He has a great feel for the market and a real talent for turning a product vision into concrete solutions. He is a genuine treasury of ideas.
Work on developing an IoT product groupFull recommendation on LinkedIn ↗
He showed a lot of organisational knowledge and creativity, which let us carry out the plans we had smoothly.
Work on sales and training projectsFull recommendation on LinkedIn ↗
Przemysław is an expert in his field and, on top of that, a great enthusiast of building automation, electrical engineering and everything else he works on professionally.
Work on products and distribution in building automationFull recommendation on LinkedIn ↗
Przemek is a very ambitious, thorough and responsible manager. His curiosity about the world and about new technology is a huge asset.
Work on developing the product range for automation systemsFull recommendation on LinkedIn ↗
Common questions

Before you ask

What does a product manager in building automation actually do?

Stands in between. On one side the engineers and what can be built, on the other the market and what someone needs. My job is to bring those two sides together, then to make sure the result reaches someone who knows what to do with it.

Why does an electrical engineer care about AI?

Curiosity. I wanted to see what it can really do before I believed the promises. Today AI sits inside my daily work: data analysis, materials, prototypes. Most posts on this blog come out of those attempts.

Did you really write the tools on this site yourself?

The assumptions, the scope and the checking of results are mine; AI helps a lot with the code. I say so openly on every tool, because if I teach people to use AI deliberately, I should show where my work ends and the machine starts.

Want to talk, or invite me to speak?

Talks, expert comment, podcasts and a plain exchange of experience: the easiest way to reach me is LinkedIn or the collaboration page. I run consulting, installations and commercial training under a separate brand, TECH.WILDE.

Look inside the toolkit

The tools I reach for every day and the training I have done. All in one place, with links to the posts where I put them to work.