Skip to content
Nahed
PortfolioServices
Blog
Contact
Search
Site Analytics
Profile
PortfolioServicesBlogContact
Tools
Instagram AnalyzerLearning TrackerConversation PracticeWatermark StudioSite AnalyticsAll Tools
About
About NahedRunningGalleryNotes

©2026 Nahed. All Rights Reserved.

Nahed Nakib instagram IconNahed Nakib facebook IconNahed Nakib linkedin IconNahed Nakib github Icon

Web development services

Web development services.

New websites, focused improvements, and custom web products using WordPress, React, and Next.js. The technical choice follows what the project needs and how it will be maintained.

Start a projectView portfolio

Services

01New websites02Website improvements03Custom web applications

Services

What I can help with.

Three types of work, each scoped around a specific problem and a usable result.

01

New websites

A complete website for a business, organisation, personal brand, or campaign — planned around the information visitors need and the way your team will maintain it.

Good fit for
Company websites, non-profits, portfolios, blogs, campaign pages, and new online projects.
Expected result
A clear, responsive website that is ready to publish and practical to manage.

Typical scope

  • Page structure and user journeys
  • Interface design and responsive development
  • WordPress or Next.js implementation
  • CMS setup, technical SEO, analytics, and launch

02

Website improvements

Focused work on an existing website when the useful answer is to repair, simplify, or extend what is already there instead of rebuilding everything.

Good fit for
Slow pages, mobile problems, difficult editing, inconsistent design, missing features, and ongoing WordPress work.
Expected result
A more reliable website with the specific problems fixed and unnecessary disruption avoided.

Typical scope

  • UX and responsive fixes
  • Performance and Core Web Vitals work
  • Design-system and accessibility cleanup
  • New pages, forms, integrations, and features

03

Custom web applications

Web products that need structured data, accounts, dashboards, admin tools, or integrations beyond the limits of a standard website.

Good fit for
Member areas, internal tools, directories, custom platforms, and workflow-based products.
Expected result
A focused application built around the real workflow rather than a collection of disconnected features.

Typical scope

  • React and Next.js interfaces
  • Supabase authentication and databases
  • Admin panels and content workflows
  • APIs, email, webhooks, and third-party services

How the work is approached

The less visible parts still matter.

A website is not finished when the desktop screen looks good. The structure, editing workflow, performance, and handover affect whether it remains useful.

01

Scope before code

The pages, features, responsibilities, and technical approach are clarified before the build grows.

02

Responsive by default

The result is designed and tested for phones, tablets, and desktop screens.

03

Real content workflows

Editing and publishing are considered so the site remains usable after launch.

04

Technical foundations

Performance, accessibility, SEO basics, analytics, and browser behaviour are part of the implementation.

Choosing the platform

WordPress or Next.js?

Neither is automatically the better choice. The right platform depends on the content, features, editors, and changes expected after launch.

WordPress

For content-led websites

A good fit when editors need a familiar CMS, the project is primarily pages and content, and standard integrations cover the required functionality.

Common examples
Business sites, organisations, blogs, campaigns, and publications.

Next.js

For custom behaviour

A better fit when the project needs accounts, structured data, dashboards, custom workflows, or tighter control over the interface and integrations.

Common examples
Web applications, member areas, tools, portals, and custom platforms.

Process

From brief to launch.

A clear sequence keeps scope, decisions, and feedback visible throughout the project.

  1. 01

    Brief

    You share what exists, what needs to change, and what a useful result looks like.

  2. 02

    Scope

    I review the work, ask the missing questions, and outline the approach, estimate, and timeline.

  3. 03

    Build

    The project is implemented in reviewable stages so feedback happens while decisions are still easy to change.

  4. 04

    Launch

    The final result is tested, published, and handed over with the information needed to manage it.

Practical questions

Before you send a brief.

The exact answer depends on the project, but these are the useful starting points.

How much does a project cost?

Cost depends on the scope, content, integrations, and condition of any existing website. After reviewing the brief, I send a practical estimate instead of guessing before the work is understood.

How long does a project take?

A focused improvement can take days, while a complete website or custom application usually takes several weeks. The schedule is agreed after the scope and dependencies are clear.

Can you work on an existing website?

Yes. I can review an existing WordPress or front-end project, identify the useful changes, and work on improvements without assuming that a full rebuild is necessary.

Do I need a finished specification?

No. A short description of the current situation, the audience, and the result you need is enough to begin. The missing technical questions can be worked out during scoping.

What happens after launch?

The project includes testing and handover. Ongoing updates, maintenance, or additional features can be planned separately when they are needed.

Have a project in mind?

Start with a short brief.

Explain what exists, what is not working, and what you need the website or application to do. I'll reply with questions and a practical next step.

Tell me about the projectSend a simple message