Questions
Answers before you ask
The questions operations directors, CIOs and owners raise most often in a first conversation with us — answered directly.
Working with White Owl
What does the free consultation involve?
A 45-minute working session with a senior consultant — not a salesperson. We'll discuss your current systems, operational pain points and objectives, and you'll leave with an honest view of your options and indicative effort, whether or not you engage us.
Who do you typically work with?
Freight forwarders, 3PLs, customs brokers and the supply chain arms of trading and manufacturing groups. Engagements range from single-office forwarders preparing for their first TMS to multi-country groups running regional rollouts across the GCC.
Do you cover both the UAE and Saudi Arabia?
Yes — we operate from offices in Dubai and Riyadh and deliver on the ground in both markets. Regional platforms and requirements such as Dubai Trade, FASAH and ZATCA e-invoicing are part of our standard delivery scope, not an add-on.
Do you work in both English and Arabic?
Yes. Our consulting team is bilingual, and we deliver training, SOPs and change communications in English and Arabic. For rollouts in Saudi Arabia in particular, Arabic-language enablement is a major driver of branch-level adoption.
Can you work alongside our internal IT team and the software vendor?
That is the normal setup. The vendor manages their scope, your IT team manages infrastructure, and we take ownership of the outcome — one integrated plan, one reporting line, and a single owner of delivery so timelines stop slipping between parties.
CargoWise & technology
What does a CargoWise implementation typically cost and how long does it take?
Timelines depend on modules, branch count and data readiness, but a single-country forwarding implementation typically runs 4–7 months, while multi-country programs run 9–15 months. We scope every engagement with a fixed methodology and transparent commercial model after a short diagnostic, so you see the full cost picture — including internal effort — before committing.
We're already live on CargoWise but adoption is poor. Can you help?
Yes — adoption recovery is one of our most common engagements. We run a structured diagnostic to find the configuration gaps and workflow mismatches forcing your team into spreadsheets, then fix the system, rebuild SOPs and coach users on the floor. Most clients see usage climb above 85% within one to two quarters without re-implementing.
Do you only work with CargoWise?
CargoWise is our deepest specialization, but our project management and business transformation practices are platform-agnostic. We regularly lead vendor selections, TMS and WMS programs, and digital transformation initiatives across the logistics technology landscape.
Can you help us choose between platforms before we commit?
Yes. Our vendor selection work is platform-agnostic: we map your operational requirements, run a structured evaluation across the logistics tech landscape and give you a recommendation based on what serves your operation — we hold no reseller arrangements that bias the outcome.
Do you handle data migration?
Yes. Every implementation starts with a data quality and migration-readiness assessment, followed by cleansing and structured migration. Before go-live we test with scenario runs on your real jobs, quotes and declarations — not sample data.
Delivery & methodology
What is your delivery methodology?
Every engagement runs on the same four-phase methodology: Diagnose, Design, Deliver, Embed. Each phase has defined entry criteria, deliverables and a decision gate, so you always know where the program stands and what happens next.
Can you take over a struggling implementation from another partner?
Yes. We begin with a two-to-three-week recovery assessment covering plan, configuration, data and stakeholder health, then present a re-baselined plan with honest trade-offs. Roughly a third of our engagements begin as recoveries of stalled programs.
What happens after go-live?
Go-live is the halfway point, not the finish line. The Embed phase keeps us on your floor through hypercare — coaching users, tuning configuration, tracking adoption analytics and measuring benefits against the original business case until the system holds up without us.
How do you measure success?
Against your numbers, not ours. During Design we agree named metrics with owners — adoption rates, processing times, invoicing speed, cost per shipment — baseline them, and report progress against that baseline throughout delivery and hypercare.
How do you manage change across multiple branches?
With structured change management, not memos from head office. We run branch-level workflow mapping during Diagnose, involve branch super-users in Design, and deliver bilingual training and SOPs on the floor — so every location goes live on one way of working.