Institutional Engagement Playbook

A step-by-step playbook for engaging Malaysian institutions — from first research to signed partnership. Each phase includes actions, scripts, communication templates, and milestone criteria.

Two institution tracks run in parallel through the same phases:

• Track A: Financial Enablers — Banks, DFIs, financing platforms (SME Bank, BSN, RHB, Planworth, Bank Rakyat)
• Track B: Government & Development Agencies — Ministries, statutory bodies, economic corridors (TERAJU, CIDB, MATRADE, HDC, MRANTI)

Phase 1: Target Selection & Research

Duration: Week 1–2 | Owner: Biz Dev Lead | Gate: Target card complete for each institution

What to Do

1. Select 3–5 priority institutions from the Institutional Subscribers list. Prioritize by:

   • Confirmed SME reach (CIDB, SME Bank, Planworth are top tier)
   • Existing relationship warmth (have you met anyone there?)
   • Strategic fit (does their mandate overlap with SPOT’s value?)

2. Build a Target Card for each institution with:

   • Full name, type (Bank/DFI or Government), and SME reach estimate
   • Key decision-maker name, title, department
   • Their top pain point (match from pre engagement)
   • Recent news or initiative that creates a timing hook
   • Recommended track (A or B)

3. Research the decision-maker. LinkedIn, conference appearances, published interviews. Note their preferred communication style and any mutual connections.

4. Prepare the one-page SPOT brief. A PDF or print-ready summary covering: what SPOT does, the 4 differentiators, Malaysian-context specificity, and the pilot program offer. This is your leave-behind for every interaction.

What to Say (Internal Prep Only)

No external communication in this phase. Use this framing to align internally:

“We are targeting [Institution] because they serve [X] SMEs and their [specific pain point] is directly addressed by SPOT’s [specific capability]. The timing hook is [recent news/initiative]. The decision-maker is [Name], [Title], and our best approach angle is [warm intro / event / cold outreach].”

Milestones

• 3–5 Target Cards completed
• One-page SPOT brief finalized
• Internal alignment on priority order and track assignment

Phase 2: Outreach & Introduction

Duration: Week 2–4 | Owner: Biz Dev Lead | Gate: Meeting confirmed with decision-maker or direct report

What to Do

1. Exhaust warm paths first. Check for mutual connections, shared event attendance, or introductions through existing partners. A warm intro converts 3–5x higher than cold outreach.

2. If warm path exists: Ask the connector to send a brief introduction email (you draft it for them).

3. If no warm path: Use cold outreach. Channel depends on track:

   • Track A (Banks/DFIs): LinkedIn message or direct email to the Head of SME Banking / Credit Operations / Digital Transformation
   • Track B (Government): Official letter addressed to the Secretary-General or Director of the SME/Enterprise Development division, followed by a phone call to the liaison officer

4. Follow up exactly once after 5 business days if no response. Then pause and try a different decision-maker or angle.

What to Say

Warm Introduction Request (to your connector)

Hi [Connector Name],

I’m reaching out because we’re introducing SPOT to [Institution]. I understand [Decision-Maker Name] leads [their department/initiative], and our platform addresses a challenge I believe their team faces daily.

Would you be comfortable making a brief introduction? I can draft the message so it’s minimal effort for you.

For context: SPOT is an AI-powered KYB diagnostic platform that structures SME documentation into verifiable business intelligence profiles in under 8 minutes. It’s built specifically for the Malaysian regulatory environment.

Thank you for considering this.

Cold Email — Track A (Banks/DFIs)

Subject: Reducing SME document processing from 4 hours to 8 minutes

Dear [Name],

I’m writing from Odela Business Services. We’ve developed a platform called SPOT that addresses a specific bottleneck in SME credit assessment: the time your analysts spend manually extracting, verifying, and structuring applicant documents.

SPOT transforms raw corporate documents into verified, structured business intelligence profiles in 6 to 8 minutes. Every calculation is deterministic — no AI hallucination of numbers. It’s aligned with Bank Negara’s RMiT guidelines, with AES-256 encryption and full data residency in the AWS Malaysia region.

I’d appreciate 20 minutes to show you how it works with real SME profiles. No presentation — just a live demonstration.

Would [day, date] at [time] work for a brief call or meeting?

Best regards, [Your Name] Odela Business Services

Cold Email — Track B (Government)

Subject: Supporting [Agency]‘s SME development mandate with diagnostic infrastructure

Dear [Name / Yang Berbahagia Datuk / Yang Berusaha],

I’m writing from Odela Business Services regarding a platform that supports [Agency]‘s mission to [reference their specific mandate from recent news or annual report].

SPOT is a diagnostic infrastructure platform that transforms unstructured SME documentation into standardized, verifiable readiness assessments. In under 8 minutes, your officers can generate a complete business intelligence profile from raw corporate documents — supporting rapid screening for vendor programs, grant eligibility, and development tracking.

The platform is natively calibrated for the Malaysian regulatory context and aligns with national frameworks including MADANI Economy and DKN 2030.

I would like to request a brief meeting to demonstrate SPOT with 5 sample profiles. Would your team be available for a 30-minute session in the coming weeks?

Yang berkhidmat, [Your Name] Odela Business Services

LinkedIn Message (either track)

Hi [Name], I lead business development at Odela Business Services. We’ve built SPOT — a platform that structures SME documents into verifiable business intelligence in under 8 minutes. I noticed [specific thing about their work/post] and thought SPOT could be relevant to [their department’s goals]. Would you be open to a brief conversation?

Communication Guidelines

Milestones

• Outreach sent to all 3–5 targets
• At least 1 meeting confirmed
• No-response targets flagged for second attempt or alternative contact

Phase 3: Discovery Meeting

Duration: Week 4–6 | Owner: Biz Dev Lead + Product Lead | Gate: Institutional pain points documented, demo readiness confirmed

What to Do

1. Prepare a tailored agenda. Never use a generic presentation. Structure the meeting around their specific challenges:

   • Track A agenda: Current document processing workflow → pain points in verification → compliance requirements → where SPOT fits
   • Track B agenda: Current SME assessment process → data gaps in vendor/grant programs → reporting requirements → where SPOT fits

2. Listen more than you pitch. The first 15 minutes should be questions, not slides. You need to understand:

   • Their current workflow (how do they process SME profiles today?)
   • Their volume (how many SMEs do they assess per month?)
   • Their bottleneck (what takes the most time or causes the most errors?)
   • Their mandate pressure (are they under pressure to increase throughput or coverage?)

3. Ask the “magic question”:

   “If you could wave a wand and fix one thing about how your team handles SME documentation today, what would it be?”

4. Take detailed notes. Capture exact phrases they use to describe their problems — you’ll mirror this language back in the demo and proposal.

5. Confirm demo readiness. Before leaving, agree on:

   • Who will attend the demo (decision-maker + technical evaluators)
   • Whether you can use their actual sample documents (anonymized) or need to use your own
   • Date and time for the demo session

What to Say

Opening

“Thank you for making time. I want this to be useful for you, so rather than walking through a deck, I’d like to start by understanding your current process. Could you walk me through what happens today when an SME submits documents for [credit assessment / program eligibility / vendor qualification]?”

Probing Questions

• “How many SME profiles does your team process in a typical month?”
• “What’s the average turnaround time from document submission to assessment completion?”
• “Where do most delays occur — is it document collection, data extraction, verification, or the assessment itself?”
• “Are there specific compliance or audit requirements that slow things down?”
• “What percentage of applications have incomplete or inconsistent documentation?”

Closing

“This has been very helpful. What I’m hearing is that [summarize their top 2 pain points in their own words]. SPOT addresses exactly these areas. I’d like to come back and show you a live demonstration using real profiles. Would [suggested date] work for your team?”

Communication Guidelines

• Format: In-person preferred; video call acceptable for first meeting
• Attendees: Max 2 from Odela (Biz Dev + Product/Technical). Let them set their side
• Materials: Bring the one-page SPOT brief. No slides in the first meeting
• Follow-up: Send a thank-you email within 24 hours summarizing what you heard and confirming the demo date

Milestones

• Discovery meeting completed with notes
• Institutional pain points documented in their language
• Demo date confirmed with attendees identified
• Thank-you email sent within 24 hours

Phase 4: Demo & Proof of Value

Duration: Day 1 (same week as discovery) | Owner: Product Lead + Biz Dev Lead | Gate: Stakeholders confirm SPOT addresses their needs; pilot interest expressed

What to Do

1. Prepare a customized demo. Use what you learned in discovery:

   • If their pain is verification speed: demo a Full SPOT profile generation live, showing the 6–8 minute turnaround
   • If their pain is data quality: demo the confidence scoring and source-only extraction
   • If their pain is compliance: demo the audit trail, encryption, and RMiT alignment
   • If their pain is throughput: show batch processing and how one analyst handles multiple profiles

2. Use real documents. If they provided sample (anonymized) SME documents, use those. Nothing is more persuasive than seeing their own data structured by SPOT. If not, use realistic Malaysian SME sample documents from your library.

3. Demo structure (30–40 minutes):

   • 5 min: Recap their pain points (using their language from discovery)
   • 15 min: Live SPOT demo — upload documents, watch processing, review output
   • 5 min: Walk through the generated report sections
   • 10 min: Q&A and discussion

4. Never overpromise. If SPOT can’t do something they ask about, say so directly. Credibility compounds.

5. Propose the pilot at the right moment. After the demo, when engagement is highest, transition to the pilot discussion.

What to Say

Demo Opening

“In our last conversation, you mentioned that [their specific pain point, their words]. Today I want to show you exactly how SPOT addresses that. I’ll use [their documents / realistic sample documents] so you can see real output, not a staged demo.”

During the Demo

“Notice here — this is the confidence score. Any extraction below our threshold is flagged for your team’s verification. SPOT doesn’t make the decision; it gives your officers a verified starting point.”

“This calculation here — [specific financial ratio] — is processed by our deterministic engine. It’s not an AI estimate. It’s mathematically identical to what your analyst would calculate manually.”

Transition to Pilot

“What you’ve just seen is SPOT running on [their documents / sample documents]. The natural next step is to run this with your actual workflow. We propose a pilot: we process [50] of your existing SME profiles through SPOT, and your team evaluates the output against your current manual process. Zero commitment beyond the pilot.”

Handling Demo Questions

Communication Guidelines

• Format: In-person strongly preferred for the demo. Screen presence matters
• Materials: Live SPOT instance, printed sample report, one-page brief (leave-behind)
• Technical backup: Have a pre-generated report ready in case of live demo issues
• Follow-up: Within 48 hours, send the pilot proposal document

Milestones

• Demo completed with key stakeholders present
• Q&A documented — all concerns addressed or noted
• Pilot interest verbally confirmed
• Pilot proposal sent within 48 hours

The Conversion Roadmap: Demo to Implementation

"Interesting demo"               "We want this"
     ┌────────────┐              ┌────────────┐
     │  INTEREST  │──→──→──→──→  │ CONVICTION │
     └────────────┘              └────────────┘
          │                             │
     ┌────▼─────┐                 ┌─────▼───────┐
     │  DOUBT   │                 │ COMMITMENT  │
     └──────────┘                 └─────────────┘
          │                             │
     ┌────▼──────┐                ┌─────▼─────┐
     │   STALL   │                │ CONTRACT  │
     └───────────┘                └───────────┘

Every institution goes through the same psychological journey after seeing a demo. The playbook below is organized around four conversion gates — moments where the deal either advances or dies. Your job at each gate is to give the decision-maker exactly what they need to move forward.

Phase 5: Sealing the Pilot (Gate 1 — Interest → Pilot Yes)

Duration: Week 1–2 | Owner: Biz Dev Lead Conversion goal: Move the institution from “interesting demo” to a signed pilot agreement Institution’s mindset: “I liked what I saw, but I’m not sure yet. I need to justify this internally. The proposal needs to make my case for me.”

Step-by-Step Actions

Step 5.1 — Same-Day Post-Demo Follow-Up (Day 0)

Who: Biz Dev Lead Conversion purpose: Lock in recency bias. Show you move fast — it signals how you’ll operate during the pilot.

Action: Send a thank-you email within 4 hours of the demo ending. Do not wait until tomorrow.

Email template:

Subject: Thank you — SPOT demo with [Institution] on [Date]

Dear [Name],

Thank you for your time today. It was valuable to see your team’s reaction to the live processing, and I appreciated the questions about [reference a specific question they asked — proves you were listening].

As discussed, I’ll send over the pilot proposal within [2 business days]. In the meantime, here’s the one-page SPOT brief for your internal reference.

Looking forward to next steps.

Best regards, [Your Name]

Attachments: One-page SPOT brief (PDF)

Why same-day: Institutional contacts receive dozens of vendor emails daily. The first one after a meeting wins the recency bias. If you wait until tomorrow, you’re already below 5 other emails in their inbox.

Step 5.2 — Identify and Arm Your Internal Champion (Day 1)

Who: Biz Dev Lead Conversion purpose: Your champion is the person who will sell SPOT internally when you’re not in the room. Identify them now, before you send the proposal.

How to spot the champion:

• They asked the most detailed questions during the demo
• They took notes or photos of the screen
• They said something like “this would save us so much time” or “we’ve been looking for something like this”
• They stayed after the meeting to ask more questions

Action: Reach out to them directly — phone call or WhatsApp, not email. Email feels formal; this should feel like a colleague asking how to help.

What to say:

“Hey [Name], thanks again for the engaged questions during the demo. I’m putting together the pilot proposal for [primary contact]. Before I send it, I want to make sure it includes everything your team needs to evaluate SPOT fairly. Two questions: (1) What’s the one thing your [boss / compliance team / IT team] will ask about that I should address proactively? (2) Is there anyone else who needs to be in the loop before we can get to a pilot?”

Based on their answer, prepare within 24 hours:

Step 5.3 — Draft and Send the Pilot Proposal (Day 1–2)

Who: Biz Dev Lead Conversion purpose: The proposal must do two things — (1) give the decision-maker everything they need to say yes, and (2) give the champion everything they need to sell it internally.

Proposal structure (max 5 pages, PDF only):

1. Cover page — Odela Business Services logo, SPOT branding, “Pilot Proposal for [Institution]”, date, confidential marking
2. Executive Summary (half page) — What SPOT does, why the pilot, what success looks like. Written for senior leadership who weren’t in the demo — this is the page the champion hands to their boss
3. Pilot Scope — Number of profiles, document types, report tier, batch schedule
4. Pricing — Pilot rate per profile, total pilot cost, explicit note that production pricing follows standard tiers
5. Success Criteria — Mutually agreed metrics: time savings target, accuracy threshold, team satisfaction benchmark
6. Timeline — 2–3 weeks broken into 2 batches
7. Terms — Data handling, confidentiality, pilot-to-production transition path, termination clause
8. Next Steps — Clear list of what happens after signing

Pricing reference for the proposal:

Pilot rates are 30–50% below standard pricing. State this explicitly: “Pilot rates are subsidized to minimize evaluation risk. Production pricing follows standard tiers as outlined in Appendix A.”

Send the proposal to your primary contact. CC the champion and any technical evaluator you met during the demo.

Email template:

Subject: SPOT Pilot Proposal — [Institution]

Dear [Name],

Following up on our demo session, please find attached the pilot proposal for your review.

Summary:

• Scope: [30] SME profiles processed through SPOT over [2–3 weeks]
• Pilot rate: RM [X] per profile (subsidized from standard RM [Y])
• Total pilot investment: RM [total]
• Success criteria: [X]% time savings, [Y]% accuracy vs. manual baseline

I’ve also attached:

1. One-page executive summary (for leadership who weren’t in the demo)
2. Security and compliance documentation
3. SPOT platform overview

I’m available to walk through the proposal with your team, or to present to a broader group if that would help internal alignment.

Best regards, [Your Name]

Attachments:

1. Pilot proposal (PDF)
2. Executive summary (PDF, 1 page)
3. Security & compliance documentation (PDF)
4. SPOT platform overview (PDF)

Step 5.4 — Handle the Internal Review gauntlet (Day 3–21)

Who: Biz Dev Lead + Product Lead Conversion purpose: This is where most deals stall. The institution’s internal review is not a delay — it’s a buying process. Every question is a buying signal. Every objection is a chance to strengthen the case.

Institution’s internal review looks like this:

Day 3–5:  Champion reads proposal → shares with boss
Day 5–10: Boss has questions → asks champion to get answers
Day 10–14: Compliance/IT/security team review → sends questions
Day 14–21: Budget approval or procurement process
Day 21+:   Decision

Your role at each stage:

Stage 1 — Champion shares with boss (Day 3–5)

Check in with the champion on Day 3. Do not email the primary contact — call or WhatsApp the champion.

“Hey [Name], did you get a chance to share the proposal? Any initial reactions from your side? I want to be ready if [boss’s name] has questions.”

If the champion says “they haven’t looked at it yet”:

“No worries. Would it help if I prepared a 2-minute voice note or a short video walking through the key numbers? Sometimes a quick summary is easier to absorb than a 5-page document.”

Stage 2 — Boss has questions (Day 5–10)

When questions come, respond within 24 hours. Common boss-level questions:

“Is this worth the budget?”

“The pilot is designed to answer exactly that question. Here’s the math: your analyst spends approximately [4 hours] per SME profile at an estimated cost of RM [Y] in staff time alone. SPOT processes the same profile in [8 minutes] at a pilot cost of RM [X]. If the pilot confirms these numbers, the annual savings at your current volume of [Z profiles/month] would be RM [annual savings]. The pilot costs [fraction] of one month’s manual processing cost.”

“What if it doesn’t work?”

“That’s exactly why we structure this as a pilot, not a commitment. If the results don’t meet the success criteria we’ve defined together, you walk away. Total pilot investment: RM [X]. Maximum downside: known and capped. Maximum upside: [annual savings figure].”

“Can we do this next quarter instead?”

“We can, though I’d note that [reference a timing pressure — BNM circular, their annual planning cycle, upcoming audit, new program launch]. Running the pilot now means you have results in hand before [relevant deadline].”

Stage 3 — Compliance/IT/Security review (Day 10–14)

This is the most common stall point. Do not let this become a black hole. Offer to meet the compliance/IT team directly.

“I’d like to schedule a 30-minute technical briefing with your IT/security team. I’ll bring our security documentation and walk through data residency, encryption, audit logging, and any specific concerns. Can you connect me with the right person?”

Proactively prepare and send (even if they haven’t asked yet):

• Security architecture diagram (1 page)
• Data residency certification (AWS Malaysia)
• Encryption specifications (AES-256-GCM at rest, TLS 1.3 in transit)
• Audit log sample (7-year retention, immutable, correlation IDs)
• RMiT alignment mapping (section by section)

Stage 4 — Budget/Procurement (Day 14–21)

“I understand there’s a procurement process. Can you share the requirements so I can have everything prepared? I want to make this as frictionless as possible for your team.”

If they say the budget isn’t available this quarter:

“We can structure the pilot with deferred billing — the pilot runs now, and the invoice is dated against your next budget cycle. This way you don’t lose time waiting for budget allocation.”

Step 5.5 — Push for Decision Meeting (Day 14–21)

Who: Biz Dev Lead Conversion purpose: If the proposal has been circulating for 2+ weeks without a clear decision, stop emailing and start meeting.

Email template:

Subject: SPOT pilot — can we align on next steps this week?

Hi [Name],

I want to make sure the pilot proposal isn’t sitting in a review queue somewhere. I know internal alignment takes time — I’d like to help move it along.

Three options:

1. Quick call (20 min) — I can address any open questions directly
2. Broader presentation (45 min) — I present to anyone who needs to see SPOT before approving
3. Written response — You send me all open questions and I respond in detail by [next business day]

Which works best?

Best regards, [Your Name]

If they pick option 1 or 2, treat it like a mini-demo. Bring the same energy, the same live SPOT instance, and the same focus on their specific pain points. Decision-makers who weren’t in the original demo need to experience SPOT themselves — they won’t sign based on their colleague’s enthusiasm alone.

Step 5.6 — Agreement Finalization (Day 14–28)

Who: Biz Dev Lead + Legal Conversion purpose: Speed kills stalls. Once they say yes verbally, get to signature within 7 days. Every day between verbal yes and signed contract is a day the deal can die.

Steps:

1. Day 0: Verbally agree on scope, pricing, and key terms
2. Ask: “Does your organization have a standard vendor agreement template, or should we use ours?”
3. Day 1–2: Send the agreement (their template or ours, institution-specific details filled in)
4. Set a target: “Let’s aim to have this signed by [date — 7 days out] so we can kick off the pilot on [target start date]”
5. Day 3–7: Follow up daily (but briefly) until signed

Pilot agreement must include:

• Scope and number of profiles
• Pilot rate and total cost, with payment terms
• Timeline with batch schedule
• Success criteria (mutually defined)
• Data handling and confidentiality obligations (both directions)
• Termination clause (either party can exit the pilot with [X] days notice)
• Pilot-to-production transition path (what happens if success criteria are met)
• NDA or confidentiality provisions (if not already covered by a separate NDA)

Gate 1 Milestones

• Thank-you email sent within 4 hours of demo
• Internal champion identified and equipped with toolkit
• Pilot proposal sent within 2 business days
• All internal review questions addressed within 24 hours
• Compliance/IT briefing offered proactively
• Decision meeting held with all stakeholders
• Pilot agreement signed by both parties
• Pilot kickoff date confirmed

Phase 6: Building Conviction Through the Pilot (Gate 2 & 3 — Confidence → Recommendation)

Duration: Week 2–4 (2–3 weeks) | Owner: Product Lead + Biz Dev Lead Conversion goal: Move the institution from “let’s test this” to “I’m recommending this to my leadership” Institution’s mindset: “I’m putting my reputation on the line by running this pilot. SPOT needs to prove itself on our data, with our team watching. If the first batch is bad, I’ll kill it and move on.”

Step-by-Step Actions

Step 5.1 — Same-Day Post-Demo Follow-Up (Day 0)

Who: Biz Dev Lead Action: Send a thank-you email within 4 hours of the demo ending. Do not wait until tomorrow.

Email template:

Subject: Thank you — SPOT demo with [Institution] on [Date]

Dear [Name],

Thank you for your time today. It was valuable to see your team’s reaction to the live processing, and I appreciated the questions about [reference a specific question they asked — proves you were listening].

As discussed, I’ll send over the pilot proposal within [2 business days]. In the meantime, here’s the one-page SPOT brief for your internal reference.

Looking forward to next steps.

Best regards, [Your Name]

Attachments: One-page SPOT brief (PDF)

Why same-day: Institutional contacts receive dozens of vendor emails daily. The first one after a meeting wins the recency bias. If you wait until tomorrow, you’re already below 5 other emails in their inbox.

Step 5.2 — Draft the Pilot Proposal (Day 1–2)

Who: Biz Dev Lead Action: Prepare the pilot proposal document. This is a formal PDF, not a PowerPoint, not a Word doc with track changes.

Proposal structure (max 5 pages):

1. Cover page — Odela Business Services logo, SPOT branding, “Pilot Proposal for [Institution]”, date, confidential marking
2. Executive Summary (half page) — What SPOT does, why the pilot, what success looks like. Written for their senior leadership who weren’t in the demo
3. Pilot Scope — Number of profiles, document types, report tier, batch schedule
4. Pricing — Pilot rate per profile, total pilot cost, note that production pricing follows standard tiers
5. Success Criteria — Mutually agreed metrics: time savings target, accuracy threshold, team satisfaction benchmark
6. Timeline — 2–3 weeks broken into 2 batches
7. Terms — Data handling, confidentiality, pilot-to-production transition path, termination clause
8. Next Steps — Clear list of what happens after signing

Pricing reference for the proposal:

Pilot rates are 30–50% below standard pricing. State this explicitly in the proposal: “Pilot rates are subsidized to minimize evaluation risk. Production pricing follows standard tiers as outlined in Appendix A.”

Step 5.3 — Send the Pilot Proposal (Day 2)

Who: Biz Dev Lead Action: Email the proposal to your primary contact. CC their technical evaluator if you met one during the demo.

Email template:

Subject: SPOT Pilot Proposal — [Institution]

Dear [Name],

Following up on our demo session, please find attached the pilot proposal for your review.

Summary:

• Scope: [30] SME profiles processed through SPOT over [2–3 weeks]
• Pilot rate: RM [X] per profile (subsidized from standard RM [Y])
• Total pilot investment: RM [total]
• Success criteria: [X]% time savings, [Y]% accuracy vs. manual baseline

I’ve also attached:

1. One-page executive summary (for leadership who weren’t in the demo)
2. Security and compliance documentation
3. SPOT platform overview

I’m available to walk through the proposal with your team, or to present to a broader group if that would help internal alignment.

Best regards, [Your Name]

Attachments:

1. Pilot proposal (PDF)
2. Executive summary (PDF, 1 page)
3. Security & compliance documentation (PDF)
4. SPOT platform overview (PDF)

Step 5.4 — Internal Champion Check-In (Day 3–4)

Who: Biz Dev Lead Action: Call or message your internal champion (the person at the institution who showed the most enthusiasm during the demo). Do not email — this is a quick, informal touch.

What to say:

“Hey [Name], just wanted to give you a heads-up that I’ve sent the pilot proposal to [primary contact]. I know you’ll likely need to build the case internally — is there anything specific I can prepare that would help? A customized ROI calculation? A version of the exec summary tailored for [their boss’s name/department]?”

Purpose of this call: You’re arming your champion to sell SPOT internally. They know their organization’s politics and approval process better than you ever will. Ask them what they need, then deliver it within 24 hours.

Deliverables to prepare based on their answer:

• If they say “my boss cares about cost”: Prepare a cost comparison table (manual processing cost vs. SPOT pilot cost vs. SPOT production cost)
• If they say “compliance team needs assurance”: Prepare a one-pager on RMiT alignment, data residency, and encryption
• If they say “procurement has their own process”: Ask for their procurement requirements and prepare to comply
• If they say “we need to see more data”: Offer to run 2–3 additional profiles at no cost as a pre-pilot taste

Step 5.5 — Week 1 Follow-Up (Day 7)

Who: Biz Dev Lead Action: Send a brief, no-pressure check-in email. The goal is to stay visible without being annoying.

Email template:

Subject: Checking in — SPOT pilot proposal

Hi [Name],

Just checking in on the pilot proposal I sent last [day]. No rush — I know internal reviews take time.

One quick update since we last spoke: we’ve added [mention a relevant new feature, case study, or industry article — something that adds value, not just noise].

Let me know if any questions come up during the review, or if there’s anyone else on your team I should speak with.

Best regards, [Your Name]

Step 5.6 — Address Internal Review Feedback (Day 7–14)

Who: Biz Dev Lead + Product Lead Action: When (not if) they come back with questions or requested changes, respond within 24 hours. Common institutional review feedback and how to handle each:

“We need more time to evaluate.”

Say: “Completely understood. Internal alignment takes time, especially for something that touches your SME workflow. Is there additional information I can provide? I’m also happy to present to a broader group — perhaps the [compliance team / digital transformation unit / procurement committee]?”

“The price is too high for a pilot.”

Say: “I understand the concern. Let me share the math: your analyst currently spends approximately [4 hours] per SME profile at an estimated cost of RM [Y] per profile in staff time alone. SPOT’s pilot rate of RM [X] is a fraction of that, and the pilot proves the savings before any production commitment. If budget is a constraint, we can also structure the pilot as [10 profiles instead of 50 / deferred payment until pilot completes / phased billing by batch].”

“We need to involve our IT/security team.”

Say: “Absolutely — let’s schedule a 30-minute technical briefing with your IT team. I’ll bring our security architect. We can cover data residency, encryption, audit logging, and any specific concerns your team has. What works for their schedule?”

“Can we do a smaller pilot first?”

Say: “Yes. We can start with 10 profiles as Batch 0 — a quick validation before committing to the full 50. If the output meets your standards, we continue to Batch 1. If not, we stop. This further reduces your risk.”

“Our procurement process requires [specific document/format/timeline].”

Say: “Send me the requirements and I’ll have everything prepared within [X] business days.”

Step 5.7 — Send Champion Materials (Ongoing during review)

Who: Biz Dev Lead Action: Whenever your champion asks for materials (or when you proactively anticipate they’ll need them), prepare and send within 24 hours. Keep a running list of what you’ve provided so you never send duplicates.

Champion toolkit items:

• 1-page executive summary (non-technical, leadership-facing)
• ROI calculation spreadsheet (pre-filled with their volume and pain points from discovery)
• Security & compliance one-pager (RMiT, AES-256, data residency)
• Case study or reference (if available from another institution)
• Comparison table: manual process vs. SPOT (time, cost, accuracy)
• Pilot success story draft (template ready for them to fill in after pilot)

Step 5.8 — Week 2 Value-Add Touch (Day 14)

Who: Biz Dev Lead Action: Send something useful that isn’t a follow-up on the proposal. This maintains relationship momentum without being “that vendor who keeps asking if we signed yet.”

Ideas:

• Share a relevant BNM circular, MITI announcement, or industry report with a brief note: “Thought this might be relevant given [what they told you in discovery]”
• Share a short video (60 seconds) of a SPOT feature that addresses a specific question they raised during the demo
• Invite them to an upcoming event, webinar, or roundtable you’re attending/hosting

Email template:

Subject: [Relevant article/report] — thought of your team

Hi [Name],

Came across this [article/report/circular] on [topic related to their pain point]. Given what you mentioned about [their specific challenge], I thought it might be useful.

No action needed — just sharing.

Best regards, [Your Name]

Step 5.9 — Push for Decision / Schedule Follow-Up Meeting (Day 14–21)

Who: Biz Dev Lead Action: If the proposal has been with them for 2+ weeks without a clear decision, it’s time to push for a meeting rather than another email.

Email template:

Subject: Next steps — SPOT pilot proposal

Hi [Name],

I wanted to check in on the pilot proposal. I understand the internal review process takes time, and I want to make sure I’m supporting that however I can.

Would it be helpful to schedule a 20-minute call with [any stakeholders who haven’t seen SPOT yet]? I can do a focused walkthrough of the specific areas they’re evaluating — whether that’s security, accuracy, integration, or pricing.

Alternatively, if there are open questions I can address in writing, just let me know and I’ll send a detailed response.

What works best for your team?

Best regards, [Your Name]

Step 5.10 — Agreement Finalization (Day 14–28)

Who: Biz Dev Lead + Legal Action: Once verbal agreement is reached, move to written contract quickly. Institutions will often have their own contract template.

Steps:

1. Ask: “Does your organization have a standard vendor agreement template, or should we use ours?”
2. If they have a template: Send it to legal immediately. Flag any non-negotiable terms (data ownership, IP, confidentiality period)
3. If using our template: Send the pre-prepared pilot agreement with institution-specific details filled in
4. Set a target signing date: “Let’s aim to have this signed by [date — typically 1 week from verbal agreement] so we can kick off the pilot on [target start date]”

Pilot agreement must include:

• Scope and number of profiles
• Pilot rate and total cost, with payment terms
• Timeline with batch schedule
• Success criteria (mutually defined)
• Data handling and confidentiality obligations (both directions)
• Termination clause (either party can exit the pilot with [X] days notice)
• Pilot-to-production transition path (what happens if success criteria are met)
• NDA or confidentiality provisions (if not already covered by a separate NDA)

Milestones

• Thank-you email sent same day as demo
• Pilot proposal drafted and sent within 2 business days
• Internal champion identified and equipped with toolkit
• All review questions addressed within 24 hours
• Follow-up meeting scheduled (if needed)
• Pilot agreement finalized and signed by both parties
• Pilot kickoff date confirmed

Phase 7: From Recommendation to Contract (Gate 4 — Conviction → Commitment)

Duration: Week 4–6 | Owner: Biz Dev Lead + Leadership Conversion goal: Move the institution from “we want this” to a signed production contract Institution’s mindset: “I’ve seen the results and I’m convinced. Now I need to convince procurement, legal, and the budget holder. Make this easy for me.”

Step-by-Step Actions

Step 7.1 — Send the Results Report with a Partnership Ask (Within 3 Days of Retrospective)

Who: Biz Dev Lead Conversion purpose: Don’t just send the report — attach a clear next step. Every document you send should answer: “What do you want me to do with this?”

Email template:

Subject: SPOT Pilot Results + Next Steps for [Institution]

Dear [Name],

Attached is the complete pilot results report covering all [30] profiles processed over [2–3 weeks].

Three numbers that matter:

• Time savings: [X]% vs. manual process
• Accuracy: [Y]% match with your team’s manual verification
• Team satisfaction: [Z]/10

Based on these results and your team’s feedback, we’d like to propose a production partnership. I’ve attached a one-page overview of three partnership models for your review.

I’d like to schedule a meeting with [decision-maker names from retrospective] to discuss which model fits best. Would [date range] work for a 45-minute session?

Best regards, [Your Name]

Attachments:

1. Pilot results report (PDF)
2. Partnership models overview (PDF, 1 page)

Step 7.2 — Prepare the Partnership Models Sheet (Pre-Meeting)

Who: Biz Dev Lead Conversion purpose: The institution needs to see options, not a take-it-or-leave-it offer. Three models let them choose based on their internal dynamics, not just your pricing.

Model 1: Volume Subscription (Track A — Banks/DFIs)

Model 2: 50/50 Co-Pay (Track A or B)

Model 3: Full Sponsorship (Track B — Government)

Step 7.3 — The Partnership Proposal Meeting (Week 4–5)

Who: Biz Dev Lead + Leadership (Odela) | Institution’s decision-maker + champion + anyone else identified in the retrospective Format: In-person, no exceptions. This is a business negotiation. Duration: 60–90 minutes Conversion purpose: Walk in with three models. Walk out with one chosen model and a verbal commitment to contract.

Meeting agenda:

Opening:

“Thank you for making time for this. The pilot produced clear results: SPOT reduced processing time by [X%] while maintaining [accuracy metric], and your team rated the experience [Z]/10. Today I want to show you three ways to bring SPOT into production, and I’ll recommend one based on what we learned about your workflow. But first — this is your meeting. Is there anything specific you want to address before we dive in?”

When recommending a specific model:

Track A (Banks/DFIs):

“Based on your team’s workflow and the volume you shared during discovery, I’d recommend the Volume Subscription at [tier] pricing. Here’s the math: at [X profiles per month], your annual SPOT investment is RM [A]. Your current manual processing cost for the same volume is approximately RM [B] in analyst time alone. SPOT pays for itself within [X] months, and from month [X+1] forward, every profile processed is net savings.”

Track B (Government):

“For [Agency]‘s [specific program], I’d recommend the Full Sponsorship model. At RM [X] per participant, SPOT profiling is [small fraction]% of your total program cost per participant. In return, every SME in the program produces a standardized, verifiable readiness assessment. This means you can measure program impact with data, not anecdotes — which strengthens your case for continued or increased program funding.”

The critical moment — asking for verbal agreement:

“Before we move to contract, I want to make sure we’re aligned. Are we agreed that [Model X] is the right approach, at approximately [volume] profiles per [period], at [pricing]? If there’s anything that doesn’t feel right, let’s discuss it now.”

If they say yes → move immediately to contract (Step 7.5). Speed kills stalls. If they say “we need to discuss internally” → schedule a specific date for the decision (Step 7.4). If they say “we have concerns about [X]” → address it in the room, right now.

Step 7.4 — Handle the Stall (Week 4–5)

Who: Biz Dev Lead + Leadership Conversion purpose: Every day between “we want this” and a signed contract is a day the deal can die. Someone gets reassigned, a budget gets cut, a new priority emerges. Handle stalls with urgency, not pressure.

If they say “we need to discuss internally”:

“Absolutely. Can we schedule a follow-up for [specific date, within 7 days]? I want to be available for any questions that come up during your discussion. Would it help if I joined for part of the internal meeting to address questions directly?”

If they say “procurement needs to run their process”:

“Understood. Can you connect me with your procurement lead? I want to proactively prepare whatever they need — vendor registration forms, compliance certificates, pricing breakdowns. The faster we can comply with their process, the faster we can get started.”

If they say “budget needs to be approved for next quarter”:

“We can structure the contract with a future effective date. Sign now, and billing begins when your new budget cycle starts on [date]. This locks in the current pricing and ensures we’re ready to deploy on day one of the new quarter.”

If they say “legal has redlines”:

“Send the redlines today. Our legal team will respond within 3 business days. We’re committed to finding terms that work for both organizations.”

The 48-hour rule: After any decision meeting, if you haven’t received a clear next step within 48 hours, reach out:

“Hi [Name], following up on our partnership discussion. I want to make sure nothing is stuck. Is there anything I can do to help move things forward? I’m happy to [provide additional information / meet with additional stakeholders / adjust any terms we discussed].”

Step 7.5 — Contract to Signature in 7 Days (Week 5)

Who: Biz Dev Lead + Legal Conversion purpose: The contract is not a formality — it’s the final conversion gate. Make it the easiest procurement decision they’ve ever made.

Day 0: Verbally agree on model, pricing, key terms. Immediately say: “I’ll have the agreement in your inbox by [tomorrow / end of week].”

Day 1–2: Send the contract. Use their template if required, or ours with institution-specific details filled in.

Day 3–5: Follow up briefly every day: “Just checking if you had any questions about the agreement.” One sentence. No pressure, just visibility.

Day 5–7: If unsigned after 5 days, escalate gently: “I want to make sure we hit our target start date of [date]. Is there anything blocking the signature that I can help with?”

Contract must cover:

• Partnership model and pricing (per-profile or subscription)
• Volume commitments (minimum and maximum)
• Payment terms and invoicing schedule
• Contract duration and renewal terms
• SLA (uptime, processing time, support response time)
• Data handling, retention, and deletion policies
• Confidentiality and NDA provisions
• IP ownership (SPOT platform = Odela; generated reports = institution’s data)
• Termination clause with notice period
• Integration scope (if applicable — Phase 2)
• Training and onboarding commitments
• Reporting and business review cadence

Step 7.6 — From Signature to First Production Profile (Week 5–6)

Who: Product Lead + Biz Dev Lead Conversion purpose: Signing the contract is not the finish line — the first successful production profile is. If the handoff from pilot to production is messy, the relationship starts with disappointment instead of excitement.

Production setup (complete before training):

• Create production workspace (separate from pilot)
• Create production user accounts (may be larger than pilot team)
• Configure SSO if required
• Set up billing automation
• Configure custom report branding if included in contract

Training (2 sessions):

1. Officer training (2 hours): Hands-on — log in, upload documents, process a profile, review output, flag issues. Everyone processes at least one profile during training.
2. Executive briefing (30 min): How to read a SPOT report, what the numbers mean, what to look for. No hands-on — just interpretation.

Phased rollout (don’t go big-bang):

• Week 1–2: Pilot team on production (they already know the system — validates setup)
• Week 3–4: Expand to one additional department or branch
• Week 5–8: Full rollout to all intended users
• Week 9+: Optional integration scoping (Phase 2)

First 30 days — be hyper-available:

Step 7.7 — Ongoing Partnership (Month 2+)

Who: Biz Dev Lead (relationship) + Product Lead (technical) Conversion purpose: The goal is not just retention — it’s expansion. A satisfied institution becomes a reference, a co-marketing partner, and a gateway to other institutions.

Monthly business review:

• Usage metrics: profiles processed, active users, processing time trends
• Support tickets: volume, resolution time, recurring themes
• Upcoming SPOT features relevant to their use case
• Feedback and feature requests

Quarterly strategic review:

• Partnership KPIs vs. contract commitments
• Expansion opportunities (new departments, higher volume, different use cases)
• SPOT product roadmap share
• Next quarter priorities

Annual partnership renewal:

• Annual impact report: total profiles processed, time saved, ROI delivered
• Contract renewal and pricing discussion
• Goals for the next year
• Co-marketing opportunities (case study, joint press release, event speaking)

Gate 4 Milestones

• Pilot results report sent within 3 days of retrospective
• Partnership proposal meeting completed with all decision-makers
• Partnership model verbally agreed
• Contract sent within 48 hours of verbal agreement
• Contract signed within 7 days of verbal agreement
• Production environment provisioned
• Training completed for all user groups
• First production profile processed successfully
• Month 1 summary report delivered
• Partnership transitioned to ongoing management

Quick Reference: Track Differences

Timeline Summary

Week 1–2   ████████ Phase 1: Target Selection & Research
Week 2–4   ████████ Phase 2: Outreach & Introduction
Week 4–6   ████████ Phase 3: Discovery Meeting
           ╔══════════════════════════════════════════════╗
Week 6     ║ Phase 4: Demo & Proof of Value               ║
Week 6–8   ║ Phase 5: Sealing the Pilot (Gate 1)          ║
Week 8–10  ║ Phase 6: Building Conviction (Gates 2 & 3)   ║
Week 10–12 ║ Phase 7: Recommendation → Contract (Gate 4)  ║
           ╚══════════════════════════════════════════════╝

Post-demo conversion: 4–6 weeks from demo to signed contract.

Conversion Diagnostic

If a deal stalls, diagnose where it died: