Platform Rebuilt.
Results Delivered.

Took FundedNext from a fragmented, outdated dashboard to an integrated modern platform managing 10,000+ funded accounts, each carrying real capital, daily payout obligations, and compliance requirements. Cut operational inefficiency by 40%, lifted trader engagement by 35%, and eliminated 18.5% of support volume through eight targeted product decisions.

RoleProduct Manager II
CompanyNext Ventures · FundedNext
TimelineApril 2025 — Present
Team20 People (Cross-functional)
DomainFintech · SaaS · Prop Trading
Type1-to-N: Inherited live platform, drove growth
The Problem
Traders worked across a fragmented, outdated dashboard with no integration between core flows, creating friction in every critical task.
The Solution
Eight targeted product decisions rebuilt the platform into a modern, integrated experience that made core tasks faster and measurably reduced failure points.
My Role
PM II owning the full roadmap for a 20-person cross-functional team across engineering, design, QA, and compliance.
The Impact
40% operational efficiency gain, 18.5% of support tickets eliminated, and 35% engagement lift across 10,000+ funded trader accounts.

Three problems that were quietly costing the business

When I joined FundedNext, the platform was holding traders back rather than helping them succeed. Three things needed to change urgently.

01

Traders had no visibility into their own account. There were no notifications, no real-time risk data, and no way to know what was happening between logins. People found out about KYC deadlines and payout issues only when things had already gone wrong.

02

The platform had compliance gaps that created financial and regulatory exposure. Abusive trading patterns were going undetected. Account security had no enforcement layer. The team had no tooling to catch bad actors before they caused damage.

03

The internal team was blocked by manual work. Five repetitive workflows were consuming hours every day across 20 people. None of them required any human judgment. They were just processes nobody had automated yet.

One strategy, eight decisions

These weren't three separate problems. They were one: a platform that hadn't kept up with the product it was supposed to support. The strategy was to fix the foundation first, starting with compliance and visibility, then build engagement and efficiency on top.

Every decision was sequenced deliberately. Notifications before the dashboard revamp. Compliance before enforcement. Automation before anything else, so the team had the capacity to execute everything that followed.

The eight things I shipped over the course of this project are documented below, each one with the problem it solved, the change it made, and the result it produced.

8 features shipped across a 20-person cross-functional team

How far the platform has moved across six dimensions

These six areas capture the full scope of the work. The numbers represent a rough score out of 10, based on capability and coverage at each stage.

When I joined Fragmented dashboard, no notifications, no compliance tooling, manual workflows eating team capacity.
Today Notifications live, risk cards deployed, compliance framework in place, automation running, password policy enforced, calculators built.
Trader Transparency
Before: 2After: 9
Platform Security
Before: 3After: 8
Workflow Speed
Before: 3After: 9
User Engagement
Before: 4After: 8
Support Health
Before: 2After: 8.5
Compliance Coverage
Before: 2After: 8

Eight features, and why each one mattered

Each section below shows the problem as it stood, the change I made, and the result. Numbers are based on measured outcomes tracked over 4 weeks post-launch.

Shipped

Workflow Automation — freeing 20 people from repeated manual work

Before

Five manual workflows were running every day: ticket tagging, account status updates, payout checks, report generation, and notification dispatch. None of them required any judgment. They just consumed time from 20 people who had more important things to do.

After

Built a full automation pipeline in n8n covering all five workflows. Each one now runs on a trigger without human input. The team gets the output, not the process of producing it.

The decision to do this first wasn't just about efficiency. Every other initiative on the roadmap depended on the team having bandwidth. Clearing these five workflows was the thing that made everything else possible to ship on time.

I mapped each workflow with the ops team first, task by task and person by person, to identify every decision point. Only one step across all five workflows actually needed human input. Everything else was just moving data from one place to another.

40%+ reduction in operational task time across the team
Manual (Before)
Ticket tagging
Account status checks
Payout reconciliation
Daily reports
Alert dispatching
Automated (After)
n8n trigger pipeline
Event-driven updates
Auto reconciliation
Scheduled reports
Rule-based alerts
Shipped

Notification System — traders stop finding out about problems too late

Before

The platform had no notification layer. Traders found out about KYC deadlines, payout status, and account alerts only when they logged in, sometimes days after something had changed. Most would then contact support.

After

Shipped a full backend and frontend notification system covering 8 event categories across both CFD and Futures products. Traders get notified the moment something relevant happens to their account.

It was also a retention mechanism. Traders who feel connected to their account are more likely to stay active. A notification at the right moment ("your payout has been processed" or "your KYC needs attention") is the difference between a trader who feels looked after and one who churns quietly.

The notification categories were chosen based on what was generating the most support tickets. KYC and payout alerts alone covered 60% of the ticket types we saw before launch.

35% lift in user engagement (30-day session return rate)
8 Notification Categories · CFD & Futures
KYC
KYC Status
Verification required or approved
Payout
Payout Updates
Submitted, processing, paid
Risk
Risk Alerts
Drawdown thresholds approached
Account
Account Events
Challenge pass, fail, reset
Security
Security Alerts
Login from new device or location
Trade
Trading Alerts
Positions flagged or auto-closed
Promo
Promotions
Discounts and plan offers
System
System Updates
Downtime, rule changes, news
Shipped

2FA Flow Redesign — removing friction from users who hadn't even traded yet

Before

Every new user (including free users just exploring the platform) was forced to set up two-factor authentication during signup. This blocked a significant number of early users and generated 18.5% of all support tickets.

After

2FA now triggers only when an account has real value worth protecting: after KYC completion or after 14 days of activity. Free explorers get a smooth start. Funded traders are still protected.

It was the hardest decision to push through internally. Compliance wanted universal 2FA for all users, which sounds like the safe choice, but the data told a different story. 18% of support volume was coming from users who had never made a deposit and never placed a trade. They were not at risk. The platform was.

Security should scale with exposure. An account that holds $0 doesn't need the same protection as an account that holds $5,000. Once that framing landed, the decision was straightforward.

18.5% of all support tickets resolved — a single flow change
Sign up Forced 2FA 18.5% abandoned
→ support ticket
Sign up Explore freely
KYC done 2FA triggered Protected
Day 14 2FA triggered Protected
Shipped

Risk Parameter Cards — traders can see the cost of a bad trade before it's too late

Before

Traders had no live view of their risk exposure. They could be silently eating through their drawdown buffer with no warning, and only found out they'd breached a rule when they lost access to their account.

After

Risk Cards now sit in the Account Overview and show real-time drawdown usage, profit target progress, and exactly how much an open trade would cost in potential payout deductions, with email and in-app alerts as thresholds are approached.

Prop trading rules are strict, and a lot of traders lose their accounts not because they're bad at trading, but because they don't have the information they need in the moment. A card that says "your daily drawdown is at 80% — this open trade will push it to 92%" is the kind of feedback that changes a decision before damage is done.

The cards also show the full breakdown of potential payout deductions from active trades, so traders aren't surprised at payout time. Transparency at the right moment builds trust.

Traders now see risk exposure before they breach rules, not after
Risk Overview · Live Caution
Daily Drawdown Used 3.8% / 5%
Max Drawdown Used 6.1% / 10%
Profit Target Progress 7.2% / 10%
Open Position Impact -$142 if closed now
Payout Deduction Risk $68 at current exposure
⚠ Your daily drawdown is approaching the limit. Closing the current XAUUSD position would bring it to 4.2%.
Shipped

Compliance Framework & Ban-Prevention — catching abusive patterns before they cause damage

Before

Abusive trading (exploiting platform rules, using banned strategies, or manipulating the evaluation environment) was going undetected. The team had no monitoring system, and by the time issues were caught, the financial exposure had already happened.

After

Built a monitoring framework with automated pattern detection for suspicious activity. Flagged accounts go through a defined review pipeline with clear enforcement protocols (from warning to restriction to ban) based on severity and evidence.

This was as much a fairness problem as a financial one. Legitimate traders following the rules were competing in an environment where some people weren't. The compliance framework makes the playing field more honest.

The enforcement process is structured deliberately: it escalates in stages rather than jumping straight to bans. That protects both the platform and the traders, since some flagged patterns turn out to be mistakes rather than intent.

Platform integrity protected. Abusive accounts handled before financial damage
Compliance Pipeline — flagged account flow
1
Pattern Detection
Automated monitoring flags suspicious trading patterns across all accounts
2
Manual Review
Flagged accounts reviewed by the Identity & Investigation Squad for context
3
Escalation Decision
Three tiers: warning, account restriction, or permanent ban — based on severity
4
Enforcement & Record
Action taken, account status updated, case documented for future reference
Shipped

Advanced Password Policy — 90-day reset cycle with enough warning to not be annoying

Before

Accounts had no password lifecycle enforcement. A trader who signed up two years ago could still be using the same credentials, potentially compromised or shared, with no prompt to change them.

After

Mandatory password reset every 90 days, with in-app and email reminders at 15 days and 3 days before expiry. Traders get enough notice that it's not a surprise. They're never locked out without warning.

For a platform that holds people's funded trading accounts, security hygiene isn't optional. For traders whose accounts have passed evaluation and hold real capital, the stakes are higher. A compromised account is not just a support problem. It's a financial and reputational one.

The reminder timing was deliberate. 15 days is enough time to plan. 3 days creates urgency without panic. No reminders meant no preparation, which meant a locked account and a support ticket. That pattern is now gone.

Account security hygiene enforced at scale across 10,000+ traders
90-Day Password Lifecycle
Day 0 — Password set
Day 75 — First reminder
Day 87 — Final reminder
Day 90 — Reset required
Day 75: In-app banner + email — "Your password expires in 15 days"
Day 87: In-app notification + email — "Expires in 3 days"
Day 90: Mandatory reset prompt on next login
Shipped

Margin & Swap Calculators — CFD traders stop leaving the platform to do the maths

Before

CFD traders needed to know their margin requirement and overnight swap costs before entering a trade, but had to calculate these outside the platform, using spreadsheets or third-party tools. This broke the trading workflow and sometimes led to trades placed with the wrong numbers.

After

Native margin and swap calculators built directly into the platform. Traders enter their lot size, instrument, and account currency, and get the exact margin required and daily/weekly swap cost without leaving the page.

This feels like a small feature. In practice it removes one of the most common reasons CFD traders interrupted their own workflow. Every time a trader had to open a new tab to calculate margin, there was a chance they'd get distracted, misread a number, or just not place the trade at all.

Fewer interruptions and fewer calculation errors also means fewer "why was my trade closed" support contacts, which were regularly caused by traders not accounting for margin correctly before entering a position.

Calculation errors reduced. Traders stay in the platform to make decisions
CFD Calculators
Margin Swap
Instrument XAUUSD
Lot Size 0.50
Account Currency USD
Leverage 1:100
Margin Required $1,197.50
Shipped

FNHunt — turning passive FAQ readers into active plan buyers

Before

The FAQ page was purely informational. Traders would read a question, get an answer, and leave. There was no mechanism to turn that engagement into a purchasing decision, even though visitors were clearly in a research mindset.

After

FNHunt hides a discount coupon code inside a specific FAQ answer. Traders who read enough to find it earn a discount on their next plan purchase. Passive browsing becomes a small reward loop that directly drives conversions.

The insight behind this was simple: anyone reading the FAQ is already interested enough to learn about the product. They're one nudge away from buying. Rather than just answering their question and letting them leave, FNHunt gives them a reason to keep reading and a reason to come back.

It also doubled as a product education mechanism. Traders who find the coupon have read enough of the FAQ to be well-informed about the rules, which reduces the "I didn't know" support tickets that often follow first purchases.

FAQ converted from static reference into active conversion driver
FNHunt — How it works
📖
Step 1 — Read the FAQ Trader arrives with a question. They start reading through answers.
🔍
Step 2 — Find the code A coupon code is hidden inside one of the answers. Finding it means actually reading the content.
🎁
Step 3 — Redeem the discount The code gives a plan discount. A well-informed trader converts. They already know the rules.

How I decided what to build and what to skip

The outcome numbers are visible. Here is what went into deciding each one.

How I found the problems

  • Built an n8n pipeline to pull all Intercom support tickets into Power BI
  • Tagged every ticket by issue type and root cause
  • 18% of tickets were about identity and account access. That set the priority order before any PRD was written
  • A time audit with the ops team mapped 5 manual workflows. None required human judgment, just repeated steps that blocked 20 people

Why this order and not another

  • Used an impact/reversibility matrix, not pure RICE scoring
  • Automation came first because it was slowing the entire team. Every other initiative would ship faster once that bottleneck was cleared
  • The dashboard revamp was held back in Phase 1: changing the UI before fixing the notification layer would just move the friction somewhere else
  • Compliance was sequenced after notifications. You cannot enforce trading rules if traders have no visibility into their own account status

The hardest tradeoff

  • Compliance wanted universal 2FA for all users. Removing it from free user onboarding looked like a security step backwards
  • The real cost of that policy: 18% of support volume, mostly from users who had never traded
  • The security requirement only applied meaningfully to funded accounts, not free users exploring the platform
  • Resolution: no 2FA until KYC completion or 14 days of activity. Free users get a smooth start. Funded accounts stay protected

How success was measured

  • Efficiency: tracked task completion time across the 5 manual workflows before and after automation, over 4 weeks post-launch. The 40%+ is the reduction in time-on-task
  • Support volume: the n8n/Power BI pipeline tracked whether resolved tickets for the same root cause came back within 30 days. The 18.5% is durable resolution, not just closure rate
  • Engagement: notification open rates and 30-day session return rate compared to the same window before launch

What I would do differently

  • Would have shipped a smaller notification MVP first, starting with account status events only
  • Launching all notification categories at once made it hard to know which ones were driving the 35% engagement lift
  • A phased rollout would have given cleaner data and let us tune the system before reaching every active trader

Two projects currently in progress

These aren't ideas on a backlog. They are live projects with teams assigned, scopes defined, and hypotheses being tested. Here's why they matter and what success looks like.

In Progress

Full Dashboard Revamp

The current dashboard was designed for an earlier version of the product. Since then, Risk Cards, notifications, compliance alerts, KYC flows, and payout management have all been added on top of an old structure that was never meant to carry all of this.

The revamp rebuilds the dashboard from the ground up around how traders actually use it today: account overview first, risk exposure visible at all times, payout and KYC status one click away. The goal is to cut the number of support contacts at payout and KYC stages by reducing the confusion the current layout creates.

The hypothesis

If traders can see their account status, risk profile, and next required action in one view without navigating to different pages, the number of "how do I do X" support contacts at payout and KYC stages will drop by at least 20%.

Target: 20% reduction in support contacts at payout and KYC stages
In Progress

Native Mobile App

10,000+ traders are managing funded accounts from their phones. The current experience is a web app running in a mobile browser, and it shows. The actions traders need most when they're away from their desk (checking risk exposure, reading notifications, monitoring drawdown, responding to alerts) are clunky on mobile.

The app is being built to make the most time-sensitive parts of the trading experience fast and native: real-time risk cards, notification center, account status, and payout status, all accessible with the kind of speed and clarity that a mobile-first experience needs.

The hypothesis

If traders can check their risk metrics and respond to account alerts from their phone in under 10 seconds, trader retention in the first 30 days after challenge completion will improve, because the period of highest disengagement risk is when traders are between sessions, not in front of their desk.

Target: improved 30-day retention post-challenge completion

See it live

FundedNext is a live, active platform serving 10,000+ traders globally. The public site gives full context on the product. The trader dashboard is the experience I own and have been rebuilding.

Full design artifacts, Risk Cards, notification system specs, and compliance framework documentation are available on request.

Results — measured, not estimated

Every initiative was shipped against a specific target. These numbers validate the strategy. Not vanity metrics, but platform-level outcomes tied directly to product decisions.

40%+
Operational efficiency gained across payout processing, KYC flows, and funded account management by replacing core manual operations with automated workflows
18.5%
Support volume eliminated by a single flow redesign targeting the root cause of onboarding friction
35%
User engagement lifted by the platform-wide notification system across CFD and Futures product lines