Skip to main content

The RFP that survives procurement.

Requirements that force evidence instead of brochures, and the questions most 2026 templates still get wrong.

Updated 7 min readMarkdown
The RFP that survives procurement.

On 12 October 2026 I issued an RFP with two lots, thirteen automatic exclusion grounds and a four-week proof of concept on anonymised production data. Shortlist on 13 November. Demos this week. The question is not which platform wins. It is: when a vendor answers "fully compliant" about a feature that does not exist, what is procurement actually buying?

What changed

  • 29 February 2024. Zalo's OpenAPI stopped returning full user fields to applications and webhooks outside Vietnam; foreign IPs get HTTP 200 and the fields vanish silently. My 2 October 2026 review of 22 platforms found no international CMP with a first-party Zalo connector. A gate on "native Zalo" filters out honest bidders first.
  • 16 April 2024 and 5 November 2024. Zalo folded its purpose taxonomy into three tags, then replaced the after-sales quota formula. Templates in circulation still ask about four tag-5 messages a month.
  • 1 January 2026. Law 91/2025/QH15 took effect; Decree 356/2025 replaced Decree 13/2023. Consent is per purpose, silence is not consent, and the burden of proof is the controller's. A subscription centre is not a consent ledger.
  • 19 August 2026. Decree 330/2026 took effect: penalties for cybersecurity and personal-data violations, including 30–50 million VND for processing data collected without consent. It is quoted as an anti-spam decree. It is not. The three-message and one-call caps sit in Decree 91/2020, Article 13.
  • 9 September 2026. The Ministry of Public Security was still taking comments on a draft spam decree. It is not issued, yet bidders are asked to certify compliance with it.
  • 13 November 2026. Shortlist notified, demos 16–20 November, POC 23 November–18 December, contract by 15 January 2027, go-live in Q2 2027.

The decision framework

Gates before scores. Thirteen conditions are pass/fail: frequency caps, consent and data-subject rights, statutory compliance, ISO/IEC 27001, a SOC 2 report, a POC on real anonymised data, holdouts, unrestricted export, a Vietnamese interface, a hard copy, a complete price schedule, no misrepresentation, acceptance of the bid terms. Fail one and you are out.

Then the weights — the published matrix, with the last four criteria merged into two rows.

Criterion Weight What "high" looks like
Functional fit: journeys, dynamic segments, cross-channel caps 20 A mid-flight edit to a paused journey, done live, that does not corrupt customer state
Regulatory and consent architecture 20 Per-purpose consent ledger with timestamp, channel and text, exportable; withdrawal effective in minutes
Zalo channel and Vietnam IP gateway 12 Named egress and webhook IPs in Vietnam, plus a monitor for silently dropped fields
Core-system integration 10 LOS, core lending and collections each with method, direction, frequency and effort in days
Three-year TCO and price mechanics 12 Every line filled, unit declared, overage formula and exclusions named
Reliability and operability in Vietnamese 16 99.5% monthly uptime with credits; correct diacritics in segments; named in-country support
Vendor viability, references and exit 10 Three contactable financial-services references in Vietnam; 24-month written roadmap; free export

Answers are coded full, partial, roadmap, none: 100, 50, 25, 0. Mandatory items count double. The threshold is 70/100, below which no bidder reaches the POC.

Options and trade-offs

Three ways to structure the buy; the product is the easy part.

Structure Strengths Risks Three-year cost shape
A. One contract, Zalo delivery bundled through the platform's local partner One SLA, one invoice Consent split across parties you did not choose; no lever if the channel fails Licence-led and flat, indexed to file size; per-message cost inside partner margin
B. Two lots, two contracts, a three-party data agreement Each layer replaceable without the other; two suppliers at renewal You own the integration contract and the incident bridge Front-loaded year one, then licence plus usage; 200–300 VND per ZNS message
C. Platform only; keep the incumbent aggregator Fastest to sign You inherit the integration backlog; a partner change becomes your project Lowest year-one services; maintenance sits in your budget

Option B comes from a finding I did not expect. The only vendor with a long, documented official Zalo partnership is a messaging platform, not a CMP, and it has a Vietnamese legal entity. The one international CMP with Zalo workflows in its documentation routes them through that same platform. Two layers is not a compromise; it is the shape of this market.

The numbers

  • ZNS lists at 200–300 VND per message before VAT. The first CTA button is free, later ones 100 VND, a permission request 400 VND. Timeouts (15 seconds for authentication, 7,200 for others) are not billed.
  • Public list prices that make bids comparable: $2,000 a month for 15,000 contacts on one enterprise suite, $100 a month for 5,000 profiles on a mid-market platform, overage $0.009 per profile.
  • Estimate, not quote: $30,000–80,000 a year for platform plus channel at the low end, $80,000–250,000 in the middle, $250,000 and above at the top.
  • Two billing models punish compliance work: one counts deleted profiles in a monthly high-water mark, so importing and then deleting to serve a data-subject request is billed twice; another bills profiles regardless of consent.
  • Cost carries 12% and scores as (lowest TCO ÷ bidder TCO) × 100; a bidder at twice the lowest TCO still takes 6 of 12 points. It breaks ties, it does not decide.
  • Terms worth more than a discount: a 7% cap on annual increases, 120-day validity, POC priced as a line, export at no charge.

What I would do in 30 / 60 / 90 days

30 days. Turn every requirement into an evidence form: which document proves it, what the POC tests, which answer is unacceptable. Search each bidder's full documentation index for the channel name — fourteen megabytes with zero hits is evidence, a partner logo is not. Correct the Zalo block to dated values. Keep the lots separate.

60 days. Write the POC script before the demos. Two use cases: abandoned eKYC recovery, and collections reminders capped across Zalo, SMS and calls. Ten acceptance metrics, including consent withdrawal inside five minutes, full field completeness through a Vietnam-IP gateway, a working holdout. Normalise prices to one unit. Three reference calls per vendor, same six questions, and ask for the person who ran the migration.

90 days. Sign a one-page decision record: criteria, weights, scores, rejected options and why. Then the terms that outlast price — a 12-month minimum at first signing, free exit and export, service credits, audit right, an increase cap, a three-party consent agreement for the Zalo flow. Go/no-go before the Q2 2027 date, not after.

What I would not do

  • I would not make a native Zalo connector pass/fail. No international platform has one; that gate selects for confidence, not capability.
  • I would not score analyst quadrants or review counts. One vendor's public review total went from 50 to 232 in one year; reprints are sponsored by the vendors in them; a platform missing from both 2025 quadrants still runs in production at a Vietnamese lender.
  • I would not accept technographic evidence. BuiltWith-class tools show a script on a page, not a contract.
  • I would not score a three-year TCO with blank lines or an undeclared unit. A blank line means "not included", and that is a reason to stop reading.

For the non-technical sponsor

Two decisions are yours, not the team's. First, we buy in two contracts, so the messaging channel can be replaced without replacing the platform. Second, the cheapest bid will not win: cost is 12% of the score. What we are buying is evidence: four weeks on our own data, under NDA, before anyone signs.

Sources

Personal views. Client and employer details are anonymised. Figures are third-party estimates, not vendor quotes, and are dated November 2026.

No comments yet. Be the first to comment.