Aspasia: Bad timing

Aspasia was a fully built, deployed Instagram project management platform designed specifically for marketing agencies. It died because the founder ran out of personal runway and took a full-time job, listing the asset for sale after a sales strategy targeting enterprise agencies failed to convert any meaningful revenue.

The Product: Instagram Project Management for Agencies

Aspasia launched as a vertical SaaS tool built to manage Instagram workflows for marketing agencies. The stack was modern and boring in the right ways: Next.js on the frontend, hosted on Render with Cloudflare in front, and Stripe handling billing. There was no mobile app, no AI layer, and no blockchain component — just a focused web application trying to solve the operational chaos of scheduling, approvals, and content pipelines for teams running multiple client accounts.

The product was feature-complete enough to demo and deploy. It handled the core loop: content calendars, client approval flows, asset libraries, and publishing schedules tailored to Instagram’s format requirements. For an agency juggling ten clients, this replaces a messy combination of Asana, Google Drive, and Slack threads. For a solo freelancer, it is overkill. The architecture supported multi-tenancy and role-based access, meaning it was built for teams, not individuals.

The problem was not the code. The product worked. The problem was who the founder tried to sell it to.

The Sales Motion: Chasing Dragon Fruit and Missing the Market

The founder’s biggest mistake was targeting "big market agencies like Dragon Fruit etc." — established shops with dedicated operations leads, procurement processes, and existing vendor contracts. These organizations do not buy project management software from a solo founder with nine users. They buy from vendors with SOC 2 compliance, dedicated support SLAs, and reference accounts.

The lesson recorded in the post-mortem reads: "Go after Marketing Managers from big studios not worth your time chasing small ones." The phrasing is blunt. It means the founder spent the limited sales bandwidth pitching Marketing Managers at large studios — people who cannot sign a check without legal review — while ignoring the thousands of smaller agencies (5–50 people) that buy on a credit card and onboard themselves.

Enterprise sales cycles run six to eighteen months. Aspasia had roughly zero months of runway. Every week spent preparing a deck for a Director of Operations at a 200-person agency was a week not spent onboarding three 10-person shops that would have paid $200/month each. The founder learned this too late: the addressable market for a pre-revenue, single-founder tool is the long tail of agencies that feel the pain acutely and have the autonomy to solve it today.

The Runway Reality: Why Bad Timing Meant Zero Timing

The official cause of death is listed as "bad timing." In practice, this means the founder needed emergency cash and took a job. There was no funding round, no angel check, no revenue bridge. The business was a side project that required full-time attention to sell, but the founder could not afford to give it that attention without a salary.

This is the most common death spiral for bootstrapped B2B SaaS. The product takes six months to build. The sales motion takes twelve months to ramp. The founder has three months of savings. When the savings run out, the product is "fully built and deployed" but the company does not exist.

Aspasia reached nine users. That number is not a metric of traction; it is a metric of effort. Nine users means nine conversations, nine onboarding sessions, nine chances to hear "this is nice but we use Notion." It means the founder did the work. The market just did not reply with revenue fast enough.

The Metrics: Nine Users and No Revenue Engine

Nine users. Zero reported MRR. No churn data because there was no retention to measure. No CAC because there was no paid acquisition. No LTV because no one paid.

These numbers are not embarrassing. They are the default state of every SaaS product before it finds product-channel fit. The error was not the low numbers. The error was the strategy that produced them. The founder built for the enterprise but sold like a consumer app — waiting for inbound, listing on directories, hoping the product would speak for itself. Enterprise buyers do not browse Product Hunt. They respond to outbound, referrals, and proof of scale.

The pivot to a job was not a failure of the