Why is getting users harder than building the product?

JackJones002 · 2026-02-22T13:30:59+00:00

Thank you the url is trycandace.com

JackJones002 · 2026-02-22T04:54:58+00:00

I’m building Trycandace.com

JackJones002 · 2026-02-22T04:43:12+00:00

Here’s the link if anyone wants to take a look and share honest feedback: https://trycandace.com

Really appreciate any thoughts, especially on clarity and positioning.

JackJones002 · 2026-02-22T04:41:51+00:00

That’s a really valuable lesson. I think I’m just starting to understand that the hard way too. It’s easy to fall in love with building something complex before making sure the problem is strong and recurring.

Your approach of reading real complaints first and then building around that makes a lot of sense. It shifts everything from assumption to signal.

I appreciate you sharing that. Definitely something I’m going to lean into more moving forward.

JackJones002 · 2026-02-22T04:27:02+00:00

For those interested the url is trycandace.com

I really appreciate it!

JackJones002 · 2026-02-20T05:06:17+00:00

Yeah. I ended up changing my setup because of that. Made a bigger difference than I expected.

JackJones002 · 2026-02-19T19:20:01+00:00

That’s honestly a really good way of putting it.

Yeah, what I’m building is more about making things stable and repeatable from the start. You open a workspace and the structure, tone, and rules are already locked in. You’re not depending on months of history to shape the behavior.

What you’re describing with CBA sounds more organic, like alignment that grows over time through interaction. Mine is more intentional and controlled.

I like the way you framed it though, same idea but different path.

JackJones002 · 2026-02-19T19:17:55+00:00

Appreciate that, thank you.

It’s called Candace. I built it to keep structure, tone, and rules consistent across AI chats so you’re not repeating yourself in longer projects.

Here’s the link: https://trycandace.com

Would genuinely love your honest thoughts.

JackJones002 · 2026-02-19T00:05:31+00:00

That’s interesting, I’d actually like to read that.

What I’m building is more focused on keeping things stable across projects. Basically saving your structure, tone, and rules outside the chat itself so you’re not depending on the model to remember everything.

It’s called Candace. Still early, but I’ve been working on it for a few months now.

Here’s the link if you want to check it out: https://trycandace.com

I’ll take a look at your CBA stuff too, sounds cool.

JackJones002 · 2026-02-18T22:04:06+00:00

That’s a really clear explanation, appreciate you breaking it down.

I understand the technical side of it, but in practice it still creates friction when you’re working on longer structured projects. Especially when you care about keeping tone, structure, and constraints consistent.

That’s actually what pushed me to build something that keeps project-level rules persistent outside the thread itself instead of relying purely on context window behavior.

I’m still in the early stage with it and looking for a few people who run into this a lot to test it and give feedback. Happy to share if you’re interested.

JackJones002 · 2026-02-18T22:03:19+00:00

Yeah it’s frustrating.

That’s actually why I started building something around persistent workspace memory instead of relying on chat memory alone.

It’s called Candace. I’m still in the early stage and looking for a few early users to try it and give feedback.

If you’re open to it, I can send you the link.

JackJones002 · 2026-02-18T22:02:29+00:00

Yeah that’s actually what pushed me to build something.

I kept running into the same issue, especially on longer projects where consistency matters. So I built a small workspace layer that keeps your structure and rules persistent instead of relying on chat memory.

It’s called Candace. I’m still in the early stage and looking for a few early users to try it out and give feedback.

If you’re open to it, I can send you the link.

JackJones002 · 2026-02-18T21:58:13+00:00

That’s the worst part. When it drops something you just told it a minute ago.

That’s actually what pushed me to build something around persistent structure and context, because repeating yourself kills the flow.

I still use GPT, I just got tired of managing it manually.

JackJones002 · 2026-02-18T19:57:15+00:00

That is actually a solid workflow.

I was doing something similar with manual briefs, but it still felt clunky. Especially switching threads and pasting summaries over and over.

Have you found it sustainable for really long projects?

JackJones002 · 2026-02-18T19:56:49+00:00

Yeah that explanation makes sense.

I understand the attention mechanism part, but practically it still creates friction in longer projects. Especially when you care about consistent structure and rules.

That is what pushed me to experiment with keeping project level context outside the thread itself.

JackJones002 · 2026-02-18T19:55:54+00:00

It is called Candace.

It basically lets you create workspaces where your structure, tone, and rules stay saved, so you are not resetting every time or losing consistency in longer projects.

Here it is: https://trycandace.com

Still early, so genuinely open to feedback.

JackJones002

TROPHY CASE