Block (Square) Investor update
Review the key takeaways and the transcript of this earnings call.
Transcript
Preview the first fifteen paragraphs, organized by speaker.
Hello, everybody. Welcome to the Builder Lab Studio. My name is Lucas, and I'm a product manager on Buzz and Builderlab, and I'll be your host today. I'm really excited about the event today to share with all of you what we've been working on. Thank you all for coming. Thank you all for taking the time to be here with us this afternoon. I know some of you traveled to be here for the event, so hopefully we make it worth your time. Thank you all to everybody that helped organize this event. It's a really, really great venue. Over the last year, we've rebuilt Block as an intelligence. To do that, on our own terms, we've built our own tools.
Today, we're sharing those tools with all of you, and this event is an opportunity for you to see how we use them, how they work, and maybe get a chance to see for yourself how you might want to use them too. We have a great set of speakers to kick off the event today, and followed by, we'll have about an hour and a half for everyone to walk around the venue, get to know all the different stations that we've set up, and we'll come back here for Q&A with the speakers, and finally, we'll have a happy hour out by the terrace. In terms of the speakers today, we have a really great lineup. Jack is going to kick us off, followed by John and Alex from the design team.
Brad will wrap it up by telling us how it all comes together as part of Builderlab. Building our own tools while rebuilding the company takes a special leader who really understands what it means to operate as an intelligence. It's my pleasure to welcome our Block head, Jack Dorsey.
Just to set the tone, I am not one of the great speakers. But I will provide some context, and I want to start with some gratitude for you all. It means a lot that you're spending time with us here in San Francisco. This is where we started it all. We're really excited to bring everyone together, and we know that there's so many things you could be giving your attention to, and so much that demands of your time, so it's really important and special to us that you're spending a little bit of it with us. We thrive on critical feedback. Everything that we see and that we show you, I should say, and we present, please be critical, please be frank, please be upfront, and we'll make it better.
The goal here is to make something that works for everyone and that we can truly build together. I wanted to provide a little bit of context, and my slides are going to be very minimal, but I have a lot to say, but I don't want to overshare, so I am going to read my notes a little bit as well, which I never really do, but I want to get this right. I wanted to start with a very simple idea, which is a company itself is a technology. We don't often think about companies as technologies, but if you really dig into it and you meditate a little bit on it makes a lot more sense. We think of them as groups of people. We think of them as products, brands, organizations.
A company is actually one of the most important technologies we've ever invented, that I am aware of. It's a way of organizing people, information, decisions, and resources towards a common purpose. It enabled us to accomplish things together that none of us could accomplish alone. I think most of us who've been in companies have definitely felt that. Over time, we've developed a fairly standard architecture for making companies work. We organize people into functions, we define roles, we create hierarchies, we establish processes, reporting structures, management systems, all the things that we end up despising about companies, and we really haven't questioned them. We build all this software to help manage all of it, but none of this is a requirement. It's all made up, it was all designed, and it's a design that emerged from a fundamental constraint a long time ago.
For most of human history, intelligence existed only in people. If you wanted your company to know more, you needed people who knew more. If you wanted your company to do more, you needed people who had more capabilities. As the number of people increased, so did the complexity of coordinating them. We invented structures to solve that problem. Departments, management, meetings, approvals, hierarchy, so on and so forth. They're inventions that have allowed us and enabled us to build really amazing things, but they're still inventions for the moment of time that they were in. The important thing about technology is realizing that when the underlying constraints change, we can completely rethink the design of what we're working with. I believe that's exactly where we are today. We've thought a lot about this principle of companies move fast or slow based on information flow.
If you think about what actually determines how fast a company moves, it's not simply how talented its people are or how hard their work. It's how quickly information can move through the company, become understood, and turned into action. Imagine someone noticing a problem with a customer. They have all the information that matters, but what happens next? They have to write it down, they send a message, they create a ticket, they schedule a meeting. Someone else needs to understand the problem, then someone needs to decide what to do about it, then someone needs to act, and at every single step, information moves from one person to another. It's super lossy. Context gets lost, questions get repeated, decisions wait. I am sure you all have experienced that and maybe put some frameworks in place to minimize that.
Sometimes the same information is explained five or six times before anything actually happens. It is true even when everyone involved is exceptional, even if they are highly capable. The problem is not necessarily the people, it is the very architecture that we are working in. A small group of people with shared context can move remarkably fast. You have all felt that, especially if you are in startups where there are no doors, everything is shared, everything is on the same surface. Everyone understands what they are trying to do, they know what is happening, they make decisions, and they act. As a company grows, that becomes much harder. We create more structure to manage the complexity, and eventually, much of the company's energy goes towards coordinating itself, and that just feels super wasteful and inefficient.
We spent decades building software to make that coordination more efficient despite that, messaging, documents, dashboards, project management, collaboration tools. But we have mostly been improving how information flows through an existing structure through tiny little iterations. What if we could rethink the structure itself? We had this realization that all this work and thought has gone into, how do you integrate intelligence into a company? I think it might be the wrong question, and it is what we have been exploring at Block for quite some time, especially this whole past year. We are living through a fundamental change in the availability of intelligence. For the first time, intelligence is not limited to people. Machines can reason, write software, analyze information, use tools, and increasingly carry out complex work. These capabilities are improving quickly. We are all feeling that every single day.
Every company is asking how to integrate machine intelligence, but I think it might be the wrong question. We are asking how to fit this new technology into companies we have already built. How do we add AI to our products? How do we add AI to our workflows? How do we give every employee access to AI? They are useful questions, but they are not the most important question. What kind of company would we build if we were starting from scratch today? Just ground zero, from zero, what would we build? Knowing that intelligence is becoming abundant, knowing that machines can participate directly in the work, knowing that information does not always need to travel through a human hierarchy before something can happen.
We build something fundamentally different, something that is not simply a collection of people operating a collection of software tools, but a company that can understand itself, that can act through its capabilities, anticipate what is needed, and continuously improve. A company that operates as an intelligence, and the best way to integrate this machine intelligence that we are all participating in and all have access to now is to try to become it itself. But there is a really important distinction here, which is if you just add a thousand AI agents to the problem, that does not equal an intelligent company. Imagine a company with a thousand employees, and every one of them has an incredible AI assistant or thousands of them. The engineers are writing software faster, the designers are exploring more ideas, people in finance are analyzing more information.
Everyone's producing more work, and that could be great, that could be not so great. What happens when that work needs to move to another part of the company or actually be actioned upon? Someone still has to reconstruct the context, someone has to coordinate the people involved, someone still has to understand the decision, figure out who can make it, and ensure that something actually happens. We've accelerated the individual work, but the company itself may still be operating exactly the same way as it had in the past. In fact, we may have made the coordination problem even worse, because now everyone can generate more work than ever before, and I know we have felt this significantly over this past year. All that work still needs to move through the organization, and this is why I think we need to distinguish between two fundamentally different things.
One is a company that uses intelligence, the other is a company that is an intelligence. One is a collection of increasingly capable individuals and tools, and the other is a shared system. One where understanding persists beyond individual conversations, where people and agents work from common context, where capabilities can be coordinated across the company, and where intelligence recognizes what needs to happen and helps make it happen without constantly starting over, and importantly, without losing human accountability. That's a fundamentally different architecture than we're used to, so what would we actually need to build? We've been thinking about this in terms of four essential layers. The first is a world model. This is what does the company know about itself? What does it know about its customers? What does it know about its own employees? Today, a company's understanding of itself is fairly fragmented.
Some of it lives in databases and documents and conversations and the heads of its people. Much of it's disconnected. People can't easily bring it together. A world model brings these things together into a shared, evolving understanding that's constantly updated. The company, its customers, its products, its resources, its environment, and what it's trying to accomplish. It's not just a collection of information, but it's an understanding of how things relate to one another and how they're changing. The second is capabilities. This is what can a company do? What are the tools it has access to? Intelligence that understands a problem but can't do anything about it is only so useful. It needs the ability to act, to write software, to work with customers, to analyze transactions, operate systems, and execute tasks.
FULL TRANSCRIPT
Continue the full translated transcript in StockNow.
Access every statement, the English original, and speaker-by-speaker history with StockNow Pro.
View the full transcript with ProCall participants
5 people spoke on this call — only 1 are shown here.
PARTICIPANT LIST
View participant details in StockNow.
Log in to see executives and analysts, their roles, and complete speaking history.
Log in to view all participantsKeep exploring
