I want to build a crypto invoice tool with freelancers. Looking for 5–10 people
I’m exploring the idea of building a invoicing tool for freelancers that supports crypto payments.
Instead of guessing features, I want to build it with real users.
If you:
- Invoice clients regularly
- Work with international clients
- Are curious about crypto payments but find them risky or confusing
I’d love to talk.
No sales, no ads, just research and honest feedback.
If there’s real demand, I’ll build it around what you actually need.
Trending on Indie Hackers
Hi
this idea resonates with me.
I invoice clients regularly and work with international clients, so cross-border payments, fees, and delays are things I deal with often. I’m also interested in crypto payments, but like many freelancers, I find the volatility, UX, and accounting side confusing and risky in practice.
I like that you’re starting with real conversations instead of guessing features. I’d be happy to share how I currently invoice, what breaks down with existing tools, and where crypto could make sense (and where it probably shouldn’t).
No expectation of selling or pitching — just honest, practical feedback from someone who actually lives with these problems.
If this turns into a product later, even better — but I’m aligned with your research-first approach.
Happy to chat.
This sounds like an interesting build, especially if you’re thinking about real freelancer billing flows + crypto UX (e.g., handling wallet choice, network fees, confirmations). I’ve worked on freelance payment/automation tooling and have a few ideas on:
• how to frame invoice metadata so clients can pay easily on multiple networks
• how to present real-time network fee estimates without confusing users
• practical reconciliation/reporting for clients who want both crypto and fiat tracking
I’m interested in contributing — especially around invoice schema + payment UX.
One question I’d have early on: do you plan to support multi-chain payments from the start, or start with one chain and expand later? That choice tends to shape core UI/flow decisions early on.