ALTURA SYSTEMS

In production, built by us.

Before we sell a setup, we run it. These are systems we built and operate ourselves, each written up the same way: the problem, what we built, and how it runs today.

Client case studies will join these as engagements finish, written the same way and only with the client’s permission.

Automation sprints, in production

A multi-campus church, automated end to end

Organization
A multi-campus church
Connects
The church’s member database, member messaging, the giving platform and social channels
Status
In production
Built and run by
David Horton

The problem

A church with several campuses runs on a small staff and a lot of goodwill.

Visitors fill in connect cards. Gifts arrive through a giving platform. Members expect to hear from the church on the messaging channels they already use. Prayer requests, volunteer sign-ups and questions come in through forms. Each of those depends on someone copying something from one place to another, and when that person is busy, a first-time visitor does not get a call.

What we built

  • Visitor follow-upA connect card triggers a personal welcome and a follow-up task for the right pastor or team.
  • Giving notificationsGifts from the giving platform update records and notify the people who need to know, without re-keying.
  • Member messagingMember messaging driven by the church management system, so the contact list never drifts from the real records.
  • Intake routingForms go to the person responsible for that kind of request instead of a shared inbox.
  • Social publishingPosts for sermons and events are prepared and published on schedule.

How it runs

The workflows run in production, every week, with no one copying data between systems. David Horton built them and maintains them as part of running the church’s technology, which is why our sprints come with a runbook: it is the document we wished we had.

A product from Altura AI

ChurchAI.tools

What it is
AI workflows, policy and training for ministry teams
Practice
Altura AI, our applied AI practice
Status
Live
Website
churchai.tools
Monitoring
Checked every five minutes on our status page

The problem

Access to AI is solved. Using it reliably is not.

Anyone can open a chat window. What small ministry teams lack is the layer above it: a repeatable procedure for a real task, quality that does not depend on who is typing, and an agreed position on what the church will and will not use AI for. Without that layer, AI produces one impressive result and then quietly stops being used, or gets used badly where accuracy and confidentiality mattered.

What we built

  • Structured workflowsStep-by-step procedures for tasks teams repeat, such as preparing teaching material, drafting communications and writing up reports, each with the inputs, the prompting and what good output looks like.
  • Governance and policyTemplates a church can adopt: what AI may be used for, what must never be pasted into it, who reviews output, and how AI involvement is disclosed.
  • TrainingTutorials that walk a real person through a real task, rather than demonstrating a feature.

How it runs

Teams connect their own AI account. Their content goes straight to the provider they chose, not through us, and usage is billed by that provider at its own rate. Because the account belongs to the church, changing provider or leaving does not strand its work.

The same thinking shapes our client work: you hold the keys, and we tell you which provider sees what.

The AI operations team, run on ourselves

Altura’s own AI operations team

Organization
Altura Systems, Inc.
What it gives David
One place to ask for anything, work prepared overnight, and the final say on everything that goes out
Status
In daily use
Approver
David Horton

The problem

One person leads Altura, with a limited number of hours each week.

Research, outreach, content, proposals and a weekly plan would take all of those hours on their own. Hiring was not the answer at this stage. Handing it to agents with no supervision was not either.

What we built

  • A lead agentPlans the week against targets, coordinates the others and sends a report every Monday, including spend against revenue.
  • A research agentBuilds prospect lists and research briefs.
  • An outreach and content agentDrafts personal outreach notes and posts for David to approve.
  • One front doorDavid sends requests to a single assistant in the chat app on his phone, which routes them to the right agent.
  • Daily health checksThe system is checked every day, and problems reach David as alerts rather than surprises.

How it runs

Agents prepare. David approves anything sent or published, and every price, proposal and invoice. Each agent has a monthly budget cap. Delivery and proposal agents join the team when they have client work to do.

If you hear from Altura, a person approved it. That is the same rule we install for clients.

A product we build and run

Donivo

What it is
Online giving for churches and nonprofits
Built for
Churches and nonprofits, internationally
Payments
Card and international gifts through established payment processors, paid straight to each organization
Status
In early access

The problem

Giving online should be as easy as any other payment, and for many churches it is not.

Recurring gifts, givers abroad, tax receipts and year-end records make taking donations harder than it looks. Many small churches and nonprofits end up with a bank account number on a slide and a spreadsheet to reconcile.

What we built

  • Giving pages and a widgetA hosted giving page for each organization, and a form that embeds in an existing website with one script tag.
  • Recurring givingGivers set up weekly or monthly gifts and can cancel them themselves from an email link.
  • CampaignsFundraising pages with a goal and a shareable link.
  • Tax receiptsDonation receipts and tax certificates generated and emailed automatically, where the organization’s country supports them.
  • A dashboardGiving totals, donor history and CSV exports for the finance team.

How it runs

Payments go through established payment processors straight to each organization’s own account. Donivo never holds a balance, and card data stays with the payment processor; our systems keep only the transaction reference and its status.

It is in early access today and not yet open for public sign-up, so there is nothing to go and try yet. Ask on a call and we will show you. What we learned building it, about webhooks, receipts and reconciliation, is the same work we do for clients’ giving and payment workflows.

Products we build and run.

Alongside client work, Altura builds its own products for churches and nonprofits. They keep us honest about what it takes to run software that people rely on.

Yours could be the first client write-up.

Bring one workflow. If it works and you are happy to be named, we write it up the same way as these.

Book a call Compare the offers