Design
Compare the options, agree on requirements, and define the intended result.
Choose the right controls. Implement them carefully. Verify they work.
Churches with known gaps or an assessment roadmap.
A fixed-scope project with approved costs and work windows.
Verified controls, documentation, and an IT handoff.
We begin with what you already own. Recommendations account for supported features, licensing, staff capacity, and the cost of maintaining each solution.
Compare the options, agree on requirements, and define the intended result.
Pilot the change, communicate with affected users, and roll out in an agreed work window.
Check the configured control and confirm essential ministry workflows still operate.
Document settings, exceptions, ownership, and the steps your provider needs to maintain it.
Make account access harder to steal and easier to govern.
Planning range for standard work.
Expanded work receives a custom proposal.
An account-control checklist, configuration record, tested sign-in and recovery paths, and an administrator handoff.
Limit the reach of a compromised account, device, or guest connection.
Planning range for standard work.
Expanded work receives a custom proposal.
An updated network/access map, configuration records, and approved connectivity checks showing critical ministry services still work.
Know what can be recovered, by whom, and in what order.
Planning range for standard work.
Expanded work receives a custom proposal.
A backup coverage matrix, sample-restore record, recovery runbook, and named owners.
Keep access proportionate to each person’s ministry responsibilities.
Planning range for standard work.
Expanded work receives a custom proposal.
A permissions record, approved exceptions, staff guidance, and a handoff for future access changes.
Give leaders a practiced response before a difficult decision becomes urgent.
Planning range for standard work.
Expanded work receives a custom proposal.
An incident playbook, finance-verification checklist, exercise debrief, and accountable action register.
Your proposal names the systems, account and device limits, exact changes, rollback arrangements, acceptance checks, and responsible people. Published ranges apply to straightforward standard projects; complex migrations, expanded AI governance, large deployments, or extra systems are quoted separately. Hardware, subscriptions, travel, and taxes are additional. Approved smaller requests can be billed at $200/hour with an agreed spending limit.
Keep the people who know your environment involved. We agree on who makes each change, who checks it, and who supports it after handoff.
Technical handoff covers the agreed solution. Add a dedicated staff workshop when your team needs broader practice recognizing attacks and using defensive procedures.
Explore on-Site TrainingKnow your risks. Prepare your people. Leave with a plan.