Service before software
We measure success by the impact our customers have, not by features shipped. The platform exists to make the mission more durable.
About
Built by practitioners for the organizations that steward people.
Technology In Ministry is a software and infrastructure firm based in Lafayette, Indiana, serving mission-driven organizations nationwide. We were founded by a practitioner who has spent years on both sides of the table — sitting in the board meetings, then writing the code.
Founder
Charles Thurman
Charles Thurman is the founder of Technology In Ministry, LLC. With a background spanning enterprise software engineering and direct service inside mission-driven institutions, he started TIM to close a gap he’d watched widen for years: the gap between what nonprofits actually need from technology and what most vendors are willing to build for them.
TIM’s clients today include denominational bodies, grant-making programs, women’s funds, and youth-serving organizations. The work spans organizational assessment, mass messaging, grant infrastructure, and the kind of right-sized custom platforms that institutional buyers rarely find on a price list.
Founder bio is a placeholder pending review. Headshot to be added before launch.
Why “Ministry”?
The word comes from the Latin ministerium — service, work, office.
To minister to something is to attend to it. The name signals our values — service, stewardship, mission — more than it signals a religious requirement. Faith-based organizations recognize it as home; secular nonprofits should hear it as a commitment to the work of service itself.
We were born inside a faith-based context, and our deepest case studies still live there. But the methodology — practitioner-built, compliance-first, right-sized, owned-not-rented — adapts cleanly to women’s funds, youth organizations, community development, foundations, and nonprofits of every kind.
We believe every mission-driven organization, faith-based or secular, is doing ministry in the deepest sense of the word. Their work is the attending; ours is the infrastructure that lets the attending scale.
Software in service of service.
What we hold to.
Plain language
If a board member can't explain what we built to a treasurer, we haven't finished. Technical credibility doesn't require technical opacity.
Compliance, by design
TCPA, SOC 2, PCI — these are features, not footnotes. We build the audit trail in, so you never have to assemble one after the fact.
Owned outcomes
The code is yours. The data is yours. The Azure subscription is yours. We are the partner; the infrastructure belongs to the mission you serve.
Let’s begin