u/ElectronicHoneydew86

“I came to Portugal to win the World Cup, and I think that, without winning it, there’s no point in continuing,” Martinez told reporters.

(Disclosure up front: I'm building the tool I mention below, here for genuine marketing feedback, not a link drop.)

I'm pre-launch on a B2B tool and wrestling with a marketing/validation problem I'd love this community's take on: my likely users (ops, finance, sales, founders at companies with messy data) aren't hanging out on the usual indie channels, so I'm not sure my early signals mean much.

What I've set up so far:

- An honest landing page that's upfront about being pre-product (no fake screenshots).

- A 30-second feedback form next to the waitlist, I care more about why someone would/wouldn't use it than the raw signup count.

- UTM tags per channel so I can see what actually converts instead of guessing.

Where it's falling short / what I'm asking:

1. For a B2B tool whose buyers aren't on Reddit/Twitter/PH, what channels actually surfaced real early users for you?

2. At the validation stage, do you optimize the page for signups (bigger number) or for qualitative feedback (smaller, richer)? Trade-offs?

3. How do you tell "polite interest" from a signal worth acting on, from marketing metrics alone?

For context on what I'm validating: it's a "talk to your data" tool (ask a question in plain English, get the answer + the SQL it ran). Page here if it helps you critique the positioning/messaging:

https://parleyapp.vercel.app/?utm_source=reddit&utm_medium=social&utm_campaign=validation&utm_content=appmarketing

Genuinely after marketing/positioning feedback, happy to share what converts as I learn it.

Sharing a project I'm building and after honest feedback from fellow builders.

Parley lets a non-technical person ask their company data a question in plain English — e.g. "which customers are about to churn before renewal?"and it:

- writes the SQL for you,

- runs it read-only against your own data (nothing gets copied out),

- and shows you the exact query it ran, so it's transparent, not a black box.

Why I'm building it: non-technical teams wait days on the data team for simple numbers, and dashboards only answer questions someone planned for, never the one you have right now.

Stage: early access / pre-product, landing page + a 30-second feedback form. Honest feedback beats a signup for me right now.

https://parleyapp.vercel.app/?utm_source=reddit&utm_medium=social&utm_campaign=validation&utm_content=vibepromoting

If you take a look: does the value land fast, and would you or your team actually use it? Share your project below and I'll check it out too.

Sharing what I'm building , and genuinely after feedback and early testers, not just eyeballs.

Parley lets a non-technical person ask their company data a question in plain English e.g. "which customers are about to churn before renewal?" and it:

- writes the SQL for you,

- runs it read-only against your own data (nothing gets copied out),

- and shows you the exact query it ran, so it's transparent, not a black box.

The problem it solves: non-technical teams (founders, ops, sales, finance) wait days on the data team for simple numbers, and dashboards only answer questions someone planned for in advance, never the one you have right now.

Stage: early access / pre-product. There's a landing page and a 30 second feedback form. Honest feedback is worth more to me than a signup right now.

https://parleyapp.vercel.app/?utm_source=reddit&utm_medium=social&utm_campaign=validation&utm_content=promotemyapp

If you check it out, I'd love to know: does the value land in the first 5 seconds, and would you (or your team) actually use this? Drop your app below too and I'll take a look.

Sharing an idea I've been chewing on, in the spirit of this sub improve it, combine it with something better, or tell me why it won't work.

The idea (working name: Parley): a tool where a non-technical person asks a question in plain English "which customers are about to churn before renewal?" or "which products lose money after discounts and returns?" and it:

- writes the SQL for them,

- runs it read-only against the company's own data (nothing gets copied out),

- and shows the exact query it ran, so it's transparent instead of a black box.

Why I think there's something here: in most companies, non-technical teams wait days on a data/analyst person for simple numbers, and dashboards only answer questions someone predicted in advance, never the one you have right now. 

Where I want this community to push on it:

1. Improve it what's the one feature that would take this from "neat" to "we'd actually pay for it"?

2. Break it where does this fall apart? Trust in AI-written queries? Accuracy on messy schemas? Security fears about pointing AI at a production DB?

3. Expand/combine it is the real product something adjacent (auto-generated dashboards, alerts on the answers, a Slack bot)? What would you merge this with?

I'm at the validation stage. landing page + feedback form only, no product yet. If it's useful to see the framing, it's here:

https://parleyapp.vercel.app/?utm_source=reddit&utm_medium=social&utm_campaign=validation&utm_content=startupideas

Like a lot of people here, my instinct when I get an idea is to open the editor and start building. This time I'm forcing myself to validate first, and I'm sharing the process as I go.

The idea: a tool (I'm calling it Parley) where a non-technical person asks a question in plain English "which accounts are slipping toward churn before renewal?" and it writes the SQL, runs it read-only against your own data, and shows you the exact query so it's not a black box. It came from watching non-technical teammates wait days on the data team for simple numbers.

What I decided to do before building the product:

- Put up a single landing page that's honest that it's pre-product (no fake "it's live!" claims).

- Add a short feedback form alongside the waitlist because a signup tells me if someone's interested, but the feedback tells me why, and what would make them not use it.

- Tag every channel with UTM params so I can see which audience actually resonates, instead of guessing.

 Decisions I went back and forth on:

- Waitlist-only vs. waitlist + feedback form → went with both. The feedback is the real prize at this stage.

- How much to reveal about the "how" → decided to show that it displays the SQL, because the trust question ("would you rely on an AI-written query?") is the whole ballgame.

What I'm still unsure about, and would love this community's take on:

1. At the pure-validation stage, do you optimize for signups (bigger number) or for qualitative feedback (smaller but richer)? I leaned toward feedback curious if that's a mistake.

2. How do you personally judge whether a landing page has "validated" an idea? What signal actually convinced you to build, in your own projects?

3. For those who've done text-to-SQL or "talk to your data" tools what killed it for you?

Page is here if you want to poke at it (feedback form is 30 seconds):

https://parleyapp.vercel.app/?utm_source=reddit&utm_medium=social&utm_campaign=validation&utm_content=buildinpublic

I keep running into the same thing at work: someone who isn't technical needs a number from the database, files a ticket to the data team, and waits days. Dashboards only cover questions someone anticipated ahead of time, never the one you have in the moment.

I'm thinking about building Parley to fix that: you ask a question in plain English, it writes the SQL, runs it read-only against your own data (nothing gets copied out), and shows you the exact query it ran so it's not a black box.

I haven't built the product yet, I'm trying to figure out if it's worth building at all before I sink months into it. So I'm here for honest feedback more than anything.

The questions I'm stuck on:

1. Is "I can't get answers from my data fast enough" actually a problem for you, or have existing tools solved it?

2. Would you trust an AI written query if you could see the SQL? If not, what would earn that trust?

3. For anyone who's tried text-to-SQL tools before, what made you stop using them?

If it helps to see what I mean, there's a landing page with a 30-second feedback form here: https://parleyapp.vercel.app/?utm_source=reddit&utm_medium=social&utm_campaign=validation&utm_content=sideproject

but I'm just as happy to hear it in the comments. Tell me if I'm chasing a non-problem.