What you can expect when Lateral Studio develops your product

lateral logo dark

You’ve decided you want to turn your idea into an MVP to test your business with real users… what now? Here’s an overview of what that process looks like when you work with Lateral Studio.

First, the discovery call

We like to meet potential clients via Google Meet to determine if we are a fit for their product roadmap. During the discovery call, which usually lasts no more than 35 minutes, we always ask the same questions. What’s your idea? How far along in your startup journey are you? Do you have any internal or external milestones coming up? How developed is your product roadmap? Have you already validated your idea with users? 

Then, we explain how our MVP development process works. This is the shortest part of the call, since we’re obsessed with efficiency and have this down to a science. We’re software engineers at heart, so we love going straight to the point ;)

If we think that our expertise is a fit for your product, it’s time to talk availability! If we are not a good fit, we will be able to refer you to other providers who can help you. 

To book a discovery call with us, click here. 

Then, scheduling

We only work on 1 MVP at a time. 95% of our work time each week is dedicated to the current sprint, with only 5% going to admin, marketing, and business development. 

This is awesome for you because you’re getting our full attention, energy, and focus. 

The downside is that we might not be available to start working on your sprint tomorrow. Or next week. Usually, our earliest availability is 2-4 weeks out. 

Strategic workshop

When we work on a new MVP, the first step is always a workshop where we all gather together - either in person (if you’re around Milano) or via Miro. 

In this key step, we will get crystal clear on your IT strategy. We will start from your WHY and your value proposition to identify the features that deliver the biggest results to your users. Our process is unique since our business model is different from conventional software houses (as you can read here), so it’s in our best interest to create an MVP that works as fast as possible. 

The workshop takes between 3-4 hours, and the agenda and content are customized based on your specifics. However, the goal is always the same: KPI definition! We are extremely data-driven in our approach, so knowing exactly what KPIs the business idea will be evaluated against is key. 

Usually, the workshop happens in the weeks leading up to the sprint. This is also where we estimate how many sprints it’s going to take to reach your desired milestone.

First sprint

Sprints start on Monday morning and end on Friday afternoon. This is when our team is completely focused on working on your MVP. Usually, one or more software developers are involved together with a designer and a product manager: but this can change based on the plan. 

During the sprint, we will work independently as much as possible because we know the life of a founder is a busy one! However we will probably have quick questions for you (Whatsapp) and we definitely want to have regular check-in meetings every other day. Expect to dedicate between 2-3 hours of your time per week to communication with us. 

In case we need to run a test that involves your systems or users, we will organize it at a mutually convenient time. 

The sprint is over, now what?

Usually a single sprint is enough to cover the bare essentials of an MVP, so most of our projects last between 2-4 weeks. However, if you’re satisfied with the progress we have made in 1 week, you can decide to launch the MVP as is. 

Alternatively, we will continue to work together for another week.

MVP is ready

Once the MVP is ready based on the joint plan, you can test it with real users! The most intense part of our work is finished, however we like to stay up to date on the progress of your validation process. 

Once the MVP is ready, you will be able to make basic changes yourself independently. This for example includes editing text or colors or images. We do not offer ongoing maintenance services because the benefit of Low-Code is that you can manage everything yourself. 

After weeks (or maybe months) or beta testing, you can engage us again for an additional sprint or 2 to further develop the product.