Richard Neville WEB APPLICATION ENGINEERING

Richard Neville — Web Application Engineering

Think systems. Design systems. Build systems.

I design and build web applications that connect the data, people, workflows and platforms your business relies on.

You work directly with me, from the first conversation to the changes after launch.

Discuss a project Explore my work
RN monogram for Richard Neville, formed from binary digits
  • Building commercial web platforms since 2012
  • UK based, with established North American heavy-duty automotive clients
  • Direct access to the engineer responsible
  • Long-term platform relationships, not launch-and-leave delivery
Richard Neville at his desk, looking at the camera
Richard Neville Web application engineer, UK

01 — About

You speak directly to the engineer responsible.

Hi, I’m Richard.

I’m a UK-based web developer and application engineer. I’ve been working in web development since 2009, and building bespoke web applications since around 2013.

I take the time to understand your business, how things work today and what you need to improve. From there, I design and build applications that support the way you work and connect the systems you rely on.

You’ll work directly with me throughout — from our first conversation to development, launch and ongoing support.

How I work →

02 — Work

The problems I’m brought in to solve.

Your business shouldn’t have to work around its software. I help turn scattered product information, complicated ordering and disconnected systems into applications that work together—and give your team a clearer way to get things done.

Product catalogues and data

One source of information. Different ways to use it.

Product information often ends up spread across spreadsheets, supplier feeds and separate documents. Customers, distributors and sales teams need different views of it, and keeping those versions aligned becomes a job of its own.

I bring categories, subcategories, product groups and variants into a shared product system, alongside descriptions, specifications, attributes, metadata, media and supporting documents. Multilingual content and publishing rules let that same source serve different audiences, markets and languages.

  • Structured product data
  • Audience-specific publishing
  • Languages & markets
FIG. 01 — A shared product system. The right information for customers, distributors and sales teams.

Ecommerce, payments and fulfilment

From basket to delivery—and everything behind it.

Off-the-shelf platforms can be useful starting points, but growing requirements can leave a business juggling plugins, workarounds and manual steps. A useful ecommerce system needs to connect the whole buying experience.

I build baskets, customer pricing, offers and discount codes alongside accounts, address books, order history and access to invoices. Payment gateways, tax calculations, stock availability, reservations and dropshipping integrations connect the sale to the work behind it.

Shipping services, tracking, customer notifications and transactional emails keep customers informed after checkout, while order and invoice information flows into the systems your team uses.

My shipping integration experience includes FedEx and UPS; other carriers, such as DPD and Parcelforce, can be assessed for your project.

FIG. 02 — The buying experience, fulfilment and customer updates, connected around one order.

API integrations and connected workflows

Let information move. Give people the tools to manage it.

Orders re-entered into an ERP. Customer records copied to a CRM. Invoices transferred to accounting. When systems don’t share information, your team becomes the connection between them.

I build API integrations and the internal tools around them, including data mapping, validation, background synchronisation and approval workflows. Connections can bring together accounting, ERP, CRM, PIM, fleet, HR, customer service, shipping and tax systems, according to the project.

Clear checks and visible exceptions let staff see what needs attention, correct the problem and retry the record rather than losing it in a background process.

  • API integrations
  • Admin & approvals
  • Process automation
FIG. 03 — Routine information moves between systems. Exceptions reach someone who can resolve them.

Infrastructure and ongoing support

Secure foundations. Controlled releases. Ongoing care.

The application is only part of the system. Its Linux environment, web services and database need to remain secure, maintained and dependable as the software and your business change.

Security across the stack. I combine application development informed by the OWASP Top 10 with Linux hardening, cloud firewalls, access controls and regular security updates.

A clear route into production. Version-controlled changes and CI/CD workflows bring together automated checks, staging review and controlled releases. Alongside deployments, I look after monitoring, backups and troubleshooting, and help established systems move forward through migrations, PHP upgrades and careful modernisation.

  • Application & server security
  • CI/CD & deployments
  • Maintenance & upgrades
FIG. 04 — The application, its security and the environment it depends on, looked after together.

03 — Approach

From the first conversation to the work after launch.

Whether we’re improving an existing platform or building something new, we start with what your business needs to achieve. We agree the priorities, work through the design and build in stages you can review, with ongoing support after launch.

  1. Understand

    I take the time to understand your business, the people using the system and how things work today. Together, we identify what’s getting in the way and what a better solution needs to achieve.

    You get A clear understanding of the problem and priorities.

  2. Plan

    We agree the scope, the systems involved and a practical way forward. I explain the options and trade-offs, so you understand what’s proposed, what comes first and how it fits your budget.

    You get An agreed scope and a plan for delivery.

  3. Design & Build

    I work through the key user journeys, screens and interactions with you before building them. Development then progresses in working stages, with testing and regular opportunities for you to review and refine the result.

    You get A considered design and working software you can review throughout.

  4. Support & Evolve

    After launch, I continue looking after the application and the environment behind it. That includes maintenance, resolving issues and developing improvements as your business and requirements change.

    You get Ongoing support from the engineer who knows your system.

04 — FusionStack

Shared foundations. Built around your business.

My modular platform for bespoke applications, commerce and connected business systems. Reusable components give every project a stronger starting point, with more of the work focused on what your business needs.

In development. Working modules already in use.

  • FusionFramework Foundation

    The shared application foundation. Common structure and services are maintained together, with separate modules for each business’s requirements.

  • FusionCore Admin & content

    Administration, users, roles, permissions and content management, brought together in a consistent place to run the application.

  • FusionCommerce Commerce

    The commerce layer: product catalogues, orders, payments and shipping, connected with the wider systems a business relies on.

  • FusionAI Intelligence

    Intelligence within the workflow. Already turning work records, commits and merge request descriptions into editable invoice line items in FusionOps.

  • FusionConnect Integrations

    Reusable connections between business systems. GitLab, Hive and QuickBooks connectors are already in use within FusionOps.

Less reinvention.

Build on reusable foundations, so development can focus on the requirements that make your business different.

Shared improvements.

Coordinated deployment brings platform improvements and important security patches to client systems together.

Your own custom modules.

The modules and customisations developed specifically for your business are yours, separate from the shared platform.

Already at work in FusionOps.

Work tracked in GitLab and Hive becomes editable invoice lines through FusionAI. I review the invoice before posting it to QuickBooks, with FusionConnect joining the systems.

How the workflow works

I select a customer and date range in FusionOps. FusionAI uses the relevant work records, commit messages and merge request descriptions to generate invoice line items. I can edit the hours and rates, save the invoice for review and post it to QuickBooks when I’m happy with it.

A platform built and maintained by Richard Neville. Modular by design.

05 — Working together

Think systems. Design systems. Build systems.

Good systems start with a conversation.

A clear way forward, from the first discussion to the work after launch.

Richard Neville Web application engineering

From the first conversation to the work after launch, you work directly with me.

Tell me what needs to work better.

Start with a conversation

Free initial discovery, with a high-level proposal and suggested next steps.

Think systems.

  1. 01 · Conversation

    Start with a conversation.

    I start by learning about your business, the systems you use and what needs to work better. Free initial discovery gives you a high-level proposal with a suggested approach and next steps.

    Richard What needs to work better?

    You Our systems don’t talk to each other.

    We’re passing everything around in spreadsheets and email.

    Richard Let’s work out a better way.

  2. 02 · Agreed plan

    A plan before the build.

    Where a project needs deeper investigation, I propose a paid discovery phase. The scope, responsibilities and terms are then agreed with you before design and development begin.

Design systems.

  1. 03 · Wireframe

    Wireframes establish the structure.

    I lay out the key screens and journeys simply, so you can see what each one needs to do.

  2. 04 · Visual design

    The same screens, designed.

    The agreed structure takes on a considered visual design you can see and respond to.

  3. 05 · Prototype and approval

    Try it, comment, approve it.

    A prototype brings the key journeys to life, with room for your feedback and refinement before development.

Build systems.

  1. 06 · Development

    Working software you can follow.

    I turn the agreed design into a working application, connected to the systems it relies on.

  2. 07 · Staging and checks

    Review it in staging.

    You can review progress in staging while I check the application and its connections before launch.

    • Key journeys reviewed
    • Connections tested
    • Acceptance criteria met
    • Ready to deploy

  3. 08 · Launch and support

    Launch is just the beginning.

    After launch, I provide ongoing technical support, maintenance and considered improvements as your business changes.

    Live

Richard Neville Web application engineering

From the first conversation to the work after launch, you work directly with me.

Tell me what needs to work better.

Start with a conversation

06 — Contact

Let’s make your next project happen.

You might have an idea ready to explore, an application that needs improving, or systems that should work better together. Whatever stage you’re at, I’d like to hear about it.

A few details are enough to get started. I’ll read your enquiry personally and come back to you with a useful next step.

Richard Neville Independent web application engineering

Tell me what you have in mind.

Tell me a little about what you’re planning or what you’d like to improve.

I use your details to respond to and manage your enquiry. Your enquiry may be read by AI-assisted tools, including AI features in Hive, my work-management service, to help me handle it, research what you need and estimate the work, with my review. Read the Privacy Notice for details and your rights.

I usually reply the same working day, or the next working day if you get in touch outside UK business hours.

Richard Neville
Discuss a project

RICHARD NEVILLE · WEB APPLICATION ENGINEERING
NEVWEB.CO.UK

Cookie settings

Necessary

Always active

Supports site security, the enquiry form and remembering your privacy choices.

Off until you allow it. Allows Google Analytics to measure website use so I can improve it. This choice does not enable advertising features or send your enquiry text to Analytics.

Read the Cookie Policy