It Started With a Tita's Notebook
Every Filipino family has that one Tita — the one who organizes everything. She's the one who knows whose turn it is to bring lechon to the reunion, who keeps the family birthday calendar, and who somehow remembers your anniversary before you do.
Our Tita was also a part-time wedding planner. Not the glamorous kind you see on Pinterest — the practical, pen-and-notebook kind who tracked budgets on graph paper and kept vendor contacts in a battered Nokia phone. When she passed the notebook to us and said, 'Can you put this online so I don't lose it again?', we laughed. Then we looked at the 200+ pages of meticulously organized wedding checklists, vendor lists, budget trackers, and seating arrangements — and stopped laughing.
That notebook became the blueprint for WedPlanner.ph.
The Problem Nobody Was Solving (Properly)
The Philippines has one of the most vibrant wedding industries in Southeast Asia. Over 400,000 marriages are registered annually, and the average Filipino wedding costs between ₱300,000 to ₱800,000 — a significant investment for families where weddings are community events, not just couple's events.
Yet most couples were still planning their weddings with:
- Excel spreadsheets that broke when you sneezed at them
- Facebook groups full of vendor recommendations with no way to verify them
- Google Docs shared between 5 family members who kept editing the same cell
- That one cousin who 'has a spreadsheet for everything' but never shares it on time The existing tools? Either they were built for Western weddings (no ninong and ninang tracking, no despedida de soltera timeline, no abay coordinator notes) or they were expensive SaaS products priced in USD — way out of reach for the average Filipino couple.
We saw the gap. Tita's notebook had the domain knowledge. We had the technical chops. The question was: could we turn a graph-paper system into a product?
Building the MVP — Tita's Checklist Goes Digital
We gave ourselves 8 weeks. Not because of some lean startup methodology — because wedding season was approaching and we wanted to test with real couples planning real weddings.
Week 1-2: Extracting the Domain Knowledge
The first two weeks weren't coding. They were reading. We sat with Tita and went through every page of that notebook. What emerged was a surprisingly sophisticated planning system:
- Phase-based timeline: 12 months out, 6 months out, 3 months out, 1 month out, week-of, day-of
- Role-based task assignment: tasks weren't just 'to-do' — they were assigned to specific people (the couple, the parents, the coordinator, the abay)
- Budget envelope system: not just a total budget, but per-category envelopes with priority weighting
- Vendor tracking with ratings: not just contacts, but notes on reliability, pricing tiers, and whether they showed up on time This was domain gold. No Western wedding app had this structure because Western weddings don't have ninongs and ninangs as sponsors, or despedida de soltera as a pre-wedding event, or the concept of abay (entourage) with specific duties.
Week 3-6: Building the Core
We chose a stack we knew cold: Next.js for the frontend, Supabase for the database and auth, and TailwindCSS for styling. We went with Supabase specifically because we needed real-time collaboration — when the bride's mother and the wedding coordinator are both editing the seating chart simultaneously, you need WebSocket sync, not polling.
The core features we shipped in the MVP:
- Interactive wedding checklist — Tita's phase-based timeline, digitized and assignable to team members
- Budget tracker with envelopes — per-category budgets with visual progress bars and overspend alerts
- Guest list manager — with side-of-family tagging, sponsor tracking, and table assignment
- Vendor directory — seeded with Tita's contacts, searchable by category, location, and budget tier
- Entourage manager — because tracking 20+ abay members with their roles, attire, and contact info is its own logistics system One of the hardest technical challenges wasn't the features — it was the offline-first requirement. Filipino weddings happen in venues with spotty WiFi (beaches, provincial churches, garden receptions). The coordinator needs to check off tasks on the day-of without a connection. We implemented a local-first sync layer using IndexedDB and a queue-based conflict resolution system. Not glamorous, but it was the difference between a tool people use and a tool people abandon.
Week 7-8: Polish, Test, Panic
We ran the MVP through 3 test couples — Tita's actual clients who were in the 3-month-out phase of planning. The feedback was immediate and brutal:
- 'Why can't I add my ninong as a sponsor in the guest list?' — Fixed in 2 hours. We had hardcoded 'bride' and 'groom' sides only.
- 'The budget tracker doesn't let me mark something as padala (gifted by family)' — Added a 'sponsored' flag to budget items.
- 'Can the checklist send reminders to my coordinator?' — Not in the MVP, but it became our #1 feature request. Each piece of feedback confirmed what we suspected: the product was valuable because it understood Filipino wedding culture. The localization wasn't a feature — it was the foundation.
Getting First Users — The Philippine Way
Here's where most startup playbooks would say 'launch on Product Hunt' or 'post on Hacker News.' We did neither. Instead, we went where Filipino brides actually hang out:
Facebook Wedding Groups
The Philippines runs on Facebook. There are dozens of active wedding planning groups with tens of thousands of members each — Wedding Planning Philippines, Brides-to-be PH, Kasal Tipid Tips. We didn't spam. We participated. We answered questions about budget allocation. We shared Tita's checklist as a free PDF download (with a WedPlanner.ph watermark, naturally). When people asked 'is there an app for this?', someone else — not us — would recommend WedPlanner.ph.
That organic word-of-mouth brought us our first 200 users in 3 weeks. Zero ad spend.
Tita's Network
Tita had been planning weddings for 15 years. She had a WhatsApp group with 40+ past brides. We sent them a personal message (not a broadcast) asking them to try the platform and share it with any engaged friends. 12 of them became active users. 7 referred at least one new couple. The LTV of a referred user in our early data was 3.2x higher than a cold signup — Tita's network wasn't just user acquisition, it was quality user acquisition.
Wedding Expos (Pop-up Strategy)
We couldn't afford a booth at the big wedding expos (₱50,000+ for a 2x2 meter table). So we did pop-ups. We showed up at the free community wedding fairs organized by local government units and churches. We brought a tablet, a WiFi hotspot, and Tita. People could sign up on the spot, and Tita would personally walk them through the checklist. The conversion rate at these events was 40% — compared to 8% from online signups. The lesson: in the Philippines, trust is built face-to-face.
What We Learned Building a SaaS for the Philippine Market
1. Localization > Features
We spent zero time on fancy features in the MVP. We spent enormous time on getting the Filipino wedding context right. The despedida de soltera timeline. The ninong/ninang sponsor system. The abay hierarchy. These aren't 'features' — they're the reason the product exists. A Western wedding app with 100 features but no padala tracking is useless to a Filipino couple.
2. Mobile-First Isn't Optional
92% of our early users accessed WedPlanner.ph from their phones. Not surprising — the Philippines is a mobile-first country with one of the highest mobile internet penetration rates in Southeast Asia. But 'mobile-first' isn't just responsive design. It's:
- Data-light pages (many users on prepaid data)
- SMS reminders (not everyone has push notifications enabled)
- Touch-optimized interactions (drag-and-drop seating charts don't work well on a 5-inch screen)
- Offline sync for day-of coordination
3. Pricing for the Philippine Market
We launched with a freemium model: free for the core checklist and guest list, ₱299/month for the full suite (budget tracker, vendor directory, coordinator dashboard). That's about $5 USD — a fraction of what Western wedding planning apps charge, but aligned with what Filipino couples are willing to pay for a digital tool. The key insight: pricing isn't about what the product is worth in absolute terms, it's about what the market can absorb relative to the total wedding budget. ₱299/month against a ₱500,000 wedding budget feels negligible. ₱2,000/month feels like a line item.
4. Community Is the Best Marketing
Our CAC (customer acquisition cost) for the first 500 users was effectively ₱0 — just time and Tita's network. Every paid channel we tested (Facebook ads, Google Ads, influencer posts) had higher CAC and lower retention than organic community referrals. In a market where personal recommendations carry more weight than branded ads, investing in community presence pays compounding dividends.
What's Next
WedPlanner.ph is live, growing, and serving couples across the Philippines. We're now working on:
- Vendor marketplace: letting couples book vendors directly through the platform
- AI-powered budget optimization: suggesting reallocations based on the couple's priorities
- Multi-language support: Tagalog and Cebuano interfaces, because not every Filipino couple plans their wedding in English The notebook is still on Tita's desk. But now, the knowledge inside it lives in a product that any Filipino couple can access — whether they're planning a grand cathedral wedding in Manila or a beach ceremony in Palawan.
If you're building a SaaS product for a local market, here's our advice: find your Tita. Find the person with the domain knowledge that no competitor has. Digitize what they know. Build for the culture, not against it. And when in doubt, ask: would this work at a wedding in probinsya with spotty WiFi and 300 guests? If the answer is yes, you're on the right track.
Check out WedPlanner.ph to see what we built, browse our wedding checklist templates, or explore budget planning tools designed for Filipino weddings.
Top comments (0)