maxiM
dmaximboi.vercel.app/code

Projects I
shipped to
production.

Each product is live, named, and built for a real organisation or business. I take a messy operational problem, design the data and the interface, then deploy something people can click today.

The stack is pragmatic: React or Angular on the front, Node and Express on the API, MongoDB or PostgreSQL underneath. If you hire me, this is the standard: ship, document, stay reachable, worldwide.

MCAS
meritcollege.vercel.app
School Management System

Merit College Academic System

MCAS follows how schools actually run: term calendars, class groups, result compilation, and staff clearance. Student profiles, roles, attendance, academic reporting, and daily paperwork live in one product. It is live and built to extend without rewriting the core.

  • Student records and class groups
  • Staff and admin management
  • Attendance tracking
  • Results and academic reporting
Visit live site
Lab
omegalabaffairs.vercel.app
Laboratory Platform

De-Omega Lab Affairs

Labs lose time when results live in disconnected notebooks. De-Omega Lab Affairs tracks experiments, outcomes, and lab activity with clear records, repeatable entries, and a searchable dashboard.

  • Experiment tracking
  • Result archives
  • Lab activity logs
  • Precision first records
Visit live site
Ariyo
ariyostitches.vercel.app
Fashion and Branding

AriyoFashion Stitches

AriyoFashion needed more than a gallery. The site carries brand voice, product presence, and a path for customers to engage before they walk in.

  • Brand identity online
  • Catalog presentation
  • Customer engagement
  • Mobile first browsing
Visit live site
D26
digital26.online
Business Platform

Digital26

Digital26 is the live business platform I run at digital26.online. It is built to present the work, take enquiries, and keep the operation on the public internet.

  • Live business platform
  • Client facing presence
  • Operations online
  • Owned domain
Visit live site
How I work

From brief to browser.

Scope

We agree the users, the records, and the one workflow that must not break. Vague make an app briefs wait until the outcome is named.

Build

Schema, API, auth, UI. You get something clickable early, then we tighten copy, permissions, and edge cases that only show up with real data.

Ship

Production URL, mobile behaviour, and a handover you can actually use. Maintenance is a conversation, not a disappearing act.