Gumloop grew from two founders at its Series A to nine people by hiring very selectively and using work trials.
2
The company gives employees long periods without meetings, lets them own features, and automates internal work with Gumloop.
3
A small team can move quickly when its members work well together, enjoy the intensity, and document the culture they are expected to maintain.
Summary
Max Brodeur-Urbas explains how Gumloop grew to nine people while serving large companies such as Instacart, Webflow, and Shopify. The company began with an agent interface, then shifted toward explicit workflow automation after users showed that they were describing workflows they could build with Python, APIs, and language-model queries. Gumloop hires very selectively, often bringing candidates into several-day work trials. Some hires were already customers who understood the product and wanted to use it in businesses. Internally, the team keeps meetings to a minimum, gives people room to build, and automates operational tasks with its own product. Gumloop also uses retreats, fast building challenges, and a written handbook to balance intense work with a culture people want to join. Max is candid that luck may explain part of the outcome, and that these practices depend on having a genuinely small team.
Gumloop moved from an agent interface to explicit workflows
Max first built a simple interface for AutoGPT after seeing that people in its Discord wanted to use AI but could not clone a repository or set up software locally. He initially imagined Agent Hub as "GitHub for agents." The problem was that agents were not immediately useful for many requests. Users were describing complex workflows instead. If they could write some Python, make API calls, and run language-model queries, they could automate the request directly. Max and his co-founder changed the product so users could define a sequence of nodes in a workflow rather than ask an agent to do everything.
Gumloop raised its Series A with two people and later grew to nine. Max says the company can remain small only if each hire is exceptional, so the founders screen candidates very carefully. The co-founder of Instacart, who invested in Gumloop, advised Max not to lower the bar. His advice was that a candidate should be an obvious choice, or the company should pass. Gumloop has conducted hundreds of interviews and many work trials. Max says this approach can confuse investors who expect a heavily funded company to hire quickly, but every person has a large effect on a team of this size.
Max calls one hiring pattern "product-led hiring." Two Gumloop customers left their jobs to join the company. They already liked the product and knew how it could be used inside a business, so the founders did not need to persuade them about the company's purpose. A former Instacart customer joined to work on enterprise relationships and larger customers. Gumloop's head of education and community previously worked at Webflow and had created a Zapier course and automation workshops. Max says building a product that reaches the people a company might want to hire can make recruiting easier, although he also attributes part of this outcome to luck.
Work trials reveal fit better than interviews alone
Gumloop brings candidates into several-day work trials and treats them as part of the team. During one retreat, two people pictured on the left were candidates who joined the group to hack together. The founders use these periods to see whether they actually want to work with someone and whether the candidate fits the team. By the end, they feel much more confident about the decision. Max says the company has done too many work trials, but the process helps preserve a high bar as the team grows.
Max says Gumloop has almost no meetings on purpose. He hires capable people and tries to give them space to work. His own calendar is busy with customers, but he wants other employees' calendars to be mostly blank so they can have deep focus time. In a larger company, several people may need to coordinate before starting a project. With a small team, Gumloop can avoid much of that synchronization. Max also stopped managing every detail of every feature. He writes rough descriptions based on customer conversations, then lets the people he hired decide how to build them.
Gumloop uses its own product to automate operations
Gumloop automates as much internal work as possible, and builds product features when an internal task cannot yet be automated. Before a customer meeting, a workflow prepares a research report that includes public information and details about the customer's current product usage. When an interesting person signs up, Gumloop sends the team information about what they are doing and drafts an email for Max. The company also has a chatbot receiving about 50,000 messages per day. A workflow reads those conversations, identifies what users are confused about, and feeds that information into product decisions. Max says these automations replace tasks that might otherwise take several hours of someone's day.
The team often asks, "What if we built it today?" and sometimes sets a 45-minute timer to ship a feature with Cursor. Max warns that this pace can cause burnout if the question turns into an expectation to work late every night. Gumloop tries to offset the intensity with retreats in appealing locations, good food, and activities such as rock climbing and biking. He thinks employees need exciting experiences to look forward to. A team of ten can fit comfortably in an Airbnb, which is one reason he sees this culture as easier to maintain while the company is still small.
Gumloop writes its internal principles in a company handbook and publishes them outwardly, even though Max says the version shown is already a month or two out of date. Writing down how the company talks about building gives the team standards it must live up to. The handbook also helps candidates understand what Gumloop is about before an initial call. Max says it is one of the things that persuades exceptional people to speak with the company or join it.
"If you're an engineer and we hired you to build exceptional product, we should let you do that, not make you talk about building exceptional product for 5 hours every day."07:15
Who should watch
You are founding or running a small software company and need hiring practices that work when every person changes the team substantially.
Your company has capable engineers but loses time to meetings, coordination, or manual internal tasks.
You are considering customer-led recruiting and want to see how product enthusiasm can turn into enterprise, education, or community hires.
