Phase 01 — Discovery & system design
Every engagement starts with discovery — workflow mapping, scope, risk, and a milestone-priced roadmap so we both go into the build with a shared, realistic plan.
The problem
Most software engagements fail in scope, not in code. Without a real discovery phase, requirements drift, integrations surprise everyone, and timelines slip — usually two weeks before launch.
The approach
We run a structured discovery and system-design phase: workshop the workflows with the people running them, document constraints, design the system, and produce a milestone-based plan with realistic estimates.
What we deliver
Who this is for
- Companies evaluating whether a custom build is right
- Teams that have been burned by vague scope
- Operations leaders modernising legacy systems
- Founders going from prototype to real product
Example engagements
- 2-week discovery for a multi-team operations platform
- 1-week scoping for a campaign-system rebuild
- 3-week deep-discovery for a legacy ERP replacement
- Co-founder-level architecture sprint for a SaaS MVP
How we run discovery & system design
Structured 1–3 week discovery sprint that produces a milestone-priced plan.
Kickoff workshop
Align on goals, stakeholders, and decision criteria.
1 daysWorkflow mapping
Sit with the team running the real process, document end-to-end.
3 daysArchitecture & data model
Design the system and integration approach.
3 daysPlan & estimate
Produce milestone plan, risk register, and estimate range.
3 daysTimeline & budget
Typical timeline
Discovery sprints typically run 1–3 weeks depending on the size of the engagement to follow.
Typical budget
Discovery is fixed-price by scope — most engagements run $1,500 to $15,000.
Frequently asked questions
Can we do discovery without committing to the build?
Yes — discovery is a standalone, fixed-price engagement. You leave with the plan, the estimate, and the artefacts, and you're free to take them anywhere.
What do we get out of discovery?
Workflow maps, data model, integration blueprint, architecture decision record, risk register, milestone plan, and a realistic estimate range. Everything you need to make a build/no-build decision.
How long does discovery take?
Most discovery sprints run 1–3 weeks depending on engagement size. Smaller campaign-system builds need a week; multi-team operations platforms need three.
Who participates from our side?
The team running the real workflow, the decision-maker on budget, and the IT or engineering lead if there's a stack to integrate with.
Ready to start a project?
Tell us what you're trying to build and the outcome you need. We'll suggest a scope, timeline, and milestone-priced plan.
- Call971.255.2633
- Emailcreate@vadimages.com
We will respond within 1 business day.