Expertise / Advisory
Decide before you spend.
Most information system projects that go wrong were not badly executed: they were badly scoped. We work upstream, so that the investment decision rests on analysis rather than on a sales demonstration.
A Lytoria scoping assignment starts from your actual processes, not from the org chart or the requirements document. We spend time with the teams who run operations — sales administration, finance, procurement, production, logistics — to map what really happens, including the parallel spreadsheets and the workarounds nobody documents. That is usually where most of the requirement lies.
You end up with a file that belongs to you: current state, gaps, target architecture, costed scenarios and a phased deployment path. The document is designed to be put out to tender. If you choose another integrator to build it, it remains directly usable — which is the simplest test of its honesty.
What we do.
- 01Mapping of business processes and of the existing information system
- 02Technical audit of the application estate: debt, dependencies, operational risk
- 03Gap analysis between stated requirements and observed requirements
- 04Reasoned comparison of candidate solutions, with total cost of ownership
- 05Phased deployment path with effort, dependencies and decision gates
What you receive.
- Process and data flow mapping document
- Documented target architecture, including interfaces to be built
- Costed scenarios compared, including the option of changing nothing
- Phased deployment plan, usable in a tender process
This probably applies if.
Several departments are asking for different tools and nobody is arbitrating across the whole.
You have received integrator proposals whose pricing varies by a factor of three.
Your management data lives in files that only two people know how to maintain.
Frequently asked questions.
Let's talk about your system
An initial conversation with a consultant, with no commitment on your part and no sales pitch.