One page, one job.
A focused page built around a single purpose: a product, a campaign, an event, a portfolio. Simple in scope is not the same as cheap in execution: still responsive, still fast, still accessible, still yours.
LittleMan Dev · Maldives
- Want an exquisite website, like the one you're on?
- Want to upgrade the one you already have?
- Want to build a web app that actually does something?
Then you're in the right place. I'm Ismail Mohamed Fareed, and I design and build custom digital products: landing pages, full websites with a CMS, and web applications with real backends, admin panels and users. Not from a template. From your problem.
Who you're actually talking to
The person who replies is the person who builds it.
LittleMan Dev is the independent web and software practice of Ismail Mohamed Fareed. There is no account manager, no sales layer, and no brief that gets lost on its way to a developer, because the chain is one person long.
That means requirements are understood first-hand, decisions get made in minutes instead of meetings, and nothing about your project is anyone else's second priority.
1
Point of contact
0
Templates used
100%
Built to the brief
1# before any code exists
2problem: "what is actually broken"
3users: "who has to live with it"
4scope: "what is in, what is out"
5data: "what the system remembers"
6flows: "what happens, in order"
7done: "how we know it works"
8
9# only then: the stack
Three kinds of work
Landing pages. Websites. Software.
The line between them isn't page count. It's what the thing actually has to do.
Many pages, real content.
Multi-page business, organisation and directory sites with dynamic content, search and filtering, forms, and a CMS you can actually operate without calling me every week.
When the site becomes a system.
Authentication, user accounts, databases, role-based admin dashboards, payments, third-party integrations, real-time features, internal tools. Less about presenting information, more about running an operation.
I don't price by the number of pages. A five-page brochure site can be straightforward; a three-page application with auth, a database and an admin panel is not. Every project is estimated on what it needs.
How the work gets made
I don't start with a template.
I start with the problem.
Technology should serve the project, not the other way round. Nothing gets over-engineered to sound impressive, and nothing gets under-engineered to make my week easier.
Design is the product
Not decoration bolted on at the end. Hierarchy, structure and interaction are decided with the functionality, because they are the functionality.
Motion with a reason
Quality of movement over quantity of movement. Animation exists to show continuity, give feedback, and guide attention. Never because something could be animated.
It has to work properly
"It works" is not the finish line. Responsive, performant, accessible, maintainable, secure where it matters, tested and refined as part of the build, not sold as an extra.
Different problems, different answers
There's no house style every client gets poured into. Your content, your users and your constraints should produce something that looks like you.
Selected work · 01
Go Construction Pvt. Ltd.
Corporate website for a Maldivian construction firm, in Malé.
goconstructionmv.com
A six-service construction firm with nine years of built work and no website that reflected it. The answer was a dark, cinematic, photography-led site where the projects carry the credibility and the interface stays out of their way.
- ScopeSix pages (home, company, services, projects, team, contact) with a full project portfolio.
- DesignCinematic dark palette, amber accent, editorial grid, film grain and vignette over full-bleed site photography.
- MotionNative cross-document view transitions, so page changes animate instead of blinking, plus a single shared scroll-reveal observer.
- EngineeringHand-written HTML and CSS, no framework. One IntersectionObserver instead of dozens of scroll triggers, deliberately fast on Maldivian mobile connections.
Selected work · 02
The Mosque Directory
Ministry of Islamic Affairs and Endowments, Republic of Maldives.
Not public yet. The live demo is the real application,
compiled from its own source, running on fixture data.
mosquedir.littlemandev.com
An official ministry platform giving the public a nationwide, searchable directory of mosques across every atoll and island in the Maldives, fully bilingual in Dhivehi and English, with proper right-to-left support.
- Phase 1Bilingual web app: interactive map, search, mosque records, a downloadable resource catalogue, and a role-based admin module for ministry staff, taken to a production-hardened release with a full security and performance pass.
- Phase 2Rebuilt as a native iOS and Android app on a revised ministry brief, adding prayer times, Qibla direction, the Hijri calendar, offline access, announcements and mosque issue reporting.
- HandoverClean integration points prepared for the ministry's own systems (Microsoft SQL Server, Microsoft 365 sign-in and eFaas national identity) to be connected after delivery.
Small by choice
I'm not alone.
I'm also not forty people.
When a project needs a dedicated designer, an illustrator, or a second pair of engineering hands, I bring in people I've worked with and trust. Complex, professional work gets the specialists it needs.
What you will never get from me is an org chart, a "team of experts" page, or a stock photo of eleven strangers in a glass meeting room. This is a one-person practice that scales up deliberately, not an agency pretending to be one.
IFIsmail Mohamed FareedDesign, build, delivery, every project
+Designers & illustratorsBrought in by project
+Engineers I trustFor scale and specialism
What you get
- One person who knows the whole system
- Direct answers, not ticket numbers
- Specialists added when the work needs them
- Honest scope, including "you don't need that"
- The same person from first call to handover
What you don't
- Invented headcount
- "Our team of experts"
- Basic / Pro / Premium packages
- Buzzwords standing in for decisions
- A junior quietly assigned to your build
The honest version
Yes, AI writes a lot of the code.
No, that's not the part that matters.
I'd rather say this plainly than let you discover it. I vibe code, heavily. But code generation is the last step of the process, not the process.
Before: the actual work
Specs, requirements, architecture
A product spec. A software requirements document. A data model and an architecture plan. Real documents, written before anything is generated, not buzzwords in a proposal.
During: execution
AI executes the plan
The model is a very fast pair of hands working to a decided design. It doesn't choose the data model, the flows, or what the product is. Those were settled first.
After: judgement
Review, reject, refine
Knowing what to reject is most of the skill. Output gets read, cut, restructured and tested until it's something I'd sign my name to.
You can prompt an AI yourself. Genuinely, you can. The difference is knowing what
to ask for, what to throw away, and what finished actually means. That's why the
things I build have a soul and an identity, instead of looking like everything else
generated this week.
How a project runs
Six steps, in this order.
You don't need to arrive with a technical specification. Explain what you want and who it's for, and I'll work out the rest.
02
Describe it
What needs to be built, what problem it solves, who uses it, what you already have, and your deadline.
03
Requirements & spec
I analyse it and write out the actual scope and specification, so we're both agreeing to the same thing.
04
Estimate & terms
A price estimate based on that scope, with the payment model and schedule fixed in the quotation.
05
Development
I build it. You see progress at the agreed checkpoints rather than at the end.
06
Payment & handover
Final payment, then delivery and transfer of the agreed project assets.
Understand → Plan → Design → Build → Test → Refine → Deliver. The technology comes after the understanding.
Payment
Projects are divided into agreed checkpoints.
An initial payment is made before development begins. The remainder is split across agreed milestones or paid on completion, depending on the size and structure of the project.
Smaller projects
50 / 50
Deposit to start · balance on completion
A deposit and a final payment. Nothing more complicated than it needs to be.
Medium projects
40 / 40 / 20
Deposit · milestone · completion
A payment mid-build means you see working software before the balance is due.
Larger applications
30–40 + milestones
Deposit · per milestone · final
Each milestone is defined in the quotation, so every payment is tied to something delivered.
- The exact schedule is agreed before development begins and written into the quotation. It does not move afterwards.
- I don't take 100% upfront, and I don't build for weeks at my own risk on a promise of payment at the end. The risk is split, deliberately.
- Final delivery and transfer of the agreed project assets follows the agreed payment terms.
Delivery & ownership
What you own, and what it costs to run.
Ownership is settled in writing before the build, not argued about after it. Depending on the agreement, delivery can include the live site, the source code, the admin dashboard, hosting and domain access, DNS, credentials and documentation.
- Landing pages and websites. Ownership of the domain can be transferred to you on completion. If the domain stays registered under me, because it's billed to my card, that cost is billed to you.
- Applications I continue to manage. Running costs are quoted upfront as a monthly or annual figure covering hosting, databases, APIs, storage and maintenance.
- Unpaid services get cancelled. If those recurring costs aren't paid, I cancel the services they pay for. That's stated plainly here so it's never a surprise later.
- If you take the project over, I'm not responsible for maintaining it unless ongoing maintenance is separately agreed.
✓Live site, deployed
✓Source code & repository
✓Admin dashboard + accounts
✓Hosting & domain access
✓DNS configuration
✓Credentials, transferred securely
✓Documentation
·Third-party costs per agreement
·Maintenance only if agreed
Let's build it
Tell me what's broken.
Or what should exist.
You don't need a spec, a wireframe, or the right words for it. Describe the problem and I'll take it from there.
Chat · fastest↗
Start a conversation
Straight through to me, in your browser. No account needed.
Email · primary↗
info@littlemandev.com
Best for briefs, documents and quotations.
Call · WhatsApp · Telegram↗
+960 797 5770
Call it, or message the same number.
Email · secondary↗
dotcomscript@gmail.com
The business inbox is still being set up, so this one always works.
© 2026 Ismail Mohamed Fareed · Maldives
Understand the problem first, then build the right thing.