Skip to content

    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. At the end of week 2 you chose accounts-payable invoice-to-purchase-order matching as the first build. Weeks 3-4 are the start of that build.
    • 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.
    • 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.

    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 lineMonth 1 scope said (fictional)Delivered (fictional)
    Engagement referenceQVW-FL-001Same reference on every weekly update and on this report
    MonthMonth 1, Mon 9 Nov to Fri 4 Dec 2026Ran as dated: week 1 is the first full week after the kickoff, and the 30-day review falls at the end of week 4
    Days a week2, Tuesday and Thursday8 of 8 lead days worked
    Weekly demoThursday 15:00 Eastern4 of 4 demos held (Thu 12, 19, 26 Nov, Thu 3 Dec)
    Review that ends this month30-day review, Fri 4 Dec 2026Held today; this report is its input
    Phase of the 90-day planSkipping 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
    Deliverable 1Written 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 2Delivered Thu 19 Nov; it names the process, the people, the systems, the redacted data and the tools for the build
    Deliverable 2Acceptance criteria for the first build, written and signed at the start of week 35 criteria, signed by Priya N. on Mon 23 Nov on the acceptance form
    Deliverable 3A working first version in your current tools, shown at the weekly demo, weeks 3-4Shown at the demos of Thu 26 Nov and Thu 3 Dec; status per criterion in section 4
    Decisions due this monthWeek 2: which opportunity becomes the first build, or stopRecorded Fri 20 Nov: AP invoice-to-PO matching; confirmed in writing by Priya N. the same day
    People and access you provideAP lead as process owner (hours to confirm), IT contact, redacted invoicesAP 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
    ToolsExisting office-suite licences only; no new toolNo new tool or licence used; nothing new to pay for
    Out of scope this monthA second build, hiring help, anything not written on the scopeNothing 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
    Sign-off 1: scope agreedSigned by Priya N. with the agreement at hour 0, Mon 2 NovDone before the month started
    Sign-off 2: month signed offAt the 30-day reviewAsked for today: decision 1 in section 3

    3. Decisions needed from you

    #DecisionWhy now
    1Sign off month 1: "delivered as written, with change request CR-1"The review that ends the month is also the month's sign-off
    2Agree month 2's written scope (draft attached: section 5)Nothing in month 2 starts before your written yes
    3Move the 60-day review from Fri 1 Jan (a statutory holiday) to Thu 31 Dec, a lead dayThe review dates are set with you
    4Name who on the AP team will run the build from its guideThe first build ends with a short guide your team runs it from
    5Confirm that the 2 criteria marked "ready to check" can be checked by the AP lead before Thu 10 DecEach criterion is accepted by you, on the criteria you signed

    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.

    MeasureMonth 1 (fictional)How it is counted
    Lead days worked8 of 8 agreedDays worked against the days in the agreement
    Weekly demos held4 of 4One demo a week at the agreed slot
    Phase decisions recorded on time1 of 1 due (week 2)Each decision recorded with the role owner's written confirmation
    Acceptance criteria signed by the start of week 3Yes, Mon 23 NovDate of the role owner's signature on the acceptance form
    First build, criteria status0 accepted · 2 ready to check · 3 not met yet (of 5)Each criterion's status
    Change requests1 raised, 1 answered in writingChange request log
    Risk and issue log6 opened at the start; 2 closed (I-01, R-02); 4 openRows in the shared log

    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).

    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. Same 2 days a week and the same Thursday demo, on a new copy of the month scope form.

    • Phase: first build, weeks 5-6, then the start of weeks 7-12 as decided in week 6.
    • Deliverables:
      1. The first build brought to its 5 signed criteria, each shown at a weekly demo and checked by the AP lead.
      2. The short guide your AP team runs the build from.
      3. 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).
    • 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.
    • People and access: the AP lead, 4 hours a week; the IT contact for any new access.
    • 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.
    • Out of scope: a second build before the week 6 decision; more than 2 days a week without a new written scope; anything not written on the month 2 scope, which goes through a change request.

    The weeks are a plan, not a fixed timeline: a delay in access to people, systems or data moves the dates day for day.

    Ask about a part-time AI leadAdwaizer services