Data and AI strategy assessment
A fixed-scope engagement, two to four weeks depending on how much there is to read, that ends with a written architecture review, a prioritized roadmap, and a cost baseline. It is deliberately useful on its own — you could hand it to another firm and they could act on it.
A senior engineer reads it and replies within one business day. Or write to emilio@lyticaconsulting.com.
- Length
- Two to four weeks
- Price
- Fixed, agreed before we start. No change orders.
- You get
- An architecture review, a prioritized roadmap, and a cost baseline
The problem this solves
Handing a platform rebuild to a firm you have not worked with is a large bet on a first impression. Most buyers who have been burned once will not make it again, and they are right not to.
So start smaller. An assessment is a bounded piece of work with a fixed price and a document at the end, and it runs two to four weeks. If we are good, you will know by then. If we are not, you have a roadmap and no long contract.
What we build
Artifacts you own, not activities we perform.
- A current-state architecture review
- What you have, how it fits together, where it will break next, and which parts are load-bearing without anyone realising.
- A prioritized roadmap
- Sequenced work with effort estimates and dependencies, ordered by what unblocks the most people rather than what is most interesting.
- A cost baseline
- What your platform costs to run now, which line items are growing fastest, and what is available to recover.
- The risks nobody has written down
- The single points of failure, the undocumented job, the person who is the only one who knows. Named, in writing.
A senior engineer reads it and replies within one business day. Or write to emilio@lyticaconsulting.com.
How the engagement runs
You should be able to picture week one before you sign anything.
Week one
Where we start
Interviews and access. We talk to the people who build it and the people who rely on it, and read the systems directly rather than the diagram of what they were meant to be.
The first weeks
The first thing that runs
Analysis, and a draft of the findings early enough that you can push back on them while it still costs nothing to change our minds.
From there
The cadence
A live readout with your team, then the written deliverable. From there you can hand us the first phase, hand it to someone else, or do it yourself.
What we need, and what you get
What we need from you
- Read access to your data platform and your cloud billing.
- An hour each with three to five people, including at least one who is unhappy with the current state.
- Permission to write down what we actually find.
What you get from us
- A fixed price and an end date agreed before we start. No change orders on an assessment.
- A document written to be used, not to sell you the next phase.
- No obligation to continue, and no pressure to.
Related
Start with an assessment
Tell us what you have and what is not working. A senior engineer replies within one business day, usually with questions, and the scope and the price are agreed before anything starts.