Contact us
All projectsEducation · Full-stack development · Bangladesh

Bright Tutor

A marketplace, an operations panel and a phone system, built as one platform for a Dhaka tuition business.

Bright Tutors connects guardians in Dhaka with qualified home tutors. Their business runs on speed: a guardian posts a need, and the team has to find, vet and confirm the right tutor before the guardian looks elsewhere.

Algoverse built them one system for the whole loop. Guardians compare tutor profiles and request one on the public marketplace. Tutors apply, get verified and buy plans online. Inside the operations panel, the team manages tuitions, CROs, payments, tasks and support across 20 modules.

Because most guardians would rather call than type, we put phone calling inside the panel. An IPTSP business number connects to a cloud PBX, staff answer and place calls from the browser, and every call is logged and reported on the panel's own dashboard.

In its first three months live, the platform handled 1,025 tuition requests, and tuition requests peaked at 428 in August.

Client
Bright Tutors (Bright Education)
Industry
Education / home tuition
Location
Dhaka, Bangladesh
Services
Web app, admin CRM, IP calling, SMS
Stack
PostgreSQL, Express, React, Node.js
Modules
20 in the operations panel
Tuition requests
1,025 in the first 3 months
Live at
brighteducations.com
Bright Tutors platform screens: the public tutor marketplace and the admin operations panel built by Algoverse

The Challenge

A tuition media business lives on speed: a guardian posts a need, and the team must find, vet and confirm a tutor before the guardian goes elsewhere. Bright Tutors needed one system to run that loop end to end. • Two sides to serve. Guardians need to find and request qualified tutors; tutors need to apply, get verified and buy plans. • A team to manage. CROs (customer relations officers) handle leads, follow-ups and payments, and management needs to see who converts what. • Money to track. Collections, dues, discounts, refunds and fraud cases had to reconcile in one place. • Calls to handle. Most guardians call rather than type, so phone calls had to reach the right person and be logged. Open question for the client: how were these handled before the platform (spreadsheets, Facebook, personal phones)? A one-line "before" makes the results land harder.

Our Approach

01

Map the business first

We sat with the Bright Tutors team to map how a tuition request moves: guardian enquiry, tutor matching, CRO follow-up, payment and confirmation. Every module was designed around that loop.

02

Build the marketplace and the panel on one backend

A single PERN-stack API serves both the public site and the operations panel, so a request a guardian submits online appears instantly for the team, with no retyping.

03

Give management live numbers

We built a dashboard with one master date range and seven operational views (collection, dues, adjustments, CRO efficiency and more), so owners see the business without asking for reports.

04

Bring the phone into the panel

We connected an IPTSP business number to a cloud PBX and embedded a browser softphone and click-to-call in the panel, so staff can call from where the customer's record already sits.

05

Ship in stages, fix in production

We launched module by module and worked from live feedback in a shared group with the client team: payment-flow edge cases, call routing and per-agent extensions were all solved against real usage.

Outcome

Bright Tutors now runs its entire tuition business from one platform: guardians and tutors on the public site, and the whole team inside a 20-module operations panel.

In its first three months live, the platform handled 1,025 tuition requests, with requests peaking at 428 in August. Phone calls moved into the panel in October 2026, giving the team one business number instead of personal SIMs.

  • 1,025 tuition requests handled in the first three months
  • 20 modules in one operations panel
  • 428 tuition requests in August, the peak month
  • 1 business number for every call, answered from the browser

Figures are taken from the platform's live dashboard, July to 10 October 2026. Phone calling went live in October 2026; caller-ID routing to each client's assigned admin is in progress.

Key Takeaway

When the marketplace, the team's tools and the phone all run on one system, every lead is captured, every call is logged, and management sees the business in real time instead of asking for reports.

Have a project in mind?

Let’s build
what’s next.

Start a project