LIVE
MARKETPLACE · LOGISTICS
ChiliAuto
Moving & logistics marketplace in Prague. Two-sided dispatching.
● SERVICE · MARKETPLACE DEVELOPMENT
We operate a live marketplace.
We know what both sides need.
ChiliAuto matches moving crews to customers across Prague — two apps, a dispatch engine, and a payment layer, all live since 2024. Every decision we made building it, we use when we build yours.
1
Marketplace in production
2
Sides built & operated
Prague
Live market
2024
Launched
● CHAPTER 01 / IS THIS YOU?
Three kinds of teams build marketplaces with us.
EARLY STAGE
Founders with a matching problem and a market to prove
You've validated the idea with manual coordination. Now you need the software to replace the spreadsheets and WhatsApp groups — and a team that knows how to seed both sides.
OPERATIONAL
Businesses drowning in manual dispatch
Bookings, assignments, driver tracking, customer notifications — all done by hand. You've outgrown the workarounds and need a platform that makes coordination automatic.
SCALING
Platforms that have supply but can't convert demand
You have the supply side working. Buyers aren't converting. Trust is missing, onboarding is broken, or the matching logic isn't surfacing the right results. We've fixed all three.
If any of this sounds like your situation — let's talk.
Book 30 minutes
● CHAPTER 02 / WHAT YOU GET
Both sides built.
Neither side neglected.
Two-sided onboarding
Separate flows for supply and demand. Each side sees only what they need.
Matching & dispatch engine
Rules-based or algorithmic. Availability, location, capacity, rating — all wired in.
Payment & escrow layer
Stripe Connect or similar. Funds held, released on completion, refundable on dispute.
Trust & identity
Verification flows, document upload, background check hooks. Buyers need to trust sellers before transacting.
Ratings & review system
Bilateral ratings. Reputation built over time. Bad actors surface early.
Mobile-first for both sides
Supply-side needs a field app. Demand-side needs simplicity. We build both.
Admin & moderation panel
Approve providers, resolve disputes, manage categories. Operations without engineering.
Analytics & liquidity view
Supply/demand imbalances, conversion funnels, churn signals. You'll know where the market is thin before users do.
● OUR TEAM
One engagement.
Eight disciplines.
You don't coordinate a roster of freelancers. You get one cross-functional team with a single delivery manager answering to you. Engineering, design, QA, marketing, and executive oversight — fully handled.
CTO
Technical Director
Architecture decisions, code quality, technical strategy. The engineering starts and stops here.
PDM
Delivery Manager
Your single point of contact. Scope, timeline, and budget — owned by one person.
DEV ×2
Senior Developers
Two senior engineers on every build. No juniors carrying the core product.
UX/UI
Product Designer
Design grounded in user research. Prototyped, tested, then built — not decorated after.
QA
QA Engineer
Testing before your users ever see it. Bugs caught in staging, not in production.
MKT
Marketing Specialist
Go-to-market strategy and analytics built alongside the product, not bolted on after launch.
CEO
Account Director
Executive oversight on every engagement. When escalation is needed, it reaches a decision-maker within hours.
● ON-SITE VISITS
We come to you — if that helps.
When it makes sense, we visit your location before writing a single line of code. We sit with your team, watch how the business actually runs, and talk to the people who live in the problem every day. It's not a sales call. It's a listening exercise. The domain understanding you get from two days on-site takes months to build over video calls — and it shows in the product.
● CHAPTER 03 / RECEIPTS
One marketplace we operate ourselves.
Not a case study. A live platform with real transactions, real disputes, and a real on-call rotation.
● CHAPTER 04 / HOW WE BUILD
Five stages. Supply first, always.
01
MARKET AUDIT
1–2 weeks
WE DO
Interview both sides of your market. Map the trust gaps, friction points, and why coordination fails today.
YOU GET
Written market map, user personas for both sides, honest chicken-and-egg assessment.
02
PRODUCT DEFINITION
2 weeks
WE DO
Define both apps, shared data model, trust mechanism, and the MVP feature set that proves the market.
YOU GET
Product spec, architecture document, and a sequenced build plan.
03
SUPPLY-SIDE BUILD
6–8 weeks
WE DO
Build the supply-side first. Always. Without supply, the demand side has nothing to transact against.
YOU GET
Working supply-side app, provider onboarding flow, admin panel. Beta supply partners enrolled.
04
DEMAND-SIDE LAUNCH
4–6 weeks
WE DO
Build the demand side. Activate the matching logic. Handle the first real transactions — and the first disputes.
YOU GET
Full marketplace live, first 100 transactions processed, dispute resolution working.
05
LIQUIDITY GROWTH
Ongoing
WE DO
Matching optimization, retention loops, new categories, geographic expansion.
YOU GET
Monthly engagement, supply/demand balance metrics, growth levers documented.
● CHAPTER 05 / HOW WE SCOPE
Every marketplace is a different problem. The pricing reflects that.
We don't publish package prices because a gig economy platform and a B2B procurement marketplace are completely different builds. Here's how we figure out what yours costs.
01
Market audit sprint
Fixed-price discovery to understand your market, both sides, and the core trust problem. You walk away with a spec — whether or not we build it.
02
Scoped build
Once the audit is done, we propose a fixed scope with phased milestones. Supply first, then demand. Predictable invoices at each phase.
03
Ongoing growth
After launch, most clients stay on a monthly engagement. Liquidity optimization, new features, new markets. Pause or take it in-house anytime.
● CHAPTER 06 / WHAT YOU MIGHT BE THINKING
The honest answers.
They do — if you start by building the platform before you have supply or demand. We reverse that. The audit sprint is specifically designed to validate that the market exists before a euro is spent on code. We've declined marketplace projects where the market wasn't there. We'd rather tell you now than after the build.
Yes and no. Two apps share a backend, an auth system, a payment layer, and most of the business logic. The incremental cost of the second app is real but not double. The supply-side field app and the demand-side consumer app are built off the same foundation.
Identity verification flows, document upload, manual approval queues, and behavioral signals (cancellation rate, dispute history). We've wired all of these into ChiliAuto. They're not perfect, but they make fraud expensive enough that most bad actors go elsewhere.
Our CTO, on every engagement. Architecture, data model, matching logic — all owned by a single engineer who has operated a live marketplace. If you have technical leadership, they collaborate. If you don't, ours fills the gap.
Yes. ChiliAuto has a supply-side field app and a demand-side consumer app. We build both. React Native for cross-platform, native Swift/Kotlin when performance requires it. We're not a mobile-only studio — but we build mobile when the product needs it.
● CHAPTER 07 / FAQ
Practical questions.
Supply-side to demand-side launch: typically 12–18 weeks from kickoff. Faster if the matching logic is simple, slower if you need mobile apps on both sides.
Yes. From the first commit. Repository in your GitHub org, all licenses are yours.
Every engagement includes: CTO, Delivery Manager, two senior developers, product designer, QA engineer, marketing specialist, and account director. One delivery manager is your single point of contact.
Stripe Connect for most EU/US marketplaces. Paddle or local alternatives when the geography requires it. We wire payments to your domain model — not the other way around.
Yes. We start with a one-week audit — assess state, technical debt, and what's worth keeping. You decide what to do with the findings.
Yes, mutually. Send yours or use ours.
Tell us about your marketplace.
One live platform. Two sides. Real transactions since 2024. If you're building something similar, we've already made the mistakes so you don't have to.
REPLY IN 4 BUSINESS HOURS · NO SALES PIPELINE · MAYBE WE SAY NO