BRENDAN KING.
    All writing

    Vendasta

    Your Team Is Your User: Why Vendasta Uses Its Own Software

    Vendasta runs on the software and AI employees it sells. Our people are users of the product, so rough edges show up here first. Why that helps partners.

    Brendan King, CEO of Vendasta4 min read

    Vendasta uses its own software because our people are users of the product. When something is hard for them, we find out first. That makes the product better for our partners.

    I read a LinkedIn post from Kyle Norton of Lassie this week and agreed with it. His idea: your reps are software users, and your go-to-market stack is a product you take to market. I think that holds for any company that sells software.

    Where does "your team is your user" come from?

    Kyle's argument is simple. If your reps are users, then RevOps is the product team. A product team works in a way most internal teams do not.

    • It lives with its users and learns from them, especially the power users.
    • It ships a first version to a small group and iterates with them.
    • It watches the metrics and runs feedback sessions after launch.
    • It builds low-friction experiences that pull people through the work.

    He also asks a fair question. Would you make the users of your product switch between five screens to do one job? Of course not. Yet most companies do exactly that to their own staff.

    You can read Kyle's post on LinkedIn.

    Why does a software company need this more than most?

    Because we have a second job. Our staff are users, and they are also the first customers of what we build.

    I wrote about the business case in Run Your Company on What You Sell. This piece is about the people. A Vendasta rep, marketer or support agent has the same jobs as an agency or a local business. Capture leads. Respond fast. Book meetings. Run campaigns. Manage reputation. Support customers. We run those jobs on the platform and the AI employees we sell.

    So when the product gets in someone's way, the people who build it can hear it from a colleague. They do not have to wait for a survey or a support ticket.

    What does your own team tell you that customers do not?

    Customers leave quietly. Staff tell you what they think.

    Take the Recognition Test. I started it with our own platform. Building a complex automation or a custom report in Vendasta is out of reach for almost everyone. Only a handful of our most technical people can do it, and they say openly that they struggle. When one person in the company can use a tool, the tool is wrong.

    Or take The Floor and the Door. I looked at an AI employee screen in our own product, and the main button said Chat. Chat is how you operate an AI. An employee gets assigned a job. A teammate looking at that screen would have felt it right away.

    Both lessons started with us using our own product.

    What happens when an AI employee works for us first?

    You find out whether it finishes the job.

    Our support employee is the example I can point to. It is working on our own support tickets first, and then it goes into every partner's hands. I wrote that plan in The One Conversation.

    An internal result is a fast signal. If an AI employee cannot complete a job for a team that knows the product, it will not complete it for a busy owner either.

    What about the people who want to build their own tools?

    Kyle makes a point I agree with. The rep who scratches their own itch is valuable. Give managers and directors a governed base, with context and checks, and let them build on top.

    That is close to how I think about it at Vendasta. I wrote about it in Managing Builders. Our platform is one lane. Internal production is a second lane: the systems we run the business on, built on our own platform, with data coming through approved interfaces. Prototypes are a third lane, where anyone can try an idea. Work moves up a lane when it earns the move.

    Building on your own platform keeps builders close to the product's limits.

    Is your own team enough?

    No. Internal use is one signal, and it is never the only one. Insiders know too much, and our own needs can drown out our customers' needs. So I treat what our team learns as a quality and outcome signal. It gives us speed. It does not replace what partners tell us.

    What does our guiding principle say?

    It is one of the principles in Our Guiding Principles:

    Drink Our Own Champagne

    We are "customer one". We must use the products and services we sell to run our own business, from sales and marketing to fulfillment and support. This forces us to feel our customers' pain, drives product improvements, and ensures we fully believe in the solutions we offer. If it's not good enough for us, it's not good enough for our customers.

    What does this mean for our partners?

    They get a product that its maker depends on. When we say an AI employee can do a job, it is because our own people have handed that job over and checked the result.

    Your team is your user. Treat them like it.

    Continue the conversation

    Have a perspective to share?