HomeGift — Private Digital Offertory Web App

What the company appears to be: HomeGift is a self-reported private digital offertory web app designed for use by parishes to enable contactless giving via QR codes, NFC plaques, livestreams, parish pages or direct messages. It allows users to select an offering amount and choose between manual or bank transfer methods, with a focus on compliance, privacy, and disclosure.

What changed: During the OpenAI 2026 hackathon, the project focused on strengthening safety layers around an existing donor journey, particularly by introducing explicit disclosure and governance controls before payment processing. The author states that this effort improved compliance and clarified the payment boundary — HomeGift does not receive or hold offerings but acts as a facilitator to church-specific giving pages.

The single most important open question: Is there any evidence of actual adoption, traction, or integration with commercial payment providers? The description indicates no active Pay by Bank provider is yet integrated, and manual transfers are conditional on church-specific authorisation. This raises uncertainty about whether the product has moved beyond prototype or proof-of-concept stage.

The description states that HomeGift is a private digital offertory web app for parishes. It enables users to make donations via:

• QR codes
• NFC plaques
• Livestreams
• Parish pages
• Direct messages

Users are directed to a parish-specific giving link, where they:

1. See disclosure and policy links they must acknowledge.
2. Choose an offering amount.
3. Select a donation method (manual or bank transfer).
4. Are then redirected to either the church or selected bank/payment provider.

The author notes that HomeGift already had features like:

• Parish-specific pages
• Offering amounts
• Bank selection
• Manual-transfer support
• Baseline rate limits
• Admin capabilities
• A provider-neutral payment foundation

However, during Build Week, the focus was on adding safety and compliance layers, including:

• Explicit disclosure before amount selection
• Privacy, security, and data retention pages
• Anonymous-session tokens (HttpOnly cookies) upon acknowledgment

Inference: The app appears to be a web-based interface that acts as a bridge between donors and churches or banks, rather than holding funds itself.

The description states that HomeGift was built to address a real-world need for contactless offertory, particularly in the context of digital giving within religious communities.

It positions itself as:

• A parish-specific digital gift-giving experience
• Strengthened with privacy, disclosure, and payment-governance controls

The author claims that prior to Build Week, HomeGift already supported core functionality. The hackathon effort focused on improving trust and compliance, especially around:

• Transparency in data usage
• Clear boundaries between HomeGift and payment providers
• Ensuring donors understand who operates the page and what happens before any financial handoff

Inference: The positioning evolved from a basic giving tool to one emphasizing trust, compliance, and donor control — likely in response to concerns about cashless transactions in sensitive environments like churches.

The description states that HomeGift is intended for parishes, specifically those seeking a contactless offertory solution. It is designed to be used wherever people encounter the church, such as:

• QR codes
• NFC plaques
• Livestreams
• Parish pages
• Direct messages

There is no mention of other potential customer segments (e.g., non-religious organizations or individuals).

Inference: The primary ICP appears to be religious institutions, particularly those looking for a secure, compliant way to accept digital donations.

The description does not provide any information about:

• Revenue model
• Pricing structure
• Monetization strategy
• Customer acquisition costs
• Any commercial relationships or partnerships

It only mentions that:

• No commercial Pay by Bank provider is yet active.
• Manual transfer is conditional on church-specific authorisation and verified bank setup.
• HomeGift is actively seeking a commercial Pay by Bank integration partner.

Inference: The business model remains unclear. It appears to be in early development, with no evidence of monetization or pricing strategy beyond the stated goal of integrating with payment providers.

The author declares that HomeGift was built using:

• Neon
• Next.js 15
• PWA/service-worker support
• React 18
• Tailwind CSS
• TypeScript

It is described as having:

• Parish-specific pages
• Offering amounts
• Bank selection
• Manual-transfer support
• Baseline rate limits
• Admin capabilities
• Provider-neutral payment foundation

During Build Week, the team focused on:

• Adding safety and compliance layers
• Implementing explicit disclosure and acknowledgment steps
• Using HttpOnly cookies for anonymous session tokens after donor consent

Inference: The technical stack suggests a modern web application with progressive features. The focus on compliance and session management indicates attention to security and data handling.

The description does not contain any evidence of:

• Revenue
• Customers
• Adoption metrics
• Usage statistics
• Product-market fit
• Commercial partnerships

It states:

• HomeGift existed before Build Week.
• The current version was developed during a hackathon.
• No commercial Pay by Bank provider is yet active.
• Manual transfer is conditional on church-specific authorisation and verified bank setup.
• HomeGift is actively seeking a Pay by Bank integration partner.

Inference: There is no evidence of traction or commercial maturity. The product appears to be in an early stage, possibly pre-launch or in pilot mode.

The description does not mention:

• Competitors
• Market size
• Competitive advantages
• Differentiation from existing solutions

It focuses solely on the internal development and improvements made during Build Week.

Inference: No competitive context is provided. The author does not reference other platforms or tools for digital giving in religious settings, nor does it describe how HomeGift compares to them.

• No commercial integration: No active Pay by Bank provider is mentioned, and the team is actively seeking one.
• Manual transfer dependency: Manual transfers are conditional on church-specific authorisation and verified bank setup — suggesting limited scalability or adoption.
• Lack of traction: No evidence of revenue, customers, or usage data.
• Unproven business model: No pricing, monetization, or customer acquisition strategy is described.
• Early-stage prototype: The product appears to be in a pre-commercial phase, with no clear path to market yet.

1. What is the current status of integration with commercial payment providers?
2. How many parishes are currently using HomeGift or have expressed interest?
3. What is the intended pricing model and monetization strategy?
4. Has there been any feedback from churches or religious institutions about usability or trust?
5. What are the key assumptions underlying the product’s design, especially around compliance and privacy?
6. Are there any legal or regulatory considerations specific to digital giving in religious contexts that have been addressed?
7. How is the team planning to scale beyond a single developer (team size = 1)?
8. What are the main technical challenges remaining before full commercial launch?