When the rest of the site sells what we do,
Insights is where we explain how we think.
Architecture notes, engineering playbooks, technical deep dives, opinions, product updates, and company perspective. Published when there's something to say — not on a content-marketing calendar.
Six categories. 40 published articles. More when they earn their place.
Most ERP implementations succeed on paper and fail in operating reality. The launch demo is impressive. The training is delivered. The cutover happens. Then, somewhere between month four and year three, the system slowly stops being trusted. Reporting gets manually repaired again. Custom modules accumulate bug reports nobody fixes. Phase 2 becomes a budget negotiation that never resolves. Failure rarely looks like a technical problem. It looks like governance failure — the system was implemented, but never operated.
Read the full articleEach category serves a different editorial purpose. Articles ship when they earn their place — not on a calendar.
System design decisions and the trade-offs behind them. The "why we built it this way" notes that usually live in commit messages and ADRs.
Open category 8 playbooksHow we solve recurring production problems. Step-by-step walkthroughs of the engineering work we keep doing.
Open category 7 deep divesPerformance, scale, reliability. Deep technical detail for engineers, not management.
Open category 8 articlesThought leadership and commentary on enterprise software, Odoo, services-firm operating models, and adjacent topics.
Open category 1 updateReal updates for Deploy Monkey, Timenzo, and the Odoo modules — explaining why a feature shipped, not just what shipped.
Open category 8 articlesLinescripts' point of view on enterprise software, ERP markets, the Odoo ecosystem, and services-firm economics.
Open categoryIf a question keeps coming up in your operations, it might be worth a Linescripts article. Send it to us.