Prepared for Vaibhav Kaushik — Co-Founder & CEO
Nawgati
Fuel-tech is one of those categories where you're selling two products to two very different rooms — the operator who runs the station and the driver who just wants a shorter queue.
Your homepage forks to 'for fuel providers' and 'for you' the second someone lands, so one page carries a slow B2B procurement talk and a fast consumer install at once. The provider-side intent is the quieter, higher-value half — and it's instrumentable apart from the consumer flow today.
The signals you're sitting on
◆ SIGNAL 01
A visitor takes the 'for fuel providers' fork and reads the Aaveg or Fleet surface
Reads as
An operator self-selecting into the B2B path. Early provider evaluation.
Leaks today
Lumped into one site-wide funnel with consumer app installs; the fork choice isn't recorded as intent.
Wire this
Tag the provider fork as a separate funnel entry the moment it's chosen, and start a provider-only nurture distinct from the consumer install path.
◆ SIGNAL 02
Same provider returns to dig into congestion or compliance specifics across sessions
Reads as
A station or fleet operator working a real procurement question. High-intent, long-cycle.
Leaks today
Reads like ordinary repeat traffic; no provider-side return signal is wired to a human.
Wire this
Wire a return-visit alert scoped to the provider funnel and route it to a person who can open a procurement conversation while it's live.
◆ SIGNAL 03
A second station or a fleet manager from the same operator appears
Reads as
An internal champion bringing the network in. Multi-site expansion intent.
Leaks today
Treated as new signups; no account-level rollup, so expansion looks like noise.
Wire this
Flag a second station or fleet seat under one operator as an expansion trigger and route it to a network-rollout touch.
◆ If you wire one thing
Decide what a serious provider does before they ask for a demo, and wire those moments apart from the consumer flow so the slow, high-value half stops hiding inside install traffic.