Mobile-first support with adjacent web and backend capability
Freelance Rate Card
Senior Mobile Engineer II
Kuala Lumpur based
Freelance Rate CardKuala Lumpur basedSenior Mobile Engineer II
Freelance mobile and web product support
Clean delivery for teamsthat need mobile and web work done properly.
For product teams that need help maintaining and improving existing products through mobile feature work, bug fixing, release support, and adjacent web or backend implementation.
Async-first collaboration with weekday replies within 24 hours
Built for teams that need a dependable part-time delivery partner across app and product work
Services
Mobile-first support, with web and backend help where it actually helps.
The offer is built around existing product support, not broad consulting theatre. Mobile is the core, with web and backend support where it meaningfully helps delivery.
Mobile Feature Work
Implement scoped features inside existing Flutter apps with attention to real-world product constraints.
Bug Fixing & Stability
Resolve product bugs, clean up rough edges, and improve release confidence before shipping.
Release Support
Support app store submission, build/signing issues, TestFlight or Play Console handling, and hotfix follow-up when scope is clear.
Web & Backend Support
Handle REST integration, Laravel, Next.js, and delivery support work that helps the product move forward across mobile and web.
Availability
Built for a calm part-time setup.
Best suited to 8-16 hours per month, with 16-20 as the practical ceiling.
Async-first support; calls are limited and messages are preferred.
Best run as one anchor client or one light retainer plus a small overflow client.
Capability
Strongest when the work stays close to product delivery.
Core delivery
- Flutter
- Next.js
- Feature implementation
- Bug fixing
- REST API integration
- Laravel support
- Crashlytics
- CI/CD workflow support
Scoped carefully
- Firebase Analytics
- Native iOS tasks
- Native Android tasks
- Release support
Packages
Simple packages with clear limits.
These packages fit the actual monthly bandwidth and keep scope realistic alongside a full-time role.
For small tasks
Ad Hoc Support
8h / month
For bug fixes, scoped implementation, and small release-related work inside an existing Flutter product.
Monthly fee
RM800
per month
Included hours
8h
Overage rate
RM 100
Best for
Ad hoc support when the team needs reliable help without committing to a big retainer.
Includes
- Up to 8 hours per month
- Async-first support for features, bugs, and cleanup work
- Weekday response within 24 hours
- Meetings count toward the booked hours
Best fit
Monthly Support
12h / month
For teams that need recurring help shipping inside an existing product, without the noise of a heavy freelance arrangement.
Monthly fee
RM1,140
per month
Included hours
12h
Overage rate
RM 95
Best for
A steady monthly block for feature work, bug fixing, and release support.
Includes
- Up to 12 hours per month
- Feature implementation and bug-fix bandwidth
- Release support when the scope is clear
- Async communication, calls only when needed
For one main client
Primary Retainer
16h / month
For one primary client who needs consistent help each month and can work well in an async-first setup.
Monthly fee
RM1,520
per month
Included hours
16h
Overage rate
RM 95
Best for
Meaningful support without pushing past a sustainable side-workload.
Includes
- Up to 16 hours per month
- Priority access to available monthly capacity
- Flutter delivery plus adjacent backend/web support when relevant
- Best kept to one anchor client at a time
How To Choose
Pick the package that matches the amount of support you actually need.
Choose Ad Hoc Support if
You have a few small fixes, one-off tasks, or light release-related work and do not need ongoing monthly coverage.
Choose Monthly Support if
You expect recurring work each month and want a stable block for features, bugs, and follow-up tasks.
Choose Primary Retainer if
You want one consistent part-time engineering partner and the work fits within a realistic 16-hour monthly ceiling.
How Billing Works
Clear rules before any work starts.
This is the part clients usually ask about: unused hours, extra hours, and how feature development is quoted.
Packages reserve time
Monthly packages reserve a block of engineering time for that month. They are not pay-only-for-used-time bundles.
Unused hours normally expire
If the included hours are not fully used within the month, they normally expire unless a rollover is agreed in advance.
Small feature work can fit inside a package
Bug fixes, smaller features, release work, and follow-up tasks can be handled within the package if the scope fits the included hours.
Larger feature work is quoted separately
If the requested feature is bigger, less defined, or likely to exceed the included hours, it will usually be quoted separately based on scope and estimated man-hours.
Simple Billing Rules
Monthly packages reserve a block of engineering time for the month.
Unused hours normally expire at month end unless a rollover is agreed in advance.
If work goes beyond the included hours, extra time is billed at the package overage rate.
Bigger feature work may be quoted separately based on feature scope and estimated man-hours.
Working style
Small, clear, and accountable.
1. Scope first
The work gets framed before a number is locked in.
2. Bounded delivery
Requests are grouped into clear blocks so nothing turns vague halfway through.
3. Honest follow-up
If the scope grows, the quote grows with it instead of being hidden.
Before I Quote
What I need from you first.
What needs to be built, fixed, or cleaned up
Which platform is affected: mobile, web, backend, or mixed
How urgent it is, and whether weekend work is expected
How many hours you roughly expect per month
Whether the work is one-off or recurring
What kind of teams is this best for?
Small product teams, founders, or former employers with an existing mobile product and some adjacent web/backend needs that need steady implementation support.
Do I need to choose a package immediately?
No. The package is usually picked after scope, urgency, and expected monthly hours are clear.
Can this work for one-off tasks?
Yes. Small one-off work fits the ad hoc model. Repeating work is usually better as a light monthly package.
What happens if I do not use all included hours?
Monthly packages reserve engineering time for that month. Unused hours normally expire at month end unless a rollover is agreed in advance.
What if I want a new feature built?
Smaller features can be handled within package hours if the scope fits. Larger or less-defined feature work is usually quoted separately based on feature scope and estimated man-hours.