White labelSocial impact

Event space booking

One platform to run a multi-space social impact hub

A social impact hub in Southeast Asia ran bookings, payments, and finance in three disconnected systems, with staff joining the records by hand. Symph built the platform that holds the flow together, from member booking to finance entry.

We keep this client’s name private. The client is real, and so is the system.

At a glance

A booking, payments, and membership platform integrating a booking engine, a payment processor, and an enterprise finance system

Client: A social impact hub operating four heritage buildings as community, event, and media spaces
Industry: Social impact and community space management
Status: Live and in daily use, with a multi-year support and maintenance engagement running into 2027
Engagement: Build, then ongoing support and maintenance with scheduled feature builds

The challenge

The hub had good systems. They just did not talk to each other.

Three systems, one booking
The booking engine, the payment processor, and the finance system each held part of the same transaction, and staff joined them manually.
Engineers were the operations team
Routine staff requests were handled through direct database changes, so day-to-day operations depended on the engineering team.
That dependency was a real risk
If the support engagement ended with manual intervention still in place, no one outside engineering could service future requests.
Batch updates collided
Changing several booking statuses at once fired simultaneous webhooks, creating race conditions and risking inconsistent records.
Member administration had no owner
Organisations needed to change who held their membership seats without routing every change through staff.

How we built it

Symph worked with the client in three steps, each one building on the last.

Make the platform the connective layer
Symph built the platform as the system that holds a booking from first enquiry to finance entry. The booking engine, payment processor, and finance system each keep the one job they do well, and the platform coordinates them.
Give the client self-service control
Membership seats, space configuration, public content, FAQs, and membership terms moved into tools the client’s own teams operate. The standing goal is to retire every recurring manual engineering intervention before the support engagement ends.
Run a tested release cadence
Features are scoped against written acceptance criteria, built in sprint cycles, tested in staging by named testers across roles, regression tested, and checked against a production smoke checklist before release.

Modules

01
Space discovery and booking
Public space pages and a booking flow with pricing shown before commitment.
02
Media studio booking
Dedicated booking for the media production space, with seat selection, setup options, tiered rates, and two controlled access paths.
03
Organisation and membership accounts
Member organisations hold seats and manage their own people, replacing a departing member with a new invitation.
04
Admin booking management
Staff review, adjust, and confirm bookings, including changes after a payment link has been sent.
05
Payments and extra charges
Payment link generation, extra charges added before collection, and reminder emails before a link expires.
06
Finance synchronisation
Payment records flow into the client’s enterprise finance system.
07
Content management
The communications team manages public pages, FAQs, and membership terms without a developer.

Delivery model

01
Multi-year support and maintenance subscription
The client holds an ongoing engagement rather than paying for each change as a separate project.
02
Scheduled sprint builds
Approved features are grouped into numbered builds and released on a regular cadence.
03
Staged rollout with human acceptance
Every build moves through staging testing, regression, client user acceptance testing, and a production smoke checklist.

How it’s built

Proven architecture

The platform runs on a standard, well-understood web stack with a managed database and a hosted identity provider, built for reliability and easy maintenance.

Secure by default

Managed authentication, role-based access, encryption, and strict access controls protect member and payment data.

AI-native delivery

Symph’s engineers build with AI coding tools like Claude Code and OpenAI Codex, which is a big reason feature batches move from approval to release in weeks.

Application: Next.jsNestJSPostgreSQLFirebase AuthenticationHeadless CMS
Delivery and monitoring: GitHub Actions
AI-native development: Claude CodeOpenAI Codex

The result

One booking now runs end to end, from a member’s screen to a finance entry, without anyone retyping it.

1515features approved in a single batch
33systems joined into one booking flow

One source of truth per booking
Booking, payment, and finance records are tied to the same transaction instead of being joined by hand.
Fifteen features in one approved batch
A recent cycle covered studio access and pricing, admin booking controls, payment reminders, organisation administration, and booking form usability.
Self-service replacing manual intervention
Membership seats, space configuration, and public content are now operated by the client’s own teams.
A multi-year partnership
What began as a build is now a support and maintenance engagement running into 2027, with features approved and released in batches.