We took the game out of the page that sells the game
The product page had a heads-up display, experience points and quests. It was rewritten wholesale, and the hero was retuned twenty-nine minutes after it shipped.
The product page used to be gamified. It had a heads-up display, an experience bar, quest framing, the full apparatus. Which made a certain sense, since the product itself is gamified and the page was demonstrating the idea by being the idea.
On 2026-08-13 at twenty past midnight it was rewritten from scratch. Three files, all replaced wholesale: the template, the stylesheet and the script. Roughly 1,700 lines in and 1,300 out.
What replaced it is a tour. The CRM underneath, with a mock you can click through. Workspaces and tone-of-voice profiles. Analytics. The signals feed and the contact scraper. Sequences and the dialer. The enrichment waterfall. The call recorder. The email engine. The API and its machine interface. Then what else is included, what is coming, and a call to action.
Less arena, more receipts.
Why the game was the wrong pitch for the page
The gamification is real and I still believe in it. Sales is a ranked competitive activity whether or not the software admits it, and the experience bar in this product is attached to things that actually matter: contacts added, stages advanced, meetings booked, deals closed.
But a marketing page has one job, which is to answer the question a stranger is actually asking. The stranger is a sales professional with a quota and an existing CRM they resent. Their question is "what does this do, and is it better than what I have."
A page that opens with a heads-up display and an experience bar answers a different question, which is "what does this feel like." That is a good second question. As a first one it reads as a toy, and toys are a hard sell to somebody whose income depends on their pipeline being accurate.
The other problem is subtler. A page that performs the gamification is implicitly claiming that the gamification is the product. It is not. The product is a CRM with agents attached, and the game layer is how it feels to use, which is a real differentiator and a terrible lead. Nobody switches CRMs for confetti. They switch and then discover the confetti is unexpectedly motivating.
So the page now shows the machinery and lets the game be a section rather than a frame.
Twenty-nine minutes
That evening the homepage hero changed too, and the sequence is a good miniature of how design decisions actually resolve here.
The old hero was a fake screenshot of a database. Nobody has ever been fooled by a fake screenshot of a database, and the honest thing to do with a product whose value is not visual is to stop pretending otherwise. It was replaced at 20:19 with an animated circuit cube, ported over from the design sample onto a dark device panel, the way it had been designed.
At 20:48, twenty-nine minutes later, the panel was deleted and the cube now draws straight onto the cream background.
The commit attributes the change to Tyler's call after seeing the sample in place, and the retune is more than a background swap. Additive blending, which makes glowing things glow on a dark ground, washes everything to white on a light one, so those blends became normal. The scanline overlay and the screen-wash effect were switched off, because both are simulating a display, and there is no display any more. The alpha on the edges, traces and mark roughly doubled, because thin bright lines that read clearly against near-black disappear against cream.
That is the part people underestimate about moving a visual from dark to light. It is not a colour inversion. Every effect that was doing the work of suggesting depth was relying on the darkness, and each one has to be reconsidered separately.
There is a lovely piece of browser trivia buried in that commit. The cube draws text into a canvas using a custom font. Canvas text drawing does not trigger a lazy font load the way ordinary page text does, so the font simply is not there when the first frame renders and you get a fallback typeface. The script has to explicitly ask for the fonts before it starts drawing.
The link previews had never worked
The smallest commit of that stretch fixed the most embarrassing problem.
The site had been specifying social preview images since the marketing shell was built. Neither image file existed. Every share of this site, on every platform, for months, had rendered as a grey box.
That is the perfect example of a bug that cannot be found from inside the product. Nothing renders it. No page shows it. No test covers it, because the test would have to be "does this file exist," which feels too stupid to write until the day you learn it was not true. You find it by pasting your own link into a chat with somebody, which is a thing founders do constantly and evidently had not.
The preview image was then rebuilt twice in forty-five minutes, because the first rebuild still showed the old dark panel that had been deleted half an hour earlier.
The final commit in that run leaves a note for the future which I have already used twice: preview caches on messaging platforms are keyed per URL, so after changing a preview image you have to share the link with a junk query parameter appended to force a fresh fetch. Otherwise you spend twenty minutes convinced your fix did not deploy.
One small absurdity to finish on. The rewritten product page shipped on 2026-08-13 with a glass ticker element in its hero, a stylised stock ticker, as decoration.
Forty-six hours later we deleted the real stock ticker from the product entirely.
— DealArena Team