Week Engagements

A week – or more – embedded with your team to improve overall knowledge and deliver working systems, not slides.

Book a free call

Length: Five days or more

Format: Virtual, in person or hybrid

Best for: Teams with a defined workflow

Overview

A Week Engagement puts us inside your team for five working days or more. We choose the workflows where AI will pay off, build working systems with your people, and hand over everything needed to run and change them. By the last day there is something running in your environment that your team understands and can maintain.

The week can run virtually over our secure remote-session connection, in person at your location, or as a hybrid of the two. Either way, the work happens inside your systems and under your rules. We use the access you grant, and that access ends when the engagement ends.

Before the week starts

A scoping call to agree the target workflows and what done looks like
An internal owner who will run the system after we leave
Access to the systems involved, at the level your security team approves
Time on the calendar for the people who do the work today

Checkpoint and close-out

Every week includes a mid-week checkpoint to confirm the work is on track and adjust the plan while there is still time. The last day ends with a close-out session: we review what we built together, lay out next steps, and walk through options for future support.

What a week can produce

Agents that run a defined, multi-step process
Skills that extend the AI tools your team already uses
Prompt libraries for work you repeat
Small automations between systems you already run

Longer engagements

Some work needs more than five days. Multi-week engagements follow the same pattern, with a checkpoint each week to confirm priorities and a close-out session on the final day.

How the week runs

Prep
Scoping call
Agree the target workflows, what done looks like and who owns the result.
Day 1
Audit and select
Walk through the work as it happens today. Confirm or change the targets before any building starts.
Days 2–4
Build with your teamHands-on
Build in your environment, with the people who do the work, so the knowledge stays in the room. A mid-week checkpoint confirms the work is on track and adjusts the plan while there is time.
Day 5
Close out and hand offClose-out
Test on real cases, finish the documentation and runbook, and walk your owner through running and changing it. A close-out session reviews what we built together, lays out next steps and covers options for future support.

41% of small-business workers say it is unclear how AI applies to their specific business. The first day of a Week Engagement answers that question for your team, on your own workflows.

Source: U.S. Chamber of Commerce Foundation, Main Street AI Monitor, June 2026

What you keep

Working systems, running in your environment
Full source and configuration, yours to change
Documentation and a runbook for the person who owns it
A close-out review with next steps and a plan for what to build next
Silver support: email questions for 30 days after handoff

Nothing depends on an account with us, and nothing stops working when the engagement ends.

Support after the engagement

Every support period runs 30 days. Silver is included with every Week Engagement and can be added to shorter engagements. Gold and Platinum are available as upgrades.

Included

Silver

Unlimited email questions for 30 days
Replies within 2 business days

Gold

Unlimited email questions for 30 days
Replies within 24 hours
One 30-minute virtual check-in call

Platinum

Unlimited email questions for 30 days
Replies within 24 hours
120 minutes of screen-share support, in one session or several

Questions

Who owns what we build?

You do. Source, configuration and documentation are handed over at the end, and you can change any of it.

What if the first target turns out to be the wrong one?

Day one exists to catch that, and the mid-week checkpoint is a second chance. If either points to a better target, we agree the change with you before building further.

Virtual, in person or hybrid?

Any of the three. Virtual days run over our secure remote-session connection, joined from our session page. A common hybrid plan puts us on site for day one, while we map how the work gets done, and runs the build days virtually.

How is travel handled?

Travel costs are kept reasonable and invoiced at the end of the engagement, with receipts available on request.

Does our data leave our systems?

We build inside your environment with the access you approve, and that access ends when the engagement ends.

Compare the formats

One hourOne week or more

Hourly Training

Length: One hour or more, virtual
You bring: A question, a problem or a topic
You keep: Answers, written notes and the files we built

Day Sessions

Length: One full day, virtual, in person or hybrid
You bring: Three to five real tasks and working logins
You keep: Prompts, skills and workflows built by the group

This page