A product studio can do more than make an impressive prototype. Its real offer can be a repeatable route from an uncertain idea to a release that somebody else can operate. That gives a founder a clear way to explain the work, define an engagement and hand over a useful result. NV2 could carry that studio identity across client projects and the products the team eventually chooses to release itself.
Sell a decision before a build
An early customer may arrive asking for an app, a device or a connected service. The first engagement should establish the decision that a prototype will help make. Consider a manufacturer exploring a maintenance tool for field engineers. Before promising a full platform, the studio could investigate whether engineers can identify the right equipment and complete one service record in the conditions where they work.
The discovery offer can have a defined finish: an observed workflow, a prioritized set of uncertainties, a testable prototype and a recommendation about the next investment of effort. Give the customer a clear account of who participates and what they receive. This makes discovery a piece of work with its own value, rather than an indefinite prelude to a larger project.
Put customer access in the engagement
The studio needs access to the people who will use the product and the people who will support it. A sponsor’s description is a starting point, but it rarely captures every interruption, missing detail or workaround. Agree how the studio will reach those users before setting the delivery schedule. Identify who can arrange sessions and who can answer questions about operations between reviews.
The Service Manual research planning guide treats research as planned work with explicit questions and appropriate participants. A small studio can use the same discipline. For the field tool, the first questions might concern equipment identification, access to connectivity and the information engineers need while standing at the machine. Each question should lead to an observation the team can use.
Keep the prototype faithful to the question
A prototype does not need to contain the whole proposed product. It does need to reproduce the part of the experience under investigation. If the uncertainty concerns reading a label in poor light, test a realistic label and device. If it concerns finding a service history, use believable records with ordinary omissions and inconsistencies. The prototype should make the relevant task possible enough to observe.
Separate that test artifact from production software. Keep a list of shortcuts, simulated connections and decisions that still need engineering work. The list belongs in the handover and the review conversation. A customer should be able to distinguish a promising interaction from a release-ready system, then decide what to build next with a clear picture of the remaining work.
Make reviews end with decisions
A weekly presentation can become a long tour of design changes. Instead, give every review a short decision list. Show the evidence behind each question, state the available choices and identify the person who decides. For example, the customer may need to choose between collecting a full service record on site or allowing an engineer to finish it later from a better connection.
Record the selected option and its consequence for the next stage. Keep unanswered questions visible, with an owner and a date to revisit them. This creates a working memory for the project. When a new stakeholder joins, the studio can show how a decision emerged instead of replaying the same conversation. The engagement becomes easier to explain, estimate and transfer.
Treat handover as a product experience
A handover folder is useful only when the next team can operate what it contains. Include setup instructions, access responsibilities, the test approach, known limitations and the process for releasing a change. Walk through a fresh installation with the person who will maintain it. That exercise often reveals assumptions that remained invisible on the studio’s own machines.
For a physical prototype, include component choices, assembly notes and any special handling requirements. For software, explain environments, configuration and the boundary between customer-owned accounts and studio access. Assign a person to remove or transfer access when the engagement ends. A clean transfer lets the customer continue the work and gives the studio a defined end to its responsibility.
Choose a repeatable studio shape
The founder can specialize by customer problem, product stage or technical setting. A studio serving connected industrial tools may build a repeatable discovery method around field observation and device trials. Another might focus on internal software for operations teams. Select a shape narrow enough that the team can improve its process from one project to the next, while keeping NV2 as the company name above the offer.
Document what a standard engagement includes and the conditions that require a separate agreement. Examples include travel, production deployment, regulated environments or long-term support. This boundary helps the studio plan capacity and lets a prospective customer describe the engagement to colleagues. The first offer can be concise and concrete: investigate one workflow, test the riskiest interaction and hand over a clear next decision.
A first engagement worth repeating
Before taking on several projects, run the method through a single bounded engagement. Track time spent recruiting participants, resolving access and preparing the handover, as well as design and engineering. Those quieter tasks determine whether the studio can repeat the offer with a small team. Use the result to adjust the scope and review rhythm for the next customer.
The Service Manual’s beta guidance connects trials with real users to preparation for live operation. For a studio, the practical lesson is to make the next operating stage explicit. Write a fixed discovery engagement with one customer decision, named participants and a defined handover. That is a credible first piece of work for a studio carrying the NV2 name.