Why we built Clientflow
A growing service business often ends up with ten programs that don't talk to each other — calendar here, invoice there, leads in the inbox, routes in your head. This is the story of why we built one place for the whole thing, what it covers, and who it's for.
Where it started
My name is Daniel, and I'm a co-founder of Clientflow. My co-founder is Thomas Sparegodt — he writes the code, I handle brand, marketing and sales. We built Clientflow because we got tired of watching service businesses spend half their time juggling programs that were supposed to make work easier.
In our first conversations with Danish window cleaners, cleaning companies and plumbers, the same picture kept showing up: a Google calendar, a customer Excel sheet, an SMS thread with the team, invoices in Dinero, leads in the Facebook inbox, and a sticky note on the kitchen counter with customers to call back. Ten programs. None of them talking.
It's not a tools problem. It's a data problem. Every time a customer calls and you have to look in three places to find what they last had done, that's data not aligned. We built Clientflow to put it all in one place — and to make creating a customer, planning a route and sending an invoice as fast as writing an SMS.
Our thesis
Service businesses need something that is operational — not just a CRM, not just a calendar, not just an invoicing program. It has to be all three at once. When a field worker opens his phone at 7am, he should see his day plan with customer addresses, job descriptions and contact info. When a customer calls at 2pm, you should be able to open his card and see him, his subscription, last visit and what he owes.
That's what Clientflow is. One operating system for the whole service business — from the first lead landing in the pipeline, through the route, the day, the invoice and the payment. If you want a fast comparison of how we sit against competitors, see our guide to window cleaner software in 2026 — it covers Clientflow and most Danish alternatives.
What Clientflow consists of
We've built Clientflow around modules, each covering one area of the operation. They're deliberately designed to play together — so data from a lead flows into the customer card, the route knows about subscription agreements, the invoice knows about the job. Here's the short tour of the main ones:
- Leads & pipeline. Captures leads from the website, Facebook and phone calls. Tracks them from first touch to signed agreement. We go deep in our article on lead systems for service businesses.
- Route planning. AI optimizes the routes every morning — or every time you add a new job. For window cleaners it's typically 25–35% drive time saved. Read our deep dive on route optimization.
- Day plan. The field worker's mobile app. Today's jobs, navigation, check-in, photo, notes, completion. Built to work in five seconds between two jobs.
- Fleet & GPS. Real-time overview of where the team is. Used for customer service (precise ETAs), payroll and documentation. We wrote a GDPR guide for GPS tracking — there are rules, and you should follow them.
- Communications. SMS, email and calls collected per customer. Templates for the repetitive messages. No mixing of private inbox and company communications.
- Reports. Revenue per customer, margins per route, performance per employee. Numbers you can act on — not pivot tables.
- Customer registry. The heart of the system. All customers, subscriptions, contact info and service history. Built so creating a customer is faster than typing them into Excel.
- Workflow & automation. Recurring routines run automatically. Reminder 2 days before visit, invoice 1 day after, follow-up 7 days later. Set up the rule once. Read how we think about recurring contracts.
- Invoicing. Invoice straight from the job, synced to Dinero, Billy or e-conomic. MobilePay on the invoice so the customer pays in 10 seconds. More on automatic invoicing for service businesses.
- AI assistant. Our newest addition. It suggests replies to customer enquiries from the customer's orders, appointments and your prices, plus the actions that go with them — which you carry out in one click. You always send yourself.
Who is Clientflow for?
We've built Clientflow for a specific type of business: field-based service companies with 1–50 employees in Denmark. That includes window cleaners, cleaning companies, landscapers, pest control, plumbing, electricians and HVAC firms.
The common trait is physical customers with addresses, employees who drive out, and recurring services — either as subscriptions or repeat projects. Clientflow isn't built for hourly desk-based sellers or for e-commerce. If you wake up planning where people should go, that's you.
The classic case is a window cleaner with 3-8 employees, recurring subscription agreements, and a mix of private and commercial customers. We've written a full CRM guide for window cleaners if that's your trade. We've also migrated customers from Fenster, Workmaker and other niche tools — typically as the businesses outgrew them.
What we've held on to
When you build software for people standing with wet water and a squeegee in hand, the principles are different than for desk workers. Here's what we've held on to:
- Mobile-first actually means mobile-first. Half the day is on a phone in a car. If it doesn't work on 4G, it doesn't work.
- Fast beats fancy. Creating a customer should be done in under 20 seconds. An invoice should be sent before the worker has driven on. Every click costs.
- Danish from the ground up. We wrote Clientflow in Danish for Danish conditions. That means Danish invoice format, Danish SMS provider, Danish support — and that we understand why CVR matters for recurring contracts.
- Open pricing, no surprises. You pay a fixed base price for the company plus a fixed amount per user — and all of it is on our pricing page, not in a quote you have to ask for first.
- No 12-month lock-in. You pay one month at a time. If we don't deliver, you walk. That simple rule has shaped how we think about support, onboarding and product decisions.
The tools we connect
We've deliberately chosen fewer, deeper integrations over having a hundred half-baked ones. They work two-way so data doesn't end up out of sync at some point:
- Dinero, Billy and e-conomic for bookkeeping. Customers and invoices stay in sync both ways.
- MobilePay on the invoice. The customer taps, payment lands, reconciliation is automatic.
- Skråfoto so window cleaners and facade firms can see the property before quoting.
- Meta (Facebook & Instagram) so leads from ads land directly in the pipeline — not in an inbox no one checks.
The problems we go after
Instead of saying 'Clientflow does everything', we've tried to be concrete about which operational problems we solve. Each of these deserves its own article — and has one:
- Route optimization. Manual route planning typically costs 20-30% in unnecessary drive time. AI does it in seconds. We've measured it concretely for window cleaners.
- Recurring contracts. Fixed customers with fixed cycles need to be handled differently than one-off jobs. That means price versioning, price increases and cancellation rules.
- GPS tracking & GDPR. You're allowed to track company cars — but not without consent, and not outside work hours. We've built it to comply with the rules.
- Urgent dispatch. When a customer calls at 2pm about a water leak and you need a plumber there by 3. That case demands a completely different workflow than planned service.
- Lead management. If you don't have a system, you typically lose 30-50% of leads in the cracks. What we wrote about here.
- Customer portal. Customers in 2026 prefer to handle things themselves — booking, paying, history. It's a competitive edge if you offer it.
- Automatic invoicing. The invoice tail after a job typically takes 15-20 minutes per job if done manually. That's weeks per year.
What we're working on now
We're a small team. It's Thomas, me and a small circle around us. That means we've chosen to go deep on fewer things rather than broad on everything. Right now the focus is three areas: making AI features actually useful day-to-day (route calculation, quote drafts, automation), expanding reports so they become a real decision tool, and bringing more trades on board — we've just started conversations with electricians and HVAC.
If you're curious how we think about pricing and packaging, the pricing page is the most up-to-date place. If you want to dig into how it feels to use the platform day to day, the help center is where we've written down the practical guides — like how to set up a subscription, plan a week in the calendar or create a lead form that works.
If you want to try it
The fastest way is to create an account. We've made it so you can get started without a consultant — you can click through setup in a morning. If you're already on another system, we move your data for free — typically 1-2 business days, no lost history.
If you'd rather talk to us first, write. I answer all emails myself, and Thomas jumps on a call if you have technical questions about migration or integrations. We don't have salespeople — it's just the two of us and the product.
A final word
I know a software platform isn't the most dramatic subject to write a long article about. But service businesses are the heartblood of the Danish economy, and we believe the hour lost every day on bad tools is an hour that could have gone to family, customers or craft. That's what we're trying to build — a tool that gives time back.
If you have questions, ideas, criticism or stories from your own business, write. That's how we get better. Thanks for reading.
— Daniel
Read also
- From 10 programs to one — what it really means
- Lead system for tradespeople and service businesses
- Route optimization for window cleaners — how AI plans the day
- Automatic invoicing for service businesses
- 5 signs your service business is ready for one system
- Switching to Clientflow — we move your data for free
- All modules in Clientflow