Six months is not a lot of time to build a marketplace.
Marketplaces are among the hardest products to build well. You need to serve two distinct user groups — buyers and sellers — with different needs, different workflows, and different definitions of success. You need transaction handling, search and filtering, user profiles, communication tools, and usually some form of trust or verification system.
When CarBro came to us with the idea for an automotive brokerage marketplace, they had a clear vision and a tight timeline. They wanted to be in market within six months. Not a landing page or a prototype — a functioning product that real users could use to buy and sell cars through a brokerage model.
Here is how we made it happen.
Week 1-2: Discovery That Actually Decided Things
We spent the first two weeks in intensive discovery. Not the kind of discovery that produces a beautiful slide deck and vague next steps. The kind that forces hard decisions.
What is the core transaction? A user lists a car, a broker evaluates it, a buyer purchases through the broker. That is the irreducible flow. Everything else is secondary.
What must exist for launch? User accounts, car listings with photos and details, broker evaluation workflow, search and filtering, messaging between parties, and payment processing.
What can wait? Advanced analytics, recommendation engine, mobile app, multi-language support.
These decisions were made in the first two weeks and we stuck to them. Every feature request that came in later was evaluated against one question: does this need to exist for the core transaction to work?
Week 3-8: Building the Core
With the scope locked, we moved fast. Our approach was to build the transaction flow end-to-end first — even if it was ugly — and then iterate on each piece.
By week four, you could create a listing, and a broker could see it. By week six, the full cycle worked: list, evaluate, match with buyer, complete transaction. By week eight, the search and filtering were functional and the UI was approaching production quality.
We ran weekly demos throughout this period. Every Friday, the CarBro team saw working software. Not mockups, not progress reports — the actual product running in a staging environment. They could click through it, find issues, suggest changes.
This rhythm meant we never drifted far from what CarBro actually wanted. The maximum cost of a misunderstanding was five working days.
Week 9-14: Hardening
The second phase was about making the product reliable enough for real users. This is where many MVP projects fall apart — the core features work in demos but break under real conditions.
We focused on:
- Edge cases in the transaction flow. What happens when a listing is edited after a broker starts evaluating it? What if a buyer and seller are in different time zones? What if a payment fails halfway through?
- Performance under load. A marketplace with no users is easy to run. We load-tested to ensure the product could handle the initial user base without degrading.
- Security basics. User authentication, input validation, secure payment handling. Not enterprise-grade security theater, but the fundamentals that protect real users and real money.
- Mobile responsiveness. We did not build a separate mobile app, but the web experience needed to work well on phones since car shopping is heavily mobile.
Week 15-18: Launch Preparation
The final phase was about everything around the product: deployment infrastructure, monitoring, error tracking, and making sure the team could operate the product after we handed it over.
We also ran a soft launch — a small group of real users using the product in production while we watched for issues. This caught several UX problems that no amount of internal testing would have found. Real users do things you never expect.
What Made the Timeline Possible
Looking back, several factors made the six-month timeline work:
Ruthless scope control. We said no to good ideas regularly. A feature that would take two weeks to build might have been valuable, but if it was not essential for the core transaction, it waited.
Weekly demos. These kept everyone aligned and prevented the accumulation of misunderstandings that cause late-project rewrites.
Experienced team. This was not our first marketplace. We had patterns and architectural decisions we could reuse, which saved weeks of deliberation.
A decisive client. CarBro made decisions quickly. When we presented options, they chose the same day. Projects stall when decisions take weeks.
Discovery that forced decisions. By making hard choices in weeks one and two, we avoided the months of ambiguity that kill timelines.
What Came After
The six-month MVP was not the end — it was the beginning. After launch, we continued working with CarBro on the features we had deliberately deferred: analytics, enhanced search, notification systems, and other improvements informed by actual user behavior rather than assumptions.
This is the real power of a focused MVP: it gets you to market fast, and then real users tell you what to build next. Every feature added after launch was validated by actual demand, not guesswork.
Have a product idea with an ambitious timeline? Talk to us about how our sprint-based approach can get you to market faster than you think.