What Actually Happens in a Prototype Design Sprint? A Week-by-Week Guide for Baltimore Businesses 🧭

You have an idea for an app or a piece of software, and someone has told you to start with a prototype. Good advice. But what do you actually get for the time and money, and what happens between the first call and the finished design?
What is a prototype design sprint, and how long does it take?
A prototype design sprint is a multi-week process, that turns your idea into a clickable prototype and a development plan before any code is written. During this time our expert Project Managers are taking all of their experience from launching +95 projects and applying that to your business. This means when you come out of the process, you have fully vetted idea that has turned into a the plan for your business.
At Founders Approach it typically takes 4 to 8 weeks and costs around $10,000. You finish with something you can put in front of customers, employees or investors, plus a clear picture of what building the real thing will take.
The process follows roughly the same rhythm for every Baltimore and Maryland business we take through it. Here is how the weeks usually break down.
Why not skip straight to development?
Because changes get more expensive the later they happen. In a sprint, changing direction costs a conversation and a revised screen. In development, the same change can cost a week. A sprint also gives you a realistic estimate. A quote written without a prototype is an educated guess, because nobody has agreed yet on what is being built. All those meetings where you and the Project Manager are discussing the business model, researching customers, identifying ideal customers, and user discussions are baked into the final designs.
Weeks 1 to 2: vision, business model and the feature list
The first two weeks are conversations, not drawings. Before anyone opens a design tool, we need to understand the business behind the idea.
- Vision: What does success look like a year after launch? Who is this for, and what problem does it solve for them?
- Business model: How does this make money or save money? A subscription, a one-time purchase and an internal tool that cuts hours of manual work each lead to a different design. Picking the right one to start with is a critical decision.
- Users: Who are the different people using it (customers, staff, admins), and what does each one need to get done?
- Feature list: Everything you want goes on the board. Then we sort it into what the first version needs and what can wait.
That last step is where most of the savings come from. Our guide on MVP vs. full product explains how to decide what makes the cut. Expect some homework between calls too, usually follow-up questions that only you can answer.
Weeks 3 to 6: wireframes, revisions and staying on course
This is the longest stretch, and it is where the idea starts to look like a product. We begin with wireframes, which are simple layouts of each screen. They let you react to the flow before anyone spends time on polished designs.
Then come the revisions. You see screens, give feedback, and see them again. A few rounds is normal and healthy. It is far cheaper to move a button in a wireframe than in finished code. This is where tools like Claude Design have become very helpful. What used to take hours to revise designs after a meeting typically takes our Project Managers 75% less. Here's an example from a recent project.

Two other conversations run alongside the design work:
- Going to market: How will people find this? Who are the first ten customers? Does the launch plan change what the first version must include?
- Staying aligned: We keep checking the designs against the goals from week one. New ideas show up constantly during a sprint. Some belong in the first version, and many belong on a later list. This is the same habit that keeps scope creep out of a project later on.
By the end of this phase the wireframes have become a clickable prototype: realistic screens you can tap through on a phone or click through in a browser.
Weeks 7 to 8: put it in front of real people
A prototype nobody has tested is just an opinion. The last two weeks are about showing it to your initial users and paying attention to what happens.
- If you have employees, get them on the call. For internal tools especially, the people doing the work every day will spot problems in minutes that leadership would never see.
- If it is consumer-facing, test with strangers. When you need honest opinions, what has worked best for us is testing through sites like UserTesting.com or paid SurveyMonkey surveys, where people who do not know you give their real reactions. That is not always possible, depending on the product and the budget.
- At a minimum, show friends and family. Just know they will not always give you the best feedback, because they care about you too much to tell you something is confusing. We don't really recommend this but it is the easiest so just keep that in mind. At minimum, it should not be the only thing you do.
Whoever you test with, give them a task to complete (for example, "sign up and book an appointment") instead of asking whether they like it. Where they hesitate tells you more than what they say. For more low-cost ways to do this, read how to test your app idea before you spend a dollar on development.
What do you walk away with?
At the end of the sprint you have three things:
- A clickable prototype that real users have tried.
- A development plan that lays out what gets built and in what order.
- An estimate of what the project will take to build.
You own all of it. Everything you pay Founders Approach to create belongs to you. You can use the prototype to raise money from investors, to get buy-in from your team, or to take the plan to any developer you choose.
What should you bring to the kickoff?
You do not need a polished pitch. A rough description of the idea, a few examples of apps or sites you like, and a sense of your budget and deadline are enough to start. We put the full checklist in what to send a developer before you ask for a quote, and the same list works well for a sprint kickoff.
Ready to see your idea on a screen?
If you run a Baltimore or Maryland business and are weighing a new app or software product, a design sprint is the lowest-risk way to find out whether it is worth building. Take a look at our Baltimore prototype and dev plan service, or contact us for a free consultation and we will talk through whether a sprint fits your idea.









