Igor Araujo

Hi, my name is Igor and i build random apps to help me.

[Igor Araujo @buildwithigor]

Tried treating Chrome Web Store approval as a launch day. It wasn't. Being listed in a store nobody browses does not send traffic, it just makes the product available. Approval is permission, not distribution. The work starts after the green checkmark. #buildinpublic

[Igor Araujo @buildwithigor]

Building in public: 19 products, 4 months in, revenue still close to zero. 1 SaaS, 1 Chrome extension, 3 Gumroad kits, 14 Apify scrapers. Building was the easy part. Getting strangers to care is the real job. #buildinpublic

[Igor Araujo @buildwithigor]

Product update: InvokePay now has a free library of freelance invoicing guides. Late payments, deposits, payment terms, all covered. Written for what freelancers actually search before they trust a tool with their invoices. #buildinpublic

[Igor Araujo @buildwithigor]

@MarvellousDev I like separating those two problems. If they can't find the options, that's navigation. If they find them but can't explain the tradeoff, that's the comparison. Asking them to talk through the choice would make the feedback much more specific.

[Igor Araujo @buildwithigor]

InvokePay update: shipped /tools and /compare hub pages, plus mobile navigation. The comparison pages now have a home instead of being scattered links. Next up: getting feedback from freelancers. #buildinpublic

[Igor Araujo @buildwithigor]

@jul1anodev I'd ask them to recreate a typical invoice with dummy client details, without me explaining the steps. Useful feedback would be where they hesitate, what's missing, and whether it's easier than their current process. Not just whether they like the page.

[Igor Araujo @buildwithigor]

@golumora That's a good point. A cheaper tool isn't cheaper if moving years of invoices takes a weekend. The comparison should distinguish what can be exported, what can be imported, and what has to be moved manually.

[Igor Araujo @buildwithigor]

@zerotoaihq Good distinction. A shutdown checklist needs a separate pass for scheduled jobs and paid services, not just the app itself. 'Can anything still run or renew?' is a better final check than 'is the site down?'

[Igor Araujo @buildwithigor]

Lesson from shutting down Slack Says: deleting the app was not the last step. Domain auto-renew was still a billing loose end. That is now off too. My shutdown checklist needs to cover bills, not just code. #buildinpublic

[Igor Araujo @buildwithigor]

@progerallworld Yes, especially the chasing part. 'What did you do after the due date passed?' seems much more useful than 'would you use this?' I'd want to understand the workaround before suggesting a replacement.

[Igor Araujo @buildwithigor]

My stack for InvokePay: Next.js, Prisma, and PostgreSQL. Familiar tools for an invoicing app. The harder part is finding freelancers willing to try it and tell me what is missing. #buildinpublic

[Igor Araujo @buildwithigor]

Asking other builders: how did you find the first five people willing to try your product and give honest feedback? Not signups, actual conversations. What worked for you? #buildinpublic

[Igor Araujo @buildwithigor]

Saturday behind the scenes: reviewed my project board. Freelancer feedback for InvokePay is still in progress, and distribution ideas are piling up in the backlog. The next useful step is a conversation, not another feature. #buildinpublic

[Igor Araujo @buildwithigor]

This week: shipped /tools and /compare hubs for InvokePay, plus mobile navigation. Also closed the last billing loose end on Slack Says. One product easier to browse, one less loose end. Slow and steady. #buildinpublic

[Igor Araujo @buildwithigor]

Building in public: 3 starter kits published, an invoicing SaaS, and a Chrome extension. Also shut down Slack Says. Keeping every project alive is not the goal. Building something people pay for is. #buildinpublic

[Igor Araujo @buildwithigor]

Asking other builders: how did you find your first five users outside your own network? I'm looking for freelancers to test an invoicing tool, and I'd rather have five honest conversations than another launch-day traffic spike. #buildinpublic

[Igor Araujo @buildwithigor]

Today I reviewed my project board. Finding freelancers to test InvokePay is still in progress. Plenty of finished build tasks, but the feedback work is the one that matters next. #buildinpublic

[Igor Araujo @buildwithigor]

This week: Dev Toolbelt got Pro gating for its JSON diff viewer, Base64 file encoder, and color palette generator. Small utilities, but useful enough to package together. Slow and steady. #buildinpublic

[Igor Araujo @buildwithigor]

My stack for InvokePay: Next.js, Prisma, Railway. Familiar tools, fewer deployment decisions. The hard part is still finding people who need it, not picking another framework. #buildinpublic

[Igor Araujo @buildwithigor]

Tried running generic outreach for InvokePay to bring in early users. Didn't work because telling freelancers "try my invoicing tool" gets ignored when competing with free tools. Lesson learned: solve one specific pain like unpaid invoice follow ups instead. #buildinpublic