
VANORI
AI-Based Local Information Curation Mobile App
An AI app that curates Korean community information in Vancouver, rebuilt on data it could legally use.
Data strategy redesigned 22 days before launch
See for more โI'm a strawberry matcha girl. The colors of Luna's Notes come from a strawberry matcha: two flavors that stay distinct in one glass. They are also how I work.
Matcha
Patience with messy information, careful analysis, and the steadiness to work through uncertainty.
Strawberry
Curiosity about people, a distinct point of view, and the confidence to question the first explanation.
The blend
Thoughtful analysis with enough imagination and empathy to make the result useful.
A calm, curious marketing analyst who finds overlooked signals and turns them into thoughtful action.
I am Marketing Analyst and Content Coordinator in Vancouver.
I find the signal in the messy parts of marketing: the customer feedback, campaign results, and overlooked details that reveal what people need and what could work better.
As a Marketing Analyst & Content Coordinator, I bring those insights into social media content, email marketing, branded design, SEO, segmentation, campaign strategy, and go-to-market execution. I use performance data to understand whatโs working and why, then turn those learnings into more relevant campaigns and measurable customer acquisition.
I start with the parts other people skip: the setting no one checked, the data that only exists in a handwritten log.
I segment the audience before writing a single line of copy, so the creative starts from a real situation.
Good analysis is half the job. The other half is catching a risk early and turning a number into something a decision maker can act on.
The problem, the analysis, and the decision behind each piece of work.
Scroll over the cards, swipe, or use the arrow keys
An AI powered mobile app that brings Vancouver's scattered Korean community information into one place. I was the team's data lead.
Data lead on team DooriDoori, 4 members. I owned API research, the database schema and the curation strategy.
Korean community information in Vancouver is split across KakaoTalk open chats, Instagram, Naver Cafe and Google Maps. Students, working holiday visa holders and new immigrants struggle to tell what is relevant. The original data plan also assumed sources the app wasn't allowed to use.
| Source | Decision | Why |
|---|---|---|
| FSQ OS Places | Base layer | Apache 2.0: permanent storage and AI use allowed |
| Google Places | Display only | Terms prohibit AI training and long term storage |
| Meetup API | Events | Only free API with city wide event discovery |
| City of Vancouver Open Data | New openings | Licence dates surface new spots before Google does |
| Threads oEmbed | Community voice | The only legal channel into Korean community social content |
| Yelp, TripAdvisor, Reddit | Excluded | Analysis bans, approval timelines or cost |
A redesigned data strategy and a curation workflow for the MVP :
a bulk import of 5,000 to 15,000 Vancouver places, 100 newly opened businesses, 50 community events, and 200 priority places tagged by hand.
Checking technical assumptions against legal limits early saves the build. The real work was turning compliance findings into a decision framework a non technical team could act on.
A mobile marketplace where local businesses sell empty off peak activity slots at a discount, and people nearby book them the same day. Built in 6 weeks as Team MVP.
Marketer on a team of 4 with 2 PMs and 1 Developer.
I ran the customer and business feedback survey, owned the go to market strategy and wrote the pitch content.
Spas, bike rentals, paddle clubs and yoga studios lose revenue every week to empty off peak slots, with no fast way to reach people who are free right now. Those people don't know what is open near them, so they stay home.
Two customer problems were stacked. Discovery came first: people didn't know what was open nearby. Price is what turned interest into action. One feed solves the first, and the discount solves the second.
Our Week 2 brief named business owners as the primary user.
Before Demo Day we changed it: a business will post deals all day,
but if no one books, the loop never starts.
| Aspect | Week 2 brief | Demo Day |
|---|---|---|
| Primary user | Business owners filling quiet windows | Customers looking for something to do now |
| Core action | Business posts a time limited deal | Customer discovers and books a nearby deal |
| Payment | Pay at venue | Pay in app, free cancellation until booking closes |
A working prototype with browse, filter, book, pay and QR code flow, demoed live on Demo Day. Deals were seeded for Vancouver and payment was simulated; real listings and Stripe are the next steps.
Validate the primary user before writing the design brief, not after. Next time I would run the two sided survey first and let it pick the side that has to move first.
โ64%
swing shift hours, 199 to 71.5
โ24.1%
revenue in the 12 to 1 PM slot
โ$4,601
estimated net per month
The cafรฉ cut swing shift hours to reduce labor cost.
I wanted to know whether the cut really saved money.
ยท Role Solo analyst, data collector and presenter
ยท Tools SQLite, Excel
ยท Data Oct 2025 to Feb 2026
Detailed transactions and supplier invoices weren't available, a POS migration had erased everything before October 2025, and shift and waste logs existed only on paper. Sales were monthly while inventory and shifts were daily, so measuring waste day by day was impossible.
| Option | Wage saving | Revenue impact | Net per month |
|---|---|---|---|
| Swing cut, actual | +$570 | โ$5,171 lunch decline | โ$4,601 |
| Bean order calibration | +$270 | $0 | +$270 |
The saved wages are dwarfed by the revenue decline that came with them. Monthly data can't prove causation, but the direction is clear: this is a demand problem, not a cost problem.
Acknowledging the limits of your data is not a weakness. It is the foundation of credible analysis.

