Discovery Process

Every DevNest project starts with discovery. This is where we earn the right to build.

What discovery includes

1. Project brief review

Before we talk, we ask you to fill out a project intake form covering:

• What you're building and why
• Who your users are
• Your success metrics
• Technical constraints or preferences
• Timeline and budget range

2. Discovery call (45 minutes)

We use this time to go deeper on the brief, ask the questions a form can't answer, and get a sense of how we'd work together.

We'll cover:

• Business goals vs. technical requirements
• Design direction and inspiration references
• Existing codebase, infrastructure, or brand assets
• Stakeholder structure: who makes decisions?

3. Technical scoping

After the call, we do our own research:

Competitive analysis
Technical feasibility assessment
Architecture options evaluation
Risk identification

4. Proposal delivery

Within 5 business days of the discovery call, you'll receive:

Document	Contents
Scope of Work	Feature list, exclusions, assumptions
Technical Architecture	High-level system design
Timeline	Week-by-week milestones
Fixed Price	Single number, no surprises
Contract	Terms, IP, payment schedule

What makes a good discovery

The best discoveries happen when:

• You come with honesty about constraints, not just aspirations
• You have a clear decision-maker who can respond quickly
• You share context you think might not matter, because it usually does
• You tell us what's worked and what hasn't in the past

What happens after discovery?

Once the contract is signed and the deposit received (typically 30–40% of total), we kick off the project on the next Monday.

See Design Phase for what comes next.