Willem Ave
๐ค SpeakerAppearances Over Time
Podcast Appearances
And if we can help with that and we can have customers walking away like, oh, that was fast, that was easy, that was delightful, and all the software and tools around that, as well as staff members, that's fast, it's easy to use, right?
Kind of helping customers, making sure technology doesn't get in the way.
And I think...
At the most broad strokes, we kind of hope that most of our hardware and technology kind of fades into the background.
We want our seller's brand to stand front and center.
There's a lot of design decisions that we've made to make sure that that stays true for a seller.
No, I haven't.
I think it'd be funny to do, but no, we haven't.
The genesis for the public roadmap, and it's pretty unique for larger businesses in the space, is that
We wanted to build out in the open, and we wanted to drive accountability for what we say we're going to do, we're going to go do, and we're going to do it with speed, velocity, and quality.
As far as the granularity and the details of what we show in the roadmap, it's really a judgment call.
My general preference is to show more.
and make it kind of more raw and utilitarian rather than maybe more polished.
So I think that's why you kind of see everything, tiny little features, but also really big things will show up there.
Specifically for combos and kind of some of the capabilities, it's important for when you run a business, the software has to work for how you want to run your business.
And that's how you merchandise your sales, how you present those goods or food or services that you're creating and present them to customers.
So that's why it's important, and sellers tell us this, but it's important to be able to help sellers model their business the right way.
I mean, I think what you need for any software, and I generally agree, a lot of software is like forms and lists of things, which is interesting as a reflection.
But you need the core foundational primitives and constructs, right?
Like, for example, in the hierarchy that those things, kind of how they're designed and engineered in the backend, are important to get right and are important to be flexible.