Every number we publish,
defined and defended.
Marketing pages round up. This page doesn't. Below is every significant claim on miracuves.com — what it means, how it's counted, and where you can check it against sources we don't control. If any page on this site disagrees with this ledger, the ledger wins and that page is wrong.
- Jul 2026
- Last audited
- Quarterly
- Audit cycle
- Oct 2026
- Next review
- 5 days
- Correction SLA
Company registry
These facts don't need our word for it — every entry is on a public register, and the identifiers copy with one click for your own diligence.
Claims ledger
Each record carries the claim, its exact definition, the counting method, and a way to pressure-test it yourself. Re-audited quarterly.
Projects delivered since 2010
- What counts
- Any paid engagement with a delivered outcome — a deployed clone solution, a custom build, a major feature module, or a completed maintenance contract. One client can account for many projects.
- What doesn't
- Proposals, demos, free feasibility studies, abandoned engagements, internal tools.
- Method
- Tallied from delivery records in our project-management systems, 2010 to present, including pre-incorporation delivery by the founding team.
- Check it
- Sample the output — case studies, named client stories, live demos on every solution page.
Apps published
- What counts
- Client applications that reached a public release — an app-store listing or a production deployment. Android and iOS builds of one product count once each, because each is a separate release effort.
- Method
- Release logs and store-listing records, 2010 to present.
- Check it
- Store listings are linked from individual case studies where the client has approved disclosure.
Clients served
- What counts
- Distinct paying customers — a founder, company, or agency that completed at least one paid engagement. Counted once each, no matter how many projects they ran with us.
- Method
- De-duplicated customer records, 2010 to present.
Ready-made clone solutions
- What counts
- Distinct, maintained products with their own codebase, demo environment, and solution page — not theme variations of a single product.
- Method
- Live count of the solution catalog. This is the canonical figure; any page still reading "60+" is outdated and being corrected.
- Check it
- Count them on the solutions grid — or open one running right now: MXRevolut live demo.
Ready-made launch timeline
- What it means
- Six working days from kickoff - requirements and branding assets received, payment confirmed - to a live, branded deployment of a ready-made solution. In those six days we white-label and rebrand the solution with your details, deploy it to hosting you provide, and publish the apps to your own developer accounts.
- What it doesn't
- Custom feature development, app-store review time (Apple and Google control that), or days spent waiting on client assets. Custom builds run 2-8 weeks, scoped individually.
- What you provide
- Six working days is our build time, and it does not run past six. The clock starts when these are in hand:
- Developer account - Google Play or App Store, owned by you and verified. We publish from it; the account and the listings stay yours.
- Branding assets - name, logo, colour palette for the white-label rebrand
- Business and legal details - listing entity, privacy policy, terms of service. These are yours to supply; we cannot write them for you.
- Payment gateway account - merchant onboarding and KYC completed with your provider. We do not apply on your behalf.
- Third-party API keys - maps, SMS or OTP delivery, push notifications
- Hosting and domain - we deploy to infrastructure you provide
- Backed by
- A written guarantee in every ready-made contract: miss the timeline for reasons on our side, and we work free until launch. Terms in the refund policy.
Ready-made pricing floor
- What it means
- The entry price of our least expensive ready-made solution — fixed quote, source code included. Products price higher with complexity, and each solution page's stated price is authoritative for that product.
- Includes
- Source-code ownership on delivery, branding setup, deployment, plus the canonical support terms in FACT-007.
Support, bug resolution & product evolution
- What it means
- Every ready-made solution carries three cover periods from launch: 60 days of dedicated platform guidance, 6 months of priority bug resolution, and 12 months of continuous product evolution. This is the single canonical support promise; any page citing a different duration is outdated and being corrected.
- Dedicated platform guidance
- 60 days of direct access to the team that built your deployment - configuration, admin walkthroughs, store submission questions and day-to-day operational help.
- Priority bug resolution
- 6 months in which defects in the delivered solution are queued ahead of other work and fixed at no additional cost.
- Continuous product evolution
- 12 months in which improvements made to the underlying solution base reach your deployment.
- What it does not cover
- New features you commission after handover, third-party service fees, or work caused by infrastructure you choose to change. Those are quoted separately at a fixed price before any work starts.
- Beyond that
- Extended support runs under AMC agreements with defined SLAs, scoped per client.
First-response time
- What it means
- A human reply to new inquiries within 2 hours during working hours — Mon–Sat, 10:00–19:00 IST. Outside those hours, first thing the next working day. The single response-time promise across the site.
- Method
- Measured on inbound WhatsApp messages and form submissions.
Industries served
- What counts
- Distinct verticals with at least one delivered client project — fintech, OTT, ride-hailing, food delivery, healthcare, real estate, creator economy, and onward.
- Check it
- The spread is visible across case studies and the solutions catalog.
Canonical values
The quick-reference version. Our own team writes pages from this table — you're welcome to hold us to it.
| Claim | Canonical value | Applies to |
|---|---|---|
| Founding narrative | Operating 2010 · Inc. 2023 | Every page. No other founding dates are valid. |
| Catalog size | 90+ solutions | Ready-made clone products. |
| Launch timeline | 6 working days | Ready-made only. Custom: 2-8 weeks, scoped. |
| Pricing floor | from $1,899 | Cheapest ready-made. Each solution page is authoritative for its own price. |
| Support terms | 60 days + 12 mo updates | All ready-made solutions. Extended via AMC. |
| Response time | < 2 hrs (work hours) | New inquiries, Mon–Sat 10:00–19:00 IST. |
| Quality claim | QA process, never "bug-free" | Every page. "99.9% bug free" is retired. |
What we don't claim
Precision cuts both ways. For the record:
Bug-free software
No software is bug-free and we won't tell you ours is. We claim disciplined QA, a security checklist on every release, and 60 days of support to fix what slips through.
Certifications we haven't earned
We display no badge without the certificate behind it. When ISO 27001 is complete, it will be linked here — not before.
Inflated enterprise scope
Where large brand names appear in our portfolio, the case study states the exact scope of our work. We built modules and platforms for big brands — we did not build those brands.
Corrections log
When a claim on our site turns out to be outdated, inconsistent, or wrong, we fix it and record it here. An honest company's numbers change; a dishonest one's never do.
Published what the client provides for a 6-day launch. FACT-005 promised six working days "from kickoff" without ever defining what kickoff required. The inputs are now listed inside the record, so the condition on the promise is public rather than explained on a call.
Corrected the custom-build range to 2-8 weeks. This ledger read "2-6+ weeks" while service pages read "2-8 weeks." Canon: 2-8 weeks, scoped per project. Genuinely complex builds are quoted beyond that in writing before work starts.
Removed "99.9% bug free." The claim was unverifiable. Replaced with an accurate description of our QA process.
Unified founding-date references. Pages variously cited 2013 and 2010. Canon: operating since 2010 (as SimTechnos until Feb 2022), incorporated as a Pvt. Ltd. in July 2023.
Standardized support terms. Pages variously cited "60 days" and "12 months." Canon: 60 days of post-launch support plus 12 months of free product updates.
Standardized the catalog count at 90+. Older copy citing "60+" predates catalog growth and is being updated.
Verify us without asking us
Independent sources we don't control:
Found a number that doesn't hold up?
If any figure on miracuves.com contradicts this ledger — or this ledger itself looks wrong — tell us. Verified corrections are fixed within 5 working days and recorded in the log above, permanently.
Report an inaccuracyPRECEDENCE RULE — if any page on miracuves.com conflicts with this ledger, the ledger is correct and the page is in error. Ledger v3.1 · August 2026.
