Optimism was loud in Manila, but the corridor chats revealed what founders, funds, and operators must fix next if momentum is going to translate into durable outcomes.

Manila was buzzing. Echelon Philippines 2025 felt like the ecosystem gathering for a status check — founders comparing scars, investors calibrating theses, operators trading what actually works. I’ve built across Southeast Asia for over a decade (including an early chapter in the Philippines), and this trip felt different: Less “pitch theatre”, more “show me the workflow”. That’s a good thing.

Below is the candid version of what I heard on and off stage — the good, the bad, the ugly — and the build: Practical moves teams can ship on Monday.

The good: Speed, hunger, and a wider circle of builders

Operator energy over optics. Conversations tilted from “raising” to unit economics, funnel discipline, and hiring for the next 12 months. The strongest teams ran lean, instrumented funnels, and had crisp answers to: What breaks at 3×? What breaks at 10×?
Cross-pollination is real. Manila isn’t building in a vacuum. Founders are cross-learning with Singapore, Jakarta, KL, and Ho Chi Minh City — borrowing playbooks, sharing mistakes, even co-selling. Markets differ; operational primitives rhyme.
Enablers are levelling up. Incubators and founder networks were visible and useful. One example: Brainsparks, whose founder-first ethos (mentoring, coaching, pragmatic incubation) showed up in the quality of questions: “What’s the minimum process that unlocks the next milestone?” Not “How do I look investable?” That posture compounds.

Also Read: Exhibit smart, spend lean: Your Start Up Booth at Echelon 2026

The bad: Fragile backends and narrative debt

“Automation later” thinking. Too many teams treat automation as a nice-to-have once growth arrives. Reality: If CRM hygiene and lifecycle messaging aren’t instrumented at the seed/angel stage, CAC balloons when you step on paid. You don’t need an enterprise stack — just one you will maintain.
Narrative debt. Beautiful one-liners are undermined when product and pricing say otherwise. Rewrite promises in terms of current capabilities and a near-term roadmap. Credibility is an asset; don’t mortgage it.
Talent is spread too thin. Multi-hyphenates are common, but diffusion kills excellence. Early teams need focus with force. If everyone is “part-time PMM + part-time growth + part-time product,” nobody owns the critical metric.

The ugly: AI theatre, data spaghetti, and founder burnout

AI theatre. “Agents” on top of leaky workflows are expensive theatre. The question isn’t “Do you use AI?” — it’s “Can a new teammate repeat your process tomorrow with the same quality?” If humans can’t, AI won’t. Codify first; automate second.
Data spaghetti. Disconnected landing pages, orphaned forms, zombie lists, and a retargeting bill that makes everyone nervous. Pick one funnel spine, one CRM of record, and a primary messaging channel. Everything else is an integration, not a parallel universe.
Burnout disguised as hustle. The grind is romanticised until a key decision gets made at 3am and costs a quarter. Teams that last are boringly consistent: Weekly metrics, written decisions, recovery in the calendar. Burnout isn’t a badge; it’s a bug.

Also Read: Echelon Singapore 2025: 10 powerful sessions now available to stream

So, what now? A practical build for PH founders (and frankly, anyone)

Codify before you “AI”. Write the workflow — lead capture → qualification → demo → close → onboarding → success for each stage: Input, definition of done, owner, and SLA. Add AI once the process is explicit.
One spine, many ribs. Choose one system as your spine (CRM/marketing automation). Every page, form, and message connects to it. Add ribs — analytics, billing, support – deliberately.
Tight loops over long plans. Replace quarterly big ideas with two-week operating loops: Ship a test (offer/pricing page/webinar/outbound list), then instrument, review, keep what compounds, kill what doesn’t.
Guardrail the story. Positioning = promise × proof. Keep both current. If the product doesn’t yet do X, don’t imply it. If you have proof, surface it above the fold: Retention, cohort revenue, case studies, or what failed and how you fixed it.
Community as distribution. Treat the community as pre-and post-sales infrastructure where you educate, qualify, and retain. Partner with credible locals (e.g., Brainsparks or vertical guilds) and show up with useful specificity — teach the spreadsheet, not the slogan.

What Echelon got right (and where to go further)

Right: The agenda leaned into operator-level talks. Panels moved beyond “AI will change everything” to “Here’s what we automated; here’s what stays manual; here’s the ROI.” That honesty drives real progress.
Room to grow: An explicit Failure Track — short, surgical post-mortems from teams who tried, measured, and pivoted — would accelerate regional learning and normalise documented failure.

A personal note on the Philippines

A decade ago, I was the scrappy founder in Manila, shipping experiments and learning the hard way. Coming back as a speaker is surreal, but the emotion underneath is simple: This market is capable of world-class outcomes when ambition meets boring excellence.

The next chapter won’t be written by the loudest booth or flashiest deck; it’ll belong to teams who can answer, calmly and repeatedly: “What did we ship this week that moved the metric?”

That’s the work. And it’s enough.

—

Editor’s note: e27 aims to foster thought leadership by publishing views from the community. Share your opinion by submitting an article, video, podcast, or infographic.

Enjoyed this read? Don’t miss out on the next insight. Join our WhatsApp channel for real-time drops.

Image courtesy: Canva Pro

The post What Echelon Philippines taught me about building real moats in 2025 appeared first on e27.