Agencies do not need another SaaS reseller programme. They need a stack they can brand, deploy for a client and hand over without asking the vendor for permission every time the client wants a change. That is the practical case for a white-label source-code licence.
It is also a different business model from building a food delivery startup. The agency sells implementation, branding, integrations and support. The software licence is a line item, not the product. The margin comes from scoping the work correctly and not promising a custom platform for a template budget.
| SaaS reseller | White-label source-code licence | |
|---|---|---|
| Client billing | Agency pays vendor, marks up subscription | Agency charges for licence, build and support |
| Branding | Usually limited to logo and colours | Apps, admin, domain and code |
| Hosting | Vendor | Agency or client server |
| Custom work | Constrained by vendor roadmap | Any change the scope funds |
| Client ownership | Rental | Client owns the deployment (subject to licence) |
| Recurring revenue | Subscription margin | Hosting, maintenance, support retainers |
| Best fit | Small retainers, low ops | Project builds and managed delivery platforms |
Check the exact licence terms for client work, multiple domains and redistribution before quoting a project. Foodomaa's direct licence covers your installation; client work, multiple domains and resale may need separate terms, so confirm them with the vendor in writing.
The three agency models
Build and hand over. The agency installs, brands, integrates payments and publishes the apps, then gives the client the keys. Revenue is project-based. The risk is that the client disappears after launch and the agency has no maintenance income.
Build and manage. The agency hosts the platform and sells a monthly care plan: uptime, updates, bug fixes, menu support and reporting. This is the healthiest model if the agency has a support desk. The client gets a known monthly cost; the agency gets recurring revenue.
Build and operate. The agency runs the delivery business as a white-label operator, sometimes under its own brand. This is not really an agency model; it is an operating company. It needs rider management, restaurant recruitment and customer support, not just development.
Scoping the first client
- Confirm the client's model: single restaurant, multi-vendor, or hybrid.
- Count the apps and platforms: customer, restaurant, rider, web, admin.
- List the payment gateways and whether each is supported or custom.
- Decide who hosts, who owns the domain and who holds the app-store accounts.
- Write the support boundary: what is included, response times and what is billable.
- Plan the handover: repository, database, credentials, documentation and training.
Pricing the work without underpricing it
A common agency mistake is quoting the licence plus a few days of branding. A real launch includes menu migration, tax rules, delivery zones, gateway testing, app-store submissions, staff training and a launch support window. Those items are the project. Price them separately so the client can see what the software does and does not cover.
A simple structure: licence at cost plus a small handling fee; implementation as a fixed-scope project; hosting and care plan as a monthly retainer; custom features as change requests. That keeps the margin visible and avoids the trap of unlimited “small changes”.
Support and handover
Before launch, document the server, cron jobs, queue workers, payment credentials, SMS and map providers, app signing keys and backup process. If the client leaves, they should be able to take the deployment to another developer without rebuilding from zero. That sounds against the agency's interest; it is actually a selling point. Clients buy from agencies they can leave.
When an agency should not use a source-code licence
If the client wants a fully managed platform with no server responsibility, a SaaS reseller deal may be simpler. If the project needs a novel logistics algorithm or deep hardware integration, a product licence will not cover it; quote a custom build. And if the client's budget only covers the licence, the project is not funded. Say no before the scope becomes unpaid work.
See the white-label food delivery app page, the licence guide, or the $299 licence.