CASE STUDY

How Understanding the Word Ministries Moved 47,906 Bibles (and Counting) Off Spreadsheets and Onto One System

A Lafayette ministry traded three disagreeing workbooks for one AI-built system, built and hosted by Vital.

Talk to Our Team →All Case Studies

At a glance

  • Client: Understanding the Word Ministries, known publicly for its Bible Cartel program
  • Industry: Nonprofit and ministry
  • Location: Lafayette, Louisiana
  • Services: AI-assisted custom software, built and hosted by Vital
  • 47,906 Bibles and counting, tracked in one place, including 29,845 counted historically and brought forward from the old workbooks
  • 1,382 orders and 12,795 individual Bible records under management, with a complete timeline of 10,914 recorded changes
  • 161 change requests raised by the team in nine weeks; 159 shipped, at a median of 1.7 hours from ask to live
  • 194 automated checks, carrying 3,196 assertions, run against real production data before any release is allowed
  • 132,308 lines of code in 78 days, an estimated 7,056 to 13,231 developer hours, delivered with AI

The challenge

Understanding the Word Ministries personalizes Bibles for named people: elected officials, athletes, first responders, community leaders. Each one is engraved by hand with that person's name, their verse, their district or their team. Every Bible carries a stamped five-digit number so the person who receives it can look it up and send their story back.

The work was running on spreadsheets. One workbook held the orders, another the registry of stamped numbers, another the historical counts. Artwork moved by text message and email, and approvals happened in whichever inbox saw them first. Nobody could answer a simple question (where is this Bible now, who is drawing it, has anyone checked it) without opening three files and asking two people.

Reporting to donors meant rebuilding the same count by hand every time. The counts came out differently depending on who built them, because the spreadsheets disagreed with each other. And the ministry was growing faster than the manual version could hold.

Why they chose Vital

Founder David Hoke wanted an Acadiana team for an Acadiana ministry: someone who would sit with the people doing the work rather than hand over a system and leave.

What decided it was the approach to AI. They did not want an off-the-shelf nonprofit CRM bent into a shape it was never meant to hold. They wanted a system built around how they actually work, and AI-assisted development made a custom build affordable for an organization with no IT staff and no software budget.

The solution

Assessment

Vital sat with the team and mapped the real process (intake, artwork, quality control, approval, engraving, prayer and packaging, manifest, dispatch), then matched the spreadsheets against it. The gap between the two was the specification.

Plan

One system, two public front doors, on Cloudflare's edge network. Nothing was to be left behind in a workbook: the history would be migrated and counted alongside the new work, with no double counting across the seam.

Rollout

For the public: a live impact map, the Bible registry, downloadable Bible studies, a testimony wall, and prayer and donation intake. Anyone holding a Bible can scan the card or type the stamped number and see that Bible's story.

For the team: every order from intake to shipment. Artwork upload with review and sign-off, engraved photo capture, inventory and allocation, shipping manifests and box contents, the stamped ID registry, approval links a requester signs from their phone, and notifications so nothing waits on somebody remembering to follow up.

The history came too: 1,235 orders and 29,845 historically counted Bibles were migrated out of the workbooks rather than abandoned.

Training and ongoing support

A feedback button sits on every screen. The team raises a request where they hit the problem, and it is read the same day. Most of the training happened by the tool changing to match how they already worked.

What it took to build

The system is 132,308 lines of hand-written application code and schema across 543 files, built in 78 days across 417 releases. A separate 39,278 lines of generated import code carried the spreadsheets in; those are counted separately so they cannot pass as engineering effort.

At conventional solo-developer output of 80 to 150 lines a day, counting design, testing and rework, that is an estimated 7,056 to 13,231 developer hours, or 44 to 83 months of full-time work for one person.

Vital delivered it with AI in 78 days. That hours range is an estimate derived from lines of code, and the only figure in this case study that is not directly measured; everything else is counted from the live system.

The results

Before, the answer to "where is this Bible" lived in three files and two people's heads. Now it is one page.

  • 47,906 Bibles and counting, tracked in one place, 16,822 of them individually stamped and registered, with 11,183 named recipients on record
  • All 50 states reached, shown on a map that updates itself instead of being rebuilt by hand
  • 1,239 Bibles completed end to end inside the new system since cutover, with 10,914 recorded changes behind them, every edit carrying who made it and what the value was before
  • 5,194 files of artwork, engraved photography and paperwork (22.1 GB) filed against the Bible they belong to, rather than sitting in a text thread
  • 161 change requests from the team in nine weeks. 159 shipped, one declined, one carried forward. Median time from request to live: 1.7 hours. 147 of the 159 were resolved inside one day.
  • Seven people run the entire operation on it, most of them on phones, several of them volunteers
  • 25,044 stamped numbers on the registry, 16,822 of them issued and live; 480 shipping manifests built in the system
  • 6,269 Bibles in stock across 91 products, counted in the same place the orders are raised
  • 206 testimonies received and 325 Bibles registered by the people who received them

Frequently Asked Questions

How long does it take to replace spreadsheets with a custom system?

Understanding the Word Ministries was live and taking real orders three weeks after the first line of code, and the history was migrated in alongside it. The work did not stop while it happened; they kept shipping Bibles the whole time.

Can an organization with no IT staff run custom software?

Yes, when it is built and maintained for them. Seven people here run the whole operation on it, most on phones. Vital holds the hosting, the releases and the support, so nobody at the ministry administers anything.

What happens when we need it to work differently?

You ask, from inside the system. This team raised 161 requests in nine weeks and 159 are shipped, half of them within two hours. A tool that cannot change is a tool that gets worked around.

Running on spreadsheets that disagree with each other?

We should talk. Vital builds and runs custom systems for Acadiana businesses and nonprofits.

Talk to Our Team →