Linescripts is a services firm. But services firms that build well accumulate products — the tool you built for one engagement that turns out to be useful to everyone, the internal system that outgrows "internal." This is an honest state-of-play on the three products we maintain, and where each is headed.
Deploy Monkey — managed Odoo hosting and deployment
Deploy Monkey came out of a problem we kept solving by hand: deploying, hosting, and operating Odoo properly. Not "put it on a server" — proper deployment with CI/CD, environment management, backups, monitoring, and the ability to push a change without it becoming an event.
It is a real product now, with public pricing, used by agencies, partners, and SMBs who want Odoo run properly without building the DevOps capability in-house. The free tier exists so you can evaluate it on a real instance before committing.
Where it's going: the roadmap is depth, not breadth — tighter observability, faster pipelines, and making the boring operational guarantees (backups that are tested, restores that are quick, upgrades that are calm) progressively more boring. Deploy Monkey is the internal proof of our own Cloud & DevOps practice: it is the system we hold ourselves to.
Timenzo — team time and work tracking
Timenzo began as the internal tool we built to track our own team's time and work — the honest version, the one that reflects how engineering work actually happens rather than how a timesheet wishes it happened.
It is not a public self-service SaaS today. It runs internally and is available to others by demo and request rather than open signup. We are deliberate about that: a product earns a public launch by being genuinely ready, and we would rather show it to you directly and have a conversation than push an open signup before it has earned one.
Where it's going: continued use as our own daily tool — which is the best possible pressure on a product — and a measured path toward wider availability when it is ready to carry that.
The Odoo modules — four paid apps on the Apps store
We publish four paid modules on the official Odoo Apps store. Every one of them came from a real engagement: a capability a client needed, built properly, and then generalised and hardened to the standard a public module requires.
That order matters. We do not build modules speculatively and hope someone needs them. The module exists because a real operation needed it and used it; publication is the step after it proved itself, not before. It is the same discipline as the case studies — built on engagement, then published.
Where they're going: maintenance against current Odoo versions is the baseline commitment, and new modules join the store on the same rule — a real engagement first, publication second.
The through-line
Three products, one pattern: each came from solving a real problem for real work, and each is held to the standard of being something we use or operate ourselves. Deploy Monkey runs our own hosting practice. Timenzo tracks our own team. The modules came from our own engagements. We are wary of products that exist only as products — built to be sold, never used by the people who built them. The ones here earned their place by being useful before they were offered.