Full-Stack Developer · AI & Automation
Mamun Ahmed builds the operational software businesses run on — SaaS, CRM, education and commerce systems, plus integrations, automation and AI workflows.
business software first, then the automation around it, then AI in the one step where it earns its place
founder & ceo — AM IT Solution
typical shape
one application · one database
no microservices · no queue
Each one is a real system with real users. The case studies cover the problem, what was built, and the parts that were genuinely hard.
Built for London School of Excellence
A student recruitment and education operations platform: one student record behind many applications, a 140-university course catalogue, evidence documents, GDPR consent signing, and agent onboarding and commission — across three operational roles.
Built for US Arabian Perfume
A multi-branch retail operations platform: storefront, point of sale, branch inventory, attendance, commission and payroll, on one codebase and one database.
A full-stack e-learning platform: course discovery, checkout, enrolment, secure lesson delivery, learner progress, quizzes, certification and public certificate verification.
A CRM covering the full lifecycle from first enquiry through onboarding, agreements, contributions, delivery and payments, across four distinct product lines.
Most operational work leaks through the gaps between systems — a message read late, a date typed into the wrong day. Automation closes the gaps; AI is one node inside it, not the point of it.
before — six steps, five of them by hand
after — one system, one bounded decision
manual handoff — the step that gets skipped when the day is busy
the only step allowed to interpret anything — everything around it is deterministic
Systems built around a real process, not a template.
Organisations, permissions, billing and audit from day one.
The operational tool that replaces the spreadsheet sprawl.
Admissions, portals, learning delivery and certificates.
One catalogue and one stock position across every channel.
Webhooks, imports, notifications and the awkward edge cases.
The manual steps between systems, removed deterministically.
AI scoped to one step, with a person still deciding what ships.
I am a full-stack developer and the founder of AM IT Solution. Most of my work is the operational software a business depends on daily — the CRM the team lives in, the platform that takes the money, the system that tracks the applications.
That work has a particular character. It is long-lived, it holds real money and real people's data, and it is rarely greenfield. Getting it right has more to do with modelling the business correctly than with picking a framework.
Before touching a system I read it: the data model, the deployment, what the last person was solving. Most bad changes come from confident assumptions about code nobody re-read.
A screen that looks right over a model that is wrong is a liability. I get the entities, the states and the money definitions right first; the interface follows from them.
A green local build is not evidence. I check the deployed thing — the page served, the row written, the email received — before saying a change is shipped.
The architecture has to still make sense after a year of changes made in a hurry. Invariants that matter get enforced by the database or by a test that fails the build, not by discipline.
and in what order
Who does what, in what order, and what has to be true before the next step. Most of what looks like a software problem is an unwritten process.
Entities, states and the money definitions, fixed before any interface. A screen over a wrong model is a liability you pay for later.
Remove the manual handoffs that get skipped when the day is busy — deterministically, with the trigger narrow and the values explicit.
One bounded step: drafting, summarising, classifying. Guarded, validated, and never the thing that decides something is finished.
03 Sept 2026 · 3 min
Every tenant table carries the organisation, every query goes through one layer that puts it there, and a build-time check fails the build if application code ever reaches the database directly. The discipline is the design.
20 Aug 2026 · 3 min
Hiding a button is not security. A permission model that survives contact with a real business needs one catalogue, enforcement in the service layer, and a short list of actions that only two people may ever perform.
I founded AM IT Solution to build custom software for businesses whose operations have outgrown spreadsheets, disconnected tools and manual processes. This site is my own work; the company is where that work is delivered as a team.
visit am it solution