Inspiration

Getting paid is the least fun part of being a solo developer. The work ships, then the money stalls in chat threads: "Can you send me an invoice?" — followed by manual invoicing, a spreadsheet you forget to update, and the awkward "just following up…" message you rewrite ten times. I run my own products as an independent developer, and chasing payments eats hours that should go into building. I wanted an agent that treats getting paid like a pipeline, not a chore.

What it does

PaidPilot is an AI payment agent for solo devs and freelancers:

  1. Paste a client message — the messy email or chat where a client agrees to pay.
  2. The extraction engine reads it and pulls out the client name, email, item, amount, currency and due date, with a confidence score, into a pre-filled invoice form you can edit.
  3. One click creates a PayPal order (Sandbox Orders v2 API) and generates the payment link.
  4. An AG Grid dashboard tracks every invoice — draft, sent, paid, overdue — with inline status editing, totals and filters, so "who owes me what" is always one glance away.
  5. For overdue invoices, PaidPilot drafts the follow-up for you — a polite, firm reminder with the amount, due date and payment link, ready to send.

How I built it

Next.js 15 + React 19, all JavaScript. The PayPal integration uses the Sandbox OAuth client-credentials flow and the Orders v2 API, and it is designed to degrade honestly: with no credentials configured it returns a clearly-labelled mock order with the exact same response shape, so judges (and I) can run the full flow anywhere and switch to live Sandbox by setting two env vars. AG Grid Community powers the dashboard — it is the product's control surface, not decoration. The prototype was built with an AI coding agent (DeepSeek V4.1) working from a written spec, and every module was verified with an automated check script (extraction and reminder assertions, 14/14 passing) plus a production build.

Challenges I ran into

PayPal's API shape and a judge-friendly demo pull in opposite directions: a real integration needs credentials a judge won't have. The mock-with-identical-shape pattern solved it — one code path, two modes, zero fake claims. The other challenge was extraction quality: client messages are unstructured, so amounts hide inside "$1,200 USD", dates arrive as "by Nov 20", and the item is whatever follows "for the…". A deterministic, test-covered extractor beat a vague prompt here.

Accomplishments that I'm proud of

The full loop — message in, money tracked, late payer chased — works end to end today, verified by automated checks rather than hope. And the architecture leaves a clean seam to plug a live LLM into the extraction step without touching the rest.

What I learned

Payment UX is mostly psychology: the invoice is easy, the follow-up is the product. Building the reminder generator taught me more about why freelancers get paid late than the payment API did.

What's next for PaidPilot

Live LLM extraction as an alternative engine, PayPal webhooks so "paid" updates itself the second money lands, invoicing API support, and multi-currency reminder tones (polite → firm) based on days overdue.

Built With

Share this project:

Updates

Submission history