Getting online
Early websites, forums and hand-built layouts — learning by understanding what happened beneath the surface.
ROBERT SEEMANN · SYSTEMS TINKERER
I am Robert Seemann. I develop practical web applications and automation for small businesses and small teams where standard software leaves gaps or routine work consumes too much time.
I have been working with web technology since 1997. What began with hand-built websites grew through databases and e-commerce into structured data, automation and purpose-built browser applications.
Discuss a projectI started in the era of dial-up modems, Netscape Navigator and hand-written HTML. Limitations were normal, so understanding how things fit together mattered. That habit still shapes my work today.
Early websites, forums and hand-built layouts — learning by understanding what happened beneath the surface.
Databases, online shops and operational workflows made the web less about pages and more about processes and data.
Internal tools, automation, structured data and focused web applications that solve a concrete operational problem.
Small businesses often do not need another large software package. A rough description of what costs time, creates errors or ties up people with repetitive work is usually the better starting point.
What happens today? Which data already exists? Where do manual steps, repeated clicks or gaps between systems create friction?
I prefer the smallest sensible solution that solves the real problem cleanly over a large platform that brings unnecessary complexity.
A useful system should still make sense later. Clear structures make maintenance and further development much easier.
Web, e-commerce, data, automation, mail systems and business processes rarely exist in isolation. I like understanding the connections and making them work together more cleanly.
The label is deliberately personal. robnet.dev is not presented as a large agency: you work directly with the person who analyses the requirement and builds the solution.
My background includes a Bachelor Professional in Mechanical Engineering. It reinforced a way of thinking that suits software surprisingly well: understand components, observe dependencies, reduce friction and improve the result step by step.
Running and working with e-commerce systems adds the other side of the equation: software is only useful when it survives everyday work, changing requirements and real users.
Tell me what currently takes too much time, too many clicks or too much manual work. That is enough for a first conversation.