ZenBookr - Sell Project
Listed August 28, 2026
About ZenBookr
Complete booking SaaS for beauty & wellness pros — live on 3 domains
Project details
Website: https://zenbookr.app
Next step: <p>The single highest-leverage action is switching payments on. The billing engine is built, tested and wired to live Stripe — it has never been activated because I never completed my VAT registration. For a buyer who already has a company, that is an administrative step, not a development project.</p><p><br></p><p>After that, in rough order of effort versus return:</p><p><br></p><p>1. ACTIVATE THE SEO ASSET THAT IS ALREADY BUILT. Server-side prerendering of public professional pages at /p/{slug} gives every professional their own indexable local landing page. The function is written and passes 96 tests; it needs one rewrite rule in firebase.json plus a profile sitemap. This is roughly half a day of work for the largest organic-growth lever in the product.</p><p><br></p><p>2. SELL WHITE-LABEL TO AGENCIES. The architecture is multi-tenant on Firebase with three separate domains already in production, which is exactly what an agency reselling to salons needs — they do not want to host anything. Comparable white-label tooling sells at USD 300-500 per month per agency licence.</p><p><br></p><p>3. TURN ON THE UNUSED REVENUE PATHS. Marketplace commission logic exists but is disabled with an early return, and Stripe Connect currently runs with application_fee_amount at zero, so professionals keep 100% of what they process. Both are days of work. The honest caveat: "zero commissions" is currently a public promise on the site and in the terms, so activating either needs a contract change with notice.</p><p><br></p><p>4. SHIP THE MOBILE APPS. Android and iOS projects are scaffolded but were never published. They need Firebase config regeneration, Sign in with Apple, and store submission — one to two weeks plus review time.</p><p><br></p><p>5. BUILD THE ITALIAN MOAT. The product has no e-invoicing, and electronic invoicing to the SDI system is mandatory in Italy. Adding it is the difference between a booking tool and the only software a salon needs. It is also precisely the kind of national regulatory complexity that foreign competitors do not replicate quickly.</p><p><br></p><p>MARKET CONTEXT WORTH KNOWING: Uala, the one well-funded independent Italian player in this space, was absorbed into Treatwell in 2022. Italy is now served entirely by foreign operators — Treatwell, Fresha, Booksy — with no independent local champion, while the incumbents monetise through commissions that small salons resent. Planity has publicly stated its intention to expand into Southern Europe and has no Italian presence. There is a real opening here, and a product already localised to take it. I am simply not the one who can.</p>
For sale
Asking price: $13,000 USD
What's included
Domain name, Source code, All related data, All related design work
Everything needed to run and continue the product: • Full source code — Flutter Web app, 112 Cloud Functions, Next.js marketing site (97 pages, IT/EN/DE), and a separate Next.js API on Vercel (waitlist, contact forms, AI support chat) • The zenbookr.app domain and all subdomains • The Firebase / Google Cloud project, transferred as a whole: Firestore, Storage, Auth, hosting targets, 65 declared indexes, scheduled jobs • Supporting accounts: Brevo (transactional email), Sentry, Google Analytics 4, Search Console, Vercel • The registered Wikidata entity for the brand • Design system, logo, brand assets, and 5,000 lines of design handoff documentation • Complete EU legal pack in three languages — privacy policy, separate terms for professionals and consumers, DPA, DSA page — ready to be re-issued under the buyer's entity • A signed inventory of every credential and account, handed over via a password manager • 30 days of email support after closing ON EXISTING USER DATA: the beta accounts and their data live inside the Firebase project, so they transfer with it. The professional terms of service already contain an assignment clause permitting transfer to a third party as part of a business transfer with 30 days' notice, which removes the usual M&A blocker. Registered users must be notified of the change of data controller under GDPR — a closing task, not an obstacle. If you would rather start from a clean database, that is equally fine and simpler: there are only 15 accounts and no revenue attached to them. NOT INCLUDED: my personal Stripe account. It is tied to my identity and bank details and is not transferable. Payments were never activated, no Connect account was ever onboarded and no money ever moved, so there is nothing to migrate — you create your own Stripe account and replace three keys. The README documents exactly which ones.
Reason for selling
I am a solo developer and I have run out of time for it, not out of belief in it. Building it was the part I could do alone; taking it to market is not, and I would rather hand it to someone who can than watch it sit still. I am not selling because of a technical problem, a legal problem, or bad numbers. The honest reason is simpler: the product is finished and I am not the right person to launch it.
Project metrics
Average Monthly Visitors: Under 1K/mo
Average Monthly Revenue: Pre-revenue
Average Monthly Downloads: Pre-launch / New project