Most people hear “AI acquisition” and think of nine-figure enterprise deals — massive platforms swallowed by Big Tech. But some of the most interesting acquisitions happen at a different scale: a focused product, built to solve a specific problem for a specific audience, that becomes exactly the piece a larger company needs to complete its vision.
That’s the story of Faith Assistant.
The Problem: Ministries Drowning in Engagement Demand
Churches, parachurch organizations, publishers, seminaries, and homeschool organizations all face the same challenge: people have questions, and there aren’t enough hours in the day to answer them all.
A seminary student wants to understand a theological concept at 11 PM. A church member needs guidance on a grief support program but doesn’t want to call the office. A publisher’s readers want to go deeper on a book’s themes but there’s no interactive way to do that. A homeschool parent needs curriculum recommendations tailored to their child’s learning style.
These organizations are mission-driven. They care deeply about the people they serve. But they’re also resource-constrained — most are running lean teams that can’t scale one-on-one engagement to match demand.
The typical “solution” was a chatbot that pulled from generic databases or a static FAQ page. Neither felt right for organizations where trust, nuance, and doctrinal accuracy matter enormously.
The Insight: Train AI on the Ministry’s Own Content
The core insight behind Faith Assistant — originally called Bible Chat — was simple but powerful: instead of building a generic religious chatbot, build an AI assistant that could be trained on each ministry’s own content.
That meant a church could deploy an AI assistant that knew their specific teachings, programs, and pastoral approach. A publisher could offer readers an interactive companion trained on their actual books. A seminary could provide students with a study tool grounded in their curriculum.
This wasn’t just personalization for its own sake. In faith-based contexts, accuracy and alignment with the organization’s own theology and values isn’t a nice-to-have — it’s the entire point. A generic AI that confidently states something contradicting an organization’s core beliefs doesn’t just miss the mark; it actively damages trust.
[PLACEHOLDER: Timeline — when did you start building? How long from first code to acquisition?]
Building the Product
Faith Assistant was built as a conversational AI platform with a few key technical decisions that would later prove critical to its acquisition value.
Custom content training pipeline. Each ministry’s AI assistant was trained on their own materials — sermons, books, curriculum, program descriptions, doctrinal statements. This wasn’t simple RAG over a document dump. The system needed to understand context, maintain theological consistency, and know when to defer rather than hallucinate.
Multi-tenant architecture. Every organization got their own isolated instance with its own content, its own personality, and its own guardrails. A Southern Baptist church’s assistant behaved differently from a Catholic publisher’s assistant — because it should.
Conversational depth. The goal wasn’t surface-level Q&A. Faith Assistant could engage in extended theological discussions, walk someone through a study plan, or help a grief support team member find the right resources — all grounded in the organization’s actual content.
[PLACEHOLDER: Team composition — solo build or small team?]
[PLACEHOLDER: Scale metrics — users, conversations, ministries served at time of acquisition]
What the Acquirer Actually Cared About
On January 15, 2025, Faith Assistant was acquired by Gloo. Terms were not publicly disclosed.
For context: Gloo is a faith-and-flourishing technology platform co-founded by Scott Beck (CEO), with Pat Gelsinger — former Intel CEO — serving as Executive Chairman. Gloo’s mission is to help faith leaders and organizations grow and serve their communities more effectively through technology.
In November 2025, Gloo went public on the Nasdaq at $8.00 per share (9.1 million shares), debuting at approximately $586 million in valuation. According to their SEC S-1/A filing, Gloo acquired 15+ mission-aligned businesses through July 2025 as part of building out their comprehensive platform.
Faith Assistant is now integrated into Gloo’s AI stack.
So what made Faith Assistant valuable to an acquirer building a comprehensive faith-tech platform? Three things stand out — and they’re the same three things I look for when helping businesses build AI products today:
1. A Clear Vertical Wedge
Faith Assistant wasn’t “AI for everyone.” It was AI for faith-based organizations, purpose-built for their specific needs. This kind of vertical focus is counterintuitive for many founders — it feels like you’re limiting your market. But it’s exactly what makes a product acquirable. The acquirer doesn’t want a horizontal tool they have to reposition. They want something that already fits their ecosystem perfectly.
Gloo serves faith leaders and organizations. Faith Assistant served faith leaders and organizations. The fit was immediate and obvious.
2. Customization Trained on the Customer’s Own Content
Generic AI is a commodity. Every organization can spin up a ChatGPT instance. What they can’t easily do is create an AI that truly understands their specific content, maintains their voice, and respects their boundaries.
Faith Assistant’s content training pipeline — the ability to take a ministry’s own sermons, books, and materials and create an AI that genuinely represented that organization — was a technical moat. It’s the difference between “we added AI” and “we added AI that actually sounds like us.”
3. Trust and Values Alignment
In faith-based contexts, trust isn’t just a feature — it’s the foundation. An AI assistant that occasionally says something theologically off-base doesn’t just give a wrong answer; it can genuinely hurt someone seeking guidance during a vulnerable moment.
Faith Assistant was built with this understanding from day one. Content guardrails, theological consistency checks, and the ability for organizations to review and refine their AI’s responses weren’t afterthoughts. They were core architecture decisions.
This matters beyond faith tech. Any industry where trust is paramount — healthcare, financial services, legal, education — needs AI that’s built with the same rigor around accuracy and alignment.
[PLACEHOLDER: The acquisition story — how did Gloo find you? Did they approach you?]
The Methodology Behind the Product
Looking back, the approach that made Faith Assistant successful is the same methodology I now bring to every Rogers Technology engagement:
Start with the domain, not the technology. I didn’t build Faith Assistant because LLMs were exciting. I built it because I understood a specific problem that specific organizations faced, and I saw how AI could solve it in a way nothing else could.
Build for the customer’s content, not generic data. The most valuable AI products aren’t the ones trained on the internet. They’re the ones trained on your data — your processes, your knowledge, your voice.
Design trust into the architecture. Guardrails, accuracy checks, and human oversight aren’t limitations on AI. They’re what make AI deployable in contexts where the stakes matter.
Focus on a vertical until you own it. The temptation is always to go broad. But depth in a specific domain — understanding the nuances, the edge cases, the cultural context — is what creates real value. It’s what makes customers trust you. And it’s what makes acquirers want you.
[PLACEHOLDER: What you’re most proud of about the product]
From Building Products to Building for Others
Faith Assistant was a product I built and brought to market. But the lessons from that journey — and the methodology behind it — are exactly what I now apply when working with mid-market businesses on their AI automation initiatives.
The questions are the same whether you’re building a faith-based AI assistant or automating a business process:
- What specific problem are we solving, and for whom?
- What data and content does the AI need to be trained on?
- What are the trust and accuracy requirements?
- How do we measure success?
- What does the handoff to autonomous operation look like?
The difference is that now, instead of building one product for one vertical, I help businesses across industries apply these principles to their own operations. The technical patterns transfer. The methodology transfers. The obsession with getting the domain right — that definitely transfers.
If you’re wondering what it looks like to build and deploy AI tailored to a specific industry — that’s exactly what I do for businesses now. Whether you’re exploring AI automation for the first time or you’ve tried off-the-shelf tools and hit their limits, I can help you figure out what’s worth building and then build it.