Why I built Algorithm Invoice
I’ve worked in the music industry for decades — recording, touring, and everything in between. One constant truth: artists still need clean, reliable invoices to get paid. After trying off-the-shelf software and commissioning developers (with mixed results), I decided to take control: I learnt ASP.NET Core, HTML, CSS, JavaScript, C# (and more), and built this product from the ground up.
The goal is simple: a calm, accurate tool that respects the way musicians work — whether you’re billing for a live date, a studio session, a lesson, or a licensing fee.
Founder’s Statement
Algorithm Invoice was created out of necessity, persistence, and lived experience.
While learning to write software, I initially explored working with external developers and existing platforms, following the well-established principle that good engineers do not reinvent the wheel. My intention was never to copy or appropriate others’ work, but to collaborate legitimately, build on open standards, and deliver a reliable tool for my own professional needs.
That path proved unworkable. I encountered unreliable operators, failed engagements, and an environment where meaningful collaboration was either unavailable or discouraged. In many cases, the message was simple: build your own. In retrospect, that advice was both fair — and formative.
What followed was a deliberate decision to take full ownership of the problem. I chose to deepen my technical understanding, design the system end-to-end, and build the software from first principles. Working alone allowed me to move at the pace my ideas required, make architectural decisions without compromise, and create something that genuinely reflected how I think, work, and operate a business.
Algorithm Invoice is the result of that process. It is not theoretical software — it is shaped by real contracts, invoices, credits, payments, audits, and day-to-day operational realities. It is software I built for myself, because I needed it to exist — and because nothing available at the time met the standard I required.
I am proud of what has been created. My hope is that others find the same value in Algorithm Invoice that I do: a clear, dependable, and thoughtfully designed tool that respects both creativity and business discipline.
Dr Dennis J. Gordon
Founder, Algorithm Invoice
For musicians, by a musician
Built from real touring and studio workflows—then polished into a clean, reliable invoicing platform for everyone.
- Fast, professional invoices with clear subtotals, VAT/tax support (where relevant), and a layout clients immediately trust.
- Built-in contracts & terms — attach an agreement directly to an invoice so expectations are clear before payment. (Optional signature fields.)
- Send invoices straight from the app with branded emails and downloadable PDFs — no exporting or third-party tools required.
- Smart reminders & follow-ups — schedule polite chasers for unpaid invoices without copy-pasting or awkward emails.
- Clients that reflect real life: promoters, labels, venues, schools, private clients, agencies, and more.
- Remittances (Pro) — track payments across multiple invoices, allocate part-payments correctly, and keep your accounts clean.
- Purchase Orders (Pro) — raise and manage POs for suppliers, collaborators, and production costs, all in one place.
- Free by default — every account receives one free invoice credit each month. For many users, that makes Algorithm Invoice effectively free to use.
- Upgrade only when it makes sense — subscriptions and credits are fully flexible. Upgrade, downgrade, or cancel any time with no lock-in.
- Sign-in safety built-in — optional 2FA plus IP and device awareness, with friendly alerts when something changes.
- Also trusted by freelancers, agencies, coaches, photographers, and trades — anyone who values clear, professional billing.
How it was built
Built on ASP.NET Core with a focus on reliability, performance, and clarity. The app uses clean, accessible frontend patterns and keeps personal data to a minimum.
- ASP.NET Core Identity with two-factor authentication (2FA).
- Role-aware areas for Admin where needed.
- Optional GeoLite2 on the server to offer approximate location for security events.
Our ethos
- Privacy first: sensible defaults, clear controls, no unnecessary data.
- Clarity: plain English, British spelling, no dark patterns.
- Fairness: easy cancellations, straightforward refunds (see the Refund Policy).
Branding & content tips
Quick pointers so invoices look sharp on the web and in PDFs.
- Logo uploads: transparent PNG preferred; ~600–800 px wide. Keep file size under 500 KB.
- Fallback logo: we may use a subtle app default, but your own logo will always look best.
- Signature block: optional—use simple HTML or plain text. If you include an image, keep it small.
- Contract/Terms paging: use shorter paragraphs for cleaner page breaks in the PDF.
- Links: use full
https://URLs. - Characters: paste as plain UTF-8. Avoid curly “smart quotes” from Word.
- Use
<strong>,<ul>,<a> - Prefer 2–5 short paragraphs
- Short lines (60–90 chars)
- Break up long lists with bullets
Browser note
All browsers behave slightly differently when rendering HTML, printing PDFs, or handling animations. For the best and most consistent experience with Algorithm Invoice, we currently recommend using Microsoft Edge.
Contact
Press or partnership enquiries, or just to say hello: support@algorithminvoice.com.
