General

Lessons from Building Netlify with Matt Biilmann, CEO at Netlify

2 min read
This article was written over 18 months ago and may contain information that is out of date. Some content may still be relevant, but please refer to official documentation for the latest information.

Matt Biilmann, CEO and co-founder of Netlify, for an in-depth discussion about the company's incredible growth journey—from a bootstrapped two-person startup to a global platform serving over 5 million developers and powering sites for major companies like Unilever and Asana. Matt reflects on the key lessons he’s learned while scaling Netlify, including raising $212 million in venture capital and growing the team to 200 employees. He shares valuable insights on balancing day-to-day operations with long-term vision, navigating the challenges of hiring experienced leaders, and fostering a culture of clarity and focus. Matt also highlights the importance of reducing friction for web development teams and ensuring fast time-to-market for web projects.

Chapters

  • 00:00 - Introduction
  • 01:00 - The Origins of Netlify
  • 02:30 - Netlify’s Growth Journey
  • 04:00 - Impact of Netlify on the Web Ecosystem
  • 05:30 - Building the Right Team
  • 07:45 - From Developer to CEO: Evolving as a Leader
  • 10:00 - The Balance Between Vision and Operations
  • 12:00 - Delegating vs. Staying Hands-On
  • 15:30 - Hiring Experienced Leaders
  • 18:00 - Building Diverse Teams
  • 20:00 - Intuition in Leadership
  • 22:30 - Simplifying Goals and Objectives
  • 25:00 - The Shift in Tech Leadership
  • 28:00 - Changing Expectations for Engineers
  • 30:00 - Advice for Startup Founders
  • 32:00 - Where to Find Matt Online
  • 33:00 - Conclusion

Follow Matt Biilmann on Social Media Twitter: https://x.com/biilmann Linkedin: https://www.linkedin.com/in/mathias-biilmann-christensen-a5a3805/ Github: https://github.com/biilmann

Sponsored by This Dot: thisdot.co

Keep reading

View all posts →

Building a Bot to Fetch Discord Scheduled Events with 11ty and Netlify

If you haven’t heard of 11ty (Eleventy) yet, we are here to share why you should be excited about this new ish static site generator on the block! For clarification, a static site generator (SSG) is a tool that generates a static HTML website based on raw data and a set of templates. 11ty is an SSG with a small bundle size and no runtime, which means it only ships your code to the browser. It supports multiple templating engines providing flexibility to use templating languages like njk, .html, .md, and more. For this article, we will be using nunjucks (.njk) templating. It’s worth pointing out that 11ty is NOT a javascript framework. This article is a recap of the JS Drop training by Domitrius Clark where he showed us how to build a Discord Scheduled Event List with 11ty and Netlify. In this workshop, you will learn how to build a static generated site for a list of scheduled events fetched from a Discord server using 11ty and Netlify. A Notion document outlining the steps for this workshop. (Thanks Dom!) 👋 Before getting into the steps, make sure you have: A GitHub account and a repo created to house your workshop code A Discord account & a server for us to connect your bot to A Netlify account to deploy your application at the end Initial Project Scaffold and Install Dependencies npm init y to init a package.json with default values yarn add D @11ty/eleventy @netlify/functions tailwindcss node fetch@2 dotenv npm run all Open the new project in your favorite code editor Edit the script property of the package.json file: The above scripts are the build commands for 11ty production, CSS build for Tailwind, and also to run the dev server for testing our application. Now that we have our packages and scripts defined, let’s scaffold out the folders and files we’ll need for the site. First edit the .gitignore: Next, define the 11ty configs: Types of templating files (Nunjucks) Directories to use include build output, where get components, layouts, and includes. Defining plugins Edit the eleventy/config.js file with the following: Next, we edit the netlify config file netlify.toml to config Netlify deployment with the following: Build commands Path to Netlify functions Creating base layout and setting up Tailwind We created the includes folder with two sub folders, for our components (or macros), simply named components and layouts, which is where we’re going to be focused in this lesson. 11ty exposes the includes folders so that we have access to our layouts and components inside of our pages and inside of each other (for example using macros inside of other macros). Let’s go ahead and create the HTML scaffold for our pages. Inside of /src/ includes/layouts/ we’ll create the base.njk file. The layout will be used to wrap all of our pages. We can also create sub layouts and new layouts depending on the needs of the page. For this tutorial we will need only this base layout. For the base.njk we: We made the Tailwind styles visible to our page by adding a link tag for /styles.css We are using the title variable, because of 11ty’s data cascade, and we’re able to pull variables in from our pages frontmatter. In our files, we’ll need to define a title to ensure our layout doesn’t break. Notice the {{ content safe }}. The content variable is the page content itself. So, in our case, this will be our .njk page and components. the safe variable is a builtin filter to nunjucks, to make sure it will not be HTML escaped. Next, we will modify tailwind.config.js to make our Tailwind work as expected: And modify the styles.css file to import Tailwind utilities, base, and components: Then we edit the index.njk file with the default content and frontmatter: Now to test that everything works, start the dev server: Everything should work! Now navigate to http://localhost:8080 in your browser. Creating a Navbar component in Nunjucks Let's create a Navbar component for our layout with Nunjucks, in the src/ includes/components/ add a navbar.njk: Next, we modify the index.njk file to include the navbar in our pages and add: Now the final document should look like this: Initialize a Discord BOT from the Discord server Now that we have the template and base file set up, next we should connect the Discord bot to the page. Before we start to initialize a discord bot, we need to put some things in place, so head over to your discord. Go to the User Settings, navigate to the Advanced tab and enable the Developer Mode. Head over to the Discord Developer Portal and click on New Application to create an application. Fill in the necessary details and click on create. On the sidebar menu, navigate to Bot and click on add bot. We will need a few details for our app to connect with the Discord server. Let’s copy them to the .env file. Add environment variables DISCORD BOT TOKEN & DISCORD GUILD ID and assign the value for discord token from the Bot page by clicking reset token. For the DISCORD GUILD ID, head over to a Discord server that you manage, or create one for this tutorial, side click on the server and click on Copy ID. Now paste the ID to set the value for the DISCORD GUILD ID environment variable. Next, add the bot to your server https://discordapp.com/api/oauth2/authorize?scope=bot&client id=YOUR CLIENT ID Find the client ID from the 0Auth2 tab and click on copy. Now we are all set and connected to the server. Using global data files in 11ty to fetch scheduled events from Discord In 11ty, data is merged from multiple different sources before the template is rendered. The data is merged in what 11ty calls the Data Cascade. We will be fetching data from discord from a javascript function in the global data file. Inside of src/ data, create a new file named events.js. Previously, we created environment variables called DISCORD BOT TOKEN & DISCORD GUILD ID. Now, we can fetch our events endpoint, grab our events, and inject them into our templates. Our file will look like this: Creating the events page In the src directory, create an events.njk file: Currently we’ve just got a page rendering some static content. Let’s use Nunjucks loops to render a card for each of our events. The data we care about right now from the large event object coming back are: creator name scheduled start time description and if it’s not inside of Discord, where is it We also need to make sure we check the event for any meta data that could point us toward an external link for this event. Thankfully, this is another quick fix with Nunjucks if blocks. Our final card (should) end up looking something like below. Before we test the application, schedule a test event on Discord, restart the dev server, then click on events tab in the navbar: You should see your newly scheduled events. Pushing to GitHub and deploying to Netlify Pushing to Github Let’s initialize a repo so we can track our changes and deploy live to the web as we go. Start off with a quick command to initialize the repo: Then let’s get all of our current changes added and pushed to main, so we can create a repo. Using the GitHub CLI, create a repo and push it, This will create your repo, name it, and push up the commits all in one command. To confirm that the repo is up, run: Deploy to Netlify To create a new project on Netlify with the new repo as the base, run: Fill in the prompts. You should be asked the following: Choosing to create and configure a new site Choose your team Set your unique site name Now, you should have an admin URL and base URL link in the console. There will be a few more prompts: Authenticate Github through Netlify leave build command blank leave netlify functions folder blank Once all that is done, we’re going to want to run a few commands: git push netlify open If something was wrong with your initial linking of your code, try to run a new production deploy using: netlify deploy prod Netlify CLI will deploy the local project to the Netlify server and generate a random URL which you can visit to see the live app. Conclusion In this workshop, you learned to use 11ty to fetch and display your scheduled events from a discord server and deploy an app to Netlify. That was pretty easy! Did you run into any issues? There is more! Watch the full training on the ThisDot YouTube Channel Are you excited about 11ty? What are you building using it? Tell us what excites you!...

Hassan Sani9 mins
EleventyNetlify

This Dot AI Field Notes - Anatomy of a Coding Harness

A coding agent is not magic, it’s a loop. We call this a harness. The harness is a deterministic layer of code that wraps an LLM....

1 min
AI

AI Is Speeding Up Development. But Where Are the New Bottlenecks?

AI is accelerating development, but it’s also exposing everything else that’s broken. At the Leadership Exchange, leaders unpacked how AI is reshaping the SDLC and what organizations need to address beyond just coding to make adoption successful. Moderated by Rob Ocel, VP of Innovation at This Dot Labs, the panel featured Itai Gerchikov at Anthropic and Harald Kirschner, Principal Product Manager for GitHub Copilot & VS Code at Microsoft. Panelists explored the current state of AI adoption across the software development lifecycle and shared practical insights into how organizations can effectively integrate AI tools. Panelists discussed how companies are investing in AI tools, skills, and managed competency programs to support developers. While AI can dramatically accelerate coding, the panel emphasized that adoption affects every stage of the SDLC. Bottlenecks now appear in testing, DevOps, product delivery, and marketing as AI speeds up development. Organizations that address technical debt and process inefficiencies are better positioned to extract maximum value from AI tools. The conversation also focused on opportunities and risks. Security, governance, and workforce education were highlighted as critical factors for adoption. Panelists stressed that AI initiatives should be aligned with broader business goals rather than pursued in isolation. They noted that companies experimenting at the cutting edge need to consider organizational readiness just as carefully as technical capabilities. Panelists also explored how leading organizations are navigating the early stages of adoption. Those ahead of the curve are using structured experimentation, prioritizing process improvements, and continuously evaluating outcomes to refine their AI strategies. Learning from these early adopters allows other organizations to anticipate emerging trends and prepare for the next phase of AI adoption rather than simply replicating past approaches. Key Takeaways Investing in AI skills and tools should be done thoughtfully, with clear alignment to business objectives. Examining the full SDLC helps identify bottlenecks that AI may accelerate or expose. Organizations can gain a competitive advantage by learning from early adopters and planning for where AI adoption is heading. AI adoption is not just a technical initiative; it is a strategic transformation that requires attention to people, process, and technology. Organizations that balance innovation with operational discipline will be best positioned to capture the full potential of AI across the software lifecycle. Seeing similar challenges in your own SDLC? Let’s compare notes. Join us at an upcoming Leadership Exchange or reach out to continue the conversation. Tracy can be reached at tlee@thisdot.co....

Calypso Hernandez2 mins
AI AdoptionAILeadership ExchangeEngineering Leadership

Making AI Deliver: From Pilots to Measurable Business Impact

A lot of organizations have experimented with AI, but far fewer are seeing real business results. At the Leadership Exchange, this panel focused on what it actually takes to move beyond experimentation and turn AI into measurable ROI. Over the past few years, many organizations have experimented with AI, but the challenge today is translating experimentation into measurable business value. Moderated by Tracy Lee, CEO at This Dot Labs, panelists featured Dorren Schmitt, Vice President IT Strategy & Innovation at Allen Media Group, Greg Geodakyan, CTO at Client Command, and Elliott Fouts, CAIO & CTO at This Dot Labs. Panelists discussed how companies are moving from early AI experiments to initiatives that deliver real results. They began by examining how experimentation has evolved over the past year. While many organizations did not fully utilize AI experimentation budgets in 2025, 2026 is showing a shift toward more intentional investment. Structured budgets and clearly defined frameworks are enabling companies to explore AI strategically and identify initiatives with high potential impact. The conversation then turned to alignment and ROI. Panelists highlighted the importance of connecting AI projects to corporate strategy and leadership priorities. Ensuring that AI initiatives translate into operational efficiency, productivity gains, and measurable business impact is essential. Companies that successfully align AI efforts with organizational goals are better equipped to demonstrate tangible outcomes from their investments. Moving from pilots and proofs of concept to production was another major focus. Governance, prioritization, and workflow integration were cited as essential for scaling AI initiatives. One panelist shared that out of nine proofs of concept, eight successfully launched, resulting in improvements in quality and operational efficiency. Panelists also explored the future of AI within organizations, including the potential for agentic workflows and reduced human in the loop processes. New capabilities are emerging that extend beyond coding tasks, reshaping how teams collaborate and how work is structured across departments. Key Takeaways Structured experimentation and defined budgets allow organizations to explore AI strategically and safely. Alignment with business priorities is essential for translating AI capabilities into measurable outcomes. Governance and workflow integration are critical to moving AI initiatives from pilot stages to production deployment. Successfully leveraging AI requires a balance between experimentation, strategic alignment, and operational discipline. Organizations that approach AI as a structured, measurable initiative can capture meaningful results and unlock new opportunities for innovation. Curious how your organization can move from AI experimentation to real impact? Let’s talk. Reach out to continue the conversation or join us at an upcoming Leadership Exchange. Tracy can be reached at tlee@thisdot.co....

Calypso Hernandez2 mins
AI AdoptionAILeadership ExchangeEngineering Leadership