Custom Drupal Development
For a site that holds structured content, editorial rules and links to other systems: we design its Drupal architecture, write the custom code and hand over a documented repository.
Services
Drupal and web engineering for organisations and agencies: custom builds, our own platforms, and years of running them. You receive the source code.
An engineer reads it and replies within one business day.
Where to start
New websites, applications and products, built to be owned
For a site that holds structured content, editorial rules and links to other systems: we design its Drupal architecture, write the custom code and hand over a documented repository.
When your public website is the main way people reach your organisation, we design and build it on Drupal, and your editors get a component library to publish with.
A process that runs on spreadsheets and email becomes a web application with its own screens, permissions and history, built on Drupal around how your team works.
A product of your own, taken to a first version real users can sign up to, with sign-in, payments and admin reused from our platforms and only the new part built from scratch.
Policies, forms and tools that staff or members cannot find, brought into one Drupal intranet or portal with search, sign-in and publishing rights by role.
When the site looks dated but the content behind it is sound, we redesign what visitors see and leave the content, the page addresses and the editors' routine as they are.
For departments, programmes or branches that each need a site, we set up one shared Drupal platform on which each unit publishes on its own, under one identity.
A shop that belongs in the same Drupal site as your content, built on Drupal Commerce, or a Drupal 7 shop moved across with its catalogue and order history.
One body of content behind a website, an app and partner feeds: we set up Drupal as the editorial back end and the API they read from, with preview kept working for editors.
A feature no module provides, or a module left behind on an older Drupal: we write or port it, with tests, and hand it over in your repository.
When people struggle with a portal, an admin tool or a public site, we research how they use it and redesign the screens, handed over as a Figma component library.
When staff search documents for answers or retype forms by hand, we add an assistant that answers from your own content, or a step that reads the documents, inside the system they already use.
Your IT or product team sets the direction of a Drupal build and we staff it, at a fixed price, with the repository in your organisation's account throughout.
A system already running in production, deployed and customised for you
Your organisation gets its own deployment of EverLMS, MenuNerds, MineRooms, MineCourt or MineTickets, set up around your own process and seen working with your case before anything is signed.
Restaurant Ordering & Management Platform
In production for a restaurant franchise in Australia.
Sports Facility Booking & Management
Badminton venues in Ho Chi Minh City take court bookings online.
More platforms are on the way. All our platforms
Move off ageing platforms and find out what is really there
A site on a CMS that is unsupported or no longer fits: we audit what is worth keeping and move your content, users and files onto current Drupal, with the old addresses redirected.
For a Drupal 10 site that has to stay supported, we check each module and the custom code against Drupal 11 and 12, fix what breaks and upgrade the site in place.
When nobody on your side knows what the Drupal site is made of, we read it end to end and tell you in writing what to keep, what to change and where to look deeper.
An insurer, a board or a new owner wants to know whether the Drupal site is safe: we check it for the weaknesses attackers use and hand you the fixes in order of risk.
A tender, a complaint or your published accessibility statement puts the site in question: we test it the way disabled visitors use it and report each barrier with its fix.
Keep live systems patched, hosted, tested and improving
Sites we built and still maintain.
A live Drupal site with no team behind it gets a named team that patches it, watches it and reports each month; a site another team built starts with a takeover audit.
We keep the servers under your Drupal site running: releases, backups, certificates and alerts, on a setup you are free to take to another host.
Manual releases and environments that each behave differently, replaced by a build, test and deploy pipeline we set up for your team and hand over as code it runs itself.
When each release breaks something that used to work, we write the tests that catch it before it ships and leave your team able to extend them.
Pages that load slowly or fail Core Web Vitals: we find where the time goes on your real pages, fix the largest causes first and set a budget that keeps them fast.
Drupal work placed with us under your brand, in your tender or as your own team
Who sees what in a white-label engagement
What your client sees
Behind your agency
Your brand and your contract
NDA and non‑solicitation
When your agency wins more Drupal work than its team can build, we build it behind you, and your client only ever deals with your agency.
Your agency's clients keep a maintained Drupal site under your name: we apply the updates and fixes each month and write the report you pass on.
Drupal capacity your agency needs for months rather than one project: the same engineers join your team and take tickets as your own staff do.
When a tender or a consortium bid has to list who does the work, we appear in it as your Drupal subcontractor and deliver our share at a fixed price.
For agencies that bring our platforms to their own clients: we deploy and extend each system with you, and take that market on together.
Proof
Projects we designed and built for the client directly, and still maintain.
We redesigned sprep.org and rebuilt its Drupal theme twice, in 2017 and 2024, working directly with SPREP, and we maintain the site.
Read the case study
Fagogo, SPREP's staff intranet: designed and built by WeebPal in Drupal from the sprep.org base, and maintained since launch.
Read the case study
Apex Embroidery Designs: a Drupal store for embroidery designs, fonts and SVG files, rebuilt from Drupal 7 with its data migrated.
Read the case studyThe Weebpal team are awesome and easy to work with. They have made the design and development of the "Pacific NbS Resource Hub" a breeze and they are quick, efficient and I am really happy with the quality of their work and I highly recommend them.
Build projects
The order of work below is the one behind every build on this page: a new site, an application or a product. Migrations, takeovers and the monthly services start differently, as set out under the diagram.
Before a build is signed, we make a prototype at no charge: the content model and the admin screens running on a sample of your real content, so you correct something you can click while changes are still cheap.
Once the architecture is agreed, the scope and the price are written down and fixed. A change after that point is quoted as a change, so nothing the agreed architecture already needed comes back later as an extra. During the build you see working demos on a staging site rather than status reports, and at handover you receive the repository, the documentation and, where the system has editors, their training.
From first conversation to warranty
Not every enquiry should end in a project, and the cheapest thing we can do for both sides is say so early.
These terms hold across our services; where a service starts differently, its page says how. The full wording is on the warranty page and in why you own the source code.
Drupal is the core of what we build. Our web development service also takes work outside Drupal, and front-end frameworks such as Vue.js or React are used where a project needs them, as supporting technology rather than a separate line of work.
A custom build, such as a web application, starts from your requirements and an empty repository. A platform implementation takes one of our platforms that already does most of what you need, such as EverLMS for staff training or MineCourt for court bookings, and fits it to your organisation. Product development sits between the two: a new product of your own, with features no platform has, built on the sign-in, roles and admin layer our platforms already run in production. Whichever route you take, you receive the whole system and its source code.
With a Drupal site audit: one review of the modules, the custom code, the configuration, security, accessibility, hosting and speed, ending in a report that says what to keep, what to change and which deeper audit, if any, is worth doing. The report is yours, whoever does the work after it.
Yes. A takeover starts with an audit of the code, the modules and the hosting, priced on its own, so the maintenance plan is written from what is actually there rather than from a template. Support and maintenance covers sites we built and sites we inherit.
Yes. An agency can place Drupal work with us under its own brand, name us as a subcontractor on a tender, or reserve named engineers by the month. The NDA comes first and non-solicitation runs both ways, on the same terms for every agency; the partners page sets out how we take platform work to market together.
On the pricing page: project bands from Micro to Strategic, and a rate card for team work. Each service page names the band its work usually falls in, and the price for your project is fixed once the architecture is agreed.
More answers about ownership, the warranty and how projects run are in the project FAQ.
Tell us what you are trying to run. We will tell you which of these it is, what it takes, and whether one of our platforms already does most of it.