Inspiration
An unpaid invoice tells only part of the story. A customer may be late but satisfied—or fully paid and ready to walk away.
I created Nalbace to help busy business owners recover payments without losing sight of their customer relationships. Its purpose is to keep routine follow-up moving while bringing disputes and customer concerns to the owner’s attention.
What it does
Nalbace brings PayPal invoice information, customer conversations and payment-review tasks into a phone-first workspace.
- Today prioritizes accounts needing attention.
- Messages and History preserve customer responses and owner actions.
- Reminder workflows demonstrate scheduled emails and an optional AI call, controlled by customer-level preferences.
- Disputes and payment claims pause follow-up for review.
- Payment verification stops payment follow-up when the balance is settled.
The owner remains responsible for resolving disputes. AI does not decide whether a customer owes money or change payment facts.
How I built it
I built the local application with Next.js, TypeScript and SQLite. PayPal Invoicing supplies sandbox invoice and payment information.
The integrations include Amazon SES for controlled email delivery, Gmail for matching test replies, and Retell AI for a consented, bounded phone test. A Claude adapter supports structured suggestions with exact supporting quotes for owner review.
Routine scheduling and financial checks use deterministic rules. AI is reserved for language and conversation.
What I tested
I verified a PayPal sandbox payment returning a paid status and zero balance, with further reminder preparation blocked.
An authorized test email reached the designated inbox, and a customer reply was matched to its case. A separately authorized AI phone call captured a dispute and returned it for owner review.
The clean source installation passed 207 automated tests and a production build. The recording distinguishes simulated reminder schedules from actual provider tests.
Challenges and lessons
The hardest challenge was making automation useful without creating more work for the owner. Repeated walkthroughs led to clearer priorities, simpler customer preferences, readable conversation history and visible workflow progress.
Another challenge was keeping financial evidence separate from customer statements. “I paid” must trigger review, not automatically mark an invoice paid. A dispute must stop routine pursuit rather than trigger another reminder.
I also learned that relationship health and payment status are different: a settled balance does not necessarily mean a resolved customer concern.
What’s next
Nalbace is a functional local prototype, not a production service. Next steps include secure multi-business access, production merchant onboarding, continuous scheduling and reply handling, authenticated provider callbacks, and further usability testing.
The goal remains simple: recover payments while keeping vital relationships on course.
Built With
- amazon-ses
- anthropic-claude
- css
- ffmpeg
- gmail-api
- google-oauth
- next.js
- node.js
- paypal
- paypal-invoicing-api
- react
- retell-ai
- sqlite
- typescript