Also some feedback from me:

1)It tells me what it does and how it works. But what I want to know in the first place is why. Why would I need it?

2)https://imgur.com/a/kuZC3 here I would switch the order from left down and then right down, because the smart phone in the middle spaces this like a book, so I initially read the left side first, then the right side (1/3/2/4). Only then I realised the actual order.

3)Also I do not really understand its purpose.

PS: I am also unfortunately not in your target audience, but wish you the best luck!

I think the description above the fold should be more detailed about the purpose than just making things "smart".

I also doubt that whoever randomly comes across a tagged object will want to install your app to contact the owner, so I hope you're making sure that the QR code points to a website that can be used without the app.

But I'm not a potential customer, so if you have actual user studies then ignore what I said.

I like it! Just chiming in to say that, to oppose all the nay-sayers you'll always get on HN. I think I heard a similar concept pitched on a Startup Weekend once. The problem then was to make it so easy to use (seems you're on the right path there), maybe even without having to scan the QR code (add a 'Get in touch with my owner right now: ottomon.net/3az4xy' under the QR code, or something).

And to repeat what the other commenter said, why wouldn't you just print your phone number or email on there? Privacy is the biggest (only?) reason, I guess. Maybe you should focus more on that on your landing page. You want people to contact you if you parked someone in, but you don't want them to know your name and show up at your house at weird times just because they wanted to be friends with 'that guy with the expensive car'. People are weird.

How will you make it profitable, though? Only obvious thing I'd pay for is to get a nice pack of customized stickers/iron-on-patches/etc in various sizes.

Looks interesting.

One small piece of advice. Get rid of the three small steps selling point. From a developer perspective, you think you're explaining that the concept is simple and easy to use. From the end user stand point, they go: ugh, multiple steps. The end user's brain begins to shut down and moves into rejection mode right then and there. Steps = hassle, memorization, fear of screwing a step up, complication. It doesn't matter how many steps.

So in the three simple steps section:

Header: How Ottomon Works [have that be the bold text]

Drop the three simple steps part.

Under the header, turn it into two actions, even if in your mind it's really three steps. It's:

Place QR Code <-> Scan QR Code

If you need to include text about communicating with the owner of the code, put it in the last segment about scanning the QR code.

It's not: step 1, step 2, step 3, step blah.

It's: place codes, scan codes.

It looks interesting. But why would I use this rather than, say, a QR code with my email or phone number on it?

The code on this website is invalid when I scan it - https://blog.ottomon.net/blog/what-is-ottomon - make your demos work :-)

Looks interesting, I think this could be useful in cheap inventory management. Have you validated the idea with somebody ready to pay you actually? I think you need some pitch stories to explain use cases better. I needed a minute with "About us" and here on HN comments to figure out what you offer.

Congrats, you just launched :)