Case study · 2023
A peer-to-peer vehicle rental platform delivered in 6 working days.
FloRide needed a peer-to-peer vehicle rental platform. The Turo Clone base already carried the mechanics, so the engagement went where their product was actually different. We built the product; they launched the brand.
- Turo Clone · MXCar
- 6 working days our build time on the base
- Source code transferred to FloRide’s own account
- Solution
- Turo Clone
- Product
- MXCar
- Delivered
- 2023
- Stack
- PHP LARAVEL · MYSQL
- Build time
- 6 working days
- Blocks reused
- 16 of 20
- Source code
- Transferred
What already existed, and what did not.
The distinction that decides a project like this: the mechanics were proven before the engagement started, so the time went into the part that was theirs.
We build the product; the client launches the brand. That is the arrangement, and it only works if the handover is real: FloRide owns the source code, had a launch date in writing before work started, and can check every figure on this page against a public ledger.
None of us wanted to write fleet, availability, booking and settlement from scratch when it was already working on other platforms. We used that time on our fleet, locations and pricing.
Andre Gittens, CEO · Ride CorporationThe line between reused and built.
The work sat where it always sits on this base: fleet & classes, locations, pricing & deposits. Everything else on the list below arrived already built and proven on other engagements running the same base.
What FloRide actually needed.
A peer-to-peer vehicle rental platform is not one feature. It is 20 distinct pieces that all have to work together before a single customer can be served, and most of them already existed and had been proven elsewhere.
That distinction decides the shape of a project like this. A business does not need a dispatch engine or a settlement ledger to be invented again; it needs one that already works, then it needs the handful of decisions that make the product theirs rather than anyone else’s. The four below are the load-bearing pieces FloRide would otherwise have spent months building before proving anything to a customer.
Every platform of this kind has the same shape underneath: a set of load-bearing parts that must be correct before a single customer can be served, and a much smaller set of decisions that make it one business rather than another.
Building the first set from zero would have consumed the window before the second was even discussed. That is the decision this engagement turned on, and it was taken before any code was written.
What we settled before building.
Which of the 20 pieces were already solved, and which were genuinely FloRide’s to decide. Getting that line in the right place before any code is written is what keeps a Turo Clone engagement short, and it is the conversation we would rather have honestly than optimistically.
Where a scope genuinely does not fit a proven base, we say so during scoping and quote it as a custom build instead, even when that costs us the larger and more comfortable project.
Read the requirement back to first principles
What must exist at launch, separated from what a business can add once it has customers. Those are different lists and conflating them is what makes projects run long.
Base versus build, capability by capability
Each of the 20 capabilities assessed against the existing base as covered, partial or absent. Partial is treated as absent, because a half-fitting module costs more than a new one.
Mark what only FloRide could decide
4 decisions were commercial or jurisdictional rather than technical. Those were theirs, and the engagement is where they got implemented.
Agree the line before writing anything
16 pieces reused unchanged, 4 built. Fixing that line up front is what turns a platform of this size into a six-working-day build.
The parts that are genuinely hard.
Not marketing difficulty, actual difficulty. These are the problems any serious Turo Clone has to solve properly, and the reason building one from a blank page is a multi-quarter commitment rather than a sprint.
Each was solved once, on the base, and has been under load on other builds since. FloRide inherited the solutions rather than the problems.
Utilization is the business
An idle vehicle earns nothing. Fleet, locations and availability rules are the economics, not a feature.
Handover and return
Condition, documents, fuel and damage decide the final charge and are where disputes happen.
One-way and relocation
Vehicles ending up in the wrong city is a logistics problem the software has to model.
What we did not have to build for FloRide.
Every platform is made of the same mechanics underneath. This is the account of which of them FloRide paid attention to, and which were already solved.
Built from nothing, FloRide would have meant paying for the mechanics again: the accounts, the sessions, the payments, the admin, the permissions. That work is real, it is slow, and none of it is what makes this product different from the next one. Starting from the Turo Clone base moved that cost out of the project entirely, and the platform itself was deployed in 6 working days.
What that bought is attention. The engagement went into the 4 parts that were actually different, instead of being spread thin across 20 of them.
Everything that shipped with it.
The full working set FloRide took delivery of. Each piece was already built and proven on other engagements before this one started, which is the only honest reason a platform of this size stands up in six working days rather than months.
None of it is a demo or a scaffold. These are the same components running under other businesses in other markets, which means the failure modes are already known and already handled rather than waiting to be discovered by FloRide’s first real customers.
Reused from the Turo Clone base
Built for FloRide
The base this was built on.
The same architecture carries every Turo Clone on this page. The filled blocks are the parts built for FloRide.
Why none of this had to be written again.
Each of these was already running on other builds of the same base before FloRide started. That is the whole reason the platform was standing in days rather than months.
The decisions that were actually theirs.
A ready-made base does not remove these; it removes everything underneath them. Each one below is a choice FloRide had to make, and the engagement is where those choices got implemented.
Fleet & classes
Configured for FloRide during the engagement.
Locations
Configured for FloRide during the engagement.
Pricing & deposits
Configured for FloRide during the engagement.
Brand & theming
The identity carried across every surface, so it reads as the client’s product rather than a template.
What the six days actually cover.
Our build time on a ready-made base, and nothing else. The parts that sit with the client are named plainly.
White-label
The base is rebranded to the client’s identity across every surface.
Deploy
Stood up on the client’s own hosting, not ours.
Publish
Apps submitted from the client’s own developer accounts.
Handover
Source, schema, deployment configuration and architecture notes transferred.
The client supplies the hosting and domain, a verified developer account we publish from, branding and business details, an onboarded payment gateway with KYC complete, and any third-party API keys. Store review and merchant onboarding are controlled by Apple, Google and the payment provider, so those sit outside our window. Every figure here is defined on the facts page.
Who uses it, and for what.
Rather than screenshots of a product that has moved on since delivery, this is the set of surfaces that shipped and what each one is for. FloRide received every one of them, with the source behind each.
Every role here is a separate application with its own permissions, its own state and its own release path. Building them to work as one system is most of the engineering in a platform of this kind, and it is the part that was already finished before this engagement began.
What guards the platform.
Built into the base and hardened across every engagement running it, rather than bolted on at the end of this one. Security added late is security that has to be argued for; the controls below were load-bearing from the first deployment.
We claim the process, not a certificate. Miracuves does not hold ISO 27001, and we do not say otherwise: we build to the controls those frameworks require, and the evidence trail is there for an auditor who asks.
Role separation
Each surface sees only what its role permits, enforced server-side rather than hidden in the interface.
Audit trail
Who changed what and when, retained so a dispute can be answered with a record rather than a recollection.
Transport and storage
TLS end to end, credentials hashed, and anything sensitive at rest encrypted rather than merely obscured.
Secrets handling
Keys live in environment configuration on their own infrastructure, never in the repository we hand over.
Card data stays out
Payment details go to the gateway directly. The platform holds a reference, not a card number.
Backups and restore
Scheduled backups with a restore that was actually run, because an untested backup is a guess.
Dependency hygiene
Pinned versions and a documented upgrade path, so the handover does not start ageing on day one.
What it connects to.
The connection points are part of the base and were already written and tested. Which providers sit behind each one was FloRide’s decision, because those choices are commercial and jurisdictional rather than technical.
This is also where the client-side dependencies live. Gateway onboarding, KYC approval and merchant review are controlled by the provider, not by us, which is why they sit outside the build window rather than inside it.
Every one of these was already wired and tested in the base. What changed for FloRide was which account sat on the far side of it.
What it runs on.
The platform stack for MXCar. This describes the base as it stands today; FloRide took delivery of the source and has owned it since.
Where the six days went.
Our build time only. Store review and merchant onboarding are controlled by Apple, Google and the payment provider, so they sit outside this window and we do not count them as ours. Stating that plainly is the difference between a build time and a promise we cannot keep. Every figure here is defined on the facts page.
The six working days are guaranteed. If a ready-made platform is not live in six, we keep working free until it is. A deadline nobody is accountable for is not a deadline, and a guarantee nobody pays for is not a guarantee.
Throughout, a named team worked the build and sent FloRide progress on WhatsApp every working day. There was never a week where nobody knew where it stood, which is the part clients tell us they notice more than the date itself.
The bar below is that window, day by day. Nothing outside it is counted as ours, and nothing inside it waits on someone else.
This base has done this before.
FloRide was not the experiment. The base underneath this build had already carried other businesses in other markets before it carried theirs, which is the whole argument for reuse: the risk was retired by somebody else’s project, not by this one.
Across everything delivered since 2010 that is more than 9,000 products for over 6,000 businesses across 35+ industries. The eighty-four documented on this site are the ones with a named client and permission to show the work; most of the rest sits under NDA or white-label and is deliberately not here at all.
Every number on this page is defined and sourced on a public facts ledger. That is the whole instinct behind how this company is run: most vendors ask you to trust them, and we would rather you checked us. If we cannot back a claim, we do not make it, which is why you will not find a satisfaction percentage or an unnamed award anywhere on this site.
Blocks reused unchanged on this build, each already under load on other engagements.
ArchitectureDocumented builds running on the Turo Clone base, in different markets.
PortfolioProducts delivered for more than 6,000 businesses across 35+ industries since 2010.
Company recordApps published under clients’ own brands, counted per store release.
Company recordWhat we can state plainly.
No client figures were supplied for this build, so these are architectural and contractual facts rather than outcomes.
Full repository history, to the client’s own account
Miracuves delivery recordNone of us wanted to write fleet, availability, booking and settlement from scratch when it was already working on other platforms. We used that time on our fleet, locations and pricing.
What FloRide holds now.
The same on every engagement. What happened to the platform after handover was theirs to decide.
The questions that decide this.
Answered for this build. The same answers hold for every Turo Clone in the portfolio.
Do we own the code?
Yes. The full repository history transferred to FloRide’s own account at handover, with deployment configuration and architecture notes. It is not a licence and it is not held against a support contract.
How is six working days realistic?
Because 16 of the 20 pieces were built and proven before the engagement started. The six days are our build time on that base, not a calendar promise.
What sat with FloRide?
Hosting and domain, a verified developer account we publish from, branding and business details, an onboarded payment gateway with KYC complete, and any third-party API keys.
Will it look like everyone else’s?
No. The base supplies mechanics, not identity. Branding, flows and every customer-facing screen were built for this product.
Is this what the platform looks like today?
This describes what was delivered in 2023. What happened afterwards was FloRide’s to decide; the source transferred at handover. Clients move on, rebuild, or sell up, and none of that changes what was delivered or how it went.
Would you have said no to this project?
We are a good fit for a founder who wants a proven model launched fast, a deadline they can hold us to, and code they own outright. We are a poor fit for anyone who needs a team embedded in their office full-time, or who wants a blank page and a six-month roadmap. Being straight about that up front saves everyone a call.
Who actually worked on it?
A named team, not a rotating pool. Our leadership is public with real profiles rather than a stock-photo team page, and progress went to FloRide on WhatsApp every working day of the build.
Building something like this?
Tell us what you are building and we will say plainly whether a ready-made base fits it, including when the answer costs us the larger project.
- Ready-made platform deploys in 6 working days
- Custom builds run 2 to 8 weeks
- Source code transfers on every engagement
- Every figure here is defined on the facts page
