Skip to content

/ueber-mich

About

My name is Philipp Staudt. I am a software engineer and IT consultant — for over a decade I have been building systems at the intersection of software, hardware and data.

My first contact with IT was a game — specifically, a Snake clone in Delphi. After that came Space Invaders, a handful of small browser games, and eventually a Computer Science degree at Saarland University in Saarbrücken. Today I build business software — but the reflex is the same: watch your own lines change how the machine behaves.

What I like building are systems that remove real friction: IoT fleets that do not lie; internal tools your team can still own in five years; integrations between systems that were never meant to talk. Industries change — the pattern stays the same.

Years of software development
10+
Point of contact — start to finish
1

How I work

Three steps. No surprises.

01

Honesty over revenue

If off-the-shelf software solves your problem better, I will say so — even if it costs me the engagement.

02

Readable code over tech-flex

Maintainability beats the latest framework. Your team has to work with this in five years.

03

One person, one point of contact

You get me from first sketch to handover — no rotating consultants, no escalation hotline.

04

Documented as you go

Code, architecture, operations. If I get hit by a bus tomorrow, your team can keep going.

04 Common questions

What clients usually want to know.

What does the collaboration look like in practice?

We start with one or two workshops to clarify the problem. After that, short regular sessions (typically weekly) and visible progress throughout — no weeks of silence. You see something running every sprint.

How much does it cost?

I bill by the hour at a fixed rate. For well-defined scope I also do fixed prices — but only when the scope can be cleanly bounded. You get a rough range after the first conversation.

Do you work solo or with a team?

By default I am your single point of contact. For larger projects I bring in specialists from my network (design, infrastructure, data) — always with your approval and transparent billing.

How quickly can you start?

Typically two to four weeks after sign-off. For urgent matters (production outage, security issues) I can usually start faster.

What happens after handover?

Up to you. You can run the system entirely yourselves (with documentation and handover), or I stay on a fixed monthly retainer for maintenance and continued development. No automatic contract — you decide what you need.

Which industries do you know best?

My experience is concentrated in IoT / smart devices, energy, industrial engineering and SMB SaaS. Industry expertise rarely turns out to be the deciding factor though — understanding process and architecture matters more.

Do you work remote or on-site?

Remote by default, with occasional on-site days for workshops or go-lives. On-site work for the duration of a project is possible — German-speaking region.

Contact

Sound familiar?

Send me a short note about what you are dealing with. I will respond within 24 hours with an honest assessment — even if I am not the right partner.