Digital strategy and discovery, before you build
We define what to build before anyone writes code: requirements analysis, process mapping, enterprise architecture and a scope your stakeholders can sign off. It is the first step of every tailor-made project, or a standalone engagement.
Services in this pillar
Each service has its own page with scope, approach and buyer questions.
Digital Transformation Consulting
Assessment of your current systems and a costed, sequenced plan for what to change and in what order.
Solution Architecture
Target architecture, integration design and the technical decisions that are expensive to reverse, settled before build starts.
Business Process Management
Map, redesign and automate the processes a system is meant to support, before they are built into software.
UX/UI Design & User Research
User research, interaction design and design systems based on how people use the software at work.
When to start here
Start here when the scope is not settled. Typical signs are requirements written from a document nobody has checked against the work, vendor estimates that are far apart, or an off-the-shelf product that almost fits but whose gaps nobody has costed. A discovery engagement usually takes two to six weeks. You receive process maps, an architecture, a costed scope and a roadmap, written so that any vendor could build from them.
The same team can then build it with you. Recent design work includes the sales CRM designed for GMM Music Publishing International and the redesign of a manufacturer's maintenance system, tested with six of its users.
Questions buyers ask before committing to this
Is discovery just a paid step before the real project?
You own everything it produces: process maps, architecture, scope and roadmap. They are written so that you could hand them to a different vendor and still use them.
How long does it take?
Usually two to six weeks, depending on how many systems and stakeholders are involved. If it starts to run longer, we stop and agree with you whether the extra scope is worth paying for.
We already know what we want built. Do we need this?
Often not. If the problem is well understood, the process is stable and few systems need to connect, we can go straight to a build and settle the details in the first sprints. Discovery is worth paying for when the scope is unclear or the estimates you have received are far apart.
Can you work with our own IT team?
Yes, and the result is usually better for it. Your team knows the systems and their history; we bring a structured method and experience from other projects. We plan workshops around your team's time and share the working documents as we go.
What if the conclusion is that we should not build anything?
Then that is what we report. Sometimes the right step is to configure a system you already have, or to change a process without any new software.
Next step
Start with a conversation
Tell us about the problem you are trying to solve. A senior person reads every inquiry and replies with our view of fit, scope and cost, including when another option would suit you better.