Case study

Emmasdale SDA Church

From scattered communication to one digital centre.

Church digital platform · Strategy · UX · Full-stack development

Emmasdale SDA needed more than a new website. Information, member communication, and administration were spread across WhatsApp, Facebook, paper, and the church office.

Delivered

Public website
Member experiences
Leadership platform

Platform

One platform. Three experiences.

[ 01 ]

Public

Services
Ministries
Sermons
Events
Prayer & care

[ 02 ]

Members

Bulletin
Prayer wall
Devotions
Resources
Forms

[ 03 ]

Leaders

Reports
Care inbox
Scheduling
Administration

Context

The problem

Information was everywhere — but there was no digital centre.

Channels in play

Facebook
WhatsApp
Paper
Personal phones
Church office

Create one mobile-friendly platform connecting visitors, members, and leaders.

Shift

Before and after

Before

PDF bulletins, WhatsApp posters, and pulpit repeats — easy to contradict or lose.
Requests scattered across leaders' personal messages.
Records in clerks' files, private chats, and officers' phones.

After

One bulletin link with Sabbath School, divine service, announcements, prayer, and archive.
Public, anonymous, or confidential modes with leadership queues and follow-up.
Bulletins, submissions, approvals, reports, and care queues retained in the platform.

Outcomes

What changed

Before
Quarterly reports depended on paper and office visits.
After
Department leaders can submit reports from their phones.
Before
Prayer requests lived in private messages.
After
Appropriate requests can be shared through a prayer wall while sensitive care remains confidential.
Before
Weekly information was scattered across PDFs, WhatsApp, and announcements.
After
One digital bulletin gives members a consistent place to return to.

Method

How this was approached

The interesting part wasn't building the website — it was figuring out what needed to be built.

[ 01 ]
Investigate
Stakeholders · channels · workflows · journeys
[ 02 ]
Diagnose
Where information, participation, and admin broke down
[ 03 ]
Architect
Public + members + leaders on one platform
[ 04 ]
Build
Website · workflows · dashboard
[ 05 ]
Ship
Live platform at emmasdalesda.org

“For the first time we can point members and visitors to one place — this Sabbath, prayer, ministries, and how to get help — instead of five different WhatsApp groups.”
— Church leadership

Behind the build

Want to see how the decisions were made?

Full investigation — context, journeys, evidence, diagnosis, and implementation detail for readers who want the forensic version.

View full investigation ↓

Business context → customer journeys → evidence → diagnosis → recommendations → architecture → implementation

The business case

From scattered communication to a church digital platform

Emmasdale SDA had an active congregation, strong communication channels, and many digital touchpoints — but information, member care, and administration were spread across Facebook, WhatsApp groups, paper forms, personal phones, and the church office.

The church did not only need a better website. It needed one digital centre connecting the public, members, and church leadership.

What I investigated

·How visitors find and understand the church
·How members access weekly information and spiritual resources
·How prayer and care requests reach leaders
·How departments submit reports and information
·Where WhatsApp, paper, and office-based processes created friction

What I built

Public website

Services, ministries, events, sermons, articles, bulletin, Sabbath School, Daily with God, prayer, care, and visitor information

Member experiences

Digital bulletin, prayer wall, devotional content, resources, and church information

Leadership platform

Role-based dashboard, digital forms, quarterly reports, care inbox, scheduling, document requests, and ministry administration

The result

Visitors, members, and leaders connect through one system — public information, member participation, and operational workflows on a mobile-friendly platform.

Strategy · UX · Architecture · Full-stack development — investigated, designed, built, and shipped.

View the full investigation →

The business

3 connected audiences

Visitors & seekers

Public witness

Bulletin · care · prayer

Member life

Reports · forms · records

Leadership ops

The customer

3 customers. 3 journeys.

Visitor

“When and where is church?”

Needs

Service times
Plan your visit
Ministries

Member

“How do I stay connected all week?”

Needs

Bulletin
Prayer wall
Devotions
Events

Leader

“Can I run my department from my phone?”

Needs

Reports
Forms
Care inbox
Scheduling

The diagnostic

Where the journey breaks

Discover

Strong Facebook reach

Orient

No single official source

Participate

Prayer & care fragmented

Serve

Paper + office-bound admin

Return

Church felt tied to the building

Friction

Major points of friction

[ 01 ]
Church admin tied to paper and the church office
Quarterly departmental reports, sign-offs, and routine data still meant physical forms, clerk handoffs, or long WhatsApp threads — work that had to wait until someone was at the church or at a desk.
Impact priority
█████████░
[ 02 ]
The church stopped when you left the building
Bulletin, programme, devotions, and updates lived in Sabbath-only moments, lost PDFs, or groups you might not be in — especially for travellers, the sick, diaspora, and shift workers.
Impact priority
█████████░
[ 03 ]
Prayer was a private message, not shared intercession
People texted a leader when they needed prayer; other members rarely saw appropriate public requests or could pray alongside them in a shared space.
Impact priority
███████░░░

So what needs fixing?

Not just a website

Public websiteMember journeysPrayer & care workflowsDigital forms & reportsRole-based dashboardMobile-first rhythm

The recommendation

A digital hub for worship, community, and church operations — on one platform.

The blueprint

System architecture

            EMMASDALE DIGITAL HUB
                     │
       ┌─────────────┼─────────────┐
       ↓             ↓             ↓
    PUBLIC        MEMBERS      LEADERS
       │             │             │
   Visit · Care   Bulletin ·    Reports ·
   Ministries    Prayer wall    Forms · Care
   Sermons       Devotions      Scheduler
       │             │             │
       └─────────────┼─────────────┘
                     ↓
            ONE MOBILE-FRIENDLY HOME

What changes?

Before → after

Before	After
Paper quarterly reports	Phone-friendly submissions
Private prayer messages	Shared prayer wall
Scattered WhatsApp lists	Structured digital forms
Sabbath-only information	Extended church between Sabbaths

Business context

Emmasdale SDA Church operates as an active Lusaka congregation with visible ministries and a large online audience (~5,800 Facebook followers). Value is created through worship, discipleship, care, and stewardship — not product sales. Before the platform, that work ran through disconnected Facebook posts, multiple WhatsApp groups, pulpit announcements, paper forms, and officers' personal phones.

Investigation

Business diagnostic aligned with the implemented product, original SRS, and operating model — stakeholder interviews, channel audit, care-path mapping, benchmark against mature SDA and church platforms, and validation against live modules on emmasdalesda.org. June 2026 business diagnostic aligned with the implemented product, original SRS, and operating model: stakeholder interviews, social and WhatsApp workflow review, care-path mapping, SDA/church benchmarks, and audit of live public routes and staff dashboard domains. Evidence confirmed the product is shaped as church digital operations — content, events, ministries, care, bulletins, forms, quarterly reports, facility scheduling, Camp Meeting, church-document requests, and role-based access — not a static brochure.

Sources

Stakeholder interviews
Social and WhatsApp workflow review
Live public site and staff dashboard audit
SDA / church platform benchmarks
Product domains (roles, ministries, care, scheduling)

Evidence snapshot

[ 01 ]
Department and church work still meant paper forms, office visits, and WhatsApp lists — leaders could not reliably submit quarterly reports or collect data from their phone
[ 02 ]
Members who missed Sabbath, travelled, or worshipped online had no single place for bulletin, devotions, sermons, and announcements — the church felt tied to the building and the right chat group
[ 03 ]
Prayer often went to one leader's inbox; the congregation could not see appropriate public requests and pray together, while sensitive needs still lacked a confidential path
[ 04 ]
Visitors and members could not trust one official, current source for service times, programmes, and how to request help

Visual evidence

Screenshot
Digital Bulletin

The fix

From diagnosis to build

Administration leaders can do from their phone

Problem: Quarterly reports, departmental figures, and routine church data depended on paper, office visits, and chasing people on WhatsApp.
Decision: Move repeatable church operations into the staff dashboard with mobile-friendly flows — starting with quarterly departmental reports and digital form collection.
Solution: Quarterly report modules with online completion and leadership review; digital form builder and submission inbox; role-scoped dashboard access on phone or computer.
Implementation: Quarterly report modules with online completion and leadership review; digital form builder and submission inbox; role-scoped dashboard access on phone or computer.
Outcome: Department heads can file reports without coming to the church office; collected information lands in organised records instead of scattered lists.

Extended church — connected on the phone

Problem: Church life felt limited to Sabbath in the building — bulletin, programme, and spiritual content were easy to miss if you were away, unwell, or online-only.
Decision: Design mobile-first public experiences: one bulletin link, daily reading, Sabbath School, sermons, and announcements that stay available all week.
Solution: Digital bulletin with archive and share images; Daily with God; Sabbath School read/watch/listen; sermon and article library; events and announcements on the public site.
Implementation: Digital bulletin with archive and share images; Daily with God; Sabbath School read/watch/listen; sermon and article library; events and announcements on the public site.
Outcome: Members stay connected to Emmasdale through their phones — not only through whichever group chat they happened to be added to.

Pray together on the wall, care in the right inbox

Problem: Prayer requests disappeared into private messages; members could not see public requests and pray with others, while sensitive needs still needed confidentiality.
Decision: Public prayer wall for shared intercession; separate anonymous and confidential paths into the staff care inbox with assignment and status.
Solution: Prayer wall with privacy modes; care and contact forms; church-family notices; staff care inbox with review, assignment, and follow-up.
Implementation: Prayer wall with privacy modes; care and contact forms; church-family notices; staff care inbox with review, assignment, and follow-up.
Outcome: The congregation can see appropriate requests and pray together; confidential needs still reach the right leaders with accountability.

Collect requests and information in one system

Problem: Every camp, event, department, or document need restarted collection in a new form, chat, or paper stack.
Decision: Use platform forms and structured intakes for repeatable church operations — documents, camp, feedback, and custom collections.
Solution: Form builder and submissions; document-request workflow with tracking and PDF issuance; Camp Meeting and pledge flows where enabled; facility and care request types.
Implementation: Form builder and submissions; document-request workflow with tracking and PDF issuance; Camp Meeting and pledge flows where enabled; facility and care request types.
Outcome: Information and requests arrive in defined queues — not lost in a leader's personal messages.

Visitor confidence before they arrive

Problem: Social media showed life at the church but not a reliable answer to service times, location, expectations, and how to get help.
Decision: Official public routes: Plan Your Visit, service times in under ten seconds, ministries, contact, and care intake.
Solution: Homepage, visitor guidance, maps, leadership and ministry pages, giving guidance, livestream entry, structured contact paths.
Implementation: Homepage, visitor guidance, maps, leadership and ministry pages, giving guidance, livestream entry, structured contact paths.
Outcome: Seekers move from uncertainty to confidence before Sabbath; members share one link instead of screenshots.

Scheduling before promotion

Problem: Activities and facility use were agreed in separate conversations, then announced publicly — sometimes before a room was actually available.
Decision: Treat the scheduler as the official path for facility requests once facilities and approvers are configured — adoption is governance, not more software discovery.
Solution: Scheduler module in the staff dashboard; configuration of facilities, resources, and approvers (ongoing church setup).
Implementation: Scheduler module in the staff dashboard; configuration of facilities, resources, and approvers (ongoing church setup).
Outcome: Fewer double-booked spaces; clearer rules for weddings, ministries, and meetings — when leaders use the workflow consistently.

Strategy

Make worship easy. Make administration easy.

Two connected sides, not a page collection: Side one — public witness, weekly rhythm, and participation: official service discovery, Plan Your Visit, ministries, events, sermons and articles, digital bulletin with archive, Daily with God, Sabbath School, prayer wall, care and document intake, giving guidance. Side two — leadership and administration: role-aware dashboard for bulletin publishing, content and event approval, care assignment, digital forms, quarterly departmental reports, facility scheduler, Camp Meeting and pledges, church-document issuance, and scoped ministry administration. Publishing stays controlled; confidential prayer and counselling remain staff-only.

Implementation

Public layer at emmasdalesda.org: visitor and member journeys, bulletin workflow output, devotionals and Sabbath School surfaces, prayer and care forms, church-family submissions, document requests with reference tracking, and giving instructions. Staff dashboard: bulletin editor, announcements and sermons, event and ministry management, care inbox, forms and submissions, quarterly reports, facility and resource scheduler, Camp Meeting administration, church-document review and PDF issuance, user and role administration — with permissions that mirror church and ministry structure.

How it works

Workflows

Quarterly report from a leader's phone

1.Department head opens dashboard on phone
2.Completes quarterly report fields
3.Submits for leadership review
4.Reviewer approves or requests changes

Prayer on the wall

1.Member submits a public prayer request
2.Request appears on the prayer wall
3.Others read and pray
4.Pastoral team follows up where needed

Outcome narrative

The platform already solves substantial parts of the original diagnosis: scattered communication, unclear Sabbath information, spiritual content without a permanent home, requests lost in informal channels, paper-dependent reporting, scheduling collisions, and manual document administration — when leaders adopt it as normal practice. The next challenge is governance and rhythm: named content owners, care response expectations, scheduler adoption, and honest scope boundaries (finance ledger, payment processing, and financial requisitions remain future modules — dashboard Requisitions are church-document requests).

Before → after

Church operations before & after

Weekly information
Before
PDF bulletins, WhatsApp posters, and pulpit repeats — easy to contradict or lose.
After
One bulletin link with Sabbath School, divine service, announcements, prayer, and archive.
Prayer & pastoral care
Before
Requests scattered across leaders' personal messages.
After
Public, anonymous, or confidential modes with leadership queues and follow-up.
Institutional memory
Before
Records in clerks' files, private chats, and officers' phones.
After
Bulletins, submissions, approvals, reports, and care queues retained in the platform.

Note

Dashboard “Requisitions” manages official church-document requests — not financial expense approval. Giving pages stay informational until treasury workflows are confirmed.

Scope & limits

Implemented: public site, digital bulletin, Daily with God, Sabbath School surfaces, prayer and care intake, digital forms, quarterly reports, facility scheduler, Camp Meeting and pledges, church-document requests, role-based dashboard. Future scope: full treasury ledger, payment processing, financial requisition chains, membership register, automated WhatsApp broadcasting, broad attendance analytics. Adoption and content ownership remain ongoing.

“For the first time we can point members and visitors to one place — this Sabbath, prayer, ministries, and how to get help — instead of five different WhatsApp groups.”
— Church leadership

Capability

Technology & role

Strategy · UX · Full-stack development

Next.js
Node.js
Role-based admin
Figma

If your organisation still runs on posters and personal inboxes, the friction is structural — a platform can unify public clarity and leadership workflow without replacing human judgment.

Have a similar problem?

Your website might not be the problem. The customer journey might be.

Start a Project

One platform. Three experiences.

Public

Members

Leaders

The problem

Before and after

What changed

How this was approached

Want to see how the decisions were made?

From scattered communication to a church digital platform

What I investigated

What I built

3 connected audiences

3 customers. 3 journeys.

Visitor

Member

Leader

Where the journey breaks

Major points of friction

Church admin tied to paper and the church office

The church stopped when you left the building

Prayer was a private message, not shared intercession

Not just a website

A digital hub for worship, community, and church operations — on one platform.

System architecture

Before → after

Business context

Investigation

From diagnosis to build

Administration leaders can do from their phone

Extended church — connected on the phone

Pray together on the wall, care in the right inbox

Collect requests and information in one system

Visitor confidence before they arrive

Scheduling before promotion

Implementation

Workflows

Quarterly report from a leader's phone

Prayer on the wall

Outcome narrative

Church operations before & after

Technology & role

Have a similar problem?