Geophrase
Delivery management for businesses with their own fleet
Small business owners running their own delivery fleet have no reliable way to verify what their riders are actually doing. Rider says customer was unavailable. Address was wrong. Order came back. No proof either way.
I built Geophrase to fix this.
Here is how it works:
Customers share their exact GPS location via a map pin. Delivery boy gets routed directly there via the free agent app on Android and iOS. At handover, the customer confirms with an OTP. If delivery fails, the rider's GPS is logged at that exact moment so the store owner can see exactly where they were.
Store managers can also require Aadhaar KYC verification before a rider joins their fleet. For multiple deliveries in one trip, the app calculates the fastest route using live traffic.
Also works with third party couriers without any integration on their end. We inject a map link into standard address fields on the shipping label.
Pricing is pay per use. No monthly subscription. Rs 2 per address capture, Rs 10 per full delivery order. First Rs 500 free, no card required.
Would love feedback from anyone who has dealt with this problem.
10 Comments
I like that you're solving disputes, not just routing. Once there's objective location and delivery verification, a lot of the "customer vs rider" conversations disappear. That creates value for both the business and the delivery team.
Thanks. Yeah, that was the idea.
Glad it resonated. I actually think there's a bigger strategic implication behind that idea that I'd rather not oversimplify in a thread. What's the best email to reach you on?
Are you looking for selling something to me?
Eventually, if we both conclude I can genuinely help—yes.
But I'm not asking for your email just to pitch you.
Your reply made me think there's a strategic business decision underneath the product that I'd like to explain first. If, after that, it turns out I can genuinely help you evaluate it, I'll be completely upfront about that.
Please convince me that you can genuinely help before going beyond this thread. I am sorry, but it sounds all talk to me. So, give me something to trust your skill.
That's a fair challenge.
Here's the observation that made me stop.
Most teams assume the hard problem is deciding which accessibility issue to fix first.
I don't think that's the harder problem.
The harder problem is deciding what the product is actually optimizing for every time it recommends fixing Issue A before Issue B.
Because the moment AccessLumens says "Fix this first," it's no longer just reporting findings.
It's expressing a judgment.
Is that judgment minimizing legal risk?
Reducing user frustration?
Maximizing accessibility impact?
Minimizing engineering effort?
Those are very different decision models.
Every recommendation the product makes quietly teaches customers which one they should trust.
That's why I found your reply interesting.
To me, the product isn't simply prioritizing issues anymore.
It's beginning to define how accessibility decisions should be made.
That's the implication I thought was worth discussing.
The first rule to pitch is: understand the business you are going to pitch to and then personalize your pitch according to who you are talking to. What you did is: copy pasted something that you most likely sent to 50 other people. That's not how you get customer and moreover help people.
That's a fair conclusion based on what I shared.
I'd rather be judged on the quality of work I deliver than on my ability to win a thread, so I'll leave it there.
Wish you the best with Geophrase.
What is AccessLumens?