Technology project discovery
A technology project should start with the outcome, not a shopping list.
Map what is changing, what success looks like, which systems and vendors are involved, and the constraints around cutover. We will turn that into a working project brief before the consultation.
Technology project discovery
Define the outcome before we define the technology.
What are you building, changing or moving?
Choose everything that belongs to the project. A real project often crosses several categories.
Project type
Footprint
One relationship, many systems
The answer may cross traditional service categories.
A phone problem may really be a network problem. A website project may need hosting, email, DNS and business workflow integration. A new office may involve connectivity, Wi-Fi, computers, voice, security and vendors. We design around the whole environment instead of forcing the problem into one product box.
Prefer a human conversation?
Skip the guide entirely. Bring us whatever information you have and we can work through it together.