Before You Build
Web AppShut Down

Eloquis

Eloquis was a bootstrapped SaaS for mobile-app personalization. It lost about $20,000 without revenue because the team built for a plausible trend before proving that mobile teams felt personalization as an urgent buying need, that agencies were the right buyer, or that outreach could reach the market.

View original story

Product snapshot

What it was

Eloquis was a bootstrapped SaaS for adding personalization to mobile apps.

Who it was for

mobile app developersmobile development agenciesapp product teams

Problem / value

It aimed to help mobile teams make app experiences feel more tailored and less transactional for end users.

Core workflow

Mobile teams would add personalization behavior to their apps so users could receive more tailored in-app experiences.

Core dependency

The product depended on mobile teams seeing personalization as urgent enough to adopt and on the team finding a channel that could reach those buyers.

Product form

web appSaaSplanned API/SDK direction

Pricing model

No public pricing data found; the founder says the product achieved no revenue.

Competitors or alternatives

mobile analytics and engagement SDKsapp personalization toolsin-house mobile development workdeveloper-platform ecosystems

What happened

Summary

Eloquis was a mobile-app personalization SaaS built around the idea that app experiences should feel less transactional.

Outcome

The project shut down without revenue after the team found that personalization was not urgent enough for the market they targeted and that outreach did not create a reliable channel.

Core risk

Mobile personalization demand not urgent

Shutdown reason

The founder says the team assumed demand for mobile-app personalization, targeted the wrong customer segment, faced a crowded mobile software category, and had weak results from outreach.

Timeline

  • The founder described Eloquis as a bootstrapped SaaS.
  • The team tried email and LinkedIn outreach to mobile developer groups.
  • The founder reported losing about $20,000 and achieving no revenue.

Before you build

Why it matters

Mobile teams may agree that personalization sounds useful, but they still need a clear reason to adopt another tool now. Before building, prove who owns the problem, how often they feel it, and what channel can reliably reach them.

Primary check

Validate the buyer segment, urgency, and reachable channel before building mobile personalization features.

Checklist

  • Which mobile-app metric gets better enough that a buyer would pay this quarter?
  • Is the buyer the agency building the app, the product team owning retention, or someone else?
  • Can you get replies from the exact buyer segment without relying on a broad developer audience?
  • What evidence would prove personalization is urgent rather than merely attractive?
  • Identify who owns the personalization problem inside the mobile team and who controls budget.
  • Test whether buyers will pay for a small manual or prototype version before investing in feature depth.
  • Run channel tests with the exact buyer segment instead of broad mobile developer outreach.
  • Check whether the product name and keywords can be found by the right buyers.

Relevant if

  • You are adapting a web SaaS trend into mobile apps, developer tools, or another adjacent market.
  • Your first target segment is an agency, consultant, or service provider rather than the company that owns the end-user experience.
  • Your acquisition plan depends on cold email, LinkedIn, communities, or SEO before you have proof those channels reach buyers.

Less relevant if

  • Your buyers already ask for this workflow by name and have budget for it now.
  • You are building for an internal mobile team where adoption is mandated and distribution is not the main risk.

Pre-build tests

  • Interview mobile teams about a recent personalization decision and ask what they already tried.
  • Sell a narrow paid pilot that improves one measurable app flow before building a platform.
  • Run a small outreach test to each possible buyer segment and compare reply quality, not just interest.
  • Search-test the product name and category terms before committing to brand and SEO direction.

Transferable lessons

  • Validate urgency before building a full SaaS around a nice-to-have improvement.
  • Do not assume a web personalization trend automatically transfers to mobile apps.
  • Choose a name and discovery strategy that help buyers find the product instead of creating search confusion.