Software built by someone who runs the same kind of business you do.
Not a dev shop. An operator who builds tools for trade, then ships them and runs them. CargoDesk, our freight forwarding platform, is the proof.
The problems we build against.
Fragmented systems: disconnected tools and manual processes creating data silos across quoting, operations, and finance. Domain-blind developers: technically capable teams that don't understand Incoterms, consolidation, or why a shipment milestone matters. Slow digitization: competitors moving to cloud-native operations while legacy spreadsheets hold the line.
What we build.
Custom SaaS with multi-tenant architecture, subscription billing, and role-based access. Freight and logistics platforms: shipment tracking, documentation, carrier integration, client portals. Trading and procurement tools: quotation, order management, supplier workflows. AI where it earns its place: document processing, chat agents, predictive views. Workflow automation and integrations across the systems you already run.
Proof: CargoDesk.
Our white-label freight forwarding platform runs real logistics operations under their own brands. It's the standard every client build is held to, because we operate it ourselves. → /software
How engagements work.
A paid, fixed-price discovery sprint defines scope. Build proceeds in approved milestones. Delivery is handover or hosted, your choice, with the stack stated plainly: Next.js, Supabase, Vercel. Scoped per project; fixed price agreed before build.
FAQ
Do you take projects outside trade and logistics?
Selectively. Our edge is domain depth; if your project doesn't benefit from it, we'll say so and point you somewhere better.
Who owns the code?
You do, on handover engagements, completely. Hosted engagements state terms up front.
Can you integrate with our existing systems?
Integration is usually the point. Bring the mess; scoping starts there.
Zed Concept · Guangzhou · UAE · Founder-led since 2013