Xqivo
AI Invoice Generator — 60 seconds, no account required
What’s one book that meaningfully helped you while building?I’m 17, solo from Ghana, and still protecting rea
- Product Hunt: quiet
- Users: 20 signed up
- Events: 248
- Countries: US, Ghana, India
Lesson learned: Upvotes don't matter. Real users do.
Onto building. 🚀
Xqivo is live on Product Hunt! 🚀
https://producthunt.com/posts/xqivo
Let's go. 🙏
will appreciate it to get your upvotes and comment thanks
Hi Indie Hackers!
I'm Brian, 17, building Xqivo from Ghana.
Xqivo is an AI invoice generator for freelancers. Describe what you need in plain English and get a professional invoice in 60 seconds. No account required.
What I've built:
- 9 premium invoice templates
- AI generation with Gemini 3.5 Flash
- PDF export (client-side)
- Team collaboration on Pro plans
- PWA support (works offline)
Tech stack: Next.js, Firebase, Tailwind CSS, Paystack
Launching on Product Hunt August 4.
I'll be posting weekly updates here with revenue, users, and lessons learned.
Would love feedback from this community!
Try it: https://xqivo-new.web.app
Ask me anything about building SaaS from Ghana at 17. 🚀
-
2
"That's a really good mindset — 'short update > no update.' I think I've been overthinking what to post, waiting until I have something 'worth sharing,' and then going quiet for days.
The accountability point is real too. I've found that replying to people on Indie Hackers and Reddit keeps me in the habit of showing up, even when I don't have a big milestone to share.
How did you launch day go, by the way? Would love to hear how it went."
-
1
Honestly? Launch day was quiet. Product Hunt didn't blow up like I hoped. But I got 100 active users, 548 events, and 10-15 LIVE USERS within 30Min. So something is working.
I think the best thing that happened was realizing upvotes don't matter as much as real users. I spent weeks stressing about PH and now I'm just focused on making the product better for the people who actually signed up.
The short update thing is real too. I used to wait until I had something big to say. Now I just post whatever I'm working on. Keeps me accountable.
-
1
"100 active users and 10-15 live at once is actually solid for a quiet launch — especially at 17. That's more than most founders get in their first month.
The PH obsession is real — I've been stressing about it too. But you're right: upvotes don't pay bills. Real users do.
What's your plan for keeping those 100 users engaged? Are you doing anything specific to retain them?"
-
-
-
2
"That's really helpful to hear — especially that you stuck with the hunch until user feedback validated it. I think I've been overthinking the 'perfect' approach instead of just shipping something and seeing what happens.
On documenting in public — I'm still figuring it out too. What's been your biggest challenge with it so far? For me it's been consistency. Some weeks I post daily, other weeks I go quiet for days."
-
1
Honestly? Consistency has been the hardest part for me too. Some days I have a lot to say, other days I just want to build and not post anything.
What helped was accepting that it doesn't have to be perfect. Even a short update is better than nothing.
Also, replying to comments like this keeps me accountable. Feels less like "posting" and more like just having a conversation.
-
-
2
One thing worth an hour before you launch, because it is the single bug in an invoice tool that costs a user real money: does the model compute the totals, or only the text?
"Describe it in plain English and get an invoice" means an LLM is somewhere near the numbers, and arithmetic is the one part that has to be deterministic. The pattern that holds up is the model extracting fields (description, quantity, unit price, rate) and ordinary code doing every multiplication and sum, in integer cents rather than floats. Then assert that net plus tax equals the total before you render, and refuse to produce the PDF when it does not.
Cheap guard, and it fails loudly instead of shipping a wrong invoice that looks perfect.
Great stuff, good luck tomorrow!
-
1
This is gold. Honestly didn't think about arithmetic errors being that specific of a risk until you said it.
Right now the AI extracts fields and the code calculates everything. Totals are computed deterministically, not generated. So the LLM sets the values and the system does the math.
But I don't have a guard that refuses to render if totals don't match. That's going on my list.
Thanks for this. Really appreciate you taking the time to break it down.
-
-
1
"100 active users and 10-15 live at once is actually solid for a quiet launch — especially at 17. That's more than most founders get in their first month.
The PH obsession is real — I've been stressing about it too. But you're right: upvotes don't pay bills. Real users do.
What's your plan for keeping those 100 users engaged? Are you doing anything specific to retain them?"
-
1
"17 and shipping AI tools from Ghana — impressive. I'm building Rallynex for founders documenting their journey in public. One thing I'm curious about: how did you decide to go with 'no account required' for the generator? Was that based on user feedback or a hunch? Also, good luck on Aug 4 — I'll be watching."
-
1
Appreciate that. Rallynex sounds interesting. Documenting in public is something I'm still figuring out.
The no account thing was actually a hunch at first. I kept seeing freelancers bounce off other tools because they hit a signup wall before even trying it. So I thought, just let them generate one invoice first. They can decide later if they want to save it.
User feedback confirmed it. People kept telling me they wanted to try it without committing. So I stuck with it.
Thanks for the good luck. I'll need it. 🙏
-
-
1
Love the conversation happening here. Learning a lot from everyone's perspectives.
-
1
The "no account required" angle is actually perfect positioning for your market. Alfie makes a good point about recurring users wanting more, but from Ghana at 17 you have a distribution advantage incumbents can't match - freelancers in emerging markets are way more price sensitive and skeptical of SaaS signup friction. You're not competing with Wave or FreshBooks on features, you're competing on "works right now, no email spam, no promises". That's a wedge most established tools can't unwind because their whole business model depends on account lock-in. Good luck Aug 4.
-
1
Thanks for this. Really helpful perspective.
The "no account required" thing came from watching freelancers bounce off other tools. They'd land on a page, see the signup wall, and just leave. I wanted to remove that friction completely.
You're right that incumbents can't easily unwind that. Their entire model is built on locking people in. I don't have that baggage, so I can just focus on making it work first and asking for signup later.
Appreciate the encouragement for Aug 4. Nervous but ready.
-
-
1
Respect for the "no account required" call — that's a harder sell than it sounds because it usually means giving up recurring touchpoints with users, but it removes so much friction for a tool people reach for once and leave. I made the same call on a browser extension I'm building (zero network calls at all, not just no account) and it's been the right trade so far.
One thing on the Aug 4 date: if you're also planning to distribute anywhere with a review queue (browser extension stores, app stores, etc.) down the line, build in slack — I'm mid-review on Chrome, Edge and Firefox right now and the timelines have been unpredictable even for a small update. Product Hunt's your own launch day so that part's in your control, but worth knowing early if "launch" ever expands beyond a website you control.
Good luck Aug 4.
-
1
Appreciate this.
The no account thing was a risk honestly. I knew I'd lose some touchpoints but figured the tradeoff was worth it for getting people to actually try it without hesitation.
Good point about review queues. Right now it's just a web app so I control the updates, but down the line if I ever go into extensions or app stores I'll keep that in mind. Hadn't really thought about the timeline variance across stores.
Product Hunt feels like the right first move since I control the launch date completely. Thanks for the heads up on the store timelines though, that's helpful to know early.
Good luck with your extension reviews.
-
-
1
worth thinking about before Aug 4: no-account + client-side PDF means once the tab closes, neither you nor the freelancer has a record of what was sent. for actual invoicing that's a problem beyond UX, most places require sequential/gapless invoice numbers for tax purposes, which needs some server-side state even if you keep accounts optional. could be a lightweight "save this invoice number" ping without full accounts.
-
1
This is a really good point. I've been thinking about the no-account tradeoff and honestly hadn't fully considered the tax side of things.
Sequential invoice numbers are required in most places.
Just to clarify though — Xqivo does have accounts. When you create one, you can save all your invoices, access them anytime from the dashboard, and download them whenever you need. The no-account option is just for people who want to generate a quick one-off invoice without friction.
So the lightweight save option is actually already there. You just need to sign up to unlock it.
Appreciate you flagging this though. It's helpful to know what concerns people have upfront.
-
1
The taste test at the supermarket converts!
-
1
makes sense, that covers the storage side. one thing worth checking separately: does the account flow enforce gapless numbering (no deleted or renumbered invoices, no gaps a tax office would flag), or is it just "save and download"? saving solves the record-keeping half, but the sequence-integrity half is a different guarantee, worth having even if it's just an append-only counter behind the scenes.
-
1
That's a fair point. Right now the account flow saves invoices and tracks them, but I haven't built in explicit gapless numbering enforcement yet. It just assigns numbers as they're created.
You're right that tax offices care about gaps and deleted numbers. Worth adding an append-only counter behind the scenes even if users can still delete invoices from their view.
Adding this to my post-launch list. Appreciate you flagging it.
-
-
-
-
1
"No account required" is a conversion superpower for the one-off user who invoices their friend once. But the freelancer who invoices monthly wants saved clients, recurring templates, payment tracking, and late fee automation. That buyer needs an account. Your positioning is optimized for the user who will never return, while the recurring buyer — your actual revenue source — is being told "this isn't built for people who invoice regularly.
-
1
That's a fair point. I can see how the messaging might come across that way.
The no-account option is for people who just need a quick invoice and nothing else. But the actual product has a full dashboard with saved clients, invoice history, templates, team collaboration, and everything a regular freelancer would need. You just need to create an account to access it.
Maybe I need to make that clearer. The free generator gets people in the door, but the account is where the actual value lives for people who invoice regularly.
Appreciate the honest feedback.
-
1
You’re thinking about it right — the gap is just in who it’s for.
“Quick invoice” attracts one-time users, but the dashboard value is for people invoicing weekly/monthly.
I’d lean into repeat freelancers/agency owners and make that the core story. That’s where retention + revenue comes from.
-
1
That makes sense. I think you're right.
The quick invoice thing is the hook, but the dashboard is what actually keeps people around. I've been leading with the no-account angle because it feels like the easiest way to get people in the door, but I probably need to talk more about what happens after they try it.
Freelancers who invoice weekly or monthly are the ones who actually need the full product. I should make that clearer.
Appreciate you breaking it down like this. Helpful.
-
-
-
-
1
You’ve got both a no-account invoice flow and team collaboration in the same product.
Curious what made you build the team side before launch — did that come from freelancers you spoke to, or from how you expect Xqivo to be used later?
-
1
Honestly, it came from talking to freelancers who work with agencies or have subcontractors.
A few people mentioned they send invoices on behalf of clients or need to share access with a virtual assistant. So I added team collaboration early to cover that use case.
But the main focus has always been the individual freelancer. The team stuff is there for growth, but the core is still solo users who just want fast, professional invoices.
Good question.
-
1
I appreciate you taking the time to explain your thinking.
I'd be interested in continuing the conversation by email if you're open to it. What's the best email to reach you on?
-
1
Appreciate that. I'm always open to good conversations.
You can reach me at briansmithopoku308@gmail.com. Looking forward to it.
-
2
Thanks! I’ve just sent it over.
Looking forward to hearing your thoughts whenever you have a chance.
-
1
ohk cool was waiting but there was no email recieved here
-
1
No worries — I did send it from hello@beryxa.com.
Could you check your spam/promotions folder once? Sometimes first-time emails get filtered there. If it’s still not showing, let me know and we’ll sort it out.
-
-
-
-
-
-
Comment