HN user

dc_rog

46 karma
Posts2
Comments20
View on HN

Start telling your story about why you built it in the first place. Tell it on any community that you think people who are in a similar need will be. Get narrow, try a few small niches. Stick with it for a month and then see who is following along. That is your audience. Start to tease out features based on outcomes that those people will achieve once they are helped by your product. Let your audience tell you what they want.

Paid ads, etc, will very likely not yield good results at this early stage because you don’t know your ideal customer profile well enough and no one knows you or your product well enough to trust you. This will build over time.

Probably depends mostly on the payout country (where you are located) that will drive KYC requirements from the processor (stripe, etc), where people are paying you from (currency acceptance), and a little bit on what you are selling (e.g. subscriptions need a little more infrastructure).

“Non-US” could be any of 190+ other countries. Where specifically?

I believe there will continue to be a market for people building websites. Storefronts, landing pages, personal pages, blogs. I don’t see these going away.

The feedback I keep seeing on hn and elsewhere is a mix of ease/ownership/flexibility but still abstraction of coding and hosting that most people might not want to do. It’s a super broad space and lots of people want different things in a solution.

Advice: go after a narrow niche since the space is crowded, competitive, and arguably commoditized.

Here’s an example I saw launch recently and thought “that’s an interesting niche” https://sprout.site/en/ (No affiliation)

This is not shade because I like this space, but how did you decide YC/venture path was right for Roame? I see many bootstrapped builders in travel (or have a lower margin business around content/affiliate revenue) and would love to know why you chose to raise venture capital or if you could share your thoughts around this topic.

For early versions I’ve had a much easier time building with subscription model (used a third party, set up in one day). Unless it was a key differentiator for a customer choosing me, usage based was more complicated to set up for shipping quickly early on. There are 3rd parties that help with this but it’s more complex.

Love this askHN post.

I'm currently working on "JobMailer".

When I was looking for a job and applying to 100-200 positions, I got really good at the process. To me it seemed like a somewhat wasted skill set, because I was just looking for one job (unlike, for example, trying to acquire customers).

"JobMailer" rebundles paid subscription features that a job seeker might use only a handful of times over their search period and automates manual application tasks:

- Find good fit companies and jobs

- Reword resume/CV to mirror or match job description and keywords

- Find recruiter and hiring manager email addresses

- Write cover letter and send email to recruiter/hiring manager to get noticed

- Track email opens

- Single page hub for all application statuses (think Mint but for all different company application login pages)

The goal would be to semi-automate and submit ~50 high-quality and tailored applications in the first 30 days for a user.

In a python-based backend, one suggestion for retrieving "additional details" could be SMS via Twilio or other. Easy to use with Python and might be a good context fit for following up that doesn't require a user to be at their computer.

This also seems like a potential candidate for automating using some of the tools they might already have - forms, sheets, email. Forms has the ability to ask for additional info based on the previous answer (might fix the need to ask for more info).

You aren't generating an "invoice" but a work/spec sheet might follow a similar pattern. One of the first search results I found(no affiliation) https://howtogapps.com/generate-invoices-using-google-form-a...

You can do both to hedge that interest rate risk. Some fixed, some floating. No one knows where rates are headed and savings account providers can change rates at any time.

I’ve had that happen too. Unfortunately these seem like edge cases for most companies and sms based 2FA remains the default.

I’ve finally found a good workaround when traveling abroad: adding a local eSim for data-only and keeping my U.S. number on for receiving voice & text.