SAMPLE: Quillmere Valve Works Inc. is a fictional business. It is not a client or a prospect of Adwaizer, and every name, date, count and answer below is made up.
Fractional Lead AI: month one report (sample)
1. Summary (one page)
Quillmere Valve Works Inc. · Fractional Lead AI · Month 1 (weeks 1-4 of the 90-day plan) · Mon 9 Nov to Fri 4 Dec 2026 · 30-day review, Fri 4 Dec 2026 · Role owner: Priya N., VP Operations
- Where we are. You skipped the AI Audit, so weeks 1-2 turned your ranked list into a written scope for the first build (
growth/business/fractional-lead-ai-90-day-plan.md:19;delivery/fractional-lead/KIT.md:17). At the end of week 2 you chose accounts-payable invoice-to-purchase-order matching as the first build (delivery/fractional-lead/KIT.md:18). Weeks 3-4 are the start of that build (delivery/fractional-lead/KIT.md:19). - Delivered. The written scope for the first build, the week 2 decision record, the build's acceptance criteria signed on Mon 23 Nov, and a first version in your current office tools, shown at the Thursday demos of weeks 3 and 4.
- Against the scope. Every line of the month 1 scope was delivered as written; one change request (CR-1) was raised and answered (section 2).
- Where the build stands. 2 of the 5 signed acceptance criteria are ready for you to check, 3 are not met yet, none is accepted yet. Each build is judged against the criteria you signed, nothing else (
delivery/fractional-lead/KIT.md:111). - What we need from you today. Sign off month 1, agree month 2 in writing, and three smaller answers (section 3).
- Next month. Finish the first build against its criteria, write the guide your team runs it from, and the week 6 decision on what weeks 7-12 are for (section 5).
- Not in this report. No cost savings, revenue or results: the service promises none (
growth/business/offer-fractional-lead-ai.md:67;delivery/fractional-lead/month-scope.md:40).
2. Delivered against the month 1 scope
Each row is one line of the signed month 1 scope form, in the form's order.
| Month scope line | Month 1 scope said (fictional) | Delivered (fictional) | Kit source |
|---|---|---|---|
Engagement reference (month-scope.md:11) | QVW-FL-001 | Same reference on every weekly update and on this report | delivery/fractional-lead/2026-10-30-order-day-rehearsal.md:16 |
Month (month-scope.md:12) | Month 1, Mon 9 Nov to Fri 4 Dec 2026 | Ran as dated: week 1 is the first full week after the kickoff, and the 30-day review falls at the end of week 4 | delivery/fractional-lead/KIT.md:26; rehearsal :123 |
Days a week (month-scope.md:13) | 2, Tuesday and Thursday | 8 of 8 lead days worked | growth/business/offer-fractional-lead-ai.md:24; delivery/fractional-lead/KIT.md:35 |
Weekly demo (month-scope.md:14) | Thursday 15:00 Eastern | 4 of 4 demos held (Thu 12, 19, 26 Nov, Thu 3 Dec) | delivery/fractional-lead/KIT.md:35; growth/business/fractional-lead-ai-90-day-plan.md:24 |
Review that ends this month (month-scope.md:15) | 30-day review, Fri 4 Dec 2026 | Held today; this report is its input | delivery/fractional-lead/KIT.md:26, :67 |
Phase of the 90-day plan (month-scope.md:19) | Skipping the audit: written scope for the first build (weeks 1-2), then the first build (weeks 3-6) | Weeks 1-2 done; weeks 3-4 of the first build done | growth/business/fractional-lead-ai-90-day-plan.md:16, :19 |
Deliverable 1 (month-scope.md:21) | Written scope for the first build, from your ranked list (1. AP invoice-to-PO matching, 2. quote-request email triage, 3. search over maintenance logs), due week 2 | Delivered Thu 19 Nov; it names the process, the people, the systems, the redacted data and the tools for the build | delivery/fractional-lead/KIT.md:17; rehearsal :110 |
Deliverable 2 (month-scope.md:22) | Acceptance criteria for the first build, written and signed at the start of week 3 | 5 criteria, signed by Priya N. on Mon 23 Nov on the acceptance form | delivery/fractional-lead/KIT.md:19; growth/business/fractional-lead-ai-90-day-plan.md:16 |
Deliverable 3 (month-scope.md:23) | A working first version in your current tools, shown at the weekly demo, weeks 3-4 | Shown at the demos of Thu 26 Nov and Thu 3 Dec; status per criterion in section 4 | delivery/fractional-lead/KIT.md:19; growth/business/fractional-lead-ai-90-day-plan.md:16 |
Decisions due this month (month-scope.md:24) | Week 2: which opportunity becomes the first build, or stop | Recorded Fri 20 Nov: AP invoice-to-PO matching; confirmed in writing by Priya N. the same day | delivery/fractional-lead/KIT.md:18, :61 |
People and access you provide (month-scope.md:25) | AP lead as process owner (hours to confirm), IT contact, redacted invoices | AP lead 4 hours a week (confirmed at the kickoff, log item I-01 closed); IT contact granted test access to the ERP on Thu 19 Nov as planned; redacted invoices received in week 1. No password, key or credential was sent to us | growth/business/fractional-lead-ai-90-day-plan.md:16; delivery/fractional-lead/KIT.md:39; rehearsal :81, :113 |
Tools (month-scope.md:29-:33) | Existing office-suite licences only; no new tool | No new tool or licence used; nothing new to pay for | delivery/fractional-lead/KIT.md:42; growth/business/fractional-lead-ai-90-day-plan.md:29, :37; rehearsal :116 |
Out of scope this month (month-scope.md:35-:40) | A second build, hiring help, anything not written on the scope | Nothing outside the scope was started. CR-1 (you asked to add quote-request email triage to month 1) was answered in writing on Tue 1 Dec: not in month 1; it stays first in line for weeks 7-12, decided at week 6 | delivery/fractional-lead/KIT.md:24, :20; delivery/fractional-lead/month-scope.md:40 |
Sign-off 1: scope agreed (month-scope.md:42-:48) | Signed by Priya N. with the agreement at hour 0, Mon 2 Nov | Done before the month started | delivery/fractional-lead/month-scope.md:3; rehearsal :19 |
Sign-off 2: month signed off (month-scope.md:50-:55) | At the 30-day review | Asked for today: decision 1 in section 3 | delivery/fractional-lead/KIT.md:26, :78 |
3. Decisions needed from you
| # | Decision | Why now | Kit source |
|---|---|---|---|
| 1 | Sign off month 1: "delivered as written, with change request CR-1" | The review that ends the month is also the month's sign-off | delivery/fractional-lead/KIT.md:26, :78; delivery/fractional-lead/month-scope.md:52 |
| 2 | Agree month 2's written scope (draft attached: section 5) | Nothing in month 2 starts before your written yes | growth/business/offer-fractional-lead-ai.md:50; delivery/fractional-lead/KIT.md:79 |
| 3 | Move the 60-day review from Fri 1 Jan (a statutory holiday) to Thu 31 Dec, a lead day | The review dates are set with you | delivery/fractional-lead/KIT.md:43; rehearsal :131 |
| 4 | Name who on the AP team will run the build from its guide | The first build ends with a short guide your team runs it from | growth/business/fractional-lead-ai-90-day-plan.md:16; delivery/fractional-lead/KIT.md:88 |
| 5 | Confirm that the 2 criteria marked "ready to check" can be checked by the AP lead before Thu 10 Dec | Each criterion is accepted by you, on the criteria you signed | delivery/fractional-lead/KIT.md:87, :111 |
4. Metrics
Every figure is counted from the engagement's own records (weekly updates, the signed forms, the risk and issue log), not estimated. None is a saving, a revenue figure or a result: the service promises none (growth/business/offer-fractional-lead-ai.md:67; delivery/fractional-lead/KIT.md:111).
| Measure | Month 1 (fictional) | How it is counted | Kit source |
|---|---|---|---|
| Lead days worked | 8 of 8 agreed | Days worked against the days in the agreement | delivery/fractional-lead/KIT.md:51, :75 |
| Weekly demos held | 4 of 4 | One demo a week at the agreed slot | growth/business/fractional-lead-ai-90-day-plan.md:24; delivery/fractional-lead/KIT.md:35 |
| Phase decisions recorded on time | 1 of 1 due (week 2) | Each decision recorded with the role owner's written confirmation | delivery/fractional-lead/KIT.md:57, :61 |
| Acceptance criteria signed by the start of week 3 | Yes, Mon 23 Nov | Date of the role owner's signature on the acceptance form | delivery/fractional-lead/KIT.md:19, :73 |
| First build, criteria status | 0 accepted · 2 ready to check · 3 not met yet (of 5) | Each criterion's status | delivery/fractional-lead/KIT.md:87 |
| Change requests | 1 raised, 1 answered in writing | Change request log | delivery/fractional-lead/KIT.md:24, :77 |
| Risk and issue log | 6 opened at the start; 2 closed (I-01, R-02); 4 open | Rows in the shared log | delivery/fractional-lead/KIT.md:76; growth/business/fractional-lead-ai-90-day-plan.md:25; rehearsal :74-:81 |
Top open risks (from the log): R-01, the agreement is not a legal-reviewed contract for this offer (it was read by counsel before signing); R-03, a change in the yes on AI tools; R-05, tool or licence costs not named before a build starts (none so far). (delivery/fractional-lead/2026-10-30-order-day-rehearsal.md:76, :78, :80)
5. Next month (month 2, draft scope for your written yes)
Month 2 runs from Mon 7 Dec 2026 to the 60-day review at the end of week 8, Thu 31 Dec 2026 if you agree decision 3 (delivery/fractional-lead/KIT.md:83). Same 2 days a week and the same Thursday demo, on a new copy of the month scope form (delivery/fractional-lead/month-scope.md:7).
- Phase: first build, weeks 5-6, then the start of weeks 7-12 as decided in week 6 (
growth/business/fractional-lead-ai-90-day-plan.md:16-:17). - Deliverables:
- The first build brought to its 5 signed criteria, each shown at a weekly demo and checked by the AP lead (
delivery/fractional-lead/KIT.md:19,:87). - The short guide your AP team runs the build from (
growth/business/fractional-lead-ai-90-day-plan.md:16;delivery/fractional-lead/KIT.md:88). - The week 6 decision record, Fri 18 Dec: keep, change or stop the first build, and what weeks 7-12 are for (second build, hiring help, handover or a mix) (
delivery/fractional-lead/KIT.md:20,:62; rehearsal:130).
- The first build brought to its 5 signed criteria, each shown at a weekly demo and checked by the AP lead (
- Decisions due: the week 6 decision above. If you choose a second build (CR-1's quote-request email triage is first in line), its acceptance criteria are signed at its start; if you choose hiring help, we need your hiring manager and recruiter (
delivery/fractional-lead/KIT.md:21,:90;growth/business/fractional-lead-ai-90-day-plan.md:17). - People and access: the AP lead, 4 hours a week; the IT contact for any new access (
growth/business/fractional-lead-ai-90-day-plan.md:16). - Tools: your existing office-suite licences. Any new tool or licence is named, with its cost to you, before the work that needs it starts (
growth/business/fractional-lead-ai-90-day-plan.md:37;delivery/fractional-lead/KIT.md:42). - Out of scope: a second build before the week 6 decision; more than 2 days a week without a new written scope (
growth/business/offer-fractional-lead-ai.md:69); anything not written on the month 2 scope, which goes through a change request (delivery/fractional-lead/KIT.md:24).
The weeks are a plan, not a fixed timeline: a delay in access to people, systems or data moves the dates day for day (delivery/fractional-lead/KIT.md:24; growth/business/fractional-lead-ai-90-day-plan.md:34).