Urgent.News

What's breaking now, across thousands of outlets.

Tech

Scoping a first version: What to build first, and what to leave out

Originally published on ayurchenko.xyz . A first version is scoped well when it proves one thing to one kind of user, and leaves out everything that does not help prove it. Most first versions that disappoint were scoped as a small copy of the whole product instead of a test of one claim. This is how I scope a first version, from more than 40 products and MVPs launched over 14 years. Start from…

A well-scoped first version of a product should prove a single claim to one specific kind of user, while excluding everything that doesn't contribute to that claim. The process starts with identifying the core claim, which should be a concise sentence detailing the target user, their intended actions, and the expected outcome to confirm the claim's validity.

All elements within the first version must directly support this claim or demonstrate that it is unachievable. To evaluate each feature, ask how it supports the claim, then prioritize the features based on their significance. Essential features include the end-to-end job that the user needs to accomplish and any elements required for users to trust the product. Remove features that don't yet prove the claim, such as additional roles, integrations, or administrative panels.

Once the claim is proven true on the desktop version, consider other iterations such as a mobile app or additional features. The first version should encompass the smallest scope that still validates the claim. After the claim holds, the subsequent steps should focus on refining the product further, identifying the next stages, and ensuring all foundational aspects are addressed.

When structuring the first version, write a one-page document outlining the claim, target users, the primary job, relevant flows, excluded features, timeline, and cost. This document serves as a reference point for any new ideas that may emerge during development. Examples of successful first versions include Equi, a digital family office that streamlined onboarding by integrating identity checks and KYC/AML processes, and Deva, an AI agent platform that focused on defining core objects like agents, sources, and permissions before redesigning screens and functionalities.

Choosing between a prototype created with an AI tool and a fully built product depends on the nature of the question at hand. For assessing market interest, an AI-based prototype can provide answers quickly. However, if the product will handle real data or financial transactions, a robust build is necessary to ensure reliability and security.

Founders often question the components of an MVP, the timeline for completion, the choice of technology (e.g., Lovable or Cursor), and the associated cost. The answer typically involves focusing on the core functionality required to validate the claim, with a timeline aligned to the complexity of that functionality, and a variable cost based on specific requirements.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

How I stopped getting paged at 3am for raw SSH logs (and built a host agent for Linux)

If you run your own Linux boxes, you already know what /var/log/auth.log looks like five minutes after spinning up a fresh VPS. Nobody knows the IP. You haven't pointed a domain at it yet.

  • Vigilhold monitors Linux servers for security events without opening inbound ports.
  • Agent records and blocks malicious activities while maintaining tamper-evident audit logs.

More from Monday 16 November →