Serve more ministries.
Spend less time between systems.

Annualized fees are shown for comparison; the initial engagement term is 90 days.

We will monitor and care for the OpsIntel dashboard and its Paylocity, QuickBooks, Bill.com, and HubSpot connections, including correcting data issues and responding to vendor changes affecting those connections.

Every plan includes one completed advisory deliverable from the roadmap, email support, and a written monthly summary covering completed work, risks, decisions needed, and next priorities. In AI Foundation, that advisory deliverable is the monthly advisory package. Higher tiers retain it and add the implementation deliveries shown above.

Ashley will still validate the dashboard against July data. Existing project obligations will be reconciled at kickoff so prior work and ongoing system care are clearly accounted for.

The AI Operations engagement begins with the proposal workflow, the first feature deployed on the Kingdom One AI Operating System. We will map the current steps, use Ashley's branded template and approved service language, and configure a workflow that turns structured discovery notes or an approved transcript into a draft ready for review.

Your team keeps pricing approval and sending. Missing details and pricing questions will be flagged for review. Where recording is unsuitable, structured notes provide the input. We will include staff handoff and measure adoption and time returned.

At kickoff, we will agree the initial proposal type, inputs, template, pricing treatment, and completion checklist. Further proposal variants, an internal pricing calculator, or HubSpot agreement handoffs can follow as named deliveries.

One defined, usable item with a written scope and completion checklist: for example, a configured SharePoint site, a Teams workspace, a Planner rollout, a staff workshop, a proposal workflow, or a deployed AIOS feature.

Larger projects are split into named monthly deliveries before work begins. Monthly priorities are agreed before the month starts. Each delivered workflow includes documentation and handoff. The scope will identify the sites, users, templates, integrations, or other limits needed to make completion measurable. Proposed starting sizes and operating terms appear below; the agreement will confirm them.

Included recurring training is shown separately in the comparison. If a larger workshop is selected as a monthly delivery, that allocation will be explicit in the written scope.

Proposed delivery boundaries

These operating terms are recommended for discussion and remain subject to final scope approval and the agreement.

Each monthly delivery is one defined workflow, workspace, site, or feature. It includes design, configuration, testing, operating instructions, and handoff against a written completion checklist. One implementation runs at a time. Larger projects are divided into independently useful monthly deliveries before work starts.

Each scope includes up to two consolidated refinement rounds. Corrections needed to meet the approved checklist do not count as refinement rounds. New processes, templates, systems, or requirements are agreed as a scope change before work begins. Recurring training does not also consume a monthly implementation delivery.

For the first proposal workflow, the delivery month begins with the agreed template, service language, pricing inputs, examples, user availability, and access in place. If prerequisites are delayed, the parties agree a revised delivery date or substitute ready work.

• AI Operations meetings: One 60-minute monthly review, a 30-minute weekly check-in while a build is active, and one 60-minute staff session. Combine handoff with training where practical.
• Business hours: Monday–Friday, 9 a.m.–5 p.m. Eastern, excluding US federal holidays. Response targets apply during this window and do not promise a resolution time or after-hours coverage.
• System care: Keep all four existing dashboard connections in scope. Routine monitoring, diagnosis, and repairs are included. Connector rebuilds, platform migrations, new data sources, and large historical cleanup are separately scoped. Any tradeoff with the monthly delivery requires K1's written agreement.
• Feedback and acceptance: K1 aims to answer routine questions within three business days and review delivered work within five business days. Completion is checked against the written checklist. Silence alone does not authorize deployment, broader data access, or client sending.
• Changes and billing: Agree scope changes in writing. Use an equivalent replacement before work starts, a later delivery, or a separately approved fixed fee; no automatic extra charges.
• Blocked work: Offer ready substitute work. Unused capacity does not bank indefinitely. If K1 elects to wait on a client/vendor-blocked item, agree one reschedule within the next 30 days, replacing that period's delivery slot, while ongoing support and advisory continue.
• JamesTech delays: An approved delivery delayed solely by JamesTech remains owed without consuming the next month's delivery slot. JamesTech provides a recovery date; if recovery is not feasible, the parties use the delivery-credit or refund mechanism defined in the final agreement.
• Corrections: Correct reproducible failures against the accepted checklist for 30 days after acceptance without consuming a new delivery. New requirements and vendor changes follow the scope-change and system-care rules.
• Ownership and transition: K1 owns its accounts, data, and paid client-specific work. JamesTech retains reusable tools, with a continuing internal-use license for embedded components. At the end, provide paid work, documentation, applicable source/configuration exports, open issues, and a 60-minute transition session; remove access on the agreed date.

Embedded AI Office's initial Hiring Advisor and forecast builds use named delivery slots. Once established, they receive a monthly refresh from available approved data; extensions are future scoped deliveries.

• Maila: Sets business priorities, approves pricing and scope, and makes the engagement decision.
• Ashley: Coordinates day-to-day delivery after terms are agreed, supplies templates and process context, and participates in testing and handoff.
• JamesTech: Provides technology leadership, system care, advisory work, hands-on SharePoint and other agreed implementation, training, documentation, and reporting.
• Existing IT provider: Coordinates tenant access and related infrastructure within its separately agreed responsibilities.

Response targets describe response or acknowledgment timing, not guaranteed resolution times. Payroll integration, formal security audits, legal policy drafting, public pricing tools, ministry product development, and full migration execution require explicit scope. SharePoint architecture and implementation are part of the service menu at the selected delivery level.

Most of Kingdom One's new ministries arrive by referral, and that should stay the primary channel. Once the retainer is in place and the proposal workflow is running, there is a natural next step: a simple funnel that turns interest from ministries into booked conversations with your team, without adding manual work.

What it would include

• One landing page for a single Kingdom One service, written in your language and hosted under your brand.
• A short intake form that captures what the ministry needs and hands it to HubSpot as a contact and deal, ready for the proposal workflow.
• Automatic follow-up by email and text within minutes of a submission, so no inquiry sits unanswered.
• A weekly view of inquiries, conversations booked, and proposals started, inside the Kingdom One AI Operating System.

What it is not

• Not a promise of new leads. The funnel makes existing interest easier to act on and gives you a place to send referrals, speakers, and partner ministries.
• Not paid advertising. If Kingdom One ever chooses to run ads, that budget goes directly to the ad platforms and is decided separately.
• Not part of the monthly retainer. It is a separately scoped build, with pricing and timing agreed once the first deliveries are complete.

How we would measure it

Booked conversations and proposals started, not raw leads. If the funnel does not produce conversations your team wants, we change it or turn it off.

When

After the retainer is in place and the proposal workflow has been running for a month or two, so the funnel feeds a process that already works.