Resources · Deployment

From Signed Scope to live Orders in Four Steps

DeliveryStack is configured, not built from zero. Deployment is the work of fitting the core to your vertical, brand, and markets, then launching it in a first city with our team alongside yours.

Schedule a Platform Demo See the four steps
Typical timeline · one vertical, one city
01 · ScopeWeek 1
02 · ConfigureWeeks 2–3
03 · Brand and testWeeks 3–4
04 · LaunchWeeks 4–5

Custom features and integrations extend the timeline. Your proposal sets out the plan for your scope.

The Four Steps

Each step ends with a sign-off, so nothing moves forward on an assumption.

01

Scope

We agree what launches first: vertical, business model, city, app surfaces, and any custom work. The output is a signed scope and plan.

What we do
Requirements workshop with your team
Configuration and customisation list
Delivery plan with sign-off points
What you provide
Business model and launch city
Pricing, commission, and fee rules
Named decision-maker for sign-offs
02

Configure

The core is set up for your operation: zones, fare or delivery pricing, dispatch rules, payments, and roles. Custom features are built in parallel.

What we do
Zones, pricing, and dispatch set up
Payment gateway and integrations connected
Custom features built against the scope
What you provide
Payment gateway and merchant accounts
Service area and zone boundaries
Credentials for third-party systems
03

Brand and test

Apps and panels take your name, logo, and colours. Your team tests real orders or trips end to end before anything is public.

What we do
Brand applied across every surface
Test environment with sample data
Fixes from your acceptance testing
What you provide
Logo, colours, and app store copy
Test orders or trips by your ops team
Acceptance sign-off
04

Launch

Apps are published under your developer accounts and the platform goes live in the first city, with our team on hand through the first weeks.

What we do
App store submission and approval
Production go-live and monitoring
Hypercare support after launch
What you provide
Apple and Google developer accounts
Onboarded partners, drivers, or captains
Launch marketing in the first city

What You Own After Launch

The platform runs under your name. The relationships and the data are yours.

Your brand
Apps, panels, and emails carry your name. DeliveryStack does not appear to your customers.
Your app store listings
Apps are published under your Apple and Google developer accounts.
Your customers and data
Customer, partner, and order data belongs to you and can be exported.
Your pricing and rules
Fares, fees, commissions, and zones are set by you in the admin console.

After Go-Live

Launch is the start of operation, not the end of the project. Support continues under the plan you choose.

01

Hypercare

Close support in the weeks after launch while real volume tests the configuration.

02

Maintenance and updates

Platform updates, OS compatibility, and fixes under your support plan.

03

Expansion

New cities, verticals, or custom features scoped and quoted when you need them.

See case studies →Read the deployment FAQ →

Plan Your Deployment

Share your vertical and launch city. We will map the four steps to your scope.

Schedule a Platform Demo See Pricing