# Prove the important part before scaling the investment.

> A proof should test a consequential question about a product or system. If it only demonstrates that a model can produce text, it is unlikely to justify a larger implementation.

Canonical URL: https://marmation.com/engagements/product-validation-build/

## The decision

What result would make you stop?

Define that result before building the proof. A useful validation can fail: it tests the assumption that matters and records the conditions under which the result holds.

## The situation behind the request

A product team needs to show that a document review assistant can preserve evidence, enforce tenant roles and stay within acceptable latency. A full SaaS build would be premature, but slides will not answer these questions.

## Where the obvious solution falls short

A prototype is often sold as nearly complete software. That obscures authentication, operational cost and failure handling still to be engineered.

## How we would approach the work

Define the hypothesis, build one complete vertical slice around representative or synthetic inputs, test hard cases, record limitations and recommend the next funded stage.

## What the engagement may include

- One written hypothesis and acceptance criteria.
- Interactive workflow or technical proof aligned to the hypothesis.
- Architecture and cost/quality observations.
- Evidence summary, failures, remaining risks and build options.

## The choices worth making explicitly

A low-code prototype may suffice for a UX question. A model evaluation harness may be more appropriate for accuracy. Choose proof form by uncertainty, not visual impressiveness.

## What we would test before calling it ready

Never present a validation build as secure production software. Label simulated APIs and synthetic data plainly. The evidence should be reproducible.

## A sensible first step

Select the highest-risk assumption the team needs to resolve, then design a validation that can genuinely fail.

## Related reading

- [Build AI into the product. Not just the prototype.](https://marmation.com/solutions/ai-product-engineering/)
- [Clarity before code. Accountability through delivery.](https://marmation.com/approach/)
- [Improve the system that ships software.](https://marmation.com/engagements/ai-native-team-pilot/)