Three branded solutions,
delivered in two waves.
A focused cloning, rebranding, frontend-customisation, and redeployment engagement: Wave 1 delivers two solutions together first. The third is Wave 2 and can start within one month after Mr Nayeem confirms it.
Reuse the proven project. Change only what each brand needs.
The engagement creates three independent clones of the existing project. Each clone receives its own brand identity, agreed minor frontend adjustments, configuration, build, and deployment to the client’s servers. The underlying project and operating logic remain the foundation; this is not a ground-up rebuild. Two solutions are handled together as the first delivery wave. The third remains included at the same per-clone commercial terms and is Wave 2, which can start within one month after Mr Nayeem confirms it.
Launch two solutions efficiently
Run the first two clones together, sharing the confirmed delivery flow while keeping branding, configuration, and deployment independent.
Keep change controlled
Limit implementation to rebranding and minor frontend changes so the proven core remains stable and commercially predictable.
Reserve the third solution
Start the third clone only in Wave 2, when Mr Nayeem confirms it in writing. Once confirmed, it can begin within one month.
Deliver to client infrastructure
Build and redeploy each completed solution to the client’s servers, with app-store publishing available as a separate service.
One established core. Three independent branded deployments.
The commercial model stays simple because the work focuses on controlled reuse, visual adaptation, and deployment rather than redevelopment of the underlying product.
Clone the complete project
Prepare an independent project instance for each solution, including the existing backend, dashboards, web frontend, and mobile applications required by the confirmed flow.
Rebrand and refine
Apply the approved name, logos, colours, store assets, and minor frontend adjustments without changing the established core workflows.
Build and redeploy
Configure, validate, and deploy each solution to the client’s servers, with optional publication through The Mok Company’s developer accounts.
Clone, rebrand, adjust, and redeploy.
Each solution follows the same controlled scope. Mr Nayeem will confirm the final operating and deployment flow before implementation begins.
Three independent project clones
Create three independent branded solutions from the same proven platform, with independent branding, configuration, build outputs, deployment targets, and mobile-app listings. Each solution includes a frontend revamp across one website, two dashboards, and three mobile apps, so no solution is presented as a direct clone.
Branding application
Replace names, logos, colours, icons, splash screens, store artwork, contact details, and other agreed brand-facing elements across the web and mobile frontends.
Minor frontend customisation
Make controlled presentation and functional adjustments to all customer and vendor touchpoints (website, Admin dashboard, Vendor dashboard, and mobile apps) to keep each solution distinct. B2B Solution 1 also includes RFQ workflow work across the website, Admin dashboard, Vendor dashboard, customer app, and vendor app after requirement confirmation.
Three mobile applications per OS
Prepare the Customer, Vendor, and Delivery applications for Android and iOS for each clone, using the approved configuration and brand assets.
Wave 1: first two solutions together
Configure and deliver only the first two solutions in parallel after the delivery flow, brand packs, requested changes, approved quotes, server access, and responsibilities are confirmed.
Solution 1 is a B2B project.
Solution 2 is an Al-Nasser-style branded implementation with logo/name refresh and homepage updates only.
Wave 2: third solution after confirmation
Start the third solution only in Wave 2, once Mr Nayeem gives written confirmation and approves its final scope, changes, and quote. After confirmation, implementation can begin within one month.
Client-server deployment
Build and redeploy the agreed project components to the client’s prepared servers according to the confirmed infrastructure and release flow.
Optional app-store publication
Publish each clone’s three Android applications and three iOS applications through The Mok Company’s developer accounts as a separately priced service. Each publishing business must have its own valid D‑U‑N‑S Number before submission.
A repeatable flow for each branded solution.
Each clone follows the same commercial and delivery gates. Wave 1 is grouped as Solution 1 + Solution 2; Solution 3 is in Wave 2 and can begin within one month after written confirmation.
Confirm flow and inputs
Mr Nayeem confirms the operating and deployment flow. The client provides final brand assets, store information, server specifications, access, legal content, and required third-party accounts.
Clone, configure, and rebrand
Create the independent project instance, apply the approved brand, configure environments, and make the agreed minor frontend changes.
First demonstration
Present the working branded solution for consolidated review within 3 to 4 weeks. Approved minor corrections are completed before final client-server deployment.
Deploy and publish
Deploy the completed project to the client’s prepared servers. Where selected, prepare and submit the three apps per OS through The Mok Company’s developer accounts.
Two solutions first. The third starts in Wave 2.
Delivery dates for both waves are confirmed after Mr Nayeem approves the flow and supplies complete brand assets, server access, store content, and technical requirements. Wave 1 is delivered as a grouped first package (Solution 1 + Solution 2); Wave 2 begins within one month after written confirmation.
Wave 1 solutions together
Solution 3 (Wave 2) on written confirmation
50% down payment before kickoff, 25% after first demo, and 25% on final delivery to client servers for each solution. First demo occurs within 3 to 4 weeks, with final delivery in another 3 to 4 weeks.
Starting from $4,500 per clone. Wave 1 is grouped (Solution 1 + Solution 2), with Solution 1 (B2B) estimated at $7,000 depending on complexity, and Solution 2 (Alnasser clone) estimated at $4,500 for cloning, while Wave 2 starts from $4,500 once Mr Nayeem confirms requested changes and final quotes.
Each solution starts from $4,500 for rebranding, anti-clone frontend differentiation, and controlled frontend-adjustment scope. Total deliverables for all 3 solutions: 18 mobile applications (3 apps × 2 OS × 3 solutions) + 3 websites + 6 dashboards = 27 items. All 3 solutions include a revamp across one website, two dashboards, and three mobile apps per solution. Wave 1 is grouped and starts from $9,000 total (Solution 1 + Solution 2), while B2B complexity in Solution 1 can raise its budget to $7,000. Solution 2 is the Al-Nasser-style variant with a stronger visual rebrand and homepage updates. Solution 3 is in Wave 2, starts from $4,500, and can begin within one month after Mr Nayeem confirms requested changes and final scope. App-store publication is optional and charged per clone: $600 per OS, or $1,200 for both Android + iOS (6 app submissions for one clone).
Budget Summary
Payment Schedule · Per Clone
Google Play Publication
Per clone, The Mok Company can submit 3 Android apps (customer, vendor, delivery) through its Google Play developer account. Alternatively, if client provides and manages its own Play account, we can publish from that account instead. A valid D‑U‑N‑S Number and completed Google/Apple prerequisites are required.
Apple App Store Publication
Per clone, The Mok Company can submit 3 iOS apps (customer, vendor, delivery) through its Apple Developer account. Alternatively, client can provide its own Apple account and permissions. A valid D‑U‑N‑S Number and Apple's legal/compliance requirements must be in place.
Six App Submissions
3 Android + 3 iOS app submissions for one clone. If using The Mok developer accounts, we handle both accounts per clone. If client accounts are used, client must complete account access and D‑U‑N‑S and compliance setup.
Maintenance & Ongoing Support
Active support and minor enhancements are included as a monthly service for the selected scope. This covers routine monitoring, minor tweaks, issue triage, and minor improvements as needs evolve.
D‑U‑N‑S Number
Each publishing business must already have or register a valid D‑U‑N‑S Number. If registration is required, budget typically ranges from approximately $1,100 to $1,500 per business through the external process.
Optional Translation Add-on
Per clone, we can translate: 1 website, 2 dashboards, and 3 mobile apps into additional languages beyond Arabic. This includes translation content work only.
Client-hosted delivery with clear publishing boundaries.
The base engagement ends with deployment to the client’s prepared servers. The client remains responsible for suitable infrastructure, access, domains, certificates, third-party services, data, and recurring operating costs.
Client-Server Redeployment
Configure and deploy the agreed project components to the client’s prepared infrastructure according to the flow confirmed by Mr Nayeem.
Developer-Account Publication
The Mok Company can submit the three applications per OS through its Google Play and Apple Developer accounts at $600 per OS per clone, or publish through client-provided accounts where those are already active.
Maintenance & Ongoing Support
Monthly service including active support, routine monitoring, and minor enhancements for selected cloned solutions. Optional monthly fee: $400 per project.
Infrastructure, D‑U‑N‑S, and Compliance
Provide suitable servers, credentials through an approved secure channel, domains, certificates, a valid D‑U‑N‑S Number for each publishing business, privacy policies, terms, store declarations, support contacts, test accounts, data, and timely approvals.
A clone-and-customise engagement, not a product rebuild.
The starting $4,500 per-clone scope covers three controlled, independently branded releases, applying approved branding, anti-clone frontend revamps (website, 2 dashboards, 3 apps), baseline frontend adjustments, build preparation, validation, and deployment to the client’s servers. Mr Nayeem’s requested changes are reviewed and quoted per clone before kickoff; work beyond the baseline increases that clone’s approved price. Major UX redesign, new backend features, new integrations, architecture changes, data migration, infrastructure procurement, hosting, domains, licenses, third-party services, store fees, D‑U‑N‑S registration, policy remediation, and ongoing support are excluded unless the optional Maintenance add-on is selected per project. App-store publication is a submission service; The Mok Company can publish from its accounts, or use client-provided accounts if already enabled and compliant. Each publishing business must have a valid D‑U‑N‑S Number and pass Apple/Google review requirements. The third clone belongs to Wave 2 and starts when Mr Nayeem confirms it in writing; the target start is within one month. Final ownership, licensing, warranty, support, and source-code handover terms are defined in the signed agreement.
Companies that
chose The Mok Company.
A growing portfolio of brands across energy, hospitality, travel, automotive, retail, and real estate — all delivered under one roof.
Our masterpieces live in production.
A snapshot of platforms shipped under The Mok Company across enterprise, e-commerce, real estate, energy, and hospitality.
Taggz
Lexus Yemen
Hino Yemen
Atta Sons
Futura Energy
Turbo Compression
Printout Solutions
Triangle Heavy Equipment
Confirm the flow, then start the first two clones.
The first delivery wave can begin once the commercial terms, scope boundary, inputs, and deployment flow are formally confirmed.
Three branded solutions.
One controlled delivery flow.
The Mok Company will reuse the established project carefully, keep changes focused, and deliver each branded clone through clear commercial and technical gates.