Three offers, each with a finish line.
Every offer has a defined scope and a set price. Start with one workflow, add an assistant, or hand us the daily operational work. Whatever we build, you own.
We do not take on open-ended custom projects. A fixed scope is how we give you a firm price and a date.
The offers at a glance
| Offer | Best for | Timeline | Price |
|---|---|---|---|
| Automation sprint | One repetitive process that follows the same steps most weeks. Featured: guest follow-up for churches | 2 weeks | $4,000 Fixed price, paid upfront Founding $2,400, first 3 clients |
| AI assistant setup | Questions your staff or your people ask again and again | 7 days | $3,200 Care plan $400 Founding $2,000, first 3 clients |
| AI operations team | Daily operational work spread across several people | 2 weeks from kickoff | Monthly retainer, quoted after a call Billed monthly |
Founding rates are open to our first three clients, in exchange for a published case study.
Automation sprint
One workflow, designed, built and handed over in two weeks. We automate the process costing your team the most copy-paste, end to end, and leave you with a runbook.
- Timeline
- 2 weeks
- Price
- $4,000
- Founding price
- $2,400, first 3 clients only
- Terms
- Fixed price, paid upfront
Guest follow-up, live in 14 days
Every guest assigned to a staffer, overdue follow-ups surfaced, a weekly completion report, and nothing sent to a guest until a named staffer approves it. It runs on the church management system and giving tools the church already uses.
- Timeline
- 14 days
- Price
- $4,000
- Founding price
- $2,400, first 3 clients only
A good fit when
- The process happens every week and follows the same steps most of the time.
- The data already lives in tools: forms, a CRM, email, a calendar, spreadsheets.
- Someone on your team can own the workflow once it is live.
Typical first sprints
- Lead intakeForm or inbox to CRM, a drafted follow-up for approval, and tasks for the owner.
- Client onboardingIntake form, folders, welcome email, document requests and kickoff tasks.
- Guest follow-up for churchesEvery guest assigned, overdue follow-ups surfaced and a weekly report, with a named staffer approving each message. This is our featured sprint.
What you get
- The workflow, liveRunning in production on your accounts, tested with real cases from your team.
- A runbookWhat it does, what it touches, how to pause it and what to check when it stops.
- Error alertsFailures go to a person you name, not to an inbox nobody reads.
- A handover sessionA walkthrough with the person who will own it.
How the two weeks run
- Scoping callWe map the process as it runs today, including the workarounds, and agree the one workflow and what done looks like.
- Build, week oneWe connect your tools and build the workflow in a test setup, with approvals wherever something leaves your business.
- Test, week twoYour team runs real examples through it. We fix what they find.
- HandoverIt goes live. You get the runbook and the walkthrough.
Not in scope: a second workflow, software built from scratch, and cleaning up records that were already wrong before we arrived. One sprint is one workflow. If the scope grows while we are in it, we finish the workflow we agreed and quote the rest separately rather than quietly extending the two weeks.
AI assistant setup
An assistant trained on your own material, for your staff or for the people you serve. It answers from your documents, stays inside the limits you set, and hands over to a person when it should.
- Timeline
- 7 days
- Setup
- $3,200
- Founding setup
- $2,000, first 3 clients only
- Care plan
- $400
- Terms
- Fixed price, plus an optional monthly care plan
A good fit when
- Staff ask the same questions about policies, procedures or products.
- A public inbox or website keeps answering the same things.
- The answers are already written down somewhere, even if scattered.
What you get
- A knowledge baseBuilt from your documents, organized so the assistant answers from them rather than guessing.
- GuardrailsWhat it will and will not answer, the tone it uses, and the topics it always passes to a person.
- Handover rulesWhen a question needs a person, it goes to the named person or inbox with the conversation attached.
- A test setReal questions from your team, with the answers it gave, checked before launch.
- An admin guideHow to add or change material without calling us.
The optional care plan
Each month we update the knowledge base, review conversations for wrong or weak answers, and adjust the guardrails.
How the setup runs
- GatherWe collect the material and the real questions people ask, and agree what the assistant must never answer.
- BuildWe build the knowledge base, write the guardrails and set up the handover.
- TestYour team tries to break it. We fix the answers that were wrong and tighten the limits.
- LaunchIt goes live where your people already are, and you get the admin guide.
Not in scope: writing the material that does not exist yet. The assistant answers from documents you already have. If the policy was never written down, that is a writing job before it is an AI job, and we will tell you that on the call instead of billing you to find out.
AI operations team
The setup we run Altura on, installed for your business and run by us each month. Agents prepare. Automations send and update. A named person on your team approves anything sent, published or paid.
- Term
- Monthly retainer
- Price
- Monthly retainer, quoted after a call
- First agents
- 2 weeks from kickoff
A good fit when
- Recurring operational work is spread across several people.
- You want AI doing the preparation, with someone accountable for every outbound action.
- You would rather we run and maintain it than hire for it.
What runs each month
- Agents with clear rolesEach agent has one job, such as intake, research, drafting or bookkeeping prep, agreed with you.
- An approval queueNamed people approve, edit or reject. Every decision is logged.
- Automations that do the workConnected to your CRM, inboxes, calendars and messaging tools. They act only after approval.
- One front doorA single place your team sends requests to, such as a chat channel or an inbox.
- Daily health checksWe check the agents and workflows every day and tell a person when something needs attention.
- A monthly reviewWhat the team did, what it got wrong, and what to change next.
How it starts
- Map the workWe list the recurring work, who does it today and who should approve each kind of output.
- Install and connectWe set up the agents, the approval queue and the automations on your tools, in a project of your own.
- Supervised startEverything goes through approvals while your team learns what the agents do well and where they need limits.
- Run and reviewWe keep it running, check it daily and review it with you each month.
Not a fit: if you want agents acting with no person signing off, we are the wrong team. Approval is the part we will not remove.
Questions we get before a first call
Anything else, ask on the call or email [email protected].
Which tools can you connect to?
We connect to tools that offer an API or webhooks. That covers most CRMs, email, calendars, form builders, spreadsheets, chat apps and payment platforms. If a tool has no way in, we will tell you on the first call.
Who owns what you build?
You do. Workflows, prompts, knowledge bases and documentation belong to you. If you leave, we export them and help you move them.
Do agents ever send anything without approval?
Not in the setups we install. Anything that goes to a customer, a member or a supplier, or that moves money, waits for a named person. Internal preparation, such as research and first drafts, runs without sign-off.
Which AI models do you use?
We choose the AI provider per task, based on quality and how your data is handled, and we tell you which provider will see your data before anything is connected.
What happens if a workflow breaks after handover?
Each workflow reports its own errors to a person you name, and the runbook covers the usual fixes. If you want us watching it every day, that is part of the AI operations team retainer.
Can one sprint cover two workflows?
No. One sprint, one workflow. That is how it stays at two weeks and a fixed price. If you need two, book two sprints.
Do you take on custom projects?
Not at the moment. Fixed-scope offers let us give you a firm price and a finish date, and keep our time for the clients we already have.
Do you work outside the United States?
Altura Systems is a US company and the offers are built for US businesses. If you are elsewhere, ask. We will tell you plainly whether we can help.
Not sure where to start?
Tell us the process that costs your team the most time. We will say which offer fits, or that none does.