How to scope a digital project, from idea to launch

Why scope before you build

A digital project rarely fails because of the code. It fails because too much was built, too early, for a need nobody checked. Scoping answers three questions before the first line is written:

• Who is it for? One specific person, in one specific situation.
• What is it for? The problem they want solved, in their own words.
• How will we know it works? A number we can measure after launch.

Until those three answers fit in a few sentences, building is expensive and teaches you nothing.

1. 1The ideaWorkshop, feature sort, mockups shown to real users.
2. 2The launchA short first version, delivered every week.
3. 3ScalingMeasure, then invest: SEO, campaigns, automation.

Step 1, the idea: workshop, scope, mockups

We start with a workshop. Everyone around the table, we lay out the problem, the users and the constraints (budget, date, team, regulation). We leave with a list of features, and above all with a sort.

The sort is the real deliverable. Every feature goes into one of three columns:

1. 1In the first versionWithout it, the product is useless.
2. 2Right afterUseful, but we can launch without it.
3. 3Later, maybeWe write it down so we can stop talking about it.

Then come the Figma mockups of the key screens. A clickable mockup can be shown to five people in a week. It reveals misunderstandings before they cost days of development. We test before we build.

Step 2, the launch: a short first version

The first version does few things, but does them well and all the way through: design, web or mobile development, content, go-live. A few rules protect it.

• Visible deliveries every week. A preview address the client opens on their own. No staged demo.
• One priority list. When a new idea arrives, it takes the place of another one. It is not added on top.
• Testing as you go. On real phones and real browsers at every delivery, not the day before launch.
• Go-live rehearsed before the day. Domain, certificate, backups, payment under real conditions.

Step 3, scaling: measure, then invest

A live product without measurement moves blind. From launch day we plug in tracking: traffic, journeys, conversions. Only then do we invest, in this order.

1. Fix what blocks. The steps where visitors drop off.
2. Search. Useful pages that answer the questions people ask.
3. Campaigns. Once the site converts, not before.
4. Automations. Anything repetitive that a script or an agent can do.

Soporifik covers that whole path: the brand and logo, the store theme, then tracking for sales, search, Google Shopping and campaigns.

The pitfalls we see most

• Scope creep. Every addition looks small. Together they push the launch back by months.
• Deciding as a group with no arbiter. You need one person who makes the call, on the client side and on the team side.
• Forgotten content. Copy, photos, legal pages, translations. They are on the critical path as much as the code.
• Launching without measurement. Without numbers, every post-launch discussion is an opinion.

What you should hold at the end of scoping

• One page stating who it is for, what it is for, and what is not in the first version.
• Mockups of the key screens, already shown to users.
• An ordered priority list, with a realistic launch date.
• The number that will say whether the launch succeeded.