Senior Full-Stack Web Developer Taking work now

I build web systems that stay fast after I leave.

Twelve years of PHP, Laravel, WordPress and Shopify for teams who need more than a theme and a plugin stack. Custom builds, written by hand and documented at handover — so whoever maintains it next can.

See the work

Follow one request from click to response

Interface

The part your customers use. Clear, responsive and built around their task.

01What I doEight kinds of work

What I build, and what I'm called in to fix.

Most work is one of these. If yours sits between two of them, say so in your first email and I will tell you which one it really is.

01 Build Laravel custom application development Customer portals, billing flows, dashboards and APIs — typed, tested, and handed over with notes another developer can start from. PHP · Laravel · PostgreSQL 02 Build SaaS products with Laravel and Vue Tenants, roles, subscriptions and billing, with a Vue front end talking to your own API rather than to a template. Laravel · Vue · REST 03 Build WordPress website development Custom themes built around your content, not bought and bent into shape. No Elementor, no forty-plugin stack. WordPress · WooCommerce 04 Build Theme and plugin development Native Gutenberg blocks and plugins written for one job each, so the site carries no page builder licence to renew every year. Gutenberg · PHP · JS 05 Build AI-powered systems AI built into the Laravel app or WordPress site you already run: it reads the email, extracts the invoice, drafts the product page — and hands the decision to a person. Laravel AI SDK · WordPress AI 06 Move Migration to a new domain, host or stack Domain, hosting, mailboxes and the application itself. Every old address is mapped to its new one before anything moves, so the rankings and the inbox survive the change. DNS · Redirects · Mailboxes 07 Rescue Website redesign and optimisation A rebuild that keeps what already ranks. I profile what is actually costing you time — queries, render-blocking assets, unbounded plugins — and fix the causes, not the symptoms. Core Web Vitals · PostgreSQL 08 Rescue Fixing a hacked website Injected redirects, a Google warning, a host suspension. I remove the payload, close the way in, and write up how it happened. Cleanup · Hardening

02The processSix stations

From the first email to the day you don't need me.

Every engagement runs this way, whether it is one plugin or a whole platform. You always know which station we are standing at.

  1. 01 First email A paragraph is enough. If it is not work I am right for, I say so.
  2. 02 Scope, in writing What is included, what is not, and what it costs — before anything starts.
  3. 03 Build on a staging URL A link you can open any day, rather than a status report you have to read.
  4. 04 Your review Changes while they are still cheap, not in the week after launch.
  5. 05 Cut over Moved when your traffic is lowest, with the previous version still standing.
  6. 06 Handover Repository, tests, deployment notes and a write-up of how it fits together.

03Selected workFive platforms

Systems that went to production and stayed there.

Each one described by what it had to do and what was built to do it — with a diagram of how it fits together, because that is the part another engineer would ask about first.

See every project →

01 AI content platform

Product pages written from a photograph, in seven languages

The client uploads a photograph of a medicine; the system researches the product and drafts the page around it — description, usage, FAQ and the search copy — then carries all of it into seven languages in a single action. Blog posts work the same way, from a title and a note on the angle. The point was never novelty: every page that no longer needs a developer is a cost that stops repeating.

How it fits together
Medicine photograph1uploadedAI pipeline2draftsProduct page3one actionTranslated pageTranslated pageTranslated page

AI pipeline · Image intake · Seven locales

02 Redemption commerce platform

Coupon issue and redemption for brand campaigns

WordPress and WooCommerce carry the storefront and the campaign around it. The codes themselves live in DynamoDB: generation, issue and redemption all run against a key-value store rather than the catalogue database, because a single-use code is a lookup problem and not a relational one. A redemption never queues behind a product query.

How it fits together
WordPress · WooCommerce1callsIssue & redeem2reads / writesDynamoDB

WordPress · WooCommerce · DynamoDB · PHP

03 Content platform

Automated product content for appliance and electronics retailers

Retailers in this trade carry catalogues where every product needs specifications, copy and assets kept in step with one another. The platform takes that content in once and holds it consistent across the catalogue, which turned product content management from something done by hand into something that runs.

How it fits together
Product sources1ingestLaravel2storeMySQL3publishRetail catalogue

Laravel · MySQL · JavaScript

04 Learning platform

A learning platform that is one codebase and a database each

One deployment serves every organisation on it, each on its own domain. Each tenant also gets its own database rather than a shared table with a tenant column — so one organisation's records cannot surface in another's through a missing clause, and any single tenant can be backed up, restored or handed over on its own. The client adds an organisation without a deployment.

How it fits together
Laravel · Vue1routes by domainTenant router2one database eachTenant DBTenant DBTenant DB

Laravel · Vue · PostgreSQL

05 Property platform

Property listings with a back office of their own

Every property gets its own landing page, with its amenities, built to be found and to be acted on. Behind it sits a separate back office — not the WordPress admin — where properties, agents, clients and the leads they produce are handled in one place. The public site stays a public site, and the operation runs somewhere a plugin update cannot reach it.

How it fits together
Back office1publishesWordPress2rendersProperty pages3captureLeads

WordPress · PHP · Custom back office

04Who you would be working with

The person you brief is the person who writes the code.

Paul Edward
Paul Edward Senior Full-Stack Web Developer

I'm a senior full-stack web developer in Nagpur, India, with twelve years of production experience. I hold a Bachelor of Computer Applications and a Diploma in Web Logic.

Most of my work is PHP: Laravel applications, custom WordPress and WooCommerce, and Shopify storefronts. A fair share of it is taking over something somebody else built — which is the main reason I write mine to be handed on.

There is no account manager between us. You send a question, I answer it — usually the same working day, and in the same words I'd use to another engineer.

View my complete portfolio Start a project

Experience
12 years, continuous
Based in
Nagpur, India
Languages
English, Hindi, Marathi
Working hours
IST, overlapping EU & US East

05Testimonials

Good work. In their words.

The build matters. So does the experience of getting there.

AI product content automation
What mattered most

Saving time and money

Paul automated our website using the power of AI. Now we just upload a product image, and the complete product content is created for us. It is saving us both time and money.

Gravity Global Export CEO
Website & application development
What mattered most

Guidance at every step

Paul is a developer who can build any kind of website or application. Whenever we had a question, he guided us. The development process was smooth and stress-free, and his after-sales support was just as good.

Elsa Technologies CEO
WordPress development
What mattered most

An easier everyday

We used to put off updating our own website. Paul built a WordPress setup our team could actually use, and took the time to show us how. We left with a site we were proud of and the confidence to look after it.

Sophie Bennett Marketing Director
Laravel application
What mattered most

Clarity before code

Paul asked the questions we had not thought to ask. He turned a complicated workflow into a clear plan, explained the trade-offs, and kept us involved as the application took shape. We always understood what we were building and why.

Arjun Mehta Founder & Product Lead
Website performance
What mattered most

Fixing the real problem

What impressed us was how Paul explained the slowdown. He showed us where the time was going, fixed the underlying issues, and made the changes easy to understand. The site felt quicker, and we knew what to watch as it grew.

Daniel Brooks Managing Director
Website rescue
What mattered most

Calm under pressure

When our website was compromised, we needed someone who could make sense of the situation. Paul gave us a clear recovery plan, kept us updated, and explained what had gone wrong. His calm, methodical approach made a stressful week manageable.

Priya Kapoor Business Owner
AI workflow integration
What mattered most

Useful in daily work

Paul started with the repetitive work our team wanted off its plate. He built an AI workflow around that need, with a review step where our judgment mattered. It fitted the way we worked, which made it much easier for people to adopt.

Olivia Hayes Head of Operations
WooCommerce development
What mattered most

Care for the details

Paul paid attention to the parts of our store customers actually use: finding the right product, checking out on a phone, and receiving clear order information. He also thought about the people managing it behind the scenes. That care showed throughout the build.

Ethan Parker E-commerce Director
Website migration
What mattered most

A move with a plan

We were nervous about moving a website our business relied on. Paul mapped out the redirects, checked the forms, and walked us through the cutover. Having someone think through the small things before launch made the whole move feel under control.

Rohan Desai Business Development Director
Agency collaboration
What mattered most

Someone you can rely on

Paul was easy to bring into our team. He raised questions early, gave honest estimates, and flagged decisions before they became delays. We could see the work progressing and give our client clear updates. That made our job easier at every stage.

Charlotte Reed Agency Founder
Application handover
What mattered most

Confidence after launch

The handover was as considered as the build. Our developers received readable code, deployment notes, and a walkthrough of the decisions behind it. We could pick up the work with confidence because Paul had made the system understandable to the next person.

Lucas Morgan Engineering Manager
Ongoing development
What mattered most

Thoughtful partnership

We valued being able to bring Paul a problem before we had a solution. He listened, challenged assumptions, and helped us choose what was worth building next. The conversations were straightforward, and the work stayed connected to what our business needed.

Ananya Rao Co-founder & CEO

06QuestionsAsked often, answered plainly

What people ask before they write.

Who is Paul Edward?

I'm Paul Edward, a senior full-stack web developer based in Nagpur, India, with twelve years of production experience. I work mostly in PHP — Laravel applications, custom WordPress and WooCommerce, and Shopify storefronts — and I hold a Bachelor of Computer Applications and a Diploma in Web Logic.

What kind of work do you take on?

Custom Laravel applications and SaaS products, WordPress websites, themes and plugins, migrations to a new domain, host or stack, website speed and Core Web Vitals optimisation, and cleaning up hacked WordPress sites. If a project sits between two of those, say so in your first email and I will tell you which one it really is.

Do you work with clients outside India?

Yes. I work remotely with clients in the United Kingdom, the United States, Australia and Europe as well as India. My working hours are IST and overlap with the European and US East Coast working day.

Do you build WordPress sites with page builders like Elementor?

No. I build custom themes around your content, with native Gutenberg blocks and plugins written for one job each — so the site carries no page builder licence to renew and no forty-plugin stack to maintain.

How does a project start, and how quickly do you reply?

A paragraph by email or through the brief form is enough to start, and I usually reply the same working day (IST). You get the scope in writing — what is included, what is not, and what it costs — before anything starts, and the build happens on a staging URL you can open any day.

What do I get at handover?

The repository, the tests, deployment notes and a write-up of how it fits together — so whoever maintains the system next, including your own team, can start from it without me.

07ContactSame working day, IST

Tell me what you want built — or what's broken.

A paragraph is enough to start. If it isn't work I'm right for, I'll say so and point you somewhere better.

Start a project

Email [email protected]
LinkedIn Paul Edward
Typical reply Same working day, IST

Project brief Step 1 of 2 · The work

What do you want built?

A paragraph is genuinely enough to start. If it isn't work I'm right for, I'll say so and point you somewhere better.

The work

Pick everything that applies.

Platform

No idea is a perfectly good answer.

What are you trying to build, and what does it have to do for the people who use it? Write it the way you'd say it out loud.

0 / 1200

Two steps. Under a minute.