Day 4: Why I Built a $199 Workspace Nobody Asked For
I quit my agency job on a Tuesday. Not dramatically — I just realized I'd spent 6 years building workflows inside other people's products.
We used ClickUp for tasks. Slack for chat. Google Docs for specs. Figma for designs. Each tool cost money. Each tool broke in different ways. And every single one pushed us toward annual subscriptions because that's how SaaS survives.
By 2026, it felt absurd. My freelancer friends were spending $50-100/month on tools they barely used, just to keep access. I was doing the same thing. We were all complaining about subscription fatigue at 11 PM on Slack while nobody actually did anything about it.
So I did.
I built Melororium over 4 months — a single workspace for freelancers and agencies. Tasks, files, client management, time tracking. One product. One price. $199. Pay once. Own it forever.
The honest part? I launched with exactly 0 email subscribers, 0 organic traffic, and 0 sales. My website isn't even indexed yet because I literally just started pushing it publicly 4 days ago.
But here's what I have done:
- Written 40+ articles on melororium.com about subscription fatigue, freelance workflows, why pay-once matters
- Submitted to BetaList (pending review as Lite #169032)
- Submitted to SaaSHub (pending approval)
- Launched the /pay-once landing page today
- Published "Subscription Fatigue in 2026: How Freelancers Are Switching to Pay-Once Tools" yesterday
The numbers are small. The reach is tiny. But the signal is clear — I'm the only person talking about this specific problem in this specific way.
What surprised me most: I expected pushback. "SaaS doesn't work without recurring revenue." "You'll never scale." Instead, the first people who've seen it just... get it immediately. No explanation needed. They've been waiting for this.
The scary part is knowing that ClickUp, Notion, and Toggl have marketing budgets 100x mine. But they're also trapped by their own subscription model. They can't suddenly tell their enterprise customers "actually, you could just buy this once." I can.
I don't know if Melororium will work. Day 4 is way too early to claim victory. But I know the problem is real because I lived it for 6 years. I know the solution works because I'm using it daily. And I know there are people out there frustrated enough to notice.
Right now, I'm competing against the weight of industry convention, not against product quality.
What convinced you to switch away from a subscription tool, or what's keeping you locked in?
THE phrase
'you don't know if melororium will work' if you believe it will work, then you will doyour best to make it work
i see your tools have a great potential, i would say you don't focus much on your competitors. if you should, try to exploit their weakness and that will be your unique selling point that will make you little or extremely different from them.
Most founders are trying to be louder than everyone else; you're becoming known for a specific problem. One thing I'd look at next is turning that message into proof. Since you're already publishing consistently, it might be worth collecting stories, examples, or mini case studies from freelancers who've switched away from subscriptions. That could make the positioning even more convincing when people land on the site.
Appreciate this — the competitor angle is something I've been underusing. I've mapped their weaknesses (ClickUp's feature bloat, Notion's missing time tracking, the way Asana quietly charges per seat) but haven't turned that into pointed positioning yet. That's a gap worth closing.
The proof point is the one that stings a little, because you're right and I don't have it yet. Four days in, no case studies. What I do have is my own story — I was paying €340/month across six tools and built this to stop. That's one data point. I'm actively looking for the second and third.
If anyone reading this has switched away from a subscription stack recently — even informally — I'd love to hear what that looked like.
the 'they just get it immediately, no explanation needed' observation from the first people who've seen it is interesting but worth being careful about. the people who see it in the first four days are probably people who are already primed to agree with the pay-once argument, your network, IH readers, people looking for alternatives. the harder test is showing it to a freelancer who's satisfied with their current stack and seeing if they get it. have you done that yet and what happened
Fair point — and I've thought about this.
The honest answer: no, I haven't done a proper cold test with someone satisfied with their stack. The people who've seen it first are exactly who you described — already primed.
I've had one conversation that came close. A friend who uses Notion + Toggl + a spreadsheet and has no real complaints. His reaction wasn't "I need this" — it was "hm, interesting, but I'm not in pain." Which is probably the more common response, and I'm not pretending otherwise.
What I'm building toward: the product makes most sense when the pain is already there — usually when someone gets their third SaaS renewal in a week and does the mental math. The goal isn't to convert the satisfied freelancer cold; it's to be the obvious answer when the frustration finally surfaces.
That said — if you know someone who fits that profile and would do 20 minutes with me, I'd genuinely take that call.
The struggle is the tuition. What lessons have been worth the grind for you?
A few that actually cost something to learn:
Building for yourself first isn't a workaround — it's the only way I've found to know if a problem is real. I spent months watching myself pay for tools I didn't fully use before I trusted the frustration enough to act on it.
Pricing is a positioning statement before it's a revenue decision. When I chose $199 lifetime, I wasn't doing math — I was deciding who I was building for and what relationship I wanted with them.
The thing you're embarrassed to admit is usually the most useful thing to say publicly. The posts where I wrote "I have zero users and I don't know if this works" got more real responses than anything polished.
Still early. Ask me what the expensive lessons were in a year — I'll probably have better ones.
Pushing back gently, because I want this to work: the risk I'd stress-test isn't demand — subscription fatigue is real and you obviously lived it — it's the cost side. Support, OS updates, and bug fixes recur even when the revenue doesn't, and for a solo dev that gap is exactly what tends to push people back toward subscriptions. The pay-once tools that survive usually smuggle in a recurring edge: paid major versions every 12-18 months, or a small sync/hosting fee. On my own side project I sidestepped this by staying near-zero-maintenance on purpose, but a full workspace holding client data is a much heavier support load. Have you modeled what year-three support looks like against one-time payments that have stopped compounding?
This is the most useful pushback in the thread so far, and I want to answer it honestly rather than defensively.
You're right that support load is the hidden cost that breaks pay-once models. I've seen it happen. The tools that survive usually do exactly what you describe — paid major versions, hosting fees, something that creates a second revenue event.
Our version of that is modules. The core workspace is one price. Each new module — we're building Etsy-specific tools for our own business next — is a separate purchase. Existing customers who want it buy it. Existing customers who don't, don't. It's not a subscription disguised as something else, but it does create recurring revenue events tied to actual new value delivered.
On year-three support: no, I haven't modeled it with real numbers. That's an honest answer. What I do know is that we run the product ourselves for our own team, which keeps the initial support surface small — I'm not supporting strangers, I'm supporting my own workflow first. That doesn't scale forever, but it buys time to understand where the real load comes from before it becomes a crisis.
What did near-zero-maintenance look like for your project? Genuinely curious what constraints you set at the start.
The Day X accountability format is smart — committing publicly forces consistency. Curious what your retention looks like after day 7, when the novelty fades for early adopters. Are you seeing repeat engagement or is it one-and-done trial users?
Honest answer: day 4, nothing to measure yet — and actually we're not selling yet. Right now we're collecting a wishlist, not processing orders. The purchase buttons are there to gauge intent, but no one's been charged anything.
So the retention question is a bit ahead of where we are. The signal I'm watching right now is simpler: do people who sign up to the wishlist actually remember why they wanted it when we launch? That gap — between "I liked this" and "I'm still thinking about it 30 days later" — is the thing I'm trying not to lose people in.
The habit loop I'm building toward is the time tracker. Open Melororium, start a timer, close the task. Every working day. If that becomes muscle memory before we officially launch, retention takes care of itself.
Ask me again at launch. I'll have a real number or an honest post-mortem either way.
Day 4, 0 signups — the post title might be part of it. It says "$199 workspace" but the site shows $49 one-time. Someone who clicks through expecting $199 and sees $49 doesn't feel like they're getting a deal, they feel like something's miscommunicated. Worth syncing those so visitors aren't doing mental math before they've even read what the product does.
The other thing: the only CTAs on the site are purchase buttons. If someone isn't ready to spend $49 today — curious, wants to think about it overnight — there's no path back. No email opt-in, no waitlist, nothing. They close the tab and they're gone. Even a "keep me posted on updates" field would give you a way to reach them after launch week.
Full breakdown here: https://outboundautonomy.com/audit/05211/melororium-com?ref=ih-melororium
Both fair. The $199 is the All-Access tier — $49 is the entry module — but you're right that leading with $199 in the title creates a frame that makes $49 confusing rather than accessible. Worth a rewrite.
The email capture point is the one I actually kicked myself on. We have a waitlist flow built — it's just not prominent enough. Fixing that this week.
Skipping the link at the end though.
the risk with a product nobody asked for is usually not the build, it is how fast you can learn whether the problem exists. i would be looking for one concrete workflow that is painful enough to bring people back.
That's the right question and I've been sitting with it.
The workflow I'm betting on is: open a task, start the timer, do the work, close the task, see where your time actually went. Not in three different apps. In one place, in under five seconds.
The reason I think it's sticky: freelancers who track time do it every single working day. It's not a monthly reporting habit, it's a daily one. If Melororium owns that moment — the start of the work session — it becomes infrastructure, not a nice-to-have.
Right now we're finishing bug fixes on the time tracker. That's the module I'm watching most carefully for the "does this pull people back" signal. End of July is when I'll have a real answer.
What workflow do you look for when you're testing this kind of thing?
The subscription fatigue is real, but I think the bigger pain is the typing friction across all those tools. Even when you consolidate into one workspace, you’re still typing into tasks, docs, client messages, time entries. The input layer never changes. I’ve found that adding dictation as a universal input, hold a key, speak, release, makes the single-workspace model a lot more useful because you’re not stuck waiting on typing anymore. I built DictaFlow to work across any app for exactly this reason. dictaflow.io
This comment was deleted 17 hours ago.
The pay-once model is genuinely underserved right now and the content-first approach is exactly right for it. The thing to get ahead of early: $199 is a compelling price but the first serious objection every buyer will raise is 'what happens with updates and support?' Not in a hostile way — they've just been burned by abandoned lifetime deals before. Having a clear answer to that question before you hit the first 10 paying customers will convert a lot of hesitant buyers who'd otherwise want to wait.
The ClickUp-can't-change point is your actual moat. They're structurally unable to tell their enterprise customers to just buy it once. That's not a marketing angle — it's a real constraint they can't escape. Day 4 is early, but that asymmetry is worth leaning into hard.
One more concrete piece for anyone wondering about the roadmap: we're currently in final bug-fixing on the time tracker — minor issues at this point, nearly done. Full public launch by end of July.
The next build cycle after that is already decided — modules our team specifically needs to run our Etsy business. Not guessing at what users might want. We need it ourselves, so it gets built.
That's the part I think lifetime deal buyers should actually care about: not "will they be around" but "do they have selfish reasons to keep shipping." We do.
Both of these are worth unpacking.
On the updates question — the most honest answer I can give is: we built Melororium because our own team needed it. It's not a side project we're hoping will find an audience. We run our projects, track billable hours, and manage clients inside it every day. That's a different kind of commitment than a support SLA — if we stopped developing it, we'd break our own workflow first.
The roadmap is public (melororium.com/roadmap) and it's driven by modules we actually need ourselves — not by feature requests we're guessing at. That's the version of "we'll keep building" I can actually promise. Not "we'll be here forever" — but "we have selfish reasons to keep going."
On the ClickUp structural point — you're right and I don't say it loudly enough. They raised hundreds of millions. Their enterprise contracts require per-seat billing. Their sales team would revolt if product went lifetime. That's not changing regardless of what we do. Notion, Asana, Monday — same cap table, same constraint.
They can copy features. They cannot copy the business model without destroying existing revenue. That asymmetry is load-bearing for us.
The pay-once angle is strong, but I’d be careful not to let “subscription fatigue” carry the whole sale.
A lot of freelancers agree with that pain, but agreement is not the same as a $199 purchase.
The sharper question is: which freelancer feels enough workflow pain that pay-once becomes the reason to act now, not just a nice bonus?
If Melororium tests this too broadly, you may get positive comments but still no clear buyer signal.
Happy to map the tighter first-sales version if useful. The key is finding the segment most likely to pay first, not just the segment that agrees with the idea.
You're pointing at exactly the tension I'm wrestling with.
My working hypothesis for the first buyer: a freelancer already paying for 3+ tools (ClickUp/Asana + Toggl + something for invoices), who recently got a price-increase email from one of them. That combination — fragmented stack + fresh price hike — seems to be the trigger that moves someone from "this is annoying" to "I'm actually switching today."
Subscription fatigue gets them in the door. What closes them is the math: replace all three tools, one payment, less than two months of what they're currently paying.
Still testing this. Solo freelancers vs. small agency owners behave very differently even with the same tool stack — so the ICP might need to split.
Curious if anyone here has gone through that exact switch (fragmented stack → one tool) — what actually made you pull the trigger?
That trigger is much closer to a real buying moment: fragmented stack plus fresh price increase.
The risk now is getting agreement from both solo freelancers and small agencies, but clean purchase signal from neither.
Drop your email and I’ll send a tighter first-sales version: which buyer to test first, what switching pain to lead with, and how to know in 7 days if Melororium has a real $199 buyer path.
Full product at melororium.com — feedback welcome!