Daniel González ES

Web designer & builder · Psychology

I design pages around how people actually decide, then build and ship them myself.

Psychology student, former high-volume poker player, and the person behind PokerStudy: a bilingual web app I designed, wrote and shipped end to end, with AI as my build partner.

ES + EN
landing and app, live
0.5 s
median LCP, Core Web Vitals green
1 person
copy, design, code, deploy

Case 01 · Live · pokerstudy.app

Selling “study” to people who would rather be playing

The landing page for PokerStudy, a training app for poker players. Launched quietly on 14 October 2026, in Spanish and English.

  • Copy
  • Visual design
  • HTML/CSS
  • SEO
  • i18n
  • Performance
PokerStudy landing page hero: 'That hand you lost last week. Did you study it, or forget it?'

The problem

Poker players already have solvers that tell them the right play. What they don't have is a way to remember it at the table. But “study more” is a hard sell: it sounds like homework.

Decisions, and the psychology behind them

  • Lead with a loss, not a feature. “That hand you lost last week. Did you study it, or forget it?” Every player has that hand. Loss aversion does the selling; the product is the answer.
  • Show the real thing. The hero background cycles through real app screens, not illustrations. People trust what they can already see working.
  • Remove the risk of trying. “No card needed” next to every button, a free plan with no expiry date, and an FAQ that answers the real fears (“What happens to my data if I don't pay? Nothing is deleted.”).
  • Scarcity, but honest. A founder price for the first 100 subscriptions, stated with the exact number, so it is a real offer and not a fake countdown.
PokerStudy landing page on a phone

Built for speed and search

Plain HTML and CSS, no framework, WebP screenshots in desktop and mobile sizes, and cookie-free analytics. Separate Spanish and English pages with hreflang, a sitemap and Search Console.

What happened

512 ms
LCP, median (p75: 836 ms)
Green
all Core Web Vitals (LCP, INP, CLS)
72
visits in the first 7 days, before any promotion (some of them mine)

Honest note: the page is days old and hasn't been promoted yet, so there is no conversion rate worth quoting. I won't invent one. The first public launch posts go out this week, and I'm measuring visit → sign-up by language.

Case 02 · Shipped 19 October 2026

The first five minutes: sign-up and “Start here”

Early users told me the same thing: “it's hard to see everything at once”. The app has a lot in it, and new accounts didn't know where to begin.

  • Onboarding
  • UX writing
  • Product design
  • Front end + back end
  • Analytics
'Start here' checklist with three steps: create your first range, review it for 2 minutes, come back tomorrow (Spanish interface)
Spanish interface. The English one reads: “Create your first range · Review it: 2 minutes · Come back tomorrow”.

A checklist that ticks itself

  • Three steps, not a tour. One tiny first action (“Review it: 2 minutes”) instead of ten tooltips. A small first win lowers the cost of starting.
  • Step 3 is the habit. Spaced repetition only works if you come back, so “Come back tomorrow” is a step in its own right, with the reason next to it.
  • It reads real data. Steps tick themselves when you actually do them; nobody has to tick a box. The progress bar uses the goal-gradient effect: people speed up as they near the end.
  • It gets out of the way. It hides itself when done, and can be dismissed at any time.

A founder list without pressure

The sign-up form explains the founder price in one sentence and offers an unticked checkbox. No pre-ticked consent, no dark patterns: if someone joins the list, they meant it. It can be changed later in the account settings.

How it's measured

An SQL query reports how many new accounts reach each of the three steps and how many join the founder list. Only totals, no personal data. The numbers start this week.

PokerStudy sign-up form with an optional 'I want to be a founder' checkbox

Case 03 · Spec work, not commissioned · Reviewed 19 October 2026

Bolt Pharmacy: four small gaps between promise and page

I went through boltpharmacy.co.uk as a first-time visitor on a phone: home page, plans, and the first screen of the consultation. Bolt does a lot right. These are the places where, as a visitor, I felt the page and the promise drift apart.

  • CRO
  • Copy
  • Pricing UX
  • Regulated health

What already works

  • The BMI slider. It opens on a realistic example that shows “Likely eligible” before you've typed anything, so the visitor sees a yes before being asked to commit.
  • Proof you can check. Every regulator badge links to its public register. That beats “trusted by” logos in a category full of fear of fake pills.
  • Weekly pricing and a fair cookie choice. £/week makes the cost easy to picture, and Accept and Reject are given equal weight.
Bolt Pharmacy home page hero, with markers 1 and 4 1 4 4
Home page hero. Markers refer to the hypotheses below.
  1. “Fair, transparent prices”, but no price

    Seen: the hero promises transparent prices; the first figure appears one click away, on the plans page (from £19.75/week).

    Why it matters: someone comparing online pharmacies has one question first. When it goes unanswered, “transparent” starts to feel like a claim rather than a fact.

    Test: one line under the hero button, e.g. “Plans from £19.75/week · cancel anytime”, with no drug named, worded with compliance. Watch: hero click-through and consultation completion, so it doesn't just add price-shoppers.

  2. “3 minutes” meets “16 questions”

    Seen: the home page sets the frame “a few quick questions… 3 minutes or less”; the consultation opens with “Answer 16 short questions”.

    Why it matters: both are probably true, but the second number arrives right at the moment of commitment and feels bigger than promised. A broken expectation is more costly than a long form.

    Test: say both everywhere, “16 short questions · about 3 minutes”, and show progress as you go. Watch: consultation start → finish rate.

  3. What does month two cost?

    Seen: on Subscribe & Save, Wegovy shows £19.75/week, labelled “First month”, next to £29.75 struck through and “Save £20 every month”. I couldn't find the price from month two onwards.

    Why it matters: a surprise on the second charge hurts trust more than a higher first price helps conversion, and it shows up later as cancellations, refund requests and reviews.

    Test: add “then £X/week” to each card. Watch: conversion to first order and month-two retention together, because this one may trade a little of the first for a lot of the second.

  4. Two ratings in one hero

    Seen: a floating badge says ★ 4.5; the Trustpilot line below says 4.6 from 7,770 reviews.

    Why it matters: it's tiny, but in a regulated purchase people look for reasons to doubt. Two numbers for the same thing are one.

    Fix: one rating, from one live source. No test needed.

First screen of Bolt's consultation: 'Answer 16 short questions' 2

Honest limits

I have no access to Bolt's data, so these are hypotheses to test, not conclusions. Some may already have been tested, and some wording is limited by UK rules on advertising prescription-only medicines, so every copy change here would go through clinical and compliance review first.

What I'd want to know in week one: where the drop-off sits between the home page, the plans and question 16, and what new patients say about the second charge.

AI workflow

How I use AI to design and build

I own the why

I define the problem, the user and the bar: what the page must make someone feel and do. That part stays human, and it's where psychology helps most.

AI builds with me

I work daily with Claude Code as a build partner: copy drafts, 2–3 visual mock-ups with real data, then the code. PokerStudy (React, FastAPI, PostgreSQL, two languages) was built this way.

Nothing ships unchecked

Every change is reviewed in a real browser, on mobile and desktop, in light and dark themes, before it goes live. Prototype, measure, verify. If a guess was wrong, I say so and fix it.

This site was designed and built the same way, in an afternoon.

About

Why psychology, why poker

I'm Daniel, based in Spain. I'm studying a BSc in Psychology, and before that, poker paid for my high school and my first two years of university: over 2 million cash hands, 50,000 Spins and a lot of tournaments.

Poker taught me to make decisions under pressure and to read what people do rather than what they say. Psychology gave me the names for it: loss aversion, the forgetting curve, cognitive load. PokerStudy is where I put both to work, and web design is how I want to keep doing it.

Tools: HTML, CSS, React, Tailwind, basic Python and SQL, Cloudflare, Claude Code. Learning Figma and Webflow.

Let's talk.

gonzalezpunzanodaniel@gmail.com

Remote · Spain (CET) · English and Spanish