LoveTypes
A quiz and a book about how people love, in two languages. The product is self knowledge, so every screen had to feel like it is already talking about the reader.
Scroll the design.
The notes follow you down the page. Each one explains why that part of the screen is built the way it is, and what it is doing to the person looking at it.
The visitor is the subject
Know your type. The headline is about the reader, not about the author, and self relevant information is processed deeper and remembered longer. The book covers sit beside it, which is where the authority comes from without a paragraph of credentials.
A free door and a paid door
The quiz costs nothing and the book costs money, so the free one leads. Announcing the app as coming also buys patience, because people wait for things they have already been told about, and waiting keeps them on the list.
Three steps, drawn before they start
Take the quiz, meet your type, find your match. Showing the whole path in advance removes the fear of an endless questionnaire. Effort feels smaller once it is countable, and three is short enough to feel finished before it begins.
Proof from people like you
The testimonials sit directly before the offer returns. A quote works when the reader recognises themselves in the person saying it, so these are readers rather than experts, placed at the exact moment doubt usually arrives.
The cheapest ask goes last
Whoever did not buy the book and did not finish the quiz is offered something free at the very end. An email address costs the reader almost nothing, and it keeps a conversation open that would otherwise close with the tab.
Nothing here is a default.
Every spacing value, type size and pause in this layout came out of testing rather than taste alone. The same system has been run through enough builds, rewrites and split tests that the guessing part is mostly gone: what stays is what kept working.
The copy is treated as part of the interface, not as filler poured in at the end. A heading is a promise, a button is an instruction, and a paragraph exists to remove one specific objection. Where the project sells something directly, the checkout path is designed first and the decoration second, because an extra step before payment costs more than any visual ever earns.
Want this kind of thinking on your website?
Two sentences are enough to start. What you sell, and who you sell it to.
You get an honest answer on whether a website solves your problem at all, what it would cost, and how long it would take. No pitch deck, no discovery call that turns into a sales call.