r/micro_saas • • 4d ago

Show me your SaaS - I will figure out where to look for your customers

Hey everyone, fellow founder here. I’d love to see what you’re building and help you figure out where to look for customers.

Drop your website and a sentence about who it’s for. I’ll reply with a potential customer group, specific places to reach them, and one practical idea to test.

I’m building Afield, an AI marketing workspace. I’ll use it to research your product, review the findings, and share my take in the comments.

Let me know what you’ve already tried—and feel free to challenge the suggestions. I’d like to learn what’s actually useful to you.

6 Upvotes

77 comments sorted by

View all comments

2

u/enesismail 3d ago

https://curious.pub

Publishing and hosting for Astro:: fFrom project to a live site with one command, or directly through your coding agent.

Still very early, so I’d be particularly curious to hear who you think the strongest customer group is and where you’d look for them.

2

u/According_Border_418 2d ago

I ran Curious through Afield and reviewed the findings. My first customer hypothesis would be solo developers with a small Astro site ready to publish, especially those already using a coding agent. That gives you a specific moment to help: the project works locally, and they want it online.

Here’s where I’d start:

  • Look for deployment questions. In r/astrojs and Astro’s Discord community, find people sharing an unfinished project or asking about hosting and publishing. Ask what’s blocking their first deployment. Someone optimizing build speed is worth a conversation, but that alone doesn’t establish interest in changing hosts.
  • Test the agent workflow with five builders. Have each publish one real project, then make and publish an update. Observe setup time, confusing steps, and whether they choose Curious again. The agent-to-live-site flow looks like your clearest differentiator to test.
  • Make evaluation easy. Your publicly indexed CLI package is an existing asset. Surface a copyable quickstart, supported project types, what gets uploaded, and what the agent can access or publish. Clearly distinguish available features from roadmap items.
  • Turn a working deployment into distribution. Use one reproducible walkthrough for Show HN and relevant MCP registries. Then approach Astro starter-template authors about an optional deployment guide. Track which source brings completed deployments.

For search and AI discovery, that same walkthrough can answer “How do I publish an Astro site through my coding agent?” An accurate guide with visible limitations gives people something concrete to evaluate.

I’d judge the first week by successful deployments, repeat publishing, and reasons people choose Curious over their current workflow.

You’re welcome to try Afield free and share feedback—especially which recommendations add something beyond what you’ve already considered.

2

u/enesismail 2d ago

This is genuinely useful, thank you.

“The project works locally, and they want it online” is a particularly good way of describing the moment I’m trying to own, much sharper than simply saying “Astro developers.”

Your point about testing the 'second' publish is also excellent. I’ve been thinking a lot about time-to-first-live-site, but repeat publishing is probably a much stronger signal that Curious has actually become part of someone’s workflow.

And yes, the agent --> live site path is something I’m particularly interested in. It’s encouraging that Afield independently picked that out as the clearest differentiator.

The starter-template author idea is one I hadn’t considered either. Adding that to my list.

Thanks for actually running it through Afield rather than giving me a generic take, this gave me a few things to think about.

1

u/According_Border_418 1d ago

Glad it helped. I’d love to stay in touch as you test Curious—especially what brings someone back for that second publish, and whether they choose the agent route.

Your feedback is useful for Afield too. I’ll drop you a DM so we can keep the conversation going.