# Dr. Naomi’s roadmap to her first client

Reviewed 11 October 2026.

30 working sessions to win and serve one new paying organisation through Swift Agility. A practical plan, not a promise of a sale or an income forecast.

Start with one audience and one small paid diagnostic or workshop Naomi can actually deliver. The website is a foundation; buyer commitments, received money and accepted delivery need their own evidence.

Plan 60–90 minutes per working session, plus contracted delivery time. Dates are planning guides; repeat outreach/sales loops when a buyer is not yet ready.

## Source and adaptation

[Nick's original Whimsical board](https://whimsical.com/roadmap-to-25k-month-with-automation-P5K6f1h9YpY5ngzvCW93Pg)

### 1. Marketing and lead generation

Nick: Nick offers six routes: referrals, communities, cold email, platform sales, LinkedIn outreach and inbound social.

For Naomi: Start with existing relationships and relevant communities. Add selective email or LinkedIn outreach. Use the website and free checks as support. Platform marketplaces and building a large audience are optional experiments after the first-client cycle.

Days 1–12. The day-by-day schedule and outreach counts are suggested adaptations, not instructions specified by Nick.

### 2. Sales

Nick: Book the meeting, hold the sales conversation and send a detailed proposal/scope. Rebook no-shows, follow up unsigned proposals, revisit not-now buyers after about 30 days, and stop on a permanent mismatch.

For Naomi: Use discovery to confirm the workforce problem, decision route and purchasing steps. Offer one small paid engagement. Move to delivery only after signature and the agreed initial payment.

Days 13–20. The day-by-day schedule and outreach counts are suggested adaptations, not instructions specified by Nick.

### 3. Project management and fulfillment

Nick: Kick off, create the project entry, deliver, show the finished work and loop through revisions. Complete, collect any delivery payment, request useful additional work and follow up later if welcome.

For Naomi: Plan and deliver the diagnostic or workshop, obtain acceptance, reconcile payment, collect approved proof and discuss a relevant next programme. For long programmes, follow the signed schedule.

Days 21–30. The day-by-day schedule and outreach counts are suggested adaptations, not instructions specified by Nick.

## What already exists and what remains

### Firm identity and professional credibility — Live foundation

The website introduces Swift Agility and Dr. Naomi’s HR, teaching and research experience.

Remaining: Select relevant proof for the chosen buyer. Confirm permission for names, quotations and logos; experience claims are not measured client outcomes.

[Existing resource](https://swiftagility.co.ke/about)

### Organisation training and mentorship offers — Live foundation

Corporate mentorship and related organisation programmes are visible. Training and individual cohorts have separate destinations.

Remaining: Choose one entry offer. Avoid presenting the whole catalogue to the first buyer. Confirm the fee and available dates with Naomi.

[Existing resource](https://swiftagility.co.ke/mentorship)

### Training catalogue and brochure — Live foundation

Training pages and a printable brochure already exist; reusable source material is in the project.

Remaining: Use only the relevant programme pages. Verify current prices and dates before quoting. Existing price bands do not establish an approved fee for a new diagnostic.

[Existing resource](https://swiftagility.co.ke/trainings)

### Free readiness and appraisal tools — Live foundation

Workforce AI readiness, appraisal health check, target sheets, scorecard planning and PIP/probation documents are listed.

Remaining: Use one relevant check as the opening to a conversation. A completed check or website visit does not prove buying intent.

[Existing resource](https://swiftagility.co.ke/tools)

### Contact and consultation request routes — Live foundation

The public site provides a contact route and conversation requests.

Remaining: Naomi should verify that an enquiry reaches her operating workflow before inviting buyers. Alert delivery is unverified in this review; check the CRM daily and use manual confirmation.

[Existing resource](https://swiftagility.co.ke/contact)

### Contacts, pipeline and catalogue controls — Built; operating use to confirm

Source and September release evidence show a protected business CRM with contacts, pipeline stages, activity, follow-up dates and catalogue controls.

Remaining: Confirm Naomi’s login, current records and daily use. Private CRM records were not read for this review; current leads, deals and receipts remain unknown.

[Existing resource](https://swiftagility.co.ke/admin)

### Payroll and staff evaluation workspaces — Do not sell as activated

Payroll is labelled “Coming soon”; staff evaluation has a separate demo. Prior release records leave real employer activation pending.

Remaining: Lead with consulting or training Naomi can deliver. Sell a software commitment only after a fresh activation and acceptance check.

[Existing resource](https://swiftagility.co.ke/tools/evaluation)

### Buyer evidence, signature and paid delivery — Not established by this review

The website and build records establish capability, not current prospect commitments, signed scopes, receipts or accepted outcomes.

Remaining: Days 6–30 collect this evidence. If Naomi already has it, enter a short reference and skip the corresponding completed work.

[Existing resource](https://swiftagility.co.ke/contact)

## Evidence checkpoints

- **Offer approved:** Naomi has chosen the audience, scope, whole-KES fee and delivery capacity. Reference the approved offer sheet.
- **Buyer need confirmed:** A real buyer confirmed a problem, the intended result, who decides and how purchasing works. Reference the discovery record.
- **Signed and initial payment received:** Both the signed scope and verified initial payment exist. A proposal, invoice or CRM “won” label alone is insufficient.
- **Client accepted the delivery:** The client explicitly accepted the agreed deliverables. Reference the acceptance record; track any balance separately.

## Working sessions

### 01–05 · Choose your offer

One buyer. One problem. One paid first step.

#### Day 1: Choose one kind of buyer

**Time:** 60 minutes. **Output:** One audience and one buyer role you can reach.

1. Review the organisation services and the professional experience already on the site. Choose one organisation segment where you have both credibility and access.
2. Recommended starting hypothesis: a Kenyan learning institution with a workforce-development need. SACCOs are a valid alternative if you have a warmer route to a decision maker.
3. Write the buyer role, the recurring problem you will investigate and why you are suited to help. Park the other segments for this first cycle.

**Evidence:** An audience decision with a reason and a reachable buyer role.

**30-minute fallback:** List three relationships you could reconnect with and choose the most accessible segment.

**Templates:** T01 Audience and entry-offer sheet.

**Existing assets:** [/about](https://swiftagility.co.ke/about), [/mentorship](https://swiftagility.co.ke/mentorship)

#### Day 2: Shape a small paid first step

**Time:** 75 minutes. **Output:** A scoped entry offer a buyer can understand in one minute.

1. Draft a paid workforce diagnostic: a 60-minute sponsor conversation, review of one anonymised workflow or skill gap, and a concise action report. This is a proposed offer, not an existing approved package.
2. Set the deliverables: the agreed baseline, three prioritised actions, named client owners and a 30-day review date. Set boundaries and a realistic delivery duration.
3. Keep the free readiness check as the invitation. A short paid diagnostic leads to larger training or mentorship only if the buyer needs it.

**Evidence:** A draft entry-offer sheet with outputs, exclusions and a feasible delivery window.

**30-minute fallback:** Write three sentences: who it is for, what it changes, and what the buyer receives.

**Templates:** T01 Audience and entry-offer sheet; T12 Diagnostic findings and action report.

**Existing assets:** [/readiness](https://swiftagility.co.ke/readiness)

#### Day 3: Choose credible proof to support it

**Time:** 60 minutes. **Output:** One relevant proof sheet without unsupported claims.

1. Choose one or two relevant examples from your actual prior work and the approved source material behind the website.
2. Confirm which organisation names, quotations and materials you are allowed to share. Separate experience from measured outcomes.
3. Adapt a short capability sheet and link to the relevant service page; do not build a new general brochure.

**Evidence:** An approved capability sheet and a record of what can be shared.

**30-minute fallback:** Select one relevant experience example and note the permission still needed.

**Templates:** T02 Proof and capability one-pager.

**Existing assets:** [/about](https://swiftagility.co.ke/about), [/trainings/brochure](https://swiftagility.co.ke/trainings/brochure)

#### Day 4: Approve the fee and delivery limits

**Time:** 75 minutes. **Output:** An offer you are willing and able to sell.

1. Calculate your preparation, delivery and reporting time plus travel and other direct costs. Choose a whole-KES fee that makes the first engagement worthwhile.
2. Confirm payment milestones, revision allowance, client inputs and dates you can actually deliver. Verify any supplier or tax requirements before quoting.
3. Approve the offer sheet. Existing website price bands are reference material; they are not approval for this new diagnostic. Record the “Offer approved” checkpoint below.

**Evidence:** Naomi-approved scope, whole-KES fee, payment terms and capacity.

**30-minute fallback:** List the costs and available delivery dates; leave the fee unresolved until you can approve it.

**Templates:** T01 Audience and entry-offer sheet; T08 Proposal and statement of work; T09 Invoice, payment verification and receipt.

**Existing assets:** [/programmes](https://swiftagility.co.ke/programmes)

#### Day 5: Check the operating path before outreach

**Time:** 60 minutes. **Output:** You know how to find and respond to every enquiry.

1. Open the protected CRM and confirm that you can find Contacts, Pipeline and follow-up dates. Review existing records first; do not assume the book is empty.
2. With Innocraft, run one clearly labelled enquiry check and confirm it arrives, without contacting a real buyer. Confirm how you will notice it; notification delivery remains unverified in this review.
3. Reserve a daily 15-minute enquiry review and a 60–90-minute action session. Add the existing owner’s finance process and procurement documents to your readiness checklist.

**Evidence:** A successful enquiry-to-CRM check and your daily review routine.

**30-minute fallback:** Confirm login and review pending enquiries manually. Ask Innocraft to resolve any broken capture path.

**Templates:** T03 Prospect qualification and next-action view; T16 Weekly first-client review.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin), [/contact](https://swiftagility.co.ke/contact)

### 06–15 · Start conversations

Use relationships first, then selective outreach.

#### Day 6: Build a short, qualified relationship list

**Time:** 75 minutes. **Output:** A working list of 20 relevant organisations, as a target.

**Before this session:** Offer approved.

1. Start with existing contacts, past collaborators and permitted introductions in your chosen segment. Do not infer buying interest from names on the website.
2. Aim for 20 organisations. For each, note a buyer role, your route in, a plausible problem to check and the next action. Fewer qualified names beat irrelevant volume.
3. Keep names and contact details in the protected CRM. This public review page stores only short evidence references on your device.

**Evidence:** A CRM view or private list reference with qualified organisations and next actions.

**30-minute fallback:** Add five well-understood relationships and a next action for each.

**Templates:** T03 Prospect qualification and next-action view.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

#### Day 7: Ask five trusted people for introductions

**Time:** 60 minutes. **Output:** Five personal referral requests, as an activity target.

**Before this session:** Offer approved.

1. Pick trusted relationships who understand your work and may know the chosen buyer role.
2. Ask permission for an introduction to someone facing the specific problem in your offer. Give them a short, forwardable explanation.
3. Send each request yourself and record the response and next action. Respect a declined introduction.

**Evidence:** A private activity reference for the requests and any permitted introductions.

**30-minute fallback:** Make two thoughtful referral requests.

**Templates:** T04 Warm introduction and referral request.

**Existing assets:** [/about](https://swiftagility.co.ke/about)

#### Day 8: Contribute something useful in one community

**Time:** 60 minutes. **Output:** One relevant contribution and a conversation invitation.

**Before this session:** Offer approved.

1. Choose an existing professional or institutional community you genuinely participate in. Check its posting and promotion rules.
2. Share a short practical lesson on the chosen workforce problem and link to one appropriate free check or document tool.
3. Invite interested people to a conversation. Respond personally; do not post the full catalogue or scrape member contacts.

**Evidence:** A post reference or discussion note and the responses, if any.

**30-minute fallback:** Help one existing contact use a relevant free tool.

**Templates:** T05 Community contribution and outreach messages.

**Existing assets:** [/tools](https://swiftagility.co.ke/tools)

#### Day 9: Send five tailored conversation invitations

**Time:** 75 minutes. **Output:** Five relevant invitations, as an activity target.

**Before this session:** Offer approved.

1. Select five organisations from your qualified list. Prefer warm routes; use selective LinkedIn or email outreach where appropriate.
2. For each, explain the relevant problem you can help investigate, why you contacted them and one proposed 20–30-minute conversation.
3. Use the capability sheet and one relevant website link only. Record what you sent and when to follow up. Stop on an opt-out.

**Evidence:** Five logged invitations or a smaller qualified batch with a reason.

**30-minute fallback:** Send two specific invitations that you can explain without a template.

**Templates:** T02 Proof and capability one-pager; T05 Community contribution and outreach messages; T03 Prospect qualification and next-action view.

**Existing assets:** [/contact](https://swiftagility.co.ke/contact)

#### Day 10: Listen for a problem worth solving

**Time:** 90 minutes. **Output:** Buyer language and meeting requests grounded in responses.

**Before this session:** Offer approved.

1. Respond to introductions and outreach replies. Aim to arrange three short buyer conversations across this and the coming sessions; this is a target, not a confirmed booking.
2. Ask what happens today, what keeps going wrong, how often it happens and what improvement would matter. Avoid presenting the entire service range.
3. For genuine interest, agree a date, the right attendee roles and the agenda. If there are no replies, make another small tailored batch and review your opening message.

**Evidence:** Buyer notes or confirmed conversation dates; if none, the next outreach adjustment.

**30-minute fallback:** Follow up with two warm contacts and book one conversation if interest exists.

**Templates:** T05 Community contribution and outreach messages; T06 Discovery and buying-process notes; T07 Meeting confirmation and follow-up cycle.

**Existing assets:** [/readiness](https://swiftagility.co.ke/readiness)

#### Day 11: Review the response before adding volume

**Time:** 60 minutes. **Output:** One evidence-led adjustment to audience or message.

**Before this session:** Offer approved.

1. Count actual attempts, replies, held conversations and meetings agreed. Separate silence, not-now, not-a-fit and genuine interest.
2. If no relevant replies follow roughly ten tailored attempts, inspect relationship strength, buyer relevance and wording. Ask a trusted contact what is unclear.
3. Change one thing and send the next small batch. The numbers here are working experiments; Nick does not prescribe these quotas.

**Evidence:** A brief review with actual counts, the bottleneck and one change.

**30-minute fallback:** Review the last five messages and rewrite one weak opening.

**Templates:** T03 Prospect qualification and next-action view; T16 Weekly first-client review.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

#### Day 12: Confirm meetings and manage no-shows

**Time:** 60 minutes. **Output:** Clear bookings and respectful follow-up.

**Before this session:** Offer approved.

1. Confirm the agreed time, place or link, agenda and intended buyer role. Use the buyer’s preferred channel.
2. If someone misses a meeting, check in politely and offer two alternative times. If it is not timely, agree a revisit date rather than pursuing daily.
3. For a permanent mismatch or an opt-out, stop contact and record the reason privately. Nick’s 30-day revisit is a default only where welcome.

**Evidence:** Confirmed bookings, rebookings or agreed revisit/stop decisions.

**30-minute fallback:** Confirm the next meeting or arrange the next qualified invitation.

**Templates:** T03 Prospect qualification and next-action view; T07 Meeting confirmation and follow-up cycle.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

#### Day 13: Prepare for a real buyer conversation

**Time:** 60 minutes. **Output:** A focused agenda for a booked meeting.

**Before this session:** Offer approved.

1. If a meeting is not booked, continue the Day 9–12 loop instead of inventing a buyer.
2. Review public organisation information and the buyer’s actual response. Prepare five questions on the current problem, baseline, desired change, decision route and timing.
3. Choose one relevant example or free check. Prepare to explain the small paid first step and the next action in plain language.

**Evidence:** An agenda tied to a confirmed meeting and the buyer’s known context.

**30-minute fallback:** Write the five questions; use the remaining time to secure a meeting.

**Templates:** T06 Discovery and buying-process notes; T07 Meeting confirmation and follow-up cycle.

**Existing assets:** [/readiness](https://swiftagility.co.ke/readiness), [/tools](https://swiftagility.co.ke/tools)

#### Day 14: Hold discovery and agree the next step

**Time:** 90 minutes. **Output:** A buyer-confirmed problem and a clear decision route.

**Before this session:** Offer approved.

1. Hold the booked conversation. Ask for a concrete example, the cost of the current difficulty and the result the buyer would value. Do not invent a financial benefit.
2. Establish the sponsor, budget holder, approver and purchasing process by role. Ask about timing, required supplier documents and payment procedures.
3. If the paid first step fits, ask permission to send a scoped proposal. If not now, agree follow-up; if not a fit, close politely.

**Evidence:** A discovery record with the buyer’s problem, desired result, decision route and agreed next action.

**30-minute fallback:** If the meeting moves, rebook and continue qualified outreach.

**Templates:** T06 Discovery and buying-process notes.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

#### Day 15: Choose the strongest real opportunity

**Time:** 60 minutes. **Output:** One qualified proposal candidate, or a deliberate return to outreach.

**Before this session:** Offer approved.

1. Compare the buyer conversations. Prioritise a clear need, access to the decision route, feasible timing and a first step you can deliver.
2. Refine the offer with buyer language and clarify unresolved scope or approval questions. Record the “Buyer need confirmed” checkpoint only when those facts exist.
3. If no buyer has confirmed the need, repeat Days 9–14. Completing two weeks of activity is not a reason to send an unsolicited proposal.

**Evidence:** A qualified discovery reference and approved next step, or the next outreach cycle.

**30-minute fallback:** Clarify one unresolved need or decision question with the strongest respondent.

**Templates:** T06 Discovery and buying-process notes; T16 Weekly first-client review; T01 Audience and entry-offer sheet.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

### 16–20 · Agree the work

A clear scope, a signature and actual payment.

#### Day 16: Send one buyer-specific proposal

**Time:** 90 minutes. **Output:** A proposal the buyer asked to receive.

**Before this session:** Buyer need confirmed.

1. Use the discovery record to describe the specific problem, deliverables, exclusions, delivery dates and client inputs.
2. State the approved whole-KES fee, payment milestones, acceptance criteria and included revisions. Confirm any institutional procurement requirements.
3. Send personally to the agreed recipient and agree a review date. Keep the existing brochure as an appendix only where it helps.

**Evidence:** The sent proposal reference, recipient role and agreed review date.

**30-minute fallback:** Draft the scope and resolve one approval or procurement gap before sending.

**Templates:** T08 Proposal and statement of work.

**Existing assets:** [/trainings/brochure](https://swiftagility.co.ke/trainings/brochure)

#### Day 17: Follow up on a decision, not a document

**Time:** 60 minutes. **Output:** A buyer response or a clear next follow-up date.

**Before this session:** Buyer need confirmed.

1. At the agreed review time, ask what is needed to make a decision and whether the scope reflects their problem.
2. Resolve an unanswered question; do not resend the same proposal repeatedly or discount without understanding the objection.
3. If not signed, use a respectful follow-up cycle. For not-now, agree a revisit date; for no-fit or opt-out, close the loop.

**Evidence:** The response, blocker, next action and date in the private CRM.

**30-minute fallback:** Make one agreed follow-up and progress another qualified conversation.

**Templates:** T07 Meeting confirmation and follow-up cycle; T08 Proposal and statement of work.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

#### Day 18: Confirm the approver and remove purchase friction

**Time:** 75 minutes. **Output:** A feasible purchasing route and an agreed scope.

**Before this session:** Buyer need confirmed.

1. Ask your contact who approves, who signs, what supplier documents are required and how the invoice will be paid. Do not assume the contact can commit funds.
2. Answer scope and value questions with the buyer’s evidence. If the scope changes, revise the dates, fee and acceptance criteria explicitly.
3. Confirm the decision date and contracting process. Institutional purchasing may take longer than this calendar; continue the sales loop while it runs.

**Evidence:** An agreed purchase path, revised scope if needed and the next decision date.

**30-minute fallback:** Resolve one missing approver, supplier document or scope question.

**Templates:** T08 Proposal and statement of work; T07 Meeting confirmation and follow-up cycle.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

#### Day 19: Secure the signature and issue the agreed invoice

**Time:** 75 minutes. **Output:** A signed scope and a correctly issued initial invoice.

**Before this session:** Buyer need confirmed.

1. Obtain the appropriate parties’ written approval/signatures on the statement of work and confirm the agreed start conditions.
2. Issue the initial invoice through Naomi’s verified finance process. Check the recipient, supplier details, payment destination and terms.
3. Record signed value and invoice status separately from received money. This review site does not issue invoices, sign contracts or take payment.

**Evidence:** Signed scope and invoice references, with the agreed initial payment requirement.

**30-minute fallback:** Follow up on the missing signature or invoice requirement; do not begin delivery prematurely.

**Templates:** T08 Proposal and statement of work; T09 Invoice, payment verification and receipt.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

#### Day 20: Verify the first client is signed and paying

**Time:** 60 minutes. **Output:** The first-client milestone is supported by signature and received money.

**Before this session:** Buyer need confirmed.

1. Verify the agreed initial payment in Naomi’s actual receipt or bank/payment record and reconcile it to the signed scope.
2. Record “Signed and initial payment received” only when both exist. Keep the evidence private and put only a short reference here.
3. If either is missing, continue Days 17–19 and qualified outreach. There is no deadline-based shortcut to declaring a client won.

**Evidence:** References to a signed scope and verified initial payment; amounts stay in the finance record.

**30-minute fallback:** Reconcile one payment or obtain a clear next decision date.

**Templates:** T09 Invoice, payment verification and receipt; T16 Weekly first-client review.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

### 21–26 · Deliver a result

Agree the baseline, deliver and get acceptance.

#### Day 21: Kick off the paid first engagement

**Time:** 90 minutes. **Output:** The client and Naomi agree how the work will run.

**Before this session:** Signed and initial payment received.

1. Only start after the signed-and-paid checkpoint. Confirm the sponsor, delivery contact, dates, client inputs and final acceptance method.
2. Restate the chosen result and agree a baseline you can check. Request only the minimum necessary information; use anonymised workflow examples where possible.
3. For larger engagements, keep the contracted schedule. These delivery sessions are a checklist, not a claim that a six-month mentorship programme ends in a week.

**Evidence:** A kickoff record with owners, inputs, baseline and acceptance method.

**30-minute fallback:** Confirm one missing input or sponsor decision while keeping delivery within the agreed scope.

**Templates:** T10 Kickoff and client input checklist.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

#### Day 22: Create the delivery plan and baseline

**Time:** 90 minutes. **Output:** A short project plan with measurable starting conditions.

**Before this session:** Signed and initial payment received.

1. Create the client project record with milestones, owners, dates and deliverables. Reuse a checklist rather than managing it from memory.
2. For the diagnostic, document the sponsor conversation and one workflow or skill-gap baseline. For a workshop, prepare the agreed exercises and application task.
3. Record risks, client inputs and any decision that changes scope. Keep employee or financial data in the proper protected client system.

**Evidence:** The project plan and baseline references.

**30-minute fallback:** Complete the plan’s first milestone and resolve one missing input.

**Templates:** T11 Delivery plan and baseline record.

**Existing assets:** [/tools](https://swiftagility.co.ke/tools)

#### Day 23: Deliver the agreed diagnostic or workshop

**Time:** 90 minutes. **Output:** The contracted first deliverable exists.

**Before this session:** Signed and initial payment received.

1. Run the paid first-step work to the agreed method and schedule. Use the existing readiness or appraisal tools only where they help the actual problem.
2. For a diagnostic, prepare a concise findings report with the baseline, evidence limits and three prioritised actions. For a workshop, complete the exercises and buyer’s application task.
3. This day is a coordination session; client-facing delivery time is additional and governed by the contract. Do not substitute a generic slide deck for the agreed work.

**Evidence:** A completed deliverable reference linked to the scope criteria.

**30-minute fallback:** Finish the highest-priority agreed output or update the client on an input-dependent delay.

**Templates:** T11 Delivery plan and baseline record; T12 Diagnostic findings and action report.

**Existing assets:** [/tools](https://swiftagility.co.ke/tools)

#### Day 24: Review feedback and resolve agreed revisions

**Time:** 75 minutes. **Output:** Client feedback has a clear resolution path.

**Before this session:** Signed and initial payment received.

1. Review the first deliverable with the client and ask what is unclear or missing against the signed criteria.
2. Log agreed corrections with an owner and due date. Return to the delivery plan until the agreed work is complete.
3. Separate in-scope corrections from additional work. Obtain a separate approval for changes to fee, dates or scope.

**Evidence:** A revision log with resolved items or agreed remaining dates.

**30-minute fallback:** Resolve the highest-priority correction and confirm the next review.

**Templates:** T13 Revision log and delivery acceptance; T11 Delivery plan and baseline record.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

#### Day 25: Make the handover easy to use

**Time:** 90 minutes. **Output:** The client knows what was delivered and what to do next.

**Before this session:** Signed and initial payment received.

1. Send the finished deliverables with a short walkthrough or delivery video, as Nick recommends for making the result visible.
2. Explain the three priority actions, the client owner of each, the first step and the agreed 30-day check.
3. Request explicit acceptance against the agreed criteria. If revisions remain, return to Day 24; sending a report does not prove acceptance.

**Evidence:** The handover reference and the acceptance request or response.

**30-minute fallback:** Prepare a brief walkthrough of the most important output.

**Templates:** T12 Diagnostic findings and action report; T13 Revision log and delivery acceptance.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

#### Day 26: Confirm acceptance and reconcile the balance

**Time:** 60 minutes. **Output:** Accepted delivery and an accurate payment record.

**Before this session:** Signed and initial payment received.

1. Obtain the client’s explicit acceptance. Record the “Client accepted the delivery” checkpoint with the private acceptance reference.
2. If the contract calls for a delivery payment, issue or reconcile it through the verified finance process and follow up on its due date.
3. Record accepted delivery, total invoiced, total received and balance due separately. Never count an unpaid balance as cash received.

**Evidence:** Acceptance reference and reconciled balance status in the private finance record.

**30-minute fallback:** Resolve one acceptance question or reconcile one payment.

**Templates:** T13 Revision log and delivery acceptance; T09 Invoice, payment verification and receipt.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

### 27–30 · Earn the next step

Evidence, referrals and useful follow-up.

#### Day 27: Ask for proof and a permitted introduction

**Time:** 60 minutes. **Output:** Evidence that may support the next sale, with permission.

**Before this session:** Client accepted the delivery.

1. Ask the client what was useful and request approval for a short testimonial or factual case example. Record publication permission separately.
2. Report only measured results. If the outcome check is still pending, describe the delivered work and schedule measurement instead of claiming improvement.
3. If the client is satisfied, ask whether they would be comfortable introducing you to one relevant colleague. No referral is assumed.

**Evidence:** Approved wording/permission or a dated request; any permitted introduction stays private.

**30-minute fallback:** Ask for one specific piece of feedback and the permission needed to use it.

**Templates:** T14 Case study, testimonial and permission; T04 Warm introduction and referral request.

**Existing assets:** [/about](https://swiftagility.co.ke/about)

#### Day 28: Offer one useful next engagement

**Time:** 75 minutes. **Output:** A relevant next-work conversation, if the buyer has a need.

**Before this session:** Client accepted the delivery.

1. Review the remaining problem the client has actually identified. Choose one suitable next step: in-house training, a mentorship programme or advisory support.
2. Explain how it relates to the first result and agree whether a proposal would be welcome. Do not default to an annual retainer.
3. If accepted, start a new scoped opportunity and proposal cycle. If declined, keep the agreed outcome check or close politely.

**Evidence:** A buyer-agreed next step, revisit date or no-further-work decision.

**30-minute fallback:** Identify one remaining need from the client’s own feedback.

**Templates:** T15 Next engagement and 30-day outcome check; T08 Proposal and statement of work.

**Existing assets:** [/mentorship](https://swiftagility.co.ke/mentorship), [/trainings](https://swiftagility.co.ke/trainings)

#### Day 29: Schedule the real 30-day outcome check

**Time:** 60 minutes. **Output:** A follow-up tied to delivery, not the roadmap calendar.

**Before this session:** Client accepted the delivery.

1. Agree an outcome-check date about 30 calendar days after handover, or the date the client prefers. This roadmap’s Day 29 is when you schedule it, not automatically when it occurs.
2. Prepare questions that compare the agreed baseline with current practice. Ask what changed, what remains stuck and whether more support would help.
3. For “not now” opportunities, use the agreed revisit date. A permanent mismatch or opt-out stays closed.

**Evidence:** Agreed follow-up date, questions and client owner.

**30-minute fallback:** Schedule the check and record one baseline question.

**Templates:** T15 Next engagement and 30-day outcome check; T07 Meeting confirmation and follow-up cycle.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

#### Day 30: Review the evidence and repeat what worked

**Time:** 75 minutes. **Output:** The next cycle has a justified focus.

1. Review actual outreach, replies, held conversations, requested proposals, signed scopes, cash received and accepted deliveries. Keep every category distinct.
2. If no paying client exists yet, diagnose the bottleneck and repeat the appropriate outreach or sales loop. If one is served, use approved proof and permitted referrals for the next.
3. Make the most useful messages and delivery checklists reusable. Consider Nick’s scale and recurring-work ambition only after repeatable sales and delivery evidence; his $25K title is not Naomi’s forecast.

**Evidence:** A factual cycle review and the next seven working sessions.

**30-minute fallback:** Identify the single bottleneck and choose tomorrow’s action.

**Templates:** T16 Weekly first-client review; T03 Prospect qualification and next-action view.

**Existing assets:** [/admin](https://swiftagility.co.ke/admin)

## Template build queue

These are template specifications, not completed templates.

### T01: Audience and entry-offer sheet

**When:** First. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 1, 2, 4.

A one-page decision sheet that turns a broad consultancy catalogue into one offer Naomi can explain and deliver.

Required fields:

- Buyer role and organisation type
- One recurring problem and why it matters
- Paid first-step scope and explicit exclusions
- Deliverables, duration and acceptance criteria
- Whole-KES fee, costs, terms and capacity

### T02: Proof and capability one-pager

**When:** First. **Status:** Adapt existing material. **Suggested owner:** Naomi + Innocraft. **Days:** 3, 9.

Reuse the About page, brochure and approved intake material. Do not invent a case study or treat institutional names as new clients.

Required fields:

- Relevant experience for this buyer
- One approved example of prior work
- Actual result and evidence, or clearly labelled experience only
- Permission for named references
- Short bio and the relevant website link

### T03: Prospect qualification and next-action view

**When:** First. **Status:** Reuse CRM; adapt view. **Suggested owner:** Innocraft. **Days:** 6, 11, 12, 30.

Use existing CRM contacts and follow-ups. A daily filtered view is the future admin-home integration; no new public contact list is needed.

Required fields:

- Organisation and buyer role
- Source and relationship strength
- Evidence of need and relevant offer
- Last contact, response and next action/date
- Decision route and consent or opt-out

### T04: Warm introduction and referral request

**When:** First. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 7, 27.

Two short variants: reconnect with an existing relationship and ask a trusted person for an introduction.

Required fields:

- Relationship context
- Specific buyer and problem sought
- Why a conversation would help
- Forwardable introduction
- Permission to introduce; one clear ask

### T05: Community contribution and outreach messages

**When:** First. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 8, 9, 10.

Prepare distinct WhatsApp, email and LinkedIn versions plus one useful community post. Naomi sends personally; this site sends nothing.

Required fields:

- Buyer-specific observation
- One relevant tool or example
- A low-pressure invitation to talk
- Channel-appropriate short version
- No-show, follow-up and polite close variants

### T06: Discovery and buying-process notes

**When:** First. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 10, 13, 14, 15.

One reusable conversation guide with a place for buyer facts. The readiness check assists discovery; it does not replace it.

Required fields:

- Current process and recurring difficulty
- Frequency, baseline and impact in the buyer’s words
- What improvement would be worth paying for
- Decision maker, approver, budget and purchasing steps
- Desired timing, agreed next step and permission to follow up

### T07: Meeting confirmation and follow-up cycle

**When:** First. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 12, 17, 18, 29.

Confirmation, no-show, proposal follow-up and 30-day revisit variants. The buyer’s preference always controls cadence.

Required fields:

- Agreed date, time and location/link
- Agenda and needed attendee roles
- Reminder and no-show rebooking
- Not-now reason and agreed revisit date
- Stop-contact instruction

### T08: Proposal and statement of work

**When:** Before proposal. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 16, 18, 19.

A concise, buyer-specific proposal and scope. The existing brochure and meeting packs are source material, not a signed statement of work.

Required fields:

- Buyer-confirmed problem and desired result
- Deliverables, exclusions and client inputs
- Work dates, milestones and owners
- Whole-KES fee, tax treatment to confirm and payment schedule
- Acceptance criteria, revision allowance and signatures

### T09: Invoice, payment verification and receipt

**When:** Before payment. **Status:** Build / verify operator tools. **Suggested owner:** Naomi + Innocraft. **Days:** 19, 20, 26.

Confirm Naomi’s existing finance process first. Verify supplier/tax requirements before issuing; an invoice or payment screenshot alone is not receipt verification.

Required fields:

- Invoice number, date and agreed scope reference
- Correct supplier details and verified payment destination
- Whole-KES line items and approved tax treatment
- Due date and agreed payment milestone
- Receipt reference, amount received and outstanding balance

### T10: Kickoff and client input checklist

**When:** Before delivery. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 21.

Start only after signature and agreed initial payment. For a diagnostic, use anonymised examples and avoid copying personnel records into this roadmap.

Required fields:

- Sponsor, delivery contact and attendee roles
- Signed scope and agreed dates
- Minimal inputs and permitted access
- Baseline and success measure
- Decision and escalation channel

### T11: Delivery plan and baseline record

**When:** Before delivery. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 22, 23.

A small repeatable delivery checklist. Existing tools help produce outputs; they do not manage the client project.

Required fields:

- Milestone and owner
- Baseline, source and measurement method
- Session agenda or diagnostic method
- Due dates and client inputs
- Risk, decision and change record

### T12: Diagnostic findings and action report

**When:** Before delivery. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 23, 25.

The recommended paid diagnostic leaves the buyer with a usable plan. A workshop variant adds exercises, attendance and the buyer’s application task.

Required fields:

- Confirmed problem and evidence
- Baseline and limits of the review
- Three prioritised actions with owners
- Immediate first step and 30-day check
- Agreed deliverables and handover links

### T13: Revision log and delivery acceptance

**When:** Before delivery. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 24, 25, 26.

Resolve agreed corrections, then obtain explicit acceptance. Never silently turn a revision into unpaid additional scope.

Required fields:

- Deliverable and scope criterion
- Client feedback and agreed correction
- Owner, due date and resolution
- Out-of-scope change request
- Written acceptance and remaining balance

### T14: Case study, testimonial and permission

**When:** After a result. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 27.

Publish only approved evidence. If a later outcome is not measured yet, describe the delivered work and schedule the outcome check.

Required fields:

- Starting position and delivered work
- Measured change and evidence date
- Buyer-approved wording
- Named or anonymised publication permission
- Separate permission for a referral introduction

### T15: Next engagement and 30-day outcome check

**When:** After a result. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 28, 29.

Offer deeper training, mentorship or advisory support because it meets a demonstrated need. Do not assume every client needs a retainer.

Required fields:

- Remaining buyer-confirmed problem
- Observed benefit from the first engagement
- One appropriate next scope
- Outcome check questions and agreed date
- Accept, revisit or stop branches

### T16: Weekly first-client review

**When:** First. **Status:** Build. **Suggested owner:** Naomi + Innocraft. **Days:** 5, 11, 15, 20, 30.

A brief weekly record. Activity targets are experiments; signed value, received money and completed delivery remain separate.

Required fields:

- Personal outreach attempts and replies
- Held buyer conversations
- Proposals requested and sent
- Signed scopes, verified cash and accepted delivery
- Bottleneck, one change and next week’s actions

## Review boundaries

Public Home and Tools pages and source/release records were reviewed on 11 October 2026. Current private CRM data, payment records, automatic notifications and Naomi’s operating acceptance were not read or verified. The separate review site keeps progress on the local device only; export it to move browsers. It sends no messages and makes no CRM or financial writes. Keep private records outside it. Admin-home integration is a later step after this review.