LIVE
SAAS · MSP BILLING
Billwaze
Cloud billing for MSPs and IT consultants. Invoicing, payments, time.
● SERVICE · SAAS DEVELOPMENT
We operate four SaaS products of our own.
We know what month seven looks like.
Most agencies pitch how they'd build your SaaS. We've already done it — four times. We're still on call for them at 9 AM Tuesday.
4
SaaS in production
10,300
Active users
12
Countries served
2022
Est. Prague
● CHAPTER 01 / IS THIS YOU?
Three kinds of teams hire us for SaaS.
EARLY STAGE
Founders raising seed or Series A
You have an MVP that works, but you know the second version needs proper architecture. You want a team that's shipped this exact problem before, not "learned on your project."
SCALING UP
CTOs migrating monolith to multi-tenant
Your product works but it's bursting. Database is too hot, deployments are scary, every new client takes a week to onboard. You need someone who's done multi-tenant the right way.
BOOTSTRAPPED
Teams pushing toward sustainable MRR
You're profitable but feature velocity has stalled. Tech debt is real. You need senior hands that can ship without breaking what's already working.
If any of this sounds like you — we should talk.
Book 30 minutes
● CHAPTER 02 / WHAT YOU GET
Concrete things.
Not "scalable solutions."
Multi-tenant architecture
Row-level or schema-level isolation. Tested at scale.
Billing infrastructure
Stripe, Paddle, or LemonSqueezy — connected to your domain model.
RBAC with audit trail
Every action is owned. Every change is recoverable.
Background job queues
Workers, retries, dead-letter handling. The unsexy parts.
Observability from day one
Metrics, traces, alerts. You'll know when something's wrong before users do.
Customer onboarding flows
Activation that actually activates. Not a 14-step wizard.
Webhook ingestion + retry
Because external systems will fail. You'll handle it gracefully.
Admin tools for your support
They shouldn't need engineering to refund a customer.
● OUR TEAM
One engagement.
Eight disciplines.
You don't coordinate a roster of freelancers. You get one cross-functional team with a single delivery manager answering to you. Engineering, design, QA, marketing, and executive oversight — fully handled.
CTO
Technical Director
Architecture decisions, code quality, technical strategy. The engineering starts and stops here.
PDM
Delivery Manager
Your single point of contact. Scope, timeline, and budget — owned by one person.
DEV ×2
Senior Developers
Two senior engineers on every build. No juniors carrying the core product.
UX/UI
Product Designer
Design grounded in user research. Prototyped, tested, then built — not decorated after.
QA
QA Engineer
Testing before your users ever see it. Bugs caught in staging, not in production.
MKT
Marketing Specialist
Go-to-market strategy and analytics built alongside the product, not bolted on after launch.
CEO
Account Director
Executive oversight on every engagement. When escalation is needed, it reaches a decision-maker within hours.
● ON-SITE VISITS
We come to you — if that helps.
When it makes sense, we visit your location before writing a single line of code. We sit with your team, watch how the business actually runs, and talk to the people who live in the problem every day. It's not a sales call. It's a listening exercise. The domain understanding you get from two days on-site takes months to build over video calls — and it shows in the product.
● CHAPTER 03 / RECEIPTS
Four SaaS we operate ourselves.
Not case studies for hire. Real products, real users, real on-call rotation.
LIVE
SAAS · BEAUTY CRM
MoonBeauty
CRM for beauty salons. Appointments, staff, finances, AI features.
↗
LIVE
SAAS · LOCAL BUSINESS
MoonLinks
One QR code. All your business links. Mini-website in 2 minutes.
LIVE
SAAS · HOSPITALITY
VNP Solutions
Revenue recovery for hotels. Finds billing gaps in OTA transactions.
● CHAPTER 04 / HOW WE WORK
Five stages. Same rhythm for every SaaS we ship.
01
DISCOVERY
1–2 weeks
WE DO
Map your domain. Interview your users. Find the constraints that matter.
YOU GET
Written specification, architecture sketch, honest assessment of effort.
02
ARCHITECTURE
2–3 weeks
WE DO
Database design, service boundaries, infrastructure plan. Decisions documented.
YOU GET
Architecture document, infra-as-code skeleton, cost model.
03
MVP BUILD
8–12 weeks
WE DO
Core flows. Auth, billing, the one feature that defines your product.
YOU GET
Working software in staging every week. You ship to beta when you're ready.
04
BETA
4–8 weeks
WE DO
First customers. Real workloads. Fix what breaks under traffic.
YOU GET
Production-grade system, on-call playbook, operations dashboard.
05
SCALE
Ongoing
WE DO
Features, infrastructure scaling, technical coaching for your team.
YOU GET
Predictable monthly engagement, optionality to take it in-house.
● CHAPTER 05 / HOW WE SCOPE
Every SaaS is different. So is every engagement.
We don't publish prices because we don't sell packages. Here's how we figure out what your project actually costs.
01
Discovery sprint
A short fixed-price engagement to understand your problem. You walk away with a written spec — whether or not you continue with us.
02
Scoped build
Once we know the shape of the work, we propose a fixed scope with milestones. Predictable. No surprise invoices.
03
Ongoing engagement
After launch, most clients stay on a monthly engagement. Predictable team size. You can pause or take it in-house anytime.
● CHAPTER 06 / WHAT YOU MIGHT BE THINKING
The honest answers.
Probably yes, compared to a freelancer or an offshore shop. Probably no, compared to hiring two senior engineers for a year. The right comparison is: what's the cost of getting it wrong? We've seen rebuilds cost 3× the original budget. Our work tries not to need rebuilding.
Fair question. Two answers:
First — we've been around since 2022. We're not going anywhere because we operate seven products that depend on us being here.
Second — every line of code is yours from commit one. You can take it in-house, hand it to another team, or pause us anytime. No lock-in.
First — we've been around since 2022. We're not going anywhere because we operate seven products that depend on us being here.
Second — every line of code is yours from commit one. You can take it in-house, hand it to another team, or pause us anytime. No lock-in.
Our CTO does — and they're on every engagement, not just the kickoff call. Architecture decisions, code quality standards, and technical strategy are owned by a single person who has shipped SaaS four times. If you have your own CTO, they collaborate. If you don't, ours fills the gap until you're ready to bring technical leadership in-house.
No. About half our engagements are alongside existing teams. We come in for a specific capability — multi-tenant architecture, infrastructure overhaul, a feature your team doesn't have time for. We work as part of your team, not against it.
You don't, not from a website. The honest answer: book a 30-minute call. We'll talk about your specific problem. If we're not the right team, we'll tell you and recommend who is. About 40% of inbound, we say no to. The point isn't to win every deal — it's to do well on the deals we win.
It will. Scope always changes. Our rule: if changes exceed 20% of agreed scope, we stop and re-estimate. No surprise invoices, no scope creep silently absorbed. You get a new scope document to sign off on.
● CHAPTER 07 / FAQ
Practical questions.
For a typical multi-tenant SaaS — 3 to 4 months from kickoff to beta. Faster if scope is well-defined, slower if we're still discovering the domain.
Yes. From the first commit. Repository in your GitHub org, licenses are yours.
Yes. We start with a code audit (1 week, fixed price) — assessment of state, debt, and what's worth keeping. You decide what to do with the findings.
We pick technology after we understand the problem. Most of our SaaS work has been in mature, well-supported stacks. We're not religious about frameworks — we're religious about boring choices that work in five years.
Yes, mutually. Send yours or use ours.
Every engagement includes: CTO, Delivery Manager, two senior developers, product designer, QA engineer, marketing specialist, and account director. You don't manage roles — you talk to the delivery manager and the team handles everything else.
Prague, Czech Republic. Most clients are in EU and US time zones. Asia-Pacific clients work with our Vietnam-side team.
You can pause anytime. We document where we left off, hand over all access, and you're free. No notice period clauses, no penalties.
● CHAPTER 08 / WRITING
Deeper reading.
01
Scaling SaaS to 10K tenants
What we learned operating Billwaze across 12 countries.
→02
Multi-tenant architecture: three approaches we tried
Row-level vs schema-level vs database-per-tenant. What we kept and why.
→03
The unsexy work that keeps SaaS alive
Backups, observability, audit logs. The boring infrastructure that decides survival.
→Tell us about your SaaS.
Whether you're starting from scratch or salvaging something that's bursting — we've probably seen the shape before.
REPLY IN 4 BUSINESS HOURS · NO SALES PIPELINE · MAYBE WE SAY NO