MYBC · 2026
A casino rebuilt around the first deposit
MYBC is an international online casino and sportsbook. I measured where players got stuck, rebuilt it as a clickable mock, and moved it live piece by piece.
- Category
- iGaming · Product redesign
- Role
- Design & Marketing Lead
- Timeline
- This redesign: August to September 2026, at MYBC since December 2025
- Team
- Me, with the MYBC developers reviewing and merging
- Stack
- SvelteKit · Amplitude · HTML mock
- Status
- Live
- Client
- MYBC (employer)
- Problem
- Only 1.2% of new players made a first deposit within a week.
- What I did
- I ranked 137 problems in Amplitude, rebuilt the product as a 30 page HTML mock, and moved it into the live SvelteKit front one reviewed piece at a time.
- Result
- First-time depositors up 48%, 80 vs 54, Sep 18 to 20 against the same days a week before, on 17% fewer visitors.

01 Problem
A yellow casino that grew fast and broke often.
Only 1.2% of new players made a first deposit within a week. KYC rejected players without a reason, and USDT opened on the wrong network.
02 Constraints
- 01
A live SvelteKit product the MYBC developers own: every piece went to them for review before it shipped.
- 02
Only what runs on real data with real handlers could ship. No mock numbers, no dead buttons.
- 03
Games blocked per country, and payment marks that change by country.
03 Approach
Measure first, build it clickable, then port it.
I ranked 137 problems in Amplitude, rebuilt the product as a 30 page HTML mock, then moved it into the live front piece by piece.
- 01
One goal: first deposit
Every screen answers one question: does it move a new player to the first deposit?
- 02
A cashier, two doors
Deposit opens straight on Card or Crypto, and USDT now defaults to BSC.
- 03
One art style
14,834 of 15,884 live games now carry the new card art, 93%.
From this to this
Before · Next.js
After · SvelteKit
The yellow Next.js front, home page, against the live SvelteKit home after the port.
04 What I got wrong
Three ways to shrink the page. All three rejected.
My first three responsive passes zoomed the page, then the content, then scaled the thumbnails. Each made cards smaller at the widths people use. Now cards keep their size and a row shows only whole cards.
When a layout fails between breakpoints, change what is shown, not how big it is.
05 Results
What moved.
- +48%
- first-time depositors, 80 vs 54Sep 18 to 20 vs the same days a week before, the three days right after the new first-deposit hero and the cashier release, on 17% fewer visitors and a better traffic mix. Not a read of the whole redesign.
- +40%
- deposit volume, $30,970 vs $22,162Sep 18 to 20 vs the same days a week before, $30,970 against $22,162. Same caveats as the depositor count: 17% fewer visitors and a better traffic mix.
- 29%
- of card tab opens deposited within an hourOne day, Sep 18: 62 of 212 card tab opens ended in a deposit within an hour, against 9 to 17% on the old cashier.
- 10.1%
- of hero banner clickers deposited within a daySep 18 to 21, one-day window: 87 of 865 banner clickers deposited, and 52% of the 865 opened the cashier. No earlier baseline: the banner was new on Sep 17.
In context
06 Role and team
- Owned
The Amplitude research and the ranking of 137 problems, the 30 page HTML mock, and the port of each screen into the live front.
- Influenced
What the team worked on first: one goal, the first deposit, and every problem ranked before it got a screen.
- Built with others
The MYBC developers own the live codebase. They reviewed and merged every piece, and kept shipping their own releases alongside.
The redesign is not finished, and these numbers cover a few days, not a clean test. The method stays: measure, build it clickable, ship small steps.
Next: Marketing automationGame cards, match-day ads, social posts and blog articles made by tools I built for a casino and a gold marketplace. A person still taps approve.