What made it awkward
Those three jobs pull a WordPress install in different directions. Membership wants accounts, tiers and renewals. Events want dates, registration and a listing that does not go stale. The public pages want to be editable by staff who are not developers and should never have to open a template to change a paragraph. Off-the-shelf plugins cover any one of these well and the combination badly. The usual outcome is four plugins that each own part of the member record and disagree with each other about it.
What we built
- A membership layer where the member record is held in one place rather than split across plugins
- An events calendar with registration, run by chamber staff rather than by us
- Custom plugins for the behaviour the off-the-shelf options got wrong, so the rest of the stack stayed standard
- Editable page layouts in Elementor, so copy and structure changes do not need a developer
Stack
Where it stands
Live and in day-to-day use by the chamber's own staff, who run membership and the event calendar without coming back to us for routine changes.
On the missing numbers
There are no percentage uplifts on this page. We do not publish a client's performance figures without their written permission, and we have not asked for it on these three. What you can check instead is the work itself: each site is live at the address given, doing the thing described. If you want measured results before committing to a project, ask us and we will go and request them from the client concerned.
The service behind it
This build is part of our WordPress and WooCommerce plugin development work. The rest of what we have delivered is on the portfolio page.
The other case studies
- EduQ: E-learning store with WooCommerce enrolment
A Dutch e-learning provider selling courses directly to learners, where the catalogue, the checkout and the course access all have to be one continuous flow rather than three systems introduced to each other by hand.
- ProTranslate: Two-sided translation marketplace on Laravel
A translation marketplace rather than an agency brochure site. It has to serve customers who need a document translated and the translators who do the work, which is why it is filed here under web development and not under SaaS.