You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Market managers can onboard vendors by sharing an SMS or WhatsApp link instead of requiring an app download. The vendor taps the link, fills out a lightweight mobile web form (name, photo, product list), and their profile is created in the system. The vendor can optionally download the full app later for check-in and status features. This dramatically reduces the friction of the hardest growth lever: vendor acquisition.
Market Signal
WhatsApp Business API adoption for small vendor onboarding is proven — The Little Farm Co began at a farmers market and used WhatsApp to scale vendor engagement. Magalu saw registration rates climb after moving onboarding from email to WhatsApp. SMS open rates are 98% vs 20% for email. Twilio SMS costs ~$0.0079/message; WhatsApp Business API is free for the first 1,000 conversations/month.
User Signal
The PRD explicitly identifies "app-install friction slows early customer adoption" as a distribution risk (with vendor adoption being even harder). The project context states target vendors are "app-averse." The existing SMS check-in idea (#71) addresses day-of check-in but not the initial onboarding step — vendors must first exist in the system before they can check in via any channel.
Technical Opportunity
The Go backend can expose a lightweight vendor-creation endpoint consumed by a mobile-optimized web form (simple HTML served from Cloud Run). Twilio or WhatsApp Business API integration sends the onboarding link. The manager sends an invite from their dashboard → vendor receives a link → fills a micro-form → vendor record is created in Cloud SQL with minimal profile data. Progressive enhancement: the vendor can later claim their profile by downloading the app and linking via Firebase Auth.
Assessment
Dimension
Score
Rationale
Feasibility
med
Requires Twilio/WhatsApp API integration and a lightweight web form outside the RN app — manageable but adds a new surface
Impact
high
Vendor acquisition is the hardest growth lever; reducing onboarding friction directly increases supply-side participation
Urgency
high
Needed before or during pilot launch — vendor sign-up friction is a day-one blocker
Adversarial Review
Strongest objection: This creates a "headless" vendor profile that can't check in or manage their own status without the app, fragmenting the user experience.
Rebuttal: A headless profile is still valuable — it appears in the market directory, the manager can check them in via FR20a (manager-on-behalf check-in), and the vendor gains followers passively. When the vendor sees follower growth, the incentive to download the app is organic. This is progressive onboarding, matching the exception-first philosophy of the entire product.
Suggested Next Step
Design the lightweight vendor onboarding form (5 fields max: name, photo, product categories, market association, phone number). Evaluate Twilio SMS vs WhatsApp Business API for the invite delivery channel. Define the "headless profile" data model and the later app-claim flow.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Summary
Market managers can onboard vendors by sharing an SMS or WhatsApp link instead of requiring an app download. The vendor taps the link, fills out a lightweight mobile web form (name, photo, product list), and their profile is created in the system. The vendor can optionally download the full app later for check-in and status features. This dramatically reduces the friction of the hardest growth lever: vendor acquisition.
Market Signal
WhatsApp Business API adoption for small vendor onboarding is proven — The Little Farm Co began at a farmers market and used WhatsApp to scale vendor engagement. Magalu saw registration rates climb after moving onboarding from email to WhatsApp. SMS open rates are 98% vs 20% for email. Twilio SMS costs ~$0.0079/message; WhatsApp Business API is free for the first 1,000 conversations/month.
User Signal
The PRD explicitly identifies "app-install friction slows early customer adoption" as a distribution risk (with vendor adoption being even harder). The project context states target vendors are "app-averse." The existing SMS check-in idea (#71) addresses day-of check-in but not the initial onboarding step — vendors must first exist in the system before they can check in via any channel.
Technical Opportunity
The Go backend can expose a lightweight vendor-creation endpoint consumed by a mobile-optimized web form (simple HTML served from Cloud Run). Twilio or WhatsApp Business API integration sends the onboarding link. The manager sends an invite from their dashboard → vendor receives a link → fills a micro-form → vendor record is created in Cloud SQL with minimal profile data. Progressive enhancement: the vendor can later claim their profile by downloading the app and linking via Firebase Auth.
Assessment
Adversarial Review
Strongest objection: This creates a "headless" vendor profile that can't check in or manage their own status without the app, fragmenting the user experience.
Rebuttal: A headless profile is still valuable — it appears in the market directory, the manager can check them in via FR20a (manager-on-behalf check-in), and the vendor gains followers passively. When the vendor sees follower growth, the incentive to download the app is organic. This is progressive onboarding, matching the exception-first philosophy of the entire product.
Suggested Next Step
Design the lightweight vendor onboarding form (5 fields max: name, photo, product categories, market association, phone number). Evaluate Twilio SMS vs WhatsApp Business API for the invite delivery channel. Define the "headless profile" data model and the later app-claim flow.
All reactions