One workspace for the whole staff.
A request comes in through a form, its approvers sign off, the work lands as a task, and the team talks it through in chat. No copying between three tools.
Requests that route themselves.
Facility bookings, events, purchases, time off. Start from a church request template or build your own, set who approves each step, and every submission goes to the right people. No more 'who handles this?' threads.
- Nine templates: facility, event, purchase, check, creative and communications, time off, volunteer, background check and incident
- Approval paths with rules for who signs off at each step
- Public links: anyone can submit, no account needed
- An approved request can create a task and post to a channel
- Status tracking: waiting on someone, approved or declined
Every project, from request to done.
A list and a board for every project: events, building work, ministry launches. Break work into subtasks, start from a template, and decide the approvals waiting on you in the same place.
- List and board views
- Subtasks and reusable task templates
- Approvals waiting on you, with every step and decision on record
- Share any task into Chat
Where your staff actually talks.
Channels, threads and direct messages, with the rest of your work one keystroke away. Share a task or a request into any conversation so everyone is looking at the same thing.
- Channels for ministries, teams and events
- Threads keep side conversations out of the channel
- @mentions and emoji reactions
- ⌘K to jump to any channel, person, project or form
An assistant that knows your workspace.
Ask Eklo works from your workspace, and searches the web when a question needs it. Ask what's still open in a project, what a channel decided or what's waiting on you, or have it add a task. It only sees what you can see, and asks before doing anything that tells someone else.
- Finds tasks and searches the channels you can read
- Lists the requests waiting on your decision, and approves or declines one after you’ve read its answers on the Confirm card
- Adds tasks and changes your own, with Undo. Changing someone else’s task, or giving a task to someone or taking one from them, waits for your Confirm
- Posts in channels and sends requests, only after you click Confirm
- Reads files you attach, searches the web and makes images
- Owners and admins can turn AI off for the whole church
Eklo sits alongside solutions like Planning Center.
Keep them for your people, giving and check-ins. Eklo is where your staff runs requests and approvals, projects and tasks, and team chat.
$543 a month becomes $149.
What 25 staff pay for Slack, Asana and Jotform at list price, against Eklo Standard: one workspace, one bill.
See what you'd save at your sizeList prices in October 2026: Slack Pro billed monthly, Asana Starter billed yearly. Jotform gives churches 50% off; Slack and Asana usually don't.
- Slack Pro, 25 people at $8.75
- $219 a month
- Asana Starter, 25 people at $10.99
- $275 a month
- Jotform Silver
- $49 a month
- Slack, Asana and Jotform
- $543 a month
- Eklo Standard
- $149 a month
Ready for your IT director's questions.
Single sign-on
SAML with Okta, Microsoft Entra ID or Google Workspace, and Require SSO. Every church can use it during the beta.
No passwords
People sign in with a passkey, an emailed code or Google.
Your data, whenever you want it
Owners and admins can export the workspace’s data at any time.
Hosted in the US
On Amazon Web Services, with every subprocessor listed.
A data processing addendum
A DPA that covers how Eklo handles your church’s personal data.
An off switch for AI
Owners and admins can turn AI off for the whole church.
One flat price per church.
Every plan includes Chat, Tasks, Forms with approval workflows and Ask Eklo. You pay for the size of your team, not for every seat.
Starter
For church plants and small teams getting started.
Up to 5 members.
Standard
For single-site churches of about 500 to 1,200.
Up to 30 members. Or $1,490 a year.
Multi-Site
For multisite churches, or single sites of about 1,200 to 4,000.
Up to 100 members. Or $3,490 a year.
Enterprise
For churches of 4,000 and up, and large multisite networks.
Unlimited members. Billed yearly.
What churches ask us.
What is Eklo?
Eklo is the operating system for church staff: request forms with approval workflows, tasks and projects, and team chat in one workspace, with Ask Eklo, the AI assistant, built in. It replaces Slack, Asana and Jotform at one flat price per church.
Who is Eklo for?
The staff of churches of about 500 people and up, and the volunteers who work alongside them: the people who handle facility, event and purchase requests, run projects and keep each other up to date. Smaller teams can use Starter, free for up to 5 members.
Does Eklo replace Planning Center?
No. Eklo sits alongside solutions like Planning Center, which keep a church’s people, giving and check-ins. Eklo is where church staff run requests and approvals, projects and tasks, and team chat.
What does Eklo replace?
Slack for team chat, Asana for projects and tasks, and Jotform for request forms and approvals. For 25 staff, those cost $543 a month at list price; Eklo Standard is $149 a month.
How much does Eklo cost?
One flat price per church, not per seat. Starter: free for up to 5 members. Standard: $149 a month or $1,490 a year, for up to 30 members. Multi-Site: $349 a month or $3,490 a year, for up to 100 members. Enterprise: from $699 a month, billed yearly, for unlimited members. Paid plans can add members at $4 each a month.
What can Ask Eklo see?
In your workspace, only what the person asking can see: the people in it, the teams they can see, tasks in projects they can open, messages in channels they can read, the forms they can see, and the requests they sent or that wait on their decision, without the answers on them. It also reads files they attach, keeps notes they ask it to remember, and can search the web. It doesn’t read direct messages. Owners and admins can turn AI off for the whole church.
Is our data secure?
Eklo runs on Amazon Web Services in the US. There are no passwords to steal: people sign in with passkeys, emailed codes or Google, or with your own SAML single sign-on through Okta, Microsoft Entra ID or Google Workspace, which every church can use during the beta. Owners and admins can export the workspace’s data at any time, every subprocessor is listed, and a DPA is available.