Swiss invoicing and QR Bills in one guided workflow.
AlpInvoice helps freelancers move from client creation to invoice, QR Bill, and payment with less admin friction. It is multilingual, cloud-ready, and shaped for an internal-first release.
Swiss-first billing core
Client, invoice, QR Bill, and payout-profile flows are designed around Swiss freelancer needs.
Five-language interface
Portuguese, English, German, French, and Italian already ship in the product.
Cloud-ready architecture
Next.js, Spring Boot, PostgreSQL, and Docker fit a low-friction Railway-first launch path.
What this project already shows
AlpInvoice is not just a concept deck: it already ships the core operational flow, a multilingual product surface, and a guarded deploy model for an internal-first release.
Current release posture: internal-first, CHF-first, and deliberately gated until e-mail, storage, and billing go-live checks are complete.
- Core user value stays simple: client -> invoice -> QR Bill -> payment.
- Five product locales already exist for multilingual positioning and onboarding.
- Protected routes, JWT auth, owner scoping, and deploy guardrails are already in place.
- Split Next.js + Spring Boot stack with Postgres, Flyway, and Docker-based deployment.
Core value loop
From client to payment without accounting-style complexity
The product is shaped around the fastest path to first invoice and reliable Swiss payment collection.
Capture the client once
Save structured client data so invoices and QR Bills stay aligned.
Create the invoice fast
Compose billable items, calculate totals, and keep the backend as the financial source of truth.
Generate the right QR Bill
Guide the operator through QR-IBAN, SCOR, or NON paths with backend validation behind the scenes.
Move the customer to payment
Turn the invoice into a payment-ready document instead of another manual follow-up.
Executive and investor angle
Why this can become a strong Swiss freelancer finance product
The opportunity is not generic bookkeeping. It is a focused operational workflow for getting paid faster with less friction.
Built for non-technical freelancers
The UI emphasizes guided flows, not accounting jargon or deep configuration.
Controlled release scope
The first release intentionally stays invite-only, CHF-first, and cautious about externally dependent flows.
Monetization path already exists
Subscriptions and Stripe synchronization are in the codebase, while public checkout can stay hidden until validation is complete.
Operational discipline is already visible
Rate limiting, audit surfaces, health endpoints, and runbooks reduce avoidable launch risk.
Current readiness
What still matters before a broader rollout
The remaining work is mostly environment and operator execution, not a missing product core.
- Public presentation and app shell already support five locales.
- Protected routes, JWT-based auth, and owner-scoped data access are already implemented.
- PostgreSQL + Flyway are the intended production path, with Docker already in place.
- QR Bill rollout still depends on real persistent storage and end-to-end payment-profile confirmation.
- Public billing can remain hidden until live Stripe callbacks and pricing flows are verified.
A credible next step is now an internal deploy, not another concept phase.
Use the product narrative on this page to present the opportunity, then focus execution on Railway, domains, MailerSend, QR Bill storage, and smoke validation.