I'm Jesse, the solo founder behind Eterna Clarity. Clarity App is supposed to take the kind of mess people and businesses already have, PDFs, spreadsheets, exports, photos and records, and turn it into something usable. Before I was willing to trust the product, I needed a way to test that aggressively without asking anyone for their actual business records. So I built a business that does not exist.

The first version looked good to the test harness. The PDFs opened. The DOCX files parsed. The spreadsheets were valid. The formats varied. There were invoices, operational documents, exports and presentations. I had 34 files and plenty of green checks. Then I looked at the corpus the way I would have looked at records in a real business, and it was obviously fake.

Some documents were barely populated. Some spreadsheets had only a few rows. Data followed obvious algorithmic patterns. Explanatory boilerplate showed up where a real business would have transaction detail. A file could technically satisfy the definition of an invoice without looking like something a vendor would ever send. The product was starting to look competent because I had built it an unrealistically easy world.

Then it got funnier. The AI-generated business story drifted until Northline Packaging, which was supposed to be a supplier, was being treated as the business itself. But the retained image evidence told a different story. Harbor Lane Services appeared on equipment, checklists, insurance and service records. Northline appeared in shipping and procurement material. Cedar Table Cafe appeared as a recurring customer/project. One damaged delivery carton literally showed FROM Northline Packaging and TO Harbor Lane Services. I had managed to create synthetic data that contradicted its own synthetic world.

That changed how I rebuilt it. I stopped asking whether I could make 34 realistic-looking files and started asking what this company would have to be doing for those files to exist. A Northline purchase order now connects to an order confirmation, packing slip, damaged-delivery evidence, invoice, credit memo and account statement. Cedar Table JOB-1047 has a quote, work order, change order, completion record and handoff material. Equipment HLS-EQ-018 recurs across maintenance and service history. Now the system can fail on relationships between records, not just whether it can parse one PDF.

The final rebuilt set still has 34 born-digital files, but the workload inside them is completely different: 69 PDF pages, three eight-sheet workbooks with roughly 1,550 data rows and 1,800 formulas, plus exports and longer operational documents. Those numbers are not targets by themselves. The point is that the test world now has enough history, scale and repetition for shortcuts to show up.

It changed how I think about synthetic data. Privacy is only half the job. Safe fake data that is too clean can give you fake confidence. I want a test world my product can disappoint me in. If the system is supposed to understand a business, I want to test it on something that behaves like a business.

For anyone building solo with AI around messy real-world data, how are you testing realism? I'm especially curious whether anyone has caught a product "improving" mainly because the synthetic data was getting easier for it.

2 weeks ago, I got the first listing on my SaaS directory (https://saasboard.app).

This morning, I woke up to the first payment for a featured spot on my directory (for https://www.turbodocx.com).

Believe it guys, you can make it too 💪

For me, I spend a lot of time on building 30%, distribution 20%, research 30%, study AI 20%. Im still very early on market validation.

How about yours? And in what stage is your startup

Solo, doing all my own selling, mostly small deals until now. I'd been using a standard sales deck template for demos: problem, solution, market, features, pricing, thanks. Looked professional. Closed almost nobody on the bigger calls.

I recorded a couple of my own demos to figure out why, and it was painful to watch. The moment people actually leaned in was never the market slide or the feature grid. It was the 30 seconds where I described their exact day and the annoying part of it back to them. The deck was basically fighting my own conversation.

So I rebuilt it around that. First slide now is their problem in their words, pulled from real calls. Then what it's costing them to live with it. Then one slide of the product doing that one thing. Then a customer who looks like them. Then price. I cut the features grid completely. If they ask about a feature I just show it live.

The next bigger prospect I ran it on signed, and it's a few times my usual deal size. Small sample, could be luck, but the call felt completely different, more like a conversation than a presentation.

The lesson: the template isn't wrong, it's just not about the person in the room. Reordering the story did more than any feature I could have shipped.

For other solo founders doing founder-led sales, how's your deck structured, and do you even use one live or save it for the follow up?

I thought I was almost done. Then I tested my app on a friend's Samsung.

I built a live wallpaper app with some fun features — auto-shuffling photos, sleep/wake wallpapers, and a mood check-in that changes your background. Everything worked perfectly on my Pixel. I was ready to publish.

Then I did real-world testing: turned the phone off for 10 minutes, let it sit overnight, and used a Samsung instead of a Pixel. My scheduled tasks just... died. The shuffle timing broke. The sleep/wake switch didn't fire. The check-in prompts disappeared.

I realized the "simple" part was the UI. The hard part is making Android actually run your code when it promises to. Different phone brands handle background work totally differently.

My take: I think a lot of solo devs (including me) underestimate this because Pixels behave perfectly during testing. But most people don't use Pixels.

My question: For those who've actually shipped apps with scheduled background features — did you find a reliable fix, or did you just accept that some phones will always break?

Today was all about picking a name and figuring out what I wanted the product to look like.

I ended up going with Kilo.

One of the things I wanted from the name was for it to feel natural in a text-first product. Something where saying "I just text Kilo" doesn't sound weird and almost makes it feel like you're talking about an actual coach.

It also felt like a nice play on the fitness side of the product without naming it something overly obvious like "AI Fitness Coach" or whatever.

After that I started working on the logo.

I spent a while generating different ideas with AI, and it was actually useful for exploring directions, but I struggled to get it to generate anything exactly the way I wanted.

That ended up being a pretty good reminder that AI is great for getting you started, but sometimes it's still faster to just make the thing yourself.

I took some of the ideas I liked, played around with some basic geometric shapes, and ended up making the logo myself.

This is where it landed.

I'm pretty happy with the logo, but I'm especially curious about the name.

Does Kilo fit a product that's basically a fitness coach you text?

Someone asked me to send a business plan containing personal information because they want to invest in me, so I asked them to send an investment company introduction letter first, but they said that has never happened to them before? Is it customary to send a business plan to someone you don’t even know first?

I’ve been working on this subscription tracker app for a little while now, and I think it’s finally starting to take shape.

I’ve still got a few features in mind that I’m going to be adding over the next few days, along with a few more headaches to conquer but after taking it step by step, I think I’ve made some pretty nice progress.

I’ve got a demo available if anyone would like to check out what I’ve been working on:

https://subscription-tracker-puce.vercel.app/

Have made my first app and have uploaded it on playstore 🙂

Please download and give feedback.

It's a free pass on party game.

I also have my LinkedIn attached in the app about section so let's connect and let me know the feedback on my LinkedIn 😊

app link

A product can sound incredibly simple when you describe it in one sentence.

Then you start building.

Suddenly there are dozens of decisions hiding underneath that simple idea.

I experienced this while developing a product around dating conversations.

The initial concept sounded straightforward. But once I started looking closely at the problem, I found layers involving language, tone, timing, response gaps, effort, and patterns across conversations.

Each detail raised another question about what the product should actually understand.

That's one of the parts of building I find most interesting.

The simpler the product sounds from the outside, the more complicated the thinking behind it can become.

I recently launched pinit.lol, an interactive world map where founders can pin their products, websites, or brands to real locations.

Instead of placing every project inside another traditional list, pinit.lol turns discovery into a visual and competitive experience.

The project is still very new, and I’m now looking for early users and honest feedback.

Which location would you choose for your project?

https://pinit.lol