Case studies

Challenge, approach, result — in that order.

Each engagement written the way we ran it: what was actually broken, the sequence we used, and the numbers six months later. Client names are withheld where approval is still pending.

Engagements published
3
Sectors
Textile · Manufacturing · Distribution
Platforms
NetSuite · SAP Business One · Odoo

How we write these

Numbers you can interrogate, or we leave them out

Every figure in a Techlyst case study comes from a system the client can query, was measured against a baseline captured during Discover, and is published with their approval. Where a client will not approve a number, we describe the change qualitatively instead of estimating it.

  • Baseline measured before work starts, not reconstructed afterwards
  • Figures traced to a system report, never to a workshop estimate
  • Client sign-off on every quoted metric and quotation
  • Anonymised where commercial sensitivity requires it — never embellished

Reference calls. For serious evaluations we will introduce you to a client in your sector who has been live for at least two quarters. Ask us at proposal stage.

Get started

Want the version of this with your numbers in it?

Discover measures your baseline in two to three weeks: process map, data-quality assessment and a written recommendation you can act on with or without us.

WhatsApp