Skip to content
T73 Solutions
Start
VEIR Church mark

CASE STUDY 01 · VEIR CHURCH

One database.Three front doors.

A growing church in Huntsville was running on group texts, spreadsheets, and memory. We built a public website, a staff operating system, and a member portal on one shared database, so every guest has an owner and every family has a home.

Visit veirchurch.net ↗
ROLE
Strategy, design, and build by Zaire Willis, Executive Pastor at VEIR
WHAT WE BUILT
Public website · VEIR OS (staff) · My VEIR (members)
WHO USES IT
Guests, member households, 8 staff
STATUS
Live · Website since August 2026 · Platform since October 2026
PROOF
300+ automated security checks before launch

01 — The challenge

Everything lived in people's heads.

VEIR had no real systems. Information was spread across spreadsheets, group texts, and paper cards. Things were forgotten. Guests could visit and never hear back. Leadership had no single view of the church, and the back door was open.

Sunday attendance

Head counts texted to a group chat.

Reported in the Sunday report, with history.

First-time guests

Paper cards, typed in by hand, with no owner.

Every guest assigned to a named person, with a 24-hour clock.

Member records

An old, out-of-date spreadsheet.

Households that families maintain themselves.

Children's information

No secure home for allergies or pickups.

A locked record only VEIR Kidz leaders and pastors can see.

Finances

Expenses scattered across workbooks.

Weekly expenses inside the finance report leadership already reads.

02 — The thinking

Start with the problem. Not the platform.

Off-the-shelf church software could have stored names. It couldn't give every guest an owner, bring paper cards into the same follow-up as online visits, or keep children's information locked down by role. So we designed around how VEIR actually works.

  1. 01

    One database, three front doors.

    A guest, a member, and a staff record are the same person. One source of truth means nothing has to sync.

  2. 02

    Every guest gets an owner.

    A rotation assigns each new guest to the next available staff member. Repeat visitors go back to the same person. If no one reaches out in 48 hours, leadership is alerted.

  3. 03

    Start fresh, with consent.

    Instead of importing an old spreadsheet, every household fills out the same profile, longtime members included.

  4. 04

    Privacy you can prove.

    Each role sees only what it needs. Children's care notes, private prayer, and pastors-only notes are locked at the database level, and staff emails never contain them.

  5. 05

    Phases, not a big bang.

    The website first, then people and follow-up, then the member portal. Each phase was live and in use before the next began.

DELIBERATELY NOT BUILT

  • An app-store app and group chats (the church already lives in WhatsApp).
  • Automatic duplicate merging (a person decides).
  • Tracking or analytics inside the member portal.

03 — The system

How it fits together.

ONE SHARED DATABASE

Every email starts in the database, so none goes out unless a saved change asked for it.

04 — Try it

Don't take our word for it. Use it.

Working copies with sample data. No real member information is shown.

veirchurch.net

The front door. Plan Your Visit, the Member Profile, and Prayer all feed the same database.

05 — Proof

Privacy you can prove.

The hardest part wasn't the screens. It was proving who can see what. Before anything went live, every step had to pass a test suite that pretended to be a guest, a member, or each staff role, tried everything that role should and shouldn't be able to do, and then undid itself, so no test data was ever left behind.

NO DOUBLE EMAILS

Each email claims its slot before sending. If a send fails, the next run retries.

DAYLIGHT-SAVING PROOF

Reminders check Central time inside the database, so 9 AM stays 9 AM all year.

NO ACCOUNT PROBING

The portal never reveals whether an email belongs to a member.

KIDS' PRIVACY BY DESIGN

Allergies and care notes live in a locked record. Staff emails never contain them.

BOT AND DOUBLE-TAP PROTECTION

Every public form ignores bots and can't be submitted twice.

06 — In your business

This isn't only a church problem.

Swap the words and the same systems run a salon, a clinic, or a service business.

AT VEIR

Every guest gets an owner and a 24-hour clock.

IN YOUR BUSINESS

Every new lead is routed to the right person, with reminders and escalation.

AT VEIR

Families fill out one household profile.

IN YOUR BUSINESS

Clients complete intake once, and update it themselves.

AT VEIR

Children's care notes only certain staff can see.

IN YOUR BUSINESS

Sensitive client details locked to the roles that need them.

AT VEIR

Duplicates are flagged for a pastor to merge.

IN YOUR BUSINESS

A clean client list, without risky automatic merging.

07 — The outcome

Everyone on one accord.

DOCUMENTED

27+

member households joined in the first week of launch

  • First guest planned a visit through the website, assigned and followed up automatically.
  • Website live since August 2026. Staff and member platform live since October 2026.
  • 13 New Members Class dates generated a year ahead.
  • 7 of 8 staff in the guest follow-up rotation.

INTENDED

What VEIR built this to do, still being measured:

  • Close the back door: every guest contacted within 24 hours.
  • Leadership follow-up reviewed every week.
  • Stronger member retention, with families keeping their own information current.
“This is next level. This is phenomenal.This is going to help our church to grow.”

SENIOR PASTOR, VEIR CHURCH

STRATEGY, DESIGN & BUILD

ZAIRE WILLIS

ORGANIZATION

VEIR CHURCH, HUNTSVILLE, AL

LIVE

VEIRCHURCH.NET

Next case study →

DEW Beauty Co.

COMING SOON