Our starting point
Small audience, limited activity, no meaningful revenue yet. These are founder-reported conditions, not an analytics audit.
Đà Lạt · 10 September 2026
A conversation. A possibility. A first step.
A living workshop for Dalat.app. Find what gives you energy, imagine something bigger, and leave with one small experiment you can own.
Unlisted meeting canvas · Anyone with this link can read it. Keep private contacts and sensitive notes elsewhere.
Everything happening in Đà Lạt. The people creating it. The moments worth keeping. A discovery layer before an event, a place to participate during it, and a living memory afterward.
Small audience, limited activity, no meaningful revenue yet. These are founder-reported conditions, not an analytics audit.
Product infrastructure, multilingual access, automation, and fast experiments. Capital can support learning; attention is scarcer.
Organizers do not yet instinctively publish here. Zan still does too much. Twelve languages are infrastructure, not twelve active audiences.
Repository inspection found event pages, Moments galleries and professional uploads, venue and organizer profiles, RSVP/check-in flows, and organizer tools. Availability is not evidence of adoption.
Phuong photographed the September 8 AI workshop, then uploaded the photos herself. That was the moment the product clicked. Could participation turn into a reason to return?
HYPOTHESIS TO TEST · NOT PROVEN
Test the link: after a consent-based gallery message, do attendees return—and does an organizer publish their next event? A photo view alone is not retention.
A meaningful evening should not disappear into a chat thread or a forgotten Drive folder. Connect its date, place, organizer, story and media. Include attendees only with appropriate consent. Over years, small moments become the memory of a city.
Imagine: “On this day in Đà Lạt…” · A venue’s history · A community growing through the years. Future concepts, not current promises.
HYPOTHESIS TO TEST · NOT PROVEN
More useful events → more attendees → a reason for organizers to publish again.
More history → more sharing and search discovery → new people → new organizers.
Events link to a venue → a richer profile → discovery → more relevant events. A community node, not just a map pin.
Publishing → reusable history and followers → next event → a more valuable profile. Earn repeat use; keep sharing and exit easy.
Trusted relationships → organizers try the app → a stronger network → more opportunities → deeper city knowledge.
Upcoming and past events, real community photos, atmosphere, vegetarian options, laptop and language friendliness, accessibility, capacity, noise, groups, outdoor seating, parking and bicycles. Validate these details with the venue; do not invent ratings.
Organizer bio, identity verification where available, organizations, event history, media, communities, categories, languages and intentional contact links. Following, reputation and reviews need careful design; paid promotion must never buy a rating.
Choose by energy, not by a job title. Tap a response on any card; tap it again to clear. We are exploring strengths—not offering a salary, equity, partnership or permanent position.
0 / 15 roles explored
Find one worthwhile event we have missed.
Help someone publish their own next event.
Own the run sheet and resolve ordinary issues.
Work from a brief and deliver a curated story.
Bring the right photo, video and design people together.
Help recurring attendees feel connected.
Build useful relationships with venues and businesses.
Make a complete, accurate, findable memory.
Turn a local happening into a story people care about.
Find what makes an organizer come back.
Turn messy messages into drafts humans can verify.
Know who actually makes things happen.
Shape one repeatable gathering with a clear purpose.
Explore sponsors after value is demonstrated.
Represent the app honestly in local communities.
One project → a repeatable responsibility → organizer relationships → perhaps an area of leadership. A path to explore, not a promised promotion.
Pick a question that feels alive. Follow the story. We do not need to finish a questionnaire.
If money were not the immediate problem, what would you enjoy building? Creating, organizing, selling, connecting, leading, photography, media, solving chaos—or something else? In public or behind the scenes?
What did YOU own? What went wrong? What did you solve yourself, and where did you need help? What would you change? Who hired you, and how were you paid?
Friends, freelancers, employees or partners? Who can reliably do photo, video, design, social media, PR, promotion, MC, DJ or production? Which work have you delivered together?
Which organizers and venues do you personally know? What do they run, how often, and what is next? How strong is the relationship? Keep names and private contact details in a separate, agreed place.
Choose a result you could deliver without daily supervision. What would you decide yourself? When would you ask for help? What would you like AI to handle?
What would you like to learn? What does financial independence mean to you? Freelance flexibility, an agency, your own event/media company, leadership, a salary, project fees, commissions—or a mix?
Zan already hosts technology, AI and builder gatherings. Use one as a controlled sandbox for publishing, preparation, check-in, a clear media brief, a curated archive and consent-based follow-up. Agree a project scope and compensation separately before work begins.
INTERNAL VALIDATION ≠ MARKET VALIDATION. Zan can prove a workflow works. An independent organizer must prove someone else wants it.
The minimal-Zan test
≤ 30 minSupervision per week for the agreed responsibility. Log setup and rescue time too. Success means correct information, an approved media brief, a complete archive, ordinary problems resolved, and a checklist someone else can reuse.
Choose a starting point together. Level 2 is a useful first experiment; Level 5 is not an expectation today. Ownership includes decision rights and a clear escalation path.
Recommended: map the people who make Đà Lạt happen—and test one handoff. Start with five organizers and five venues Phuong already knows, not a city-wide directory.
Record event type, frequency, next known event and relationship strength. Use a private, agreed contact sheet. Unknown is an acceptable answer.
Have three permission-based conversations. Ask about discovery, publishing, photo delivery and next-event follow-up. No hard sell.
Invite one interested organizer to create or correct their own page. Only publish verified details with permission. If no event is ready, validate a draft and record why.
Bring one repeatable checklist, three concrete pain points, the handoff result and a log of Zan’s time. Decide continue, change or stop.
How do people find you? Where do you post? What takes too much time? What do you already pay for: design, photography, promotion, guests or coordination? Where do photos go? How do attendees find them and hear about the next event? Would you maintain a page if it took two minutes? Would multilingual discovery help? What would make this worth remembering?
“Party Friday 7pm, acoustic music, 100k, message me.”
Draft: acoustic evening · 19:00 · quoted price: 100k (confirm currency and inclusions). Still missing: exact calendar date, venue/address, organizer, booking contact and photo permission. Never guess these.
Workflow concept, not a connected inbox on this page. AI can prepare title, description, categories, VI/EN copy, other translations, social captions, SEO and image suggestions. Each collaborator uses their own authorized access; no shared personal subscriptions.
Keep basic publishing, profiles, discovery, sharing, photos and basic RSVP accessible while habits form. This is a strategic direction, not a new pricing promise. Optional services can earn money before a large audience exists.
Traction, habit and relationships. Test a tightly scoped photo, coordination or media package. Charge for a delivered result; track costs and founder time. Subsidies should buy evidence.
Only after repeat use: organizer subscriptions, automation, analytics, CRM, attendee messaging and enhanced profiles. Require a real pain point and willingness to pay.
Ticket or booking fees, commissions and paid upgrades only when transactions justify operations and compliance. No payment implementation here.
Clearly labeled sponsored events, venues, guides and tourism campaigns only after measurable relevant reach. Never sell imaginary exposure.
Organizer operating system, local business software, hospitality integrations, city partnerships, APIs or reusable city infrastructure. Evidence before expansion.
Page setup, information cleanup, multilingual copy, graphics, posters, teasers, social assets, consultation, venue coordination and RSVP preparation.
Check-in, guests, photography, video, livestream, interviews, MC, production, stage coordination and sponsor activation.
Curated gallery, highlights, recap, consent-based follow-up, testimonials, clips, next-event announcement, archive and useful analytics.
Imagine hundreds or thousands of events indexed and remembered, organizers maintaining their pages, richer venues and recurring communities. Multilingual discovery earns real use. A small team and mostly automated ingestion reduce Zan’s work. Phuong may own an operational area if the collaboration works. Monetization experiments produce evidence.
“Where is live jazz?” “Where do builders meet?” “What happened at last year’s festival?” Events, people, venues, reviews, media and recommendations connect. An organizer operating system or AI concierge might become useful. Expansion only if the local model works.
What if each city had a living graph of people, places, events, communities, businesses, stories and relationships? A local digital nervous system that helps answer what is happening, who to meet and what changed over time. Đà Lạt could be the prototype.
Define “active”: an organizer publishes a verified event, then another within their normal event cycle. Seven days can test a handoff, not establish a repeat rate. Record eligible organizers and the follow-up window before comparing.
Also track conversations → onboarding → self-published events; repeat rate; archive/media completeness; consent-based gallery returns and shares; repeat attendance; organizer satisfaction and referrals; venues validated; autonomous tasks; turnaround; accuracy. Record counts and denominators. Raw account totals are not the goal.
No fake traction, guaranteed reach or unagreed salary, equity, partnership or title.
No spam or forced moves from Facebook, Zalo or WhatsApp. Respect event visibility, photo consent, removal requests and private contact details.
Separate sponsorship from organic reviews. Use individual authorized AI accounts. Keep sensitive notes off this link and shared devices.
One experiment, clear decision rights, defined escalation. Ten organizers publishing again matter more than a hundred events entered by Zan. Do not build everything.
Not a roadmap. Park possibilities here so today’s experiment stays small. Existing features may overlap; try them before building more.
The repository already includes Moments, organizer tools and venue profiles. Test the September 8 archive and an organizer handoff before adding a dashboard.
Hypothesis: Phuong’s strongest contribution may be organizer trust and coordination. Three specific conversations tell us more than a broad claim to a media network.
Zan’s event can validate delivery. An independent organizer doing the next step without rescue is stronger evidence of demand.
At low traction, a curated archive or reliable coordination has clearer value than promoted placement. Hypothesis: scoped services are the earliest plausible revenue. Track margin and Zan’s time.
Three conversations, one attempted self-service handoff, one checklist, at most 30 minutes of Zan’s supervision. If nobody wants the handoff, preserve that result and change the offer.
The workshop uses its own subdomain so public usernames remain available. Keep this unlisted canvas temporary; use authenticated access if confidential negotiations become necessary.
We do not need to know Phuong’s permanent role today. Find one strength, give it room, learn from a real result.
Saved only in this browser, shared across English and Vietnamese. Not synced or sent to the team. Avoid sensitive notes. Clear after using a shared device.
…