Interviews and process mapping
Conversations with the people in every link of the chain, and mapping processes as they actually run — not as the procedure says. This is usually also the moment when processes come to light that nobody in leadership knew existed.
Mapping systems and data
Which systems are active today, who maintains them, what data moves between them and where it's copied by hand. This is the basis for deciding what to keep, what to replace and what to simply connect.
Finding where you're losing
Where time, money and customers leak away — with a rough estimate of what each point costs. Without this you can't prioritize, and every feature looks equally important.
Phased build plan
What gets built first, what can wait without harm, and what has to happen before what. Every phase is defined so that it delivers value on its own, even if you decide to stop after it.
Architecture
How the systems connect, where the data lives, who can access it and what happens when something goes down. This is the part that prevents expensive surprises in month six.
Full discovery document
A working document with processes, screens, interfaces, milestones and an estimate. It's yours, and you can take it to any vendor — even if that isn't us.