Skip to the main content
PicksYou

Changelog

What changed, and why

One entry per tagged release, newest first, each with the reason we shipped it. Nothing is backdated and nothing is left out: 43 releases since 27 Aug 2026.

RSS www.picksyou.com/changelog.xml, one item a release.

Major releases

All updates

  1. 5 Sep 2026 v0.24.0

    The dashboard, the month report, the fix desk, agencies and the proof property

    One release carries what the plan had numbered as five stages, because they were built and verified together. The overview shows the count with its usual range, the zero row, every question and every answer word for word, a calculator that only ever moves the width of the range, and a peers page that compares complete weeks only. Every month closes into a frozen report with a PDF and a proof link, alerts are capped at four letters a month, and a recipient can stop their own copy. The fix desk prepares changes as drafts and publishes nothing without the business's own click, recorded in a row that cannot be edited afterwards, with undo. Agencies get a workspace with clients, members, a client import, a pitch tool and per-client billing, and the client keeps the approve button. PicksYou measures itself in public at /proof as an online business, the pricing page carries a dated comparison table, and this changelog exists. The product is English only, from the interface to the invoice.

    Why we shipped this. The earlier plan tagged each stage on its own. They landed in one working tree, were verified as one, and shipping them as one honest release beats five tags on one commit. The version numbers v0.25.0 to v0.28.0 are retired; the next release is v0.29.0.

  2. 5 Sep 2026 v0.23.0

    The setup wizard, the frozen question set and one clean skin

    A claimed check now walks you through three steps: confirm the business, tick the questions we will ask, pick a plan or stay free. The set of questions is frozen the day you approve it, so a week can never be compared with a differently worded week, and every page in the product now runs on one type scale.

    Why we shipped this. You had to read a wall of settings before your first Monday. Three steps, with the questions printed in full, is what a business owner can check in ten minutes and sign.

  3. 3 Sep 2026 v0.22.1

    The new sign in notice leaves the product

    The mail that announced every sign in from a new device is gone at the root, and an account with no business on it now opens on one sentence and one action instead of an empty dashboard.

    Why we shipped this. It read as a warning about you. A security mail that fires on every phone you own is noise dressed up as care.

  4. 3 Sep 2026 v0.22.0

    Opaque identifiers and the security walk

    Every customer facing link now carries an opaque id; an old link still works for its owner and tells a stranger nothing. Twelve fixes from a security walk landed with it, including the open redirect class, limits on the forgot and reset forms, a bounded payment webhook and the content security policy switched from watching to enforcing.

    Why we shipped this. A counting id in a link tells a stranger how many customers we have and invites them to guess the next one.

  5. 3 Sep 2026 v0.21.0

    Your panel, owned

    Twenty six flaws in the account pages were fixed against a forms rulebook written from eighteen sources. The plan state of a business reads Free rather than none, the first session of a new account has an order to it, and a weeks archive and two CSV exports arrived with it.

    Why we shipped this. A panel you cannot change without writing to us is not yours.

  6. 3 Sep 2026 v0.20.0

    One identity for the whole product

    The site, the workspace, the staff panel and the mails moved onto one palette and one scale. A count is drawn in the measured face everywhere, and prose never is.

    Why we shipped this. Two type systems on one product read as two products, and a reader who has been burned by an SEO vendor notices that first.

  7. 3 Sep 2026 v0.19.0

    The WordPress plugin, WooCommerce aware

    PicksYou AI Mention Monitor reads the AI crawler hits and the AI visits on your own site and reports them to your dashboard; it changes nothing on the site. The same release wrote down what an erasure removes and what it keeps.

    Why we shipped this. The receipt that joins ChatGPT naming you on Monday to somebody arriving from chatgpt.com on Tuesday needs one line from your own server.

  8. 2 Sep 2026 v0.18.0

    The API

    Read every count, week, answer and receipt through a key you create and revoke yourself on the Account page, the same door the WordPress plugin uses. A limit per key, a limit per day, and an erasure that leaves nothing behind.

    Why we shipped this. An agency's own dashboard should be able to show a client the rows we show them, without a login of ours in the way.

  9. 2 Sep 2026 v0.17.0

    The dashboard is a working desk

    The overview leads with your count and its usual range, then with what is in the way and the minutes each fix takes. Every sampled week stays in a ledger you can walk back through.

    Why we shipped this. A dashboard that only reports leaves you asking what to do on Monday. A desk answers that.

  10. 2 Sep 2026 v0.16.2

    The owner's walk, closed

    A one week chart draws its single column inside its own box, every checklist step is a door to the thing it names, and a listing we actually saw is never described as one that does not exist.

    Why we shipped this. The owner reads this product as a stranger every few days, and his list of what is wrong beats ours.

  11. 2 Sep 2026 v0.16.1

    The check says what it measured

    A free check on a business whose trade has no question set of its own now says so, shows the questions it did ask, and prints its count against that frame instead of a confident number in the wrong one.

    Why we shipped this. A number in the wrong frame is the exact thing we promised never to print, and a reader caught us printing one.

  12. 2 Sep 2026 v0.16.0

    The account, priced and navigable in every state

    Free, active, cancelling, ended and past due: each state of a plan now prints what you pay, when it is taken and how to stop it, on every page of the account.

    Why we shipped this. The one sentence a paying reader wants on every page is what this costs and how to end it.

  13. 2 Sep 2026 v0.15.0

    Twenty nine findings from a journey walk

    Four readers walked the whole product, from the front page to the cancel button and back, as a stranger, a customer, an agency and an attacker. Every finding was fixed and re-walked before the tag, including a held invoice escaping as a PDF and a receipt mail that was lost after a hold.

    Why we shipped this. We do not get to decide that the product works. The walk decides it.

  14. 2 Sep 2026 v0.14.0

    The owner's nine, closed

    Nine items from the owner's own read of the site landed together: a rebuilt footer with two explainer pages, the labelled trust band, the sample week with the case for buying beside it, how it works as a full mechanism page, sign in doors with passkeys, and a money panel that says who told us each figure.

    Why we shipped this. A list written by the person who has to sell the thing is worth more than a list written by the people who built it.

  15. 2 Sep 2026 v0.13.1

    The craft identity everywhere else

    The results page, the pricing page, the customer panel, the staff panel and twelve customer mails all moved onto the identity the front page got a day earlier.

    Why we shipped this. An identity that stops at the front page is a costume.

  16. 1 Sep 2026 v0.13.0

    A craft identity for the site

    The winner of an internal design competition went live: a vendored type face, a warm palette, and a landing page recomposed around a real receipt with its usual range drawn on it.

    Why we shipped this. The front page has one job, which is to make a stranger believe the receipt is real before they type anything.

  17. 1 Sep 2026 v0.12.1

    Every route walked end to end

    About a hundred routes and twenty one staff sections were walked for dead ends and half finished states, and the findings were fixed: honest partial diagnostics, a banner for a run that came back with nothing, and a levelled proof band.

    Why we shipped this. A product is the paths through it, and the only way to know the paths work is to walk all of them.

  18. 1 Sep 2026 v0.12.0

    The everything polish

    One motion standard across the product, a drawn icon set through both panels, charts on the pages that had been bare tables, and legal pages telling the truth about the paid product.

    Why we shipped this. Small wrongnesses add up into a feeling that nobody is looking after the place.

  19. 1 Sep 2026 v0.11.1

    The plan cards name the assistants they buy

    Starter asks ChatGPT, Perplexity and Google AI Overviews. Growth adds Grok and Claude. The names are read from the plan itself, so a card can never promise an assistant that the plan does not ask.

    Why we shipped this. A card that gives you a count and not the names is asking you to trust a number.

  20. 1 Sep 2026 v0.11.0

    Grok and Claude join Growth

    Growth now asks Grok and Claude one pass per question on top of the base set, and the plan rows moved to €29 and €59 a month. Anybody already paying keeps the price they signed at.

    Why we shipped this. One Grok answer costs about fifteen times what a ChatGPT answer costs, so the plan that carries it is the plan that pays for it, and nobody's price moves under a running contract.

  21. 1 Sep 2026 v0.10.0

    No trials, and no promise about an outcome

    Trials and the thirty day money back promise are both gone. Weekly runs live behind a paid plan, claiming a free check grants nothing recurring, and the statutory fourteen day right of withdrawal stays exactly where the law puts it.

    Why we shipped this. We cannot promise what an assistant will say, so we stopped promising anything about it. A trial is a countdown, and neither belongs on a product whose whole claim is honest measurement.

  22. 1 Sep 2026 v0.9.5

    The closing sweep of the redesign

    The reader's own language survived on the pages nobody designs: an address that matches nothing, a page that refuses because a form was used too often, and the site checks behind a receipt.

    Why we shipped this. The pages nobody designs are the pages a reader meets on their worst day.

  23. 1 Sep 2026 v0.9.4

    One empty state, and doors written by a person

    Every empty state in the product was rewritten to the same shape: what this page is, why there is nothing on it yet, and the one thing to do about that.

    Why we shipped this. A page that says no data and stops leaves the reader guessing whether something is broken.

  24. 1 Sep 2026 v0.9.3

    A pricing table that computes itself

    The table comparing the free check with the two plans is built from the plan shapes and the same interval helper the dashboard uses. Not one number on it is typed by hand.

    Why we shipped this. A typed number is a number nobody updates on the day the roster changes.

  25. 1 Sep 2026 v0.9.2

    The staff panel gets a to-do list

    The staff panel gained a do next list, a grouped rail and keyboard review for uncertain name matches.

    Why we shipped this. An uncertain match is decided by a person, and a person deciding hundreds of them needs a keyboard rather than a mouse.

  26. 1 Sep 2026 v0.9.1

    The home page and the results page, again

    The third version of the front page and the second of the results page shipped together.

    Why we shipped this. A reader arrives on one and leaves from the other, so those are the two pages worth doing again.

  27. 31 Aug 2026 v0.9.0

    How it works becomes a page

    The mechanism moved out of a strip on the front page into a page of its own, with one label per step, and the methodology page moved out of the top bar and into the footer.

    Why we shipped this. A link into a section of another page can never be marked as the page you are reading, and the mechanism deserves more room than a strip.

  28. 31 Aug 2026 v0.8.2

    Pricing and the check form, second versions

    The pricing page and the check form on the front page were both rebuilt, and a fault in the peer comparison was fixed behind its switch.

    Why we shipped this. The form is the one thing on the front page a stranger has to use, so it gets rewritten until it is obvious.

  29. 31 Aug 2026 v0.8.1

    The footer, third version

    The footer was measured against reference sites and rebuilt: the invented facts came out and the legal row was cut back to the year and the company.

    Why we shipped this. The owner called the first one cheap, and he was right.

  30. 31 Aug 2026 v0.8.0

    The site, second version

    A top menu with pricing in it, a rebuilt footer and the count sculpture on the front page. The sign in door now tells a customer and a stranger apart, and staff got a door of their own.

    Why we shipped this. Four things the owner asked for in one afternoon, all of them about a stranger being able to find the parts of the product.

  31. 31 Aug 2026 v0.7.5

    The mark drawn at the size it was made for

    A fresh export of the owner's mark, drawn at the same height on every page, and a language menu rebuilt to hold more names than it had.

    Why we shipped this. The owner could barely see his own mark on his own site.

  32. 31 Aug 2026 v0.7.4

    The door on the front page

    The front page shows Sign in to a visitor and the way into the workspace to a customer.

    Why we shipped this. Customers had no way in from the page they land on, which is the page they had bookmarked.

  33. 31 Aug 2026 v0.7.3

    Error pages worth reading

    Six designed error pages, each one saying what happened and where to go next, with the code drawn as the page's own figure.

    Why we shipped this. A dead end with a number on it is where a reader decides whether anybody is home.

  34. 31 Aug 2026 v0.7.2

    Hotfix: deleting an account was refused

    Account deletion failed on the live database because a restore token did not fit its column. The column was widened, and MariaDB joined the test gate that runs before every ship.

    Why we shipped this. The fault could only exist on the production database, so the gate now runs on the production database engine too.

  35. 31 Aug 2026 v0.7.1

    Hotfix: a staff page threw an error

    A staff page read a database column by a name it no longer had and answered with an error. Renamed, and pinned by a test.

    Why we shipped this. It was live for a few minutes. A hotfix is an entry here like anything else.

  36. 30 Aug 2026 v0.7.0

    The design rework, and the owner's logo as drawn

    Both panels moved onto one sourced card contract, the owner's logo went in as he drew it, and the VAT setting moved to the small business mode the company is registered under.

    Why we shipped this. Two panels drawn two ways read as two products, and the tax setting has to match the paperwork rather than the code.

  37. 30 Aug 2026 v0.6.0

    Production polish, and eight mails written

    The staff and customer panels were rebuilt, the findings of a payments audit and a mail audit were fixed, eight mails were written, and billing was made ready for a live key.

    Why we shipped this. The week after money ships is the week to fix what money exposed.

  38. 30 Aug 2026 v0.5.1

    The prices move, and the owner gets a staff account

    The two plan prices moved to €24 and €45 a month, and the owner's staff account was created with its own door into the panel.

    Why we shipped this. The first prices were set before the vendor bills came in. The second set was made after them.

  39. 30 Aug 2026 v0.5.0

    Money: plans, checkout, dashboard and account

    Monthly plans through Mollie, a checkout, a customer dashboard and an account area. The staff side of the billing shipped with them.

    Why we shipped this. A weekly measurement nobody can buy is a demonstration. This is the release that turned it into a product.

  40. 29 Aug 2026 v0.4.0

    The front rebuilt to a written rulebook

    Every public page was rebuilt on one written design rulebook: one type scale, one palette, one set of components.

    Why we shipped this. A page assembled by eye drifts from the last one. Written rules mean the next page starts where the last page finished.

  41. 28 Aug 2026 v0.3.0

    The free check opens

    Type a business and a town, and the question list goes to ChatGPT, Perplexity and Google AI Overviews. Every answer comes back word for word with the name marked where it appears.

    Why we shipped this. The first thing a business owner should see is the answer itself, not a number about it.

  42. 27 Aug 2026 v0.2.0

    The sampling engine

    The part that asks an assistant a question and writes down what came back, with a seam behind it so a new assistant can be added without touching anything else. Every call records what it cost.

    Why we shipped this. Everything this product says about a business comes out of a stored answer, so the store of answers was the first thing to build and is the last thing we will change.

  43. 27 Aug 2026 v0.1.0

    The first live skeleton

    The application went up on its own server with the database, the queue and the deploy path in place, and nothing else on it.

    Why we shipped this. We would rather deploy on the first day with nothing in it than find out on launch day that the deploy does not work.

A release is a tag on the code, and an entry here is written the day the tag is cut. Hotfixes get an entry too, and a fix that undid one of our own mistakes says so.