Workshop NowSmart workshop & roadside assistance platform
The complete Workshop Now platform: Customer and Technician apps for Android and iOS, Admin, Workshop and Fleet web portals, and a secure cloud backend with smart dispatch, live tracking, payments and integrations.
- Prepared for
- Austradelink International
- Fixed budget
- $15,000 USD
- Timeline
- 14–16 weeks
- Prepared by
- Kretoss Technology
The complete Workshop Now platform, delivered for a fixed $15,000
Austradelink International plans Workshop Now as one connected ecosystem for customers, workshops, mobile technicians, fleet operators and corporate clients across Saudi Arabia. This proposal covers the full platform described in the Project Overview, delivered in 14–16 weeks for a fixed price of $15,000 USD.
We will deliver two Flutter mobile apps (Customer and Technician, for Android and iOS), three React web portals (Administration, Workshop and Fleet), and a single Node.js/PostgreSQL backend. The platform includes rule-based smart dispatch, live technician tracking, online payments and wallet, in-app chat, digital signatures and invoices, multi-language (Arabic and English) and multi-city, multi-branch and multi-company support, plus the integrations and security controls listed in the Overview.
To deliver this scope at this budget, we build on one shared backend, one shared component library across the three portals, one mobile codebase, and managed cloud services. Where a requirement can be read at very different levels of depth, such as "AI-ready" or "ERP integration", section 5 defines exactly what is delivered, so there are no surprises at acceptance.
A multi-sided platform for maintenance and roadside help in Saudi Arabia
Workshop Now aims to become the leading digital platform for vehicle maintenance and roadside assistance in the Middle East. It connects individual customers (B2C), corporate clients (B2B), workshops, mobile technicians and fleet operators.
Services include car, truck and heavy equipment maintenance, refrigeration units, roadside assistance, mobile workshop services, battery and tyre services, diagnostics, electrical, mechanical and A/C work, preventive maintenance and fleet maintenance contracts.
Revenue is planned from service commissions, corporate contracts, subscriptions, roadside memberships, fleet management fees and premium services.
Strategic objectives this platform supports
- Digitise vehicle maintenance services
- Reduce service response time with smart dispatch and live tracking
- Improve customer satisfaction through transparency, ratings and chat
- Increase workshop efficiency with work orders, quotes and invoicing
- Support fleet digital transformation with a dedicated fleet portal
- Enable data-driven decisions through dashboards and reports
- Prepare for GCC expansion with multi-language, multi-city and multi-company design
Five connected applications on one secure cloud backend
Book, track, pay
Book a service or request urgent help, track the technician live, pay online or by wallet, chat and rate.
Navigate and deliver
Receive jobs, navigate, update status, capture photos and signatures, request parts, log time and see earnings.
Run the workshop
Services, technicians, inventory, work orders, quotations, invoices, customer records and performance reports.
Manage the fleet
Register vehicles and drivers, track vehicles, schedule preventive maintenance and analyse costs.
Operate the platform
Users, workshops, fleets, pricing, promotions, support, finance reports, BI dashboard and audit logs.
Service request lifecycle (final status set confirmed in Milestone 1)
Everything in the Project Overview, with clear definitions
Select a component to see its feature list. The table after the tabs explains how features that can be built at very different depths will be delivered.
Customer mobile app · Android & iOS (Flutter)
- Registration and login
- OTP verification by SMS
- Vehicle management
- Service booking (scheduled)
- Instant roadside assistance request
- Live technician tracking with ETA
- GPS location detection and map pin
- Online payments via one gateway
- Wallet: top-up, pay, refunds
- Promotions and coupon codes
- Service history and digital invoices
- Ratings and reviews
- Push, SMS and email notifications
- In-app chat with the technician
- Arabic and English with RTL layout
- QR code on job and invoice
Technician mobile app · Android & iOS (Flutter)
- Job assignment: accept or decline
- Turn-by-turn navigation via Google/Apple Maps
- Customer contact: call and in-app chat
- Status updates through the job lifecycle
- Photo upload (before/after)
- Customer digital signature on completion
- Parts request to the workshop
- Time tracking per job
- Earnings dashboard
- Live location sharing while on a job
- Availability on/off toggle
- Arabic and English
Workshop portal · Web (React.js)
- Service catalogue and pricing
- Technician management and schedules
- Inventory: parts, stock levels, low-stock alerts
- Work orders
- Quotations sent to customers for approval
- Invoicing with VAT and PDF invoices
- Customer database
- Performance reports
- Multi-branch support
- Parts requests from technicians
Fleet portal · Web (React.js)
- Fleet and vehicle registration (bulk upload)
- Vehicle tracking on map
- Preventive maintenance schedules and reminders
- Driver management and assignment
- Maintenance history per vehicle
- Cost analysis by vehicle, type and period
- Fleet reports with export
- Service scheduling and bulk booking
Vehicle tracking uses the last location reported by the driver's or technician's app. Hardware telematics devices are not included.
Administration portal · Web (React.js)
- User management
- Workshop management and onboarding
- Technician management
- Fleet and corporate client management
- Customer support: tickets and booking intervention
- Pricing and commission rules
- Promotions and coupons
- Finance reports: revenue, commissions, payouts
- Business intelligence dashboard
- Audit logs
- Role-based access control
- Service categories, cities and settings
Backend, database and smart features
- REST API for all five applications
- Real-time layer (WebSockets) for tracking, chat and live status
- Authentication, MFA and RBAC
- Multi-company, multi-branch and multi-city data model
- Smart dispatch (rule-based)
- Preventive and predictive maintenance reminders (rule-based)
- Payments, wallet ledger and commissions
- Digital invoices with QR code
- Notification service: push, SMS, WhatsApp, email
- Reporting and analytics data views
- Audit logging and data privacy controls
- Redis caching and job queues
Core data entities
- Companies, branches, cities
- Users, roles, permissions
- Customers, vehicles, fleets, drivers
- Workshops, technicians, schedules
- Bookings, dispatch, tracking points
- Work orders, quotes, invoices
- Inventory and parts requests
- Wallet ledger, payments, payouts
- Chat, reviews, promotions, audit log
Third-party integrations
- Google Maps and Apple Maps: geocoding, map display, routing hand-off and ETA
- Payment gateway: one gateway supporting mada, Visa/Mastercard and Apple Pay, chosen by the client
- SMS gateway: one provider for OTP and alerts
- WhatsApp Business API: template messages for booking confirmations and status updates
- Email service: transactional emails and invoices
- ERP, accounting, CRM and BI: secure integration API, webhooks and scheduled exports, plus one direct connector for a client-selected system with a documented REST API
Usage fees for maps, SMS, WhatsApp, email, payment processing and hosting are paid by the client directly to each provider.
Client provides
- Merchant account for the payment gateway
- SMS sender ID registration
- Verified WhatsApp Business account
- API access to the chosen ERP/CRM system
How key features are delivered
Several items in the Overview can be built at very different depths. This table sets the level included in the fixed price.
| Requirement | What is delivered in this proposal |
|---|---|
| Smart dispatch | Automatic assignment to the nearest available, qualified technician using distance, skills, workload and availability rules, with admin override. Machine-learning dispatch is not included. |
| AI-ready / predictive maintenance | Rule-based reminders by mileage, date and service history, and a clean data structure ready for future AI models. No trained AI models are included. |
| Live tracking | Technician location shared from the app while a job is active, updated every few seconds and shown to the customer and admin. No tracking outside active jobs. |
| Wallet | Customer wallet with top-up through the payment gateway, payment for services, refunds by admin and a full transaction history. Bank payouts are handled outside the platform. |
| End-to-end encryption | Encryption in transit (TLS) and at rest (database and file storage). Message-level end-to-end encryption of chat is not included. |
| ERP, CRM, accounting, BI | Integration API, webhooks and scheduled exports for all four, plus one direct connector to a client-selected system with a documented REST API. |
| BI dashboard | Built-in operational and financial dashboard with charts, filters and exports. Connection to an external BI tool uses the exports above. |
| Disaster recovery | Automated daily backups, point-in-time database restore and a documented, tested restore procedure. Multi-region active failover is not included. |
Seven roles, each seeing only what it needs
| Capability | Customer | Technician | Workshop mgr | Fleet mgr | Support | Finance | Super admin |
|---|---|---|---|---|---|---|---|
| Book service / request help | Own | — | For walk-ins | For fleet | On behalf | — | All |
| Vehicles | Own | Assigned jobs | Customers' | Fleet | View | — | All |
| Track & dispatch jobs | Own job | Own jobs | Branch | Fleet jobs | All | — | All |
| Work orders, quotes, inventory | Approve quote | Parts request | Branch | — | — | View | All |
| Payments, wallet, invoices | Own | Earnings | Branch | Fleet | View | All | All |
| Pricing, promotions, commissions | — | — | Own services | — | — | Yes | Yes |
| Users, workshops, fleets | — | — | Own staff | Own drivers | View | — | Yes |
| Reports, BI, audit log | — | Own stats | Branch | Fleet | Support | Finance | All |
Permissions are configurable by the Super Admin. Corporate client users use the Fleet portal with company-level access.
One backend, five clients, ready to scale across the GCC
Mobile
FlutterOne codebase for both apps on Android and iOS.Web portals
React.jsThree portals sharing one component library and design system.Backend
Node.js + ExpressModular REST API with a WebSocket real-time layer.Data
PostgreSQL + RedisRelational data, caching and job queues.Infrastructure
Docker on AWS or AzureContainerised, with staging and production environments. Kubernetes-ready.Security
TLS · MFA · RBACEncryption in transit and at rest, audit logs.Seven milestones, each with a clear sign-off
Expand a milestone to see its scope, deliverables and acceptance criteria. Mobile, portal and backend work overlap so the full scope fits into 16 weeks.
Budget follows complexity, not equal slices
| # | Milestone | Weeks | Amount (USD) |
|---|---|---|---|
| Total fixed price | 1–16 | $15,000 |
Proposed terms: each milestone is invoiced on written acceptance of its deliverables and payable within 7 days of invoice. Amounts exclude third-party fees (hosting, maps, SMS, WhatsApp, email, payment processing, Apple/Google developer accounts) and any applicable taxes such as VAT or withholding tax.
16-week plan with parallel build tracks
The backend starts as soon as the data model is approved. Mobile apps and portals are built in parallel against a published API contract. Week 16 is reserved for go-live support and buffer, so launch can happen in weeks 14–15 if approvals and third-party accounts arrive on time.
Key dependencies
- Data model and API contract approved before front-end integration (week 5)
- Payment, SMS and WhatsApp accounts active before integration (week 8)
- Customer and technician flows working before fleet and workshop testing
- Feature freeze before UAT (week 13)
Client approvals
- Requirements sign-off · end of week 2
- UI/UX design approval · end of week 5
- Mid-build demo review · week 10
- UAT sign-off · week 14–15
- Go-live approval · week 15–16
Third-party setup (client-owned)
- Cloud hosting account · by week 4
- Google Maps & Apple developer keys · by week 5
- Payment gateway merchant account · by week 6
- SMS sender ID and WhatsApp Business verification · by week 6 (approval can take several weeks)
- ERP/CRM API access for the chosen connector · by week 8
Tested as it is built, verified together before launch
Functional testing
Every feature tested against approved requirements on Android, iOS and the three portals, in Arabic and English.
API testing
Automated endpoint tests for success, validation and permission cases, handed over as a Postman/OpenAPI collection.
Integration testing
End-to-end runs of the full lifecycle: booking, dispatch, tracking, payment, invoice and rating, plus each third-party integration in sandbox mode.
Security testing
Checks against the OWASP Top 10, RBAC verification, MFA, input validation, secret handling and dependency scanning.
Performance check
Baseline load test of key APIs and the real-time layer to confirm response times at expected launch volumes.
User acceptance testing
Client team tests on staging with a UAT checklist. Critical and high defects are fixed before go-live.
Independent third-party penetration testing is recommended before large-scale launch and can be arranged at extra cost.
The security controls listed in the Overview, delivered in practical form
Included
- Encryption in transit (TLS) and at rest (database and storage)
- Multi-factor authentication for admin, workshop, fleet and finance users
- Role-based access control enforced on the server
- Secure APIs: token auth, rate limiting, input validation
- Passwords hashed with bcrypt or argon2
- Automated daily backups with point-in-time restore
- Documented and tested disaster-recovery restore procedure
- Audit logs of sensitive actions
- Data privacy controls: consent, data export and account deletion requests
- Payment card data handled only by the gateway (no card data stored)
Notes
- Message-level end-to-end encryption of chat is not included
- Multi-region active failover is not included
- Formal compliance certification is not included
Please confirm whether customer data must be hosted inside Saudi Arabia under the Personal Data Protection Law (PDPL). This decides the hosting provider and region and should be reviewed by your legal advisor.
Everything listed in the RFP deliverables
- UI/UX designs (Figma) for all five applications
- Android and iOS applications (Customer and Technician)
- Admin, Workshop and Fleet portals
- Backend system and database
- Test (staging) and production environments on the client's cloud account
- Full source code in a client-owned Git repository
- API documentation (OpenAPI / Postman)
- Technical documentation: architecture, setup, deployment, database schema
- User manuals for customer, technician, workshop, fleet and admin users
- Training: up to 3 remote sessions of 2 hours (admin/support, workshop, fleet)
- Deployment support and go-live support during the final week
- Transfer of all credentials, keys and configurations
Intellectual property
As required by Austradelink, on full payment of the contract value all rights in the source code, databases, APIs, designs, documentation and configurations transfer exclusively to Austradelink International, with unrestricted access to repositories and credentials.
App store publishing
Submission to the Apple App Store and Google Play is not included unless agreed separately. We provide signed release builds and a submission checklist. The client needs its own Apple Developer and Google Play Console accounts.
What we are assuming, and what we need from you
Assumptions
- Scope is as listed in section 5, at the depth defined there
- Saudi Arabia at launch, SAR currency, multi-city enabled
- Arabic and English only
- One payment gateway, one SMS provider, one ERP/CRM direct connector
- Up to two design revision rounds per application
- The Austradelink corporate website is not part of this proposal
- Requirements are frozen after Milestone 1; later changes go through section 16
Client responsibilities
- Nominate one decision-maker for approvals
- Review and approve deliverables within 5 business days
- Provide branding, Arabic and English content and service catalogue
- Provide pricing, commission and promotion rules
- Open and pay for hosting, maps, SMS, WhatsApp, email, gateway and developer accounts
- Provide API access and test credentials for the chosen ERP/CRM system
- Provide UAT testers for each user type
Items requiring client confirmation before development begins
- Payment gatewayWhich gateway (for example one supporting mada and Apple Pay)?
- SMS and WhatsApp providersPreferred providers, and status of the SMS sender ID and WhatsApp Business verification.
- Direct connectorWhich single ERP, accounting or CRM system should receive the direct connector?
- Dispatch rulesPriority between distance, skills, workload and workshop preference; whether technicians may decline jobs.
- Commission and payout modelHow commissions are calculated and how workshops and technicians are paid.
- Hosting and data residencyPreferred cloud provider and whether data must stay in Saudi Arabia (PDPL).
- Corporate clientsConfirm that corporate clients use the Fleet portal, and any contract-specific pricing rules.
- Launch citiesWhich cities and service categories go live first.
Not part of the $15,000 fixed price
These items are mentioned as future plans or revenue ideas in the client documents, or go beyond the delivery levels in section 5. They can be quoted separately through a change request.
A fixed price works when changes are handled openly
Client submits the change in writing (email or shared tracker).
We assess impact on scope, cost and timeline within 3 business days.
A written change order gives the extra cost, revised dates or a scope trade-off.
Work starts only after the client signs the change order.
The change is built, tested and added to the relevant milestone.
Small clarifications that do not change effort are handled without a change order.
Included bug fixing is separate from paid maintenance
60-day post-launch warranty
For 60 calendar days after go-live, we fix at no extra cost any defect where the delivered software does not work as described in the approved scope.
- Covers bugs in all delivered applications
- Critical issues acknowledged within 1 business day
- Fixes released to staging, then production
Excludes new features, requirement changes, third-party service outages or API changes, hosting issues, and changes made by others.
Maintenance and enhancements
Phase 9 of the RFP (maintenance and enhancements) is offered as a separate monthly plan or hourly support after the warranty, quoted on request.
- OS, framework and security updates
- Server monitoring and incident response
- New features and enhancements
- App store release management
No maintenance fee is included in the $15,000 development price.
How each delivery is reviewed and signed off
- Each milestone has its own acceptance criteria, listed in section 8
- We submit each deliverable with release notes and test instructions
- The client reviews within 5 business days (proposed)
- The client accepts in writing or lists defects against the agreed criteria
- We fix listed defects and resubmit; only the fixed items are re-reviewed
- Proposed term: with no response or defect list within 10 business days, the milestone is treated as accepted
Final project acceptance
- All features in section 5 work on production at the defined depth
- Full lifecycle passes end-to-end across all five applications
- All integrations work with the client's live accounts
- No open critical or high-severity defects
- Source code, documentation, manuals and credentials handed over; training delivered
Fixed-price full platform development
USD, fixed price for the full scope in this proposal, paid across seven milestones on acceptance.
- Scope
- Customer and Technician apps (Android & iOS), Admin, Workshop and Fleet portals, backend, integrations, security, documentation and training
- Duration
- 14–16 weeks from kickoff
- Warranty
- 60 days post go-live bug fixing (proposed)
- Excludes
- Third-party fees, taxes, app store submission, items in section 15
- IP
- Transfers to Austradelink International on full payment
- Validity
- 30 days from issue (proposed)