A new company. Roughly fifteen years of the same problem.
We would rather be straight with you than pad a page with logos we do not have. Here is who we are, what we know, and how we intend to earn the work.
Experience sits in the team, not in a client list.
Fyndroot is early. What is not early is the experience behind it: close to fifteen years spent building, integrating and supporting the systems that run at the physical edge of a business — route to market for FMCG, food and beverage, dairy and distribution, and the gates those goods and people move through.
That time was spent in the unglamorous parts — loading bays, settlement disputes, ERP interfaces that fail overnight, reps in basement markets with no signal, finance teams reconciling receipts that do not tie out. It is where the design decisions in this platform actually come from.
Depth over breadth
We build two products, both for the physical edge of the business — the route and the gate — for the way that work actually runs, not the way a generic platform assumes it does.
Senior attention
You work with the people who designed and wrote the system. There is no layer between you and the engineering.
Prove it on a pilot
A controlled scope runs live before anything scales — a set of routes, or a single gate. If it does not hold up there, it does not deserve your rollout.
Early-partner terms
Being early with us should be worth something. Pricing, roadmap influence and support reflect that.
Things you only build after you have been burnt.
A short list of the details that tend to be missing from platforms designed at a distance from the work. Three from each product.
Sequence pools for offline documents
Numbers are pre-allocated to the device, so an invoice raised with no signal is a real, sequential, auditable document.
An independent gate check
Security confirms the physical load against the system load — before the van leaves and again when it returns.
Authorisation codes for exceptions
Replacements and exceptional check-ins need a supervisor-issued code. Controlled generosity, fully audited.
A re-runnable integration
A staging layer with per-entity process status, so a failed night's sync is diagnosed and replayed, not reconstructed by hand — and it is optional, because the suite runs standalone.
Isolation the database enforces
Row-level security bound per request, so a query that forgets to filter still cannot return another organisation's records. The guarantee does not depend on every developer remembering it.
Blockers instead of errors
"Gate-out blocked: seal number missing" is an answer the guard can act on, listed against the movement — not a failure message that sends them to find a supervisor.
Configuration that keeps its history
Editing a form publishes a new version rather than overwriting the current one, so a movement captured last year still renders with the fields it was actually captured under.
Your path to go-live.
Six steps, in this order, every time, for either product. Step two is optional — if you are running standalone, masters are loaded straight into the platform instead.
Discover
We map how your operation actually runs — roles, channels and trade terms for Route to Market; sites, gates, movement types and approval chains for GateFlow — against the platform, and agree the configuration blueprint.
Connect or load
Master data goes in — customers, products, prices and routes, or sites, gates, departments, hosts, contractors and vehicles — by bulk Excel or CSV import if you are running standalone, or through integration mappings built and rehearsed on staging if you are not.
Configure
Roles and permissions, journey plans and promotions, or forms, checklists and workflows — plus approval rules and print formats. Configuration, not code.
Pilot
A controlled scope runs live for an agreed window — a set of routes, or one gate. Field feedback and data quality are reviewed daily.
Roll out
Wave-based deployment across the remaining routes, sites or gates, with train-the-trainer enablement and role-specific quick guides.
Tune
Hypercare through the first cycles, then quarterly reviews of the configuration — scorecards and promotions, or checklists and approval chains — as your operation evolves.
Businesses where the work happens outside the office.
FMCG
High SKU counts, dense routes, promotion-heavy trade.
Food & Beverage
Expiry discipline, returns, and a shelf that must stay full.
Dairy & Water
Daily rounds, returnable containers, deposits and bottle ledgers.
Distribution & Wholesale
Multi-principal portfolios, credit control, and cash on the road.
Manufacturing
Inbound material and outbound dispatch, weighbridges, seals and contractor crews at the gate.
Warehousing & Logistics
Vehicle turnaround, dock discipline, and gate passes for material that leaves the premises.
Campuses & Facilities
Visitors, contractors, couriers and assets across corporate, residential and institutional sites.
Multi-site groups
An office and a plant on one system, with the difference between them held in configuration rather than in two products.
Any market, any language
Multi-lingual on web and mobile, multi-currency and multi-organisation — so the same platform fits a single-city distributor and a multi-country group alike.
Bring us your hardest route — or your busiest gate.
Forty-five minutes, a live environment, and the people who built it. Judge the work, not the pitch.