Zion Church

The description states that Zion Church is a church management platform for Ugandan churches, intended to ease collecting offertory, fundraisers, and memberships. The author, Allan Kisembo, built it as a personal project during a hackathon using GPT 5.6 Terra, Convex, Next.js, Vercel, and VSCode. It is presented as a web app with features including announcements, donation collection, fundraisers, and email capture for membership.

Key commercial due-diligence questions include:

• What is the actual market demand for this solution in Uganda?
• How does the author plan to scale beyond one person building it?
• Is there any evidence of early user feedback or adoption?

The most important open question: Is there a viable business model or path to traction that can be demonstrated from the self-reported evidence?

The description states:

• Zion Church is a web app.
• It enables churches to manage themselves digitally.
• Features include publishing announcements, collecting donations, setting fundraisers, and capturing emails for membership.

Inference: Based on the author's own write-up, it appears to be a SaaS-style platform built for small-scale church operations in Uganda. The author claims to have used GPT 5.6 Terra for development, though this is not a standard toolchain and may refer to an experimental or proprietary approach.

The description states:

• The product is positioned as "a church management platform for Ugandan churches."
• It aims to ease collecting offertory, fundraisers, and memberships.
• The author built it after being disturbed by poor donation channels during mass services.

Inference: This is a self-described solution to a perceived problem in local church operations. The positioning appears to be niche — targeting churches in Uganda specifically — with an emphasis on digital transformation of traditional church activities.

The description states:

• The target customer is "Ugandan churches."
• The platform is meant for churches to manage their own activities digitally.

Inference: The ICP seems to be small-to-medium-sized churches in Uganda, particularly those seeking digital tools for basic administrative tasks like announcements and donations. However, no evidence of specific customer segments or personas is provided.

The description states:

• No explicit pricing model is mentioned.
• The platform collects offertory, fundraisers, and memberships.
• It is described as a "web app" that enables churches to manage themselves digitally.

Inference: There is no evidence of a monetization strategy or pricing structure. The author does not indicate whether the platform will be free, subscription-based, or transaction-fee driven.

The description states:

• Built using GPT 5.6 Terra (author claims to have used this for development).
• Backend is Convex.
• Frontend uses Next.js.
• Hosted on Vercel.
• Code editor is VSCode.
• GitHub is used for version control.

Inference: The technical stack suggests a modern web application built with serverless components and frontend frameworks. However, the use of "GPT 5.6 Terra" is unusual and may be a misstatement or experimental approach; further clarification would be needed to assess delivery capability.

The description states:

• The author built it during a hackathon.
• It was submitted to the OpenAI 2026 hackathon on Devpost.
• The author claims to have made progress despite time constraints.
• He plans to market the platform within weeks after submission.

Inference: No evidence of traction, revenue, or user adoption is provided. The project appears to be in early development stage, with no indication of prior users or customer engagement beyond the author’s own experience.

The description states:

• No mention of competitors.
• The author does not reference existing church management platforms or tools.

Inference: There is no evidence of competitive analysis or awareness of existing solutions. It is unclear whether similar products already exist in Uganda or globally, and how this product would differentiate itself.

The description states:

• Only one team member (the author).
• Built during a hackathon with limited time.
• No revenue, customer, or traction data.
• The use of "GPT 5.6 Terra" is unusual and unverified.

Inference:

• Risk of scalability due to single-person development.
• Lack of early traction raises questions about market viability.
• Unusual technical claims (e.g., GPT 5.6 Terra) may indicate lack of clarity or overstatement.
• No evidence of business model, pricing, or go-to-market strategy.

1. What specific problems in church management are you solving, and how do you know these are real?
2. Have you spoken to any churches about their needs or willingness to pay for such a service?
3. How will you scale beyond one developer?
4. What is your plan for monetization and pricing?
5. Are there existing church management tools in Uganda that you're aware of?
6. Can you demonstrate any early user feedback or engagement?