What we do
White-label Drupal for agencies, builds and migrations for companies, and products we run
-
Agencies that need Drupal engineers under their own name
Partner programmeWe build in your repository and tracker, look after your clients' live sites under your brand, reserve engineers for you by the month, or join your tender as a named subcontractor. A mutual NDA comes first, non-solicitation runs both ways and the warranty is held by your agency.
Nothing we deliver under an agency's name appears on this site. Agencies that give us Drupal work have reviewed us by name, among them Ingenuity Solution in the United States and Sazae in Australia.
-
Companies and organisations: new builds, migrations, upgrades and support
What we buildWe design and build websites, portals, intranets, web applications and Drupal Commerce stores. We move sites off Drupal 7, WordPress, Joomla or a bespoke CMS with their content, users and files, and upgrade Drupal 10 sites to 11 and 12. We also maintain live sites, including ones another team built, after a takeover audit.
Running today: CreAct's CAB and iCAB application for a consultancy in the UAE and Switzerland, and Apex Embroidery Designs' store, moved off Drupal 7.
-
Products we build and run, for training, restaurant ordering and bookings
Our productsEverLMS runs training, MenuNerds restaurant ordering, MineRooms hotels and MineCourt court bookings. We deploy one on your domain with your roles and content set up, and adapt it where you need more; what already runs is not charged as if it were written again, and you receive the running system and its source code. Agencies deliver the same products to their clients with us, under the agency's name.
Running today: EverLMS for JFC's staff training and MenuNerds for a restaurant franchise, both in Australia, and MineCourt for badminton venues in Ho Chi Minh City.
Milestones
What we have built, year by year
Each client system named here is still running, and each links to its case study or product page.
-
2012: WeebPal is founded
Zircon, the first thing we publish on Drupal.org, goes up that March and later becomes the first free Drupal 8 theme there.
-
2017: sprep.org redesigned
SPREP case studyWe redesign SPREP's main site and rebuild its Drupal theme; SPREP brings the second redesign back to us in 2024.
-
2021: Apex Embroidery Designs leaves Drupal 7
Apex Embroidery Designs case studyWe design the store and rebuild it on Drupal, carrying its catalogue and data over from Drupal 7.
-
2023: H&N Corporation
H&N Corporation case studyOne Drupal site for H&N's services between Australia and Vietnam, with visa and passport applications made online behind a customer account.
-
2024: CreAct's CAB and iCAB application
CreAct case studyFor a strategy consultancy in the UAE and Switzerland, we build a web application on Drupal from scratch, with each client company given its own permissions.
-
2026: JFC on EverLMS
JFC case studyJFC's safety, compliance and operations training for staff and contractors in Australia goes live on EverLMS, deployed and customised by us.
-
2026: MenuNerds for a restaurant franchise
MenuNerdsMenuNerds goes into production for a restaurant franchise in Australia, each store on its own subdomain and guests ordering by QR code at the table.
Our commitments
What you can hold us to
Each of these has its own page, which sets out what it covers and where it stops.
-
A prototype before you sign
How we workFor a new build or one of our products, the first thing you see is a design, a clickable prototype or a working demo on real code, made at no charge before anything is signed.
-
A price fixed once the architecture is agreed
Project sizes, Micro to StrategicScope and cost are committed against an architecture you have seen, and they move only if you change the scope.
-
The source code is yours
Source code ownershipCustom work is yours from the first commit: the repository, custom modules, theme and deployment configuration.
-
A warranty of one to three years
Warranty termsOne year by default on every development project, up to three by agreement, with defects fixed by the team that built the system.
-
Response targets we publish
Support and maintenanceCritical issues are answered first, high priority within 1 business day and normal within 3 business days. Support runs in business hours; cover outside them is an option, priced separately.
-
Code you can read before you hire us
Our open-source workOur modules are published on Drupal.org, where anyone can read the code and the issue queues; the current WE Mega Menu release runs on Drupal 10.3, 11 and 12.
Questions
Questions we get asked
Who will we talk to?
An engineer. Every enquiry is read by an engineer, and the first call about a project is with one; the team page sets out who does what.
Do you only work with Drupal?
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.
Why Drupal?
Because a large share of any enterprise product is users, roles, permissions, audit history, translation and an administrative interface, and Drupal has those tested, maintained and open. Starting from a bare framework means rebuilding them and owning the bugs. It is also open source, which is what makes handing you the whole thing possible.
Do you build mobile apps?
Only as part of a web system we build, where a native app is genuinely warranted: offline use, push notifications or hardware the browser cannot reach. We build it in Flutter against the same API, and we do not take standalone app work.
What does the warranty actually cover?
Defects in what we delivered on a development project, measured against what was agreed, and the Drupal core and contributed security releases applied during the term. It is not a support contract and does not cover a change of requirement; the warranty page sets out the boundary in full.