Skip to content

Blog

Product Development & Technology

Your First 30 Days With a Product Studio: What Happens Week by Week

The first 30 days with a product studio: week one sets access and goals, week two tests the riskiest assumption, weeks three and four ship a first slice.

7 min read
Portrait of Tarik Gonen.
Tarik Gonen
Business Analyst Lead
Dithered illustration of two marble hands pulling a mason's line taut between stakes across bare ground at dawn, the first course of stones laid along it and a pink knot at the nearest stake.
logo of Facebook
logo of X
logo of LinkedIn
logo of Reddit
logo of Telegram
Contents
No headings found on page

The first 30 days with a product studio should turn an idea, or an unfinished app, into a shared plan and a first working piece of the product. Week one sets up access, goals and decision rights. Week two tests the riskiest assumption. Weeks three and four build a small slice, release it to real users and review what comes back.

Picture a founder who has just signed with a studio to build a tool for small property managers. The contract is done and the kickoff is on Monday. They wonder what they should prepare, how often they will hear from the team, and what they should be holding at the end of the month to know the money is well spent. Most studios can answer those questions, but few write the answers down before the work starts.

What is a product studio, and how is it different from an agency or a freelancer?

A product studio is a team that takes a product from idea or early version to something real users rely on, covering product strategy, design and engineering in one group. It differs from a development agency in that it shares responsibility for what gets built, not only for building what was specified.

The difference shows most in the first month, because each option starts in a different place:

  • Product studio. Starts with: the problem, the users and the riskiest assumption. Owns: product decisions with you, plus design and engineering. First-month output: a tested direction and a first working slice.

  • Development agency. Starts with: a specification you provide. Owns: delivery against that specification. First-month output: progress against a fixed scope.

  • Freelancer. Starts with: a defined task. Owns: that task. First-month output: one piece of work, with you holding the plan together.

  • First in-house hire. Starts with: onboarding into your company. Owns: whatever you assign. First-month output: usually setup and learning, with a long-term payoff.

None of these is right for every company. A studio fits best when the founder knows the problem well but needs help deciding what to build first and then building it.

What happens in week one?

Week one is about control and clarity: the founder owns every account, the team has access to everything it needs, and both sides agree on the goal for the month and on who decides what. No product code should be the main output of week one.

A marble hand setting the last bronze weight on the curling corner of an architectural plan unrolled across a stone table

The kickoff covers the problem in the founder's words, the users and how to reach them, what exists already (research, designs, code, a waiting list) and the constraints: budget, deadlines, regulations and any promises already made to customers. It ends with one written goal for the month, such as "five property managers complete a rent reminder setup without help," rather than a list of features.

What to have ready before kickoff

  • Access to anything that exists: code repository, hosting, domain, design files, analytics and any third-party accounts, all in the company's name.

  • A short list of people the team can talk to: potential users, early customers or the person who knows the business rules.

  • Anything already written down: notes from customer calls, a pitch deck, a rough specification or the prompts used with an AI tool.

  • One named decision-maker on your side, and a fixed weekly slot for review.

What happens in week two?

Week two tests the assumption that would hurt most if it were wrong, before anything expensive is built on it. That might be whether users actually have the problem, whether they will switch from what they use now, or whether a key integration works the way everyone hopes.

The test is usually a mix of user conversations, a clickable prototype and a small technical spike. Some teams use a fixed format for this. Google Ventures describes its design sprint as "a five-day process for answering critical business questions through design, prototyping, and testing ideas with customers." Others run a looser version over the same week. The format matters less than ending the week with an answer and a decision.

If you have not validated the idea at all yet, it is worth doing that before the studio work starts. Our guide to validating a startup idea in two weeks and the earlier post From Idea to Validation cover how.

What happens in weeks three and four?

Weeks three and four build the smallest slice of the product that a real user can use from start to finish, release it to a few of them and review what happens. A slice is one complete journey, such as sign up, add a property and send one reminder, not a set of half-finished screens.

Two marble hands lowering the newest pink stone drum onto a classical column under construction

Work runs in short cycles with a review at the end of each. Common frameworks differ on the length: the Scrum Guide defines Sprints as "fixed length events of one month or less to create consistency," while Basecamp's Shape Up method says "we work in six-week cycles." In a first month, a weekly review usually works best, because the founder sees working software often enough to correct direction early.

What a weekly review should include

  1. A demo of what works now, on a real device, with realistic data.

  2. What was learned from users or tests since the last review.

  3. What changed in the plan and why.

  4. The decisions the founder needs to make before the next review.

The Scrum Guide puts the purpose of a review well: "to inspect the outcome of the Sprint and determine future adaptations." A review that only reports progress against a list is a status meeting, not a review.

What should you have at the end of the first 30 days?

At the end of the first month you should hold evidence, a working slice and a plan, all in your own accounts. If you cannot point to each of these, ask why before signing up for month two.

The 30-day checklist

  • Every account, domain and credential in the company's name, with the studio's access listed.

  • A written answer on the riskiest assumption, with the evidence behind it.

  • One journey that real users have completed in a live or staging environment.

  • A list of what users did, where they got stuck and what they said.

  • A short, ordered plan for the next month, with what was deliberately left out.

  • A codebase you could hand to another team, with a readme that explains how to run it.

What changes if the studio is taking over an existing app?

When the studio starts from an app someone else built, the first month shifts from discovery to assessment: get control of the accounts, review the product, the code and the launch readiness, and decide part by part what to keep, fix or replace. Building new features comes after the app is stable.

The sequence is the same in spirit: control first, then a decision based on evidence, then one visible change shipped safely. Our post on whether to fix or rebuild an unfinished app walks through that first month in detail, and what breaks when an AI-built app gets real users lists the gaps that usually turn up in the review.

How we approach it at Vizio AI

We treat the first month as a test of the direction and of the working relationship, not only as a build phase. For a new product, we start with the riskiest assumption and the evidence needed to settle it, which is why a new product with us can start with a validation sprint before any feature work is planned.

For an app that stalled before launch, we follow the four steps on our Finish Your Build page: review the product, the code and the architecture; diagnose what to keep and what to fix; finish the gaps that matter most while leaving the working parts alone; then stabilise, test, deploy and put it in front of real users. In both cases the decisions are written down with their reasons, accounts stay in the founder's name, and the founder sees working software every week.

This sits in our Venture Studio.

Sources

FAQs.

01

02

03

04

05

Read more.

Dithered illustration of two marble hands pulling a mason's line taut between stakes across bare ground at dawn, the first course of stones laid along it and a pink knot at the nearest stake.
Your First 30 Days With a Product Studio: What Happens Week by Week
Tarik Gonen
7 min

The first 30 days with a product studio: week one sets access and goals, week two tests the riskiest assumption, weeks three and four ship a first slice.

Dithered illustration of a fragmented marble face looking down at a jeweller's tray where gems are sorted by size, the largest stone glowing amber under a brass lamp.
AI Lead Scoring in Your CRM: Start With the Rules You Already Trust
Omer Faruk Ilhan
7 min

Add AI lead scoring by writing down the rules sales already trusts, cleaning CRM data, then testing the AI score against those rules before reps use it.

Dithered illustration of a marble hand holding an oil lamp out across a threshold, its pink flame lighting the first stones of a mosaic path.
Onboarding for AI Products: Getting Users to Their First Good Answer
Umut Durgut
8 min

Onboard AI product users by stating what it can and can't do, offering example prompts and sample data, and reaching a useful answer in the first session.

Think AI-first.
Move future-fast.

Let’s build what’s next! From product ideas and intelligent workflows to data-driven systems and scalable growth operations.

Book a Strategy Call