ProCraft — Case study 04Jeddah, Saudi Arabia

Bhatkal CommunityJeddah.

A community organisation serving a large expatriate membership in English and Urdu — three separate builds, each solving one specific operational job.

Doc — WORK/04 · Rev ACommunity organisationWeb development, custom platforms — three projects
Community organisation · Jeddah, Saudi ArabiaWeb development, custom platforms — three projects
04

Bhatkal Community Jeddah (BCJ)

02Project snapshot
Challenge

Volunteer time is the scarcest resource

Objective

Tools committees can run themselves

Solution

Three small builds, one job each

Outcome

Three separate engagements

Wide technical drawing of connected community systemsPlate 02 — three builds, one community
Fig. 01 — a community served in English and Urdu.Three engagements
04The challenge

Built to survive volunteer time.

A community organisation serving a large expatriate membership, operating in English and Urdu.

Community organisations run on volunteer time. Anything requiring technical skill to maintain stops being maintained. Everything had to be manageable by non-technical committee members.

The friction

Volunteer time is scarce

Technical upkeep stops

Two languages, one small team

Before — how community work got done
Member need
Committee WhatsApp
Volunteer hours
Manual admin
Burnout
05The transformation

Before

  • One big system idea
  • Manual administration
  • Developer-dependent

After

  • Three small tools
  • Committee-run admin
  • Volunteer-friendly upkeep
06Project goals

What needed to change.

01

Every tool manageable by non-technical committee members.

02

Serve a bilingual membership — English and Urdu — as equals.

03

Solve one operational job per build, nothing speculative.

04

Keep each system small enough that volunteers actually run it.

07Plan of work

Six stages, repeated three times.

01Discover

We map the business, audience and where the current setup breaks.

02Strategize

What gets built, what stays manual, what it costs and how long.

03Design

Experience and interface agreed on paper before development.

04Build

Developed to the drawing with scalable, modern technology.

05Launch

Tested, deployed, the team trained — run in parallel until it holds.

06Grow

Improve, maintain and evolve. Support with a name and a number.

08Who it serves

One community. Different needs.

RoleCommittee

Runs portals and admin without developers.

RoleMembers

News, events and services — in English and Urdu.

RoleApplicants

Educational awards, applied for online.

RoleFamilies

Ramadhan planning, shared.

Three builds — one community
09The three builds

Three tools, one job each.

BCJ digital
Community portal
  • News & events
  • Bilingual EN/UR
  • Services
Awards portal
  • Applications
  • Review
  • Administration
Ramadhan planner
  • Schedule
  • Reminders
10The method
What we’d tell a similar organisation

Smallest thing, real problem.

Build the smallest thing that solves one real problem. Hand it to the committee. When it holds, repeat. Three builds later, the community runs its own systems.

One problem
Smallest build
Volunteer handover
It holds
Repeat
Awards portal · Ramadhan planner — plates pendingPlate — the three builds
11Deliverables

What we delivered.

01Community portal

Bilingual English/Urdu, committee-run.

02Educational Awards Portal

Applications and administration online.

03Ramadhan Planner

One season, one job, done well.

04Committee handover

Training so it survives volunteer turnover.

12Technology

The build.

Representative build — chosen for volunteer-friendly upkeep.

PlatformsCustom web
ContentBilingual system
WorkflowsApplications
AdminVolunteer-friendly
13Result
Outcome

Three separate engagements — the strongest signal available that the first one worked.

BeforeVolunteer burnout
AfterCommittee-run systems

A business like this one?

Same starting condition, different sector — tell us where your current setup breaks and we’ll map it in one working session.