Thread by @BrendanOfEarth

Just listened to the @IndieHackers podcast. @csallen spoke with @dvassallo. This quote struck me: "As soon as something inspires me... I tend to do it almost immediately, at least I’ll start." So I'm going to live-validate an idea right now. Join in with ideas/input. Thread 👇

My hypothesis: Users of SaaS apps often need to upload data from flat files (csv, excel). Designing and coding this feature is really annoying - multiple file-formats, complex error handling, unclear UX - and a source of support.

My initial product idea is a service that handles file parsing, customizable validation, generates a template for users to fill out, and provides a UI with error-correcting feedback. Probably in the form of an API + SDK.

Hypothesized value props: 1) Don't spend time coding, outsource it. 2) Avoid nasty bugs because a user used Excel 2008 on a Mac and you hadn't tested that. 3) Error feedback is robust so the feature is self-serve resulting in fewer pissed customers and less support.

My validation process is to start with really big unknowns, turn those into knowns or strong beliefs. Then look at the next level of unknowns and work on those, and so on until I've figured out why it's a bad business idea. If I don't figure that out, maybe it's worth working on.

1st unknown: Is this actually a problem?
--> I can say yes it is for at least me as I solved this at my last job.
2nd unknown: Do others have this problem and if so how do they solve it?
Let's go. #buildinpublic #indiedev #indiehackers

I have three initial thoughts on how to establish others having the problem. 1) Post in dev communities asking how they do it. 2) Google search 3) Find potential competitors.

Posting in dev communities -> I sent this to the #coding channel of the @MicroConf Connect Slack. I'll follow up here with any responses.

Also posted an Ask HN on hacker news news.ycombinator.com/item?id=253531…

On Hacker News, I just got a response: flatfile.io. Let's go check it out.

Here's a quick loom of my first impressions of flatfile.
loom.com/share/fe86de02…
Takeaways 1) The website is written for developers - I assume this means that their sales process probably starts with a dev needing a solution and trialing.

2) Pricing is high. $2 per file ($99 min) or $399 + $1/file. -> This tells me they are probably doing enterprise sales which is reflected with their schedule a demo CTA.

3) Website is clean and modern. *I would need a strong point of differentiation.*

Next step: see if we can find out how big they are.

From owler, they've taken almost $10mil in seed funding. Techcrunch article says 14 employees as of June with the goal of ramping to 25 by EOY. 160 customers with 300 sitting on a waiting list. Also they are positioning themselves as part of SaaS onboarding primarily.

I'm calling others having the problem confirmed + willingness to pay based on a competitor having 100+ customers.

To pursue this as an indie, I'd need to differentiate and niche. Recurring uploads/integrations are an idea here.

More research needed. End of thread for now.

@threadreaderapp unroll please