Four years. It's both a short time and a long time. A short time, because a company that builds a management tool is never truly finished. A long time, because these four years have confronted us with realities we couldn't have anticipated from a blank canvas. We listened, adjusted, and sometimes started from scratch. Here's what this adventure has taught us.
Four years, and a conviction that hasn't wavered.
When we started building Djaboo, we began with a simple observation: the leaders of very small and small businesses spend a disproportionate amount of their energy managing tools, rather than developing their business. Not because they lack rigor, but because the available solutions have long been designed for large structures, with complex interfaces, mandatory training and costs that do not correspond to the reality of a small team.
Our initial conviction was this: a manager of a very small or small business should be able to register a client and send an invoice in less than two minutes, without any technical or accounting skills. This conviction hasn't changed one bit in four years. What has evolved is our understanding of what this means in practice, feature by feature, user feedback by user feedback.
We didn't start with the technology and then move towards the usage. We started with the usage and then moved towards the technology. It's a difference that may seem insignificant, but it changes everything in the daily trade-offs a product team has to make.
What the leaders of very small and small businesses have taught us about their real problems
The first lesson learned over these four years is that the real problems faced by leaders of small businesses aren't always the ones they initially raise. When people talk about invoicing, they're really talking about cash flow. When they talk about CRM, they're talking about time wasted searching for scattered information. When they talk about project management, they're talking about dysfunctional collaboration.
Administrative tasks consume a considerable amount of time for the managers of very small businesses, and this burden is almost always underestimated when starting a business. It's not a minor constraint: it's a silent drain on time and money.
What we heard, time and again, was the same frustration: juggling multiple tools that don't communicate with each other. One software for quotes, another for invoices, a third for customer tracking, a fourth for projects. Each tool works well in its own lane, but no one coordinates everything. The result: duplicate data, data entry errors, missed follow-ups, and a fragmented view of actual business activity.
Many companies today use invoicing software, but few still issue their invoices in a structured, machine-readable format. The equipment is there, but integration is still sorely lacking.
Why we chose the all-in-one approach rather than stacking tools
This observation led us to a fundamental choice: to build an integrated suite rather than yet another specialized tool. This wasn't a commercial decision. It was a decision based on consistency with what we were observing in the field.
The accumulation of tools has a cost that isn't reflected in monthly subscriptions. It's paid for in hours of data re-entry, signed quotes that are never converted into invoices, and customer histories that are impossible to find when they're needed most. For a small business, this hidden cost can quickly exceed that of a unified solution.
We therefore chose to bring together in Djaboo everything a team of 1 to 100 people needs to run its business: customer relationship management, invoicing, agile project management, financial tracking, team collaboration, and a knowledge base. Not to be exhaustive, but to ensure these components work together seamlessly, with a shared database and an interface that doesn't force users to switch tools every ten minutes.
This choice has its requirements. An all-in-one tool must be simple enough not to discourage users, and robust enough to support a growing business. It's a constant balancing act, and we don't claim to have achieved it once and for all.
What we have built, and what we have deliberately discarded
Building a product is as much about deciding what not to do as what to do. Over the years, we've received requests for a wide variety of features. Some were legitimate, and we incorporated them. Others would have made the tool more cumbersome without any real benefit to users.
We built a financial and invoicing management system designed for non-accountants. We built a CRM that allows you to track your clients and prospects without prior training. We built an agile project management system adapted to small teams, including teams working with freelancers. We built self-regulating automation techniquess which eliminate repetitive tasks without requiring technical skills.
What we rejected was complexity for complexity's sake. Some tools on the market multiply parameters, views, and modules to the point that users spend more time configuring their tool than using it. We deliberately resisted this temptation. Our guiding principle has always been the same: can a busy executive, without an IT team, use this feature on the very day it's activated?
We also eliminated the need for a locked-down approach. Djaboo connects to the tools you already use: Gmail, Outlook, Google Drive, Zoom, Skype, and Teams. Because a management tool should integrate with your workflow, not the other way around.
The five lessons we have learned from these four years
Simplicity is an ongoing process. A tool that is easy to use is not a tool lacking in features. It's a tool whose complexity has been absorbed by the design team, so the user doesn't have to worry about it. Maintaining this simplicity through ongoing development is probably the most difficult challenge we've faced.
Adoption depends as much on the medium as on the product. We learned that the quality of a tool isn't enough if the user is left to fend for themselves with a question. That's why we invested in responsive support, available in under three minutes on average. A small business owner doesn't have time to wait 48 hours for a response to a support ticket.
Needs evolve with growth. A company of three people does not have the same needs as a team of thirty. We have learned to build a tool that supports this evolution without forcing a migration to another software at each stage of growth.
Trust is built in difficult times. Bugs happen, and updates sometimes create friction. What distinguishes a lasting relationship from a temporary one is how we handle these moments. We've learned to communicate quickly, to fix things quickly, and not to downplay what deserves to be taken seriously.
User feedback is the best roadmap. No product roadmap can replace what users express in their daily use. Some of our best development decisions stemmed from seemingly insignificant comments. We learned to listen differently, to look for the problem behind the request.
What awaits us: electronic invoicing and reasoned automation
Two topics will be the focus of much of our attention for the coming months.
The first is the electronic invoicingThe reform is underway and its timetable is now set: From September 1, 2026, all French companies, including micro-enterprises and SMEs, must be able to receive electronic invoices. The obligation to issue electronic invoices will extend to micro-enterprises and SMEs from September 1, 2027.This is not a constraint that can be postponed. Structured formats (Factur-X in particular) and the mandatory use of... approved platforms will transform the way businesses manage their invoicing processes. Our role is to make this transition as seamless as possible for our users, without requiring them to become tax regulation experts.
The second is automation. We believe in reasoned automation: the kind that eliminates tasks without added value (payment reminders, creating recurring invoices, updating customer records) without claiming to replace human judgment in important decisions. Artificial intelligence opens up real possibilities, but we remain cautious about promises that exceed what the technology can realistically deliver today for a very small business or a small to medium-sized enterprise (SME).
Our belief is that automation should free up time for what cannot be automated: customer relations, strategic decision-making, and business development. It should not replace these activities.
Thank you
Four years is, above all, a human adventure. Thank you to each and every one of you who have placed your trust in Djaboo, sometimes from the very first weeks, sometimes by joining the adventure more recently. Thank you for your feedback, your criticisms, your suggestions, and your patience during times when the tool wasn't yet up to your expectations.
Today, over a thousand teams use Djaboo to manage their business. Each of you teaches us something. That's what makes this work worthwhile, and that's what motivates us to continue.
The next four years promise to be at least as demanding as the first four. We approach them with the same conviction as at the start: your time is precious, and our role is to save you time.













