MVP Build Intake

Project basics

Start with the outcome—not a feature list.

Project / company name

Your name and role

One-sentence MVP goal

Problem being solved

Build environment

Target MVP launch date

Budget range

Hard deadline or event

Users and core journey

Define exactly who uses it and the shortest valuable path.

Primary user

Other user roles

Core happy path

Top 3 user actions

Expected users at launch

Primary devices

MobileDesktopTablet

Accessibility / language needs

MVP scope and features

Separate launch-critical requirements from ideas that can wait.

Must-have features

Nice-to-have features

Explicitly out of scope

Accounts / login?

User permissions

Payments?

Scheduling?

Rules, calculations, or qualification logic

Content and visual direction

Supply launch-ready assets or authorize reasonable first-pass placeholders.

Brand status

Desired tone

Brand assets and links

Reference sites/apps

Required pages / screens

Final copy and content

May we draft missing MVP copy?

Photography / imagery

Data, forms, and documents

Define every input and where the information must go.

Forms and exact fields

Data captured, stored, or displayed

File uploads?

Imports / existing data?

After-submit behavior

Reports, dashboards, exports

GoHighLevel configuration

Complete this if any part will live in or connect to HighLevel.

Never place passwords or API keys in this form. Grant access securely after scope approval.

GHL location / sub-account

Existing vs. new setup

CRM pipeline and stages

Custom fields, tags, and lead sources

Workflow triggers and actions

Email / SMS content and timing

Calendar

Phone/email status

Snapshot or reusable template needed?

Integrations and automation

Map systems, ownership, and the direction of every data flow.

Systems to connect

Data flow

API / webhook documentation links

Notifications

Failure handling

AI behavior (if any)

Technical setup and access

Identify ownership and prerequisites. Share secrets only through an approved secure channel.

Domain

Hosting preference

Technology constraints

Data storage preference

Environments and release process

Existing assets / repositories

Legal, privacy, and trust

Flag requirements early; this intake does not replace professional legal advice.

Industry / jurisdiction requirements

Consent required?

Age or location restrictions?

Required legal documents

Security requirements

Success, testing, and handoff

Give the MVP a finish line that can be objectively tested.

Definition of done

Acceptance tests

Success metrics for first 30 days

Final decision maker

Feedback turnaround

Known risks, assumptions, or unanswered questions

Review and export

Your answers stay in this browser unless you export and send them. Review the brief, then download a copy.

Before delivery, attach any logos, copy documents, field lists, workflow diagrams, sample data, legal text, and API documentation referenced above. Send credentials separately through a secure method.