Building Nvoyce, I hit a decision most invoicing tools get wrong: which payment rails to support.
The obvious move is to lock users into one processor. Cleaner to build, and there's usually a revenue share in it. But almost every freelancer I talked to already had a way they got paid, and it was rarely the same way twice. Some clients Venmo. Some do bank transfer. Some pay a Stripe link without blinking. A designer told me her best client had paid her via Zelle for four years and wasn't going to change for anyone's software.
Honestly the auto invoice generation after a proposal gets accepted is such a time saver, I basically just sent a proposal and the pay link was already in my client's inbox before I even thought about it.
@hilal1o3m This is exactly the moment we built it for 😄 The whole idea was that the second a client says yes, the money part should already be handled, no "let me go make an invoice" tab-switch that kills momentum. Thrilled it landed for you. Thanks for the kind words, Hilal!
The flow from accepted proposal to generated invoice is a really thoughtful touch, saves so much back-and-forth. Love how clean it feels, no extra clicks or filler screens.
@nazarkkpnaa3r5 Appreciate this, Nazar. "No extra clicks or filler screens" is honestly the bar we hold every screen to. Accepted proposal to invoice in your client's inbox should feel like one continuous motion, not a workflow. Glad the polish showed.