How Vordali Inc Combines Analytics and User Experience to Reduce Unpaid Invoices

I was already thinking about making an app to help stop businesses from losing money to unpaid invoices. And then I saw a Facebook post from a local owner of Little Caesars talking about how frustrating it was. They have people call in and order food but never pay. I eventually reached out to the owner to gather more data on the problem. Come to find out that one location loses at minimum $800 a month in unpaid orders. This is when I knew I could make something to help stop them from bleeding revenue by making a text-to-pay service with analytics and a dashboard that shows their ROI with our product, among many other data points. Too many businesses are losing revenue due to non-payments. Vordali Commit is the solution. Customers don't want to give personal information over the phone to a stranger, so we fixed that.

Growth tactics are getting the idea and name out there and getting positive feedback about what it can do. Flopped, Facebook posts are getting no traction. Vordali is in its early prelaunch stages, so we have not done much in this regard. We will be targeting word of mouth and in-person reach-outs to discuss directly with business owners. This is part of our pilot program ground work. Once we get the pilot off the ground, we will be focused on ad campaigns, and that will extend into online ads and ads within the city to start. Once we have established a user base, our plans for national ads will be viewed. We just know that once a business owner sees the work Vordali can do for them, that word of mouth will be more powerful than anything else. Because if Vordali can save a business $800 a month, they will tell their other business friends.

I am in a startup phase, looking for pilot businesses to sign up for my product. I am about to have an app available to make for easier use. And I am anticipating user needs by adding in features that I know businesses would already want to see. Our potential customers complain about the community's lack of follow-through with orders. We plan to design our products around helping limit this issue. We will have analytics that track customers' payment history and, eventually, the business can be given insight about potential problem customers. Our dashboard will be like another employee, who remembers all the customers and their tendencies. We also know businesses like speed. So our app is fast and easy to learn and use. You can send a payment request in under 30 seconds and track the information live in the dashboard. Once customers pay, you see it live in the dashboard and then you can start preparing the orders.

Having a SaaS, most people just build a quick product and spit it out and pay no mind to it. They are thinking about revenue and how fast they can turn it. I am building solutions, an interactive experience, the product is alive, it has analytics that help businesses grow and avoid loss. It shows ROI in real time with our product, and how much they are saving by using it. It plays out like a mission, giving them tasks to complete for signup and progression through the app in their business. It promotes growth, and rewards them for it. We don't spit them out into an app and say good luck. We see a lot of apps that are static, with no direction. We have introduced an interactive design that will work as a new employee to help manage information for the business. Easy to navigate and easy to learn and solves their problems.

After we are through with our pilot program, the goal is to get feedback from users and to work on those features. We have plans for other products that will tie into Commit, and they will be worked on as well. We have products that will help tie into verification needs, calendar needs, meetings needs, and all will work intelligently with each other. Our favorite part is Labs, where businesses can come to us with new problems. Here, we can research and build a product to fix the problem.

We are in pilot stage. I'm proud of the product.

I started from scratch. I have always wanted to do it, I just sat down one day and said it's time to make something. I have a systems-building mindset, and I was reading to build a system that actually helped. I currently also work for the government and run a small retail business, so this is something I haven't tackled before. It's a new area, but one I have wanted to get into for a long time. I just finally decided it was time to do something new. I found problems that needed solutions and started designing what will work.

I am a perfectionist, and it gets in the way of forward working sometimes. I get stuck on a cosmetic and overthink it for too long. I spend too much time perfecting things in the design. I have made mistakes in the coding process along the way that have put me behind and have taken days to resolve. I have gotten in my head about designing and end up costing myself more working time as well. The whole process is a learning one. I am not done learning, and I am not done making mistakes. Every day is a new checkpoint and a new learning experience.