Pathfinder Consultant

From Tutor LMS on WordPress to a custom learning platform built for security

Next.js · Education

We replaced WordPress, Tutor LMS and WooCommerce with a custom Next.js learning platform: payments, analytics, 2FA, passkeys and an MCP server for AI agents.

Pathfinder learning platform storefront

Problem

Pathfinder’s courses ran on WordPress with Tutor LMS and WooCommerce. Three systems that weren’t designed together made enrolments, payments and reporting hard to manage. Every plugin update was a risk, and every plugin was another way in for attackers.

Solution

We built one custom platform that does the whole job: course catalogue, enrolment and payments, live classes, quizzes, certificates, instructor earnings and reporting, all behind an admin protected by two-factor login and passkeys.

The client

Pathfinder Research & Consultancy Center teaches research skills to students, graduates and professionals in Bangladesh. That covers research methods, academic writing and publishing, plus wider skills courses.

Why leave WordPress

Tutor LMS and WooCommerce worked when the catalogue was small. As courses and students grew, the stack got harder to run. Course data, orders and payments lived in separate plugins, reports didn’t line up, and the site depended on a long chain of third-party plugins that all needed updates.

What we built

One platform, designed around how Pathfinder actually works:

  • Learning: courses, bundles, categories and tags, live classes, quizzes, assignments, Q&A, announcements, certificates and reviews.
  • Sales: orders, coupons, payments through SSLCommerz in Bangladeshi taka, sales reports and instructor earnings.
  • Content: pages and posts, so the team can publish without a developer.
  • Analytics built in: first-party, cookieless visitor and conversion tracking that excludes staff and bots. It replaces a stack of third-party scripts.

Security first

An LMS holds personal data and takes payments, so security was part of the design from day one:

  • Two-factor authentication and passkeys for staff accounts.
  • Role-based access, so admins, staff, instructors and students each see only what they need.
  • An MCP server, so the team can use AI agents for routine admin work through a controlled, authenticated interface instead of handing over passwords.

See it live at pathfinderconsultant.com.

Have a project like this?

Book a 15-minute call with the engineer who’d do the work. You’ll leave with a clear next step, even if it isn’t us.