Make a product page feel like a product page

Okay, so now this one is about really creating an Amazon style experience, right? So I think what's missing from these product pages is they need to feel like a product page. In fact, I, we go there, we don't know what we're buying. So imagine that we're buying a laptop. Imagine that we're buying, you know, some kind of you know, product, which we are, right? So what we need to have, and again, we can start with a couple, but then we add more, but we already have quite a lot of good materials and maybe do some with more, others with less. Same thing with Amazon, right? But my point here is that for every, you know, it's almost like, imagine like when I go to Amazon, what I see is I see the product description, what is there. I see the price on the right with the buy button. I see the, um, and this is the product page itself, right? Not the search results, which is kind of where we start in other, or this sort of the category navigation. But when I go to the product page, I should see, and I see screenshots. I see tons of screenshots. I should see fundamentally here screenshots of the vote, screenshots of the grant, the mandate. We have lovely screenshots that we can take, even infographics and videos and notebook LM infographics, right? Like we can add all sorts of stuff, right? The point is we need these placeholders so we can put tons and tons of examples and screenshots of actually what you get from that particular product, right? And I think that's very important, right? And Um, you know, what's the, um, you know, like what's the board version of the guidance, right? What does the mandate look like? What does the, the things look like? So it's almost like a really cool kind of like, you know, carousel style environment that we have that. And eventually, yeah, we can add videos to it. We should have product specs, right? Because again, it depends where you buy, you have different product specs. We, you know, we should have SKUs and technical details and also add a section for reviews and comments, which we're about to get very soon because, I want to sort of give this service to a lot of people and then get them to comment and do a review in exchange. We will we'll have a lot of reviews very soon, but it's okay. Like, you know, this product is Amazon that don't have stars and don't have reviews. So, so let's, um, you know, let's, um, um, you know, add the placeholder for that, which is, and it's in comments, right? So fundamentally, this should really feel like an Amazon or e-commerce, typical e-commerce kind of page, right? Um, and of course, that some of these data eventually should come from riskmandate.ai, but we can create it for now and then add it. And again, this becomes very product specific. And every time we add a product, we add one of these, right? And, and fundamentally, that's what we're selling, right? And, and I think this will um, really make a massive difference. And again, start by creating prototypes of this on the side, and then we review it, and then we, we wire it up, right? And but I think this will really make a difference. And again, starting with the four product lines, and eventually we should be also customizing this to the audience, right? Because again, the audience, if you think about it, these screenshots should be different depending on the audience, because you know there's more technical audience, less technical audience, so this becomes everything. Um, and it's it's almost like different editions, like you know when you know when you have a, a product that has different colors or different sort of features, uh, or you can flick. You know, do you want this in blue and red, etc.? And here it's almost like, do you want it? In, you know, do you want this for the startup founder? Do you want this for the investor version? Do you want this? So you should be able to switch also easily, um, depending where you are, right? So you should be able to see your you know the different audiences and different kind of mini SKUs, almost like the product has.

The diagnosis is blunt and it is right

“We go there, we don’t know what we’re buying.” A level page on this store argues about what a policy is. A product page shows the thing. Those are different documents and the store has only ever written the first one.

Screenshots are the substance, not decoration

“Screenshots of the vault, screenshots of the grant, the mandate… what does the board version of the guidance look like.” Every one of those exists already — the synthetic run alone produced 43, and the review pages embed a live vault. What is missing is a place on a selling page to put them.

Specs and SKUs, because a product has them

The store has 62 of them and prints none. Stripe is about to need the catalogue anyway, so the spec block and the rail's product list are the same data.

Reviews, with the emptiness admitted

“There’s no product on Amazon that doesn’t have stars and reviews.” The memo asks for the placeholder now and says the reviews are coming, given away in exchange for comment. An empty review section that says it is empty is this site’s house style — it is what the two upper levels already do about never having been sold.

Editions, which is the five-audience memo arriving from the other side

“Do you want this for the startup founder? Do you want the investor version?” Framed here as a product variant rather than a separate path — same switch, same data, on the product page instead of at the front door. The two memos want one mechanism.

Prototype first, and there is already a place for that

“Start by creating prototypes on the side, then we review it, then we wire it up.” /lab/ is exactly that surface: five prototypes of one flow, every one of them stating on its own face that nothing there can be bought. A prototype product page belongs there and inherits that protection for free.