The posts under this tag cover the software a small company depends on and the security that keeps it running: choosing between building and buying, what a custom application costs to build and to keep alive, how a website is hosted so that it survives a busy day and a bad one, backups that have actually been restored, access control for a firm with five logins and no IT department, and what an audit of an existing system looks for. They come from the technology practice and from our own infrastructure, which is documented in the open where it can be. Each post names the tools, the monthly cost, and the trade-off taken, and states when a recommendation stopped being true. Read this tag if you own a company whose systems were set up by someone who has since left, or if you are about to commission software and want to know which questions to ask before the first invoice.
We automated almost every administrative task in a small German holding and hit a wall at the tax return. The blocker is a licence clause rather than a missing feature. Here is the tool matrix, the two walls behind it, the one German tool nobody names, and the deadline that settles the question.
AI-native operationsSoftware and securityLaw and tax notes
No open-source tool can file a German tax return →We modelled a web studio for trade businesses in Rhein-Main and buried the idea. Then we measured what nobody in Germany has measured since 2018: 142 tradespeople's websites drawn in Frankfurt and the surrounding towns, 122 read in full. Every one carries an Impressum. Three in four offer neither a price nor an appointment.
Search and AI visibilitySoftware and securityIndustry assessmentsRhein-Main
94% of German trades have a website. What is missing →