Candy Dash in Use: Six Tools of Our Own Instead of SaaS Subscriptions

Every company knows the list: one tool for HR, one for equipment, one for sales, plus Excel templates and Word files for everything no tool covers. Each makes sense on its own. Together they add up to a monthly bill nobody questions anymore – and a dozen places where our data lives.

We have started cancelling that list. Not on principle, but because the math has flipped: with AI coding tools like Claude Code, building your own software is now cheaper than renting it. Since August 2026 this is no longer a thesis for us but day-to-day business – six tools are in production, and the whole team works with them every day.

What CANDY DASH really is

CANDY DASH is not a dashboard, it is the front door: one login for all tools, plus roles, user management and a status page that shows whether everything is running. Sign in once and you get into every tool. A bell collects whatever is still open across all tools, and every tool carries the same menu bar at the top – if you can use one, you can use them all. Six tools hang off it:

• CANDY WORK – time tracking, leave and expenses. It calculates hours, overtime and Hamburg's public holidays on its own, knows travel allowances and time-off-in-lieu days, and has replaced an Excel template that had been passed around the team for years. Replaces our previous HR tool.
• CANDY PIPE – deals on a kanban board, contacts and invoices. A won deal doesn't disappear; it moves to the second board and is only done once the invoice is paid. Replaces our previous CRM.
• CANDY TASK – projects, tasks and collaboration. With one rule at its core: whoever hands off a task stays on it. It remains on their list until it's done – and only the person who currently holds it can tick it off. Replaces our previous project management tool.
• CANDY STASH – our tech arsenal: every device, every robot, every cable, plus location, depreciation and quarterly planning for the TECH FLAT. Replaces our previous rental software.
• CANDY NOTES – meeting notes without preconditions. Open the tool, type, done. Below the text sits what follows from the conversation, and every line becomes a task in CANDY TASK with one click. In use since mid-September.
• CANDY PROPOSAL – proposals built from templates instead of copy-pasting from old documents. The draft lives in the database, the finished Word document comes at the push of a button.

None of this is a product we want to sell. It is software that works exactly the way we work – instead of us working the way the software expects. You can see that in the tools: no vendor would have built the delegation chain in CANDY TASK or the two life cycles of a deal in CANDY PIPE for us. They only make sense for us – and that is exactly why everyone uses them.

Six tools, one workflow

The biggest difference to a collection of separate subscriptions only shows in how the tools work together. An inquiry becomes a deal in CANDY PIPE. One click on it opens CANDY PROPOSAL with company and address already filled in, and CANDY PIPE issues the proposal number. Once the job is won and delivered, CANDY PIPE creates the next tasks in CANDY TASK itself: first "upload receipts", then "send invoice".

The kick-off notes in CANDY NOTES are attached to the same deal, and their to-dos land as tasks with the right people. Where clients need timesheets, we book the hours in CANDY WORK directly onto the deal. Nobody types anything twice – and the bell in the portal tells everyone what is waiting for them next.

Built alongside the day job

The tools have been in use for two months. People from our team built them alongside their day jobs – nobody changed roles for it, and we didn't hire any developers. Since then the suite has kept growing: CANDY NOTES went live in mid-September, together with an onboarding that walks new colleagues through every tool right in the portal.

Two years ago that would have been nonsense. Build our own HR tool, for a team our size? The development costs would have swallowed decades of licence fees.

What has changed is the speed. The effort shifts from programming to describing: whoever can say exactly what their own expense process looks like gets exactly that process as software. That is the core of vibe coding – and the reason we don't just talk about it with clients but do it ourselves. The side effect is bigger than it sounds: change requests don't land in a vendor's ticket backlog, they are often live the same day.

Demos without real data

Since the end of September CANDY DASH runs a second time: as a demo with made-up companies, made-up deals and a made-up colleague called Lena Brause. That lets us show the tools in client meetings without a single real client name crossing the screen. The demo starts from scratch every time. All screenshots in this article come from there – the tools themselves speak German.

What running it costs

Everything runs on a single server at Hetzner in Germany – four cores, eight gigabytes, €8.49 a month. Plus a second machine that receives an encrypted backup every night. Set against a dozen SaaS subscriptions with per-seat pricing, that calculation doesn't take long.

It only becomes honest with the second half, though: software you build yourself isn't free. Someone has to maintain it, secure it and develop it further, and that is real working time. A SaaS vendor delivers support, updates and compliance – nobody does that for us anymore. That's why we built operations in from day one: two-factor sign-in, sessions that can be revoked instantly, encrypted connections into every tool, a rehearsed backup restore, a watchdog that posts to our Teams channel when a tool stops responding, and a weekly check of all dependencies for security vulnerabilities. This is not a side topic, and anyone running their own software shouldn't treat it as one.

Our calculation behind it: instead of ongoing subscription fees, we essentially pay for the server, the use of the AI models and our own time. That pays off – but only because the tools are now good enough to keep our own time manageable. And it doesn't pay off for everything: we are not rebuilding our accounting software, nor our email. The line runs where specialist knowledge and liability begin.

The data stays in-house

The topic that comes up first in every conversation we have with banks and mid-sized companies is data sovereignty. Our HR data, proposals and deals now sit on our server, not with a vendor whose list of subcontractors we skim once a year in the data protection annex. The tools run completely separately from this website – reading here doesn't bring you any closer to them.

The actual point

For us, CANDY DASH is an AI case study on ourselves – just like Martha, our AI agent in the messenger. We constantly tell clients what AI makes possible today. The most credible argument is to do it ourselves and show the results – including the places where it gets stuck. If you want to see all the tools with screenshots: we have documented CANDY DASH as a project.

And it changes a fundamental question in purchasing: for years the standard question was "Which tool do we buy?". It is turning into "Build or buy?" – and the answer increasingly differs from what it was two years ago. We work out which of your subscriptions stand up to that question at the Vibe Coding Scoping & Build Day.