My own product

Simple invoicing for independent businesses.

Preparing an invoice, taking payment, and knowing what still needs attention belong to the same business workflow. I built PaySegue to connect those steps, with a straightforward payment experience for the client and an invoice history for the business.

Payment is part of a longer workflow.

An independent business needs to set out the work, send the invoice, and see what has been paid. Its client needs to understand the amount and complete checkout. The application also has to account for failed payments, refunds, and voided invoices when the process takes a different path.

Build around the invoice and its history.

I brought customer details, line items, pricing, and payment terms into one editor, with a summary of the total and estimated processing costs before sending. The client can review the invoice and pay through Stripe without creating an account. Funds go directly to the service provider’s connected payment account.

I built the application around payment transitions so that a successful payment, failure, or refund is part of the invoice’s history. Invoice and receipt emails support the same workflow, with the business able to see what needs attention.

From draft to paid, with every exception recorded.

A business can prepare an invoice, send it by email or share its payment link, and follow it from draft through sent, viewed, and paid. Failed payments, refunds, and voided invoices remain recorded with it.

The full application, end to end.

I handle the invoice interface, application services, database, Stripe integration, invoice and receipt emails, and the development and release workflow. Testing and review focus on the transitions where a mistake could affect a customer’s invoice or payment record. I use AI in development, and I own the decisions and the delivered work.

Where this applies to your product.

If your product connects customer actions with payments or business records, I can help you map the whole workflow, decide how exceptions should behave, and build the interface and integrations together. The work includes what happens after the initial transaction.

4+ months of sustained development to build and launch PaySegue, with ongoing development and maintenance.