Loading page…
A payment-first accounting layer matches shop and SaaS transactions to invoices, archives, and tax-ready exports.
3 paying customers · €9/month base fee + 15 cents/invoice (volume price down to €0.03)
Start with the payment, prove which order it belongs to, then give the tax adviser an export that raises no follow-up questions.
Fewer bars = easier, cheaper, or faster for an AI-assisted solo builder. Editorial judgments based on the case details.
Christian built Rechnungskit to solve his own e-commerce accounting problem at Happy Coffee. Existing tools handled pieces of the workflow, but he wanted to trace every payment to its order, invoice, required records, and tax export. He rebuilt that process from the payment outward, then turned it into a SaaS product for online shops, software businesses, and digital-product sellers. It supports integrations for Shopify, WooCommerce, Shopware, and an API, with payment connections and checkout features added as customers ask for them. A sandbox lets merchants test real data without sending invoices to customers. Christian says the first bill was €0.60, three customers were paying, 50–60 leads had come through LinkedIn, and larger shops in testing processed 8,000–10,000 invoices monthly. He charges a €9 base fee plus usage, with volume pricing. The product is early: its strongest assets are a specific workflow, direct founder support, and a clear trust story around archiving and security.
Christian says all 50–60 signups or leads he had counted came through LinkedIn. He posted relevant material two or three times a day for months, with roughly 4,600 contacts or followers and weekly reach of 20,000–50,000 people.
The quick-reference card — acquisition channels, replication playbook, risks & traps, and our verdict — is members-only.
Join the Unicorn Club — $5/moCancel anytime, in one clickPaste into Claude Code / Codex and get a working version of this product end-to-end.
Two production-grade prompts per idea — a full build spec and an SEO growth plan — plus 10 tailored build specs a week. Members only.
Join the Unicorn Club — $5/moCancel anytime, in one clickEvery claim traces back to a listed source — open any of them and check the number yourself.
Data credibility: Christian reports the customer count, €0.60 first bill, pricing, LinkedIn lead totals, and Search Console figures in an interview; none are independently audited here. Treat the payment count and prospective test volume as founder-reported, not verified recurring revenue. Legal-compliance and security descriptions are also founder claims and need independent review.
The first customer booked on the last day of a month. Christian recalls that the account displayed two or three invoices or similar items.
Rechnungskit's early loop connects customer learning, product coverage, and founder-led content. Happy Coffee served as the first internal user, exposing the need to match payments with orders and produce a usable tax export.
At the interview stage, Rechnungskit had three paying customers, about 15 shops expected to move soon, and 25–30 more interested but not yet into active testing. That is a long evaluation queue for a product touching invoices, payment records, and archived data.
Rechnungskit is a payment-first accounting and invoicing workflow for online shops, SaaS businesses, and digital-product sellers. It starts with a payment from a processor or account, finds the order or billing record that explains it, applies the relevant transaction details, and prepares information for tax-adviser processing. It can produce e-invoice material, retain an immutable archive, and export data to DATEV. Its sandbox supports realistic testing of cancellations, credits, discounts, and international billing without sending documents to customers. Integrations named in the interview include Shopify, WooCommerce, Shopware, an API, and multiple payment providers. Our read: the core product is a reconciliation and evidence layer, not simply another invoice editor. The narrow promise should stay visible in onboarding: connect a source, match a payment, inspect exceptions, and preview the final export. That sequence lets a finance operator judge value before moving a live process. Legal formats and retention settings should be versioned and reviewed by qualified professionals as rules change.
The pricing described is a €9 monthly base fee plus usage, starting at €0.15 per invoice and falling to €0.03 at higher volume. Christian said the base fee is waived in a customer's first month. The first bill was €0.60, and three customers were paying at the time of the interview. He also expects the archive to remain a paid service for customers who cancel but still need retained records; customers have 90 days to download their archive after cancellation. The model combines a recurring platform fee with transaction-based pricing and ongoing archive value. Our read: this can align price with merchant activity, but the service must keep its variable infrastructure and support cost below the per-invoice contribution. High-volume shops processing 8,000–10,000 invoices a month were in testing, not yet reported as live revenue. Use actual retained-customer data to test whether the base fee, volume tiers, and long-term archive plan pay for compliance support and storage.
Christian says he built the product with AI coding tools and SvelteKit, and describes an infrastructure using Hetzner, Bunny CDN, and write-once-read-many object storage for archived records. He says backups run at least every 60 seconds, with another daily copy in Finland and client-side encryption. The product includes payment-provider and shop integrations, a sandbox, security documentation, and a DATEV export. His development process includes local testing, smoke tests, security checks, and a reversible deployment approach. The interview gives no hosting bill, support cost, gross margin, or retention data. Our read: transaction volume can make the product more valuable while increasing archive and support obligations. Model storage, reprocessing, failed imports, and customer onboarding before treating the low per-invoice price as scalable. Keep a transparent recovery process and test restored data; for a product that holds accounting records, operational trust is part of the feature set, not an infrastructure footnote.
Copy the payment-first framing and the decision to build from a real internal workflow. Rechnungskit began with a founder who needed his own shop's payment, order, invoice, and tax-export chain to work; that gave him concrete edge cases and an initial operating environment. Copy the sandbox too: it lets a prospect check their own data before a risky cutover. The founder's comparison pages and security documentation also answer the questions a cautious buyer will ask. Our read: start with one commerce platform and one payment source, then add only the connectors requested by active test users. Do not imitate the product's broad ambitions before proving that matching accuracy, export quality, and support time work for a narrow buyer. Give tax advisers a reviewable sample and make the process reversible. The first product promise should be less cleanup and fewer unanswered questions at month end, with every compliance statement backed by current legal review.
The product operates near legal requirements, financial records, and customer payment data. A wrong invoice classification, incomplete archive, or failed migration could damage trust quickly. Regulations and e-invoice formats can change, so the founder's descriptions need continuous professional review rather than being treated as permanent rules. The breadth of integrations also creates maintenance work, while the current sales process involves hands-on testing and adviser conversations. Low per-invoice pricing could be strained by support and storage costs, particularly for customers with complex historical data. Search impressions are not yet signups, and the larger shops cited are still testing. Our read: the most serious risk is promising an effortless compliance outcome before the product has proven every relevant case. Keep claims precise, log every transformation, preserve the source data, and make exports easy to inspect. The business will live or die on accuracy, migration confidence, and customer renewals—not on how quickly another connector can be added.
The four founder playbooks — first customers, first dollar, the flywheel, the silent stretch — are in the Unicorn Club, on this idea and on all 1,435 others. The story, the numbers, the sources and every later section stay open to everyone.
Join the Unicorn Club — $5/moCancel anytime, in one click