What can a one-week MVP phase actually deliver?

Define the smallest end-to-end behavior that a real user or operator can review. The useful boundary includes the happy path, the most important failure state, and a clear handoff rather than a collection of disconnected screens.

Good candidates include one onboarding step, one enquiry-to-record workflow, one customer portal action, one bounded automation, or one conversion path. Each can be observed and accepted without suggesting that the surrounding product is complete.

Poor candidates rely on unresolved compliance questions, broad migrations, several unknown integrations, multiple applications, or a backlog whose priorities have not yet been decided. Those conditions call for scoping or discovery before a delivery commitment.

A small services business already has approved website copy and a CRM account, but enquiries still arrive in an inbox and are retyped by hand. A responsible one-week phase can connect one published form to one validated CRM record and confirm the result with the business owner.

The week starts with the agreed fields, consent copy, access, error state, and acceptance examples. Delivery covers the form submission, validation, CRM handoff, confirmation state, and a failed-submission path; it does not include a CRM migration, campaign automation, analytics programme, or redesign of the wider website.

Acceptance evidence includes successful and failed test submissions, the resulting CRM records, a short walkthrough, configuration notes, and the remaining-risk list. The handoff names who owns the form, CRM credentials, third-party charges, and the next product decision.

ProductBuild is looking for new partnerships for 2026. For a small number of well-matched founders and businesses, we can deliver one selected Phase 1 feature over one week, up to 40 hours, with no professional-services fee.

Selection follows a fit and scope conversation; it is not automatic. Before the week begins, both sides agree the feature, dependencies, exclusions, acceptance criteria, and handoff. Hosting, software, APIs, licences, devices, and all other third-party expenses remain with the partner.

The phase follows the same quality standards as paid ProductBuild delivery. Its no-fee boundary changes the commercial terms, not the care applied to design, engineering, review, and handoff. The purpose is to establish working trust through a bounded piece of delivery, not to promise an open-ended engagement or support beyond the agreed handoff. Referrals, testimonials, reviews, case studies, and endorsements are optional and are never consideration for the work. Any endorsement connected to the no-fee phase must disclose that fact. Continuing work requires a separately agreed paid partnership.