Series
Choosing and owning software
Buy, connect or build; who owns the code; how to choose a supplier and renew old software without stopping the work.
After this series you can:
- You decide per piece of work: buy, connect or build, and count your spreadsheet's hours and errors.
- You pick a supplier on your own requirements and record, before signing, that the code and data are yours.
- You arrange who maintains old or orphaned software, whom you call when it breaks, and what comes first.
05 · Basic
Choosing and owning software
Buy, connect or build; who owns the code; how to choose a supplier and renew old software without stopping the work.
What this series does not cover
- Which package to buy: we do not compare Exact, AFAS or Odoo.
- What software, licences or maintenance cost.
- The legal side of contracts and tenders.
Terms
- build vs buy
- The choice, per piece of work, between buying a package, connecting systems, or building software.
- hidden costs
- The hours and errors a file costs you that never show up on an invoice.
- ownership
- Written agreement that the code, documentation and data are yours, also when you leave.
- shadow administration
- Lists and spreadsheets beside your package, for the work the package cannot hold.
- legacy
- Software that still works, but that nobody in your company dares to change any more.
- client portal
- A secure login where each customer sees only their own orders, invoices and documents.
- maintenance agreement
- An agreement on who watches your software, who fixes errors, and how you notice.
- IT roadmap
- A short plan that gives every IT step an order, a reason and a dependency.
