The challenge
A marketplace only works if someone checks who joins, steps in when a job goes wrong, and keeps money moving. That work needs one place, not a spreadsheet per task.
What we built
- Dashboard: platform totals at a glance (users, jobs, verified tradespeople, completion and cancellation rates, revenue, payouts, disputes and support tickets), with alerts and recent activity
- Tradespeople: a full profile for each, showing onboarding progress, rating, completed jobs, free leads left and last activity, with tabs for verification, certificates, banking, wallet and payouts, recent jobs, reviews and support history, plus one-tap email, call or WhatsApp
- Customers and accounts: search and filter users, update contact details, change roles, and suspend or delete accounts
- Verification: a queue for new tradespeople, with each trade certificate approved or rejected on its own and notes kept against it
- Jobs: every job on the platform, with flags, notes and cancellation by an administrator
- Disputes: assigned, prioritised, escalated, annotated and resolved in one place
- Payouts: tradesperson withdrawals reviewed, approved or rejected, then tracked through processing to paid, or failed
- Banking: Skillteq's own bank accounts and transactions, verification of tradespeople's bank details, and the Paystack connection set up and tested from the portal
- Pricing and agreements: the rules that set booking fees and commission, tradesperson rate agreements, and service levels assigned to individual tradespeople
- Referrals: commissions approved or reversed singly or in bulk, fraud flags reviewed, failed referral payouts retried, and milestone tiers, reward rules and fraud thresholds edited, with a leaderboard
- Service catalogue: categories and subcategories created, reordered, given icons and switched on or off
- Content: legal and FAQ pages drafted, published and withdrawn, appearing in the apps and on the website
- Helpdesk: tickets with tags, priorities and assignment, plus groups, templates, macros and categories, automatic assignment rules, SLA tracking, and ticket linking and merging, with updates appearing live
- Staff and permissions: staff invited by email, roles built from a permission matrix, individual overrides, and access removed when someone leaves
- Analytics: charts of platform activity, plus cookie-free usage analytics across the apps, portal and website
How it works
The portal is a Next.js web app that works directly on the same database as the apps. Staff sign in with their own accounts, and every action, including payouts, is checked against their role on the server before it runs.
- Staff→
- Admin portal→
- Database→
- Apps and website