The company
One marketplace, two brands, and a boundary we don't cross.
Klick is a single marketplace company. KlickDeliver moves parcels and KlickRide moves people, on one core that treats the difference between them as configuration rather than as two products stapled together.
How we're put together
A courier job and a ride are the same machine with different cargo.
Both need identity, geography, supply, dispatch, quoting, payment orchestration, financial events, notifications, support and reputation. They differ in payload, pricing policy, worker eligibility, insurance and regulation — and every one of those differences is expressed as configuration or as a module, never as a fork.
What Klick owns
- Quoting, and the policy version every quote was produced by
- Dispatch, the job's state, and the evidence attached to each transition
- Payment orchestration — the hold, the capture, the refund
- Invoices and receipts for individual deliveries and rides
- Safety processes, and the corroboration a ride's start and end rest on
- A durable financial outbox, so nothing that happened is lost on the way out
What it deliberately doesn't
- Accounting. Journals, payables, receivables, revenue, tax and reconciliation belong to AccountsAI, and Klick does not keep a second ledger beside it.
- Consolidated B2B invoicing. Where an account wants one periodic bill instead of a charge per job, BillAI aggregates the usage and issues it.
- A dependency on any of them at dispatch time. Patterns from LogisAI's geo and routing work were reused as Klick's own code, not called as someone else's service.
Four rules
The constraints the build isn't allowed to break.
These are not aspirations in a document. A test suite fails the build on a region or currency literal in shared code, on a governed policy value frozen as a constant, on an import of a sibling product, and on floating-point money — and each of those checks has its own test proving it fires when the violation is planted.
No region limits in code
Nothing in the shared platform names a city or a country. Which markets are open is configuration approved by a person, and the absence of region-specific code never blocks a launch that doesn't need it.
Regional code lives in regional services
When a place genuinely needs different behaviour, it gets its own service inside that region's cell — and its answers are snapshotted so a decision can be replayed later. It never arrives as a branch in shared code.
Config over code
Anything expressible as governed configuration must not become code. Pricing is written in a language that cannot loop, call out or reach the network — a restriction nobody can misconfigure is worth more than one that has to be remembered.
The sibling products stay domain-pure
No marketplace concept — rides, parcels, drivers, jurisdictions — is allowed into AccountsAI, BillAI or LogisAI. They publish their own facts; Klick subscribes.
The reason is plain: the next market, vertical or brand should be an approval someone signs, not an engineering project someone schedules. A guardrail nobody has watched fail is one nobody can trust, so each of ours has been watched failing.
How we're growing
Demand first, drivers in cohorts, spend only past a threshold.
No network before a zone
The company does not subsidise a citywide network before one dense zone works. Demand is seeded first and drivers are activated in cohorts against it, so nobody is recruited into an empty queue.
Thresholds, not enthusiasm
Acquisition spend expands only when pickup time, completion, repeat use, contribution and support capacity all pass numbers agreed in advance — agreed before we know whether we'll like the answer.
Hypotheses, not forecasts
The year-one planning case is a set of assumptions about insurer pricing, processor terms, legal treatment and retention. Real numbers replace them as they arrive, including the ones that make the plan worse.
Talk to us.
Drivers, businesses, regulators and people who want to argue with the four rules — all at the same address.