Discovery and scoping

Find out what to build, before you commit to building it.

Duration: 1 week

Most failed technology projects don’t fail in the development phase – they fail in the week before development starts. A discovery project is a focused week together with your team: we map technical constraints, assess what is realistic, define exactly what should be built, and give you a written scope you can take to a developer, a board, or a budget meeting.

What you get

• Discovery sessions (5–8 hours) with your team
• Integration mapping against existing systems
• Written technical scope with a realistic estimate (SOW)
• Architecture recommendation
• Flagging of compliance and data residency
• A document you can use to secure budget or brief a team

Who it’s for

• Businesses with a clear problem, but unsure what to build
• Innovation teams that need a technical assessment before budget approval
• Founders who have received wildly different estimates
• Companies that have stalled in the middle of a project
• Anyone who has been burned by unclear scope

What happens next?

If the scope points to an internal tool, move on with Internal AI tools. A customer-facing product? Then MVP Light or MVP Enterprise is the next step. The discovery cost is deducted from the project if you continue with us.