> ## Content Index
> Fetch the complete content index at: https://www.artisancraft.dev/llms.txt
> Use this file to discover other available public pages before exploring further.

# Episode 4 — Building the MVP
- URL: https://www.artisancraft.dev/episode-4-building-the-mvp/
- Published: 2025-12-29T09:07:25.000Z
- Updated: 2025-12-29T09:08:45.000Z
- Description: Episode 4 tells the story of building the MVP: the small breakthroughs, the unexpected challenges and the decisions that shaped dotmap’s first usable version.
- Author: Daniel Plomp
- Tags: saas, buildinpublic, productdesign, mvp, founderjourney

Every product looks polished in hindsight.  
The MVP stage is where things are messy, fragile and surprisingly exciting.

dotmap started as a rough prototype: a basic map, a few markers and just enough UI to test the idea.

But that early version revealed almost everything about what dotmap would eventually become.

---

## The first glimpse of the idea

The moment the first real markers appeared on the map — representing test profiles — the concept clicked.

Seeing people placed in real locations made the product feel alive.  
It felt intuitive in a way no wireframe could replicate.

---

## Simplifying the experience

The hardest part of the MVP wasn’t building features — it was deciding what not to build.

Originally, there were ideas for:

- activity feeds
- in-app connections
- messaging
- recommendations
- team pages

They were all removed.

The MVP had to answer one question only:

**Does a map-first directory make sense?**

Everything else was noise.

---

## The challenges that shaped the product

Some of the biggest breakthroughs came from unexpected frustrations:

- showing overlapping markers without clutter
- presenting profiles cleanly across devices
- making filters intuitive instead of overwhelming
- designing a professional profile that felt honest and focused
- striking the right balance between “directory” and “portfolio”

These weren’t technical problems — they were *experience* problems.

And solving them helped define dotmap’s overall philosophy.

---

## The moment it felt real

When the first complete end-to-end flow worked…

1. create an account
2. set your professional details
3. add skills
4. appear on the map
5. become discoverable

…dotmap officially transformed from an idea into a product.

---

## Next episode

Episode 5 explores why supporting multi-stack professionals is essential — and how dotmap avoids ecosystem silos.

## All episodes

- [Episode 0 - Building dotmap](https://www.artisancraft.dev/building-dotmap-episode-0/)
- [Episode 1 - Why I started building dotmap](https://www.artisancraft.dev/episode-1-why-i-started-building-dotmap/)
- [Episode 2 — Designing the concept](https://www.artisancraft.dev/episode-2-designing-the-concept/)
- [Episode 3 — A map-first way to explore tech](https://www.artisancraft.dev/episode-3-a-map-first-way-to-explore-tech/)

[![CTA Image](https://storage.ghost.io/c/8f/6e/8f6ec642-540e-4f85-ac9b-beb628cb9cfd/content/images/2025/10/symbol-2.png)](https://www.artisancraft.dev/consulting-services/) 

I offer hands-on consulting to help you resolve technical challenges and improve your CMS implementations.

Get in touch if you'd like support diagnosing or upgrading your setup with confidence.

[Learn more ](https://www.artisancraft.dev/consulting-services/)