Solution
CRM
Off-the-shelf CRM systems know one model: a contact belongs to a company, a company has deals. As soon as a customer is also a sales partner, or several contract relationships run in parallel, that model ends.
Read the topic page →: CRMKnowledge
Articles on the cost, selection and operation of custom software. No sign-up, no newsletter required.
Continuously updated, without a date
Solution
Off-the-shelf CRM systems know one model: a contact belongs to a company, a company has deals. As soon as a customer is also a sales partner, or several contract relationships run in parallel, that model ends.
Read the topic page →: CRMSolution
An ERP system is meant to carry the path from quote to invoice all the way through. In practice that path breaks at the handovers: the order is entered again from the quote, the warehouse hears about it too late, accounting retypes the line items.
Read the topic page →: ERPSolution
In most mid-sized companies the figures already exist, they are just spread out: revenue in accounting, pipeline in the CRM, stock in inventory management, utilisation in the project software, the rest in spreadsheets. Anyone who wants an overview assembles it by hand once a month.
Read the topic page →: CEO dashboardSolution
The prototype was running in two weeks, and now it no longer carries the work. Where no-code builders fail once a tool goes into daily operations — and what remains of what you have built.
Read the topic page →: When no-code hits its limitsSolution
Over the years, another tool arrives for every task. Each one was the right decision on its own. Together they form a landscape without a shared data store, where staff switch between systems, enter data more than once and nobody knows which version applies any more.
Read the topic page →: When off-the-shelf hits its limitsSolution
Orders come in through a shared mailbox, the status sits in the subject line, data lives in spreadsheets that travel by email. That works for a surprisingly long time — until a message is missed, two people edit the same file, or the one person who kept the overview is away.
Read the topic page →: Excel and emailSolution
Customers write via WhatsApp, email, Telegram and forms — and internally everything lands in separate inboxes that only individual people can see. Off-the-shelf tools bundle the channels, but fall short on fine-grained user permissions, deep automation and the cost per user in large teams.
Read the topic page →: Multichannel inboxIndustry
A reseller brings its own end customers. Part of the range falls under the margin scheme, another part runs on commission.
Read the topic page →: RetailIndustry
The payroll run itself takes place in edlohn or DATEV and stays there. What costs time in payroll bureaus is the route there and back: clients submit hours and personnel notifications by email, spreadsheet and on paper, queries go round in circles, deadlines are chased by phone, and the results have to be distributed in a GDPR-compliant way.
Read the topic page →: Payroll accountingIndustry
Enquiries arrive by email and are retyped. On-site measurements are taken on the building site and transferred in the evening. Scheduling lives in a calendar that one person keeps in their head.
Read the topic page →: TradesIndustry
The quote sits in one tool, the project in a second, the hours in a third, the invoice in a fourth — and in the end nobody knows exactly whether a client is worth it.
Read the topic page →: Service firms and agenciesIndustry
One agent brings sub-agents along, each on their own rates, and on cancellation the commission has to be clawed back across every tier. At the same time, the speed between lead and quote decides who wins the deal.
Read the topic page →: Sales organisationsNo-code and off-the-shelf ·
Cost, backend, deployment, security and lock-in: why the same five problems occur with Base44, Lovable, Bolt.new, Replit Agent and v0 — with a comparison table.
No-code and off-the-shelf ·
Credits, SEO, security for user data, custom domain, mobile app: the five most common Base44 problems and what to check before go-live.
No-code and off-the-shelf ·
Supabase and the data model, credits, SEO, code export, production security: the five most common Lovable problems and how to solve each of them.
No-code and off-the-shelf ·
Token consumption, Bolt Database or Supabase, connection errors, deployment, code ownership: the five most common Bolt.new problems — with checklists.
No-code and off-the-shelf ·
Cost model, production configuration, unwanted changes by the agent, suitability for operations: the five most common Replit Agent problems.
No-code and off-the-shelf ·
Credits, backend, Supabase, GitHub, deployment: the five most common questions about v0 by Vercel — and what to check on the way into production.
Operations and technology ·
AI coding solves the problem of producing code. Production engineering solves the problem of trust — why more AI-generated code needs more engineering, not less.
No-code and off-the-shelf ·
Does your company fit the data model of an off-the-shelf system — or the other way round? Eight test questions and a quick check with twelve questions.
I run the intro calls myself. 30 minutes, free of charge, with no sales pressure — you find out whether custom software pays off for you and what it would cost. If it does not, I will tell you that too.
Book an intro call