Netlify People Team Builds Custom Software Without Engineers, Saves $10K Annually.

Non-technical teams building their own software is no longer a hypothetical. Netlify's People team spent the past year replacing vendor tools with custom applications they built themselves, none of them engineers.

The team, comprised of HR, talent acquisition, and operations staff, shipped an employee survey tool replacement, custom hiring dashboards, a gamified onboarding system, and a self-serve hiring enablement platform. The result: $10,000 in annual software costs eliminated and hours reclaimed weekly, according to a detailed account by Chelsey Madsen, the team's leader.

This represents a fundamental operational shift from reactive support to what Madsen describes as strategic partnership, and from passive tool users to active systems designers.

The term "vibe coding" describes their methodology: building functional software through AI-assisted development without formal programming training. The approach emphasizes low-stakes experimentation as the primary learning mechanism.

"Start low-stakes," Madsen advises. "Low pressure experiments are how you learn without fear." The team began with simple internal tools before progressing to more complex systems affecting multiple departments.

Critical to their success was early collaboration with security and engineering teams, not post-launch validation. This prevented significant rework and ensured solutions met organizational standards from the beginning.

All applications run on Netlify's deployment infrastructure, which the team was already familiar with from their internal operations work.

The custom hiring dashboards consolidated data from multiple sources into unified views for recruiting teams. The gamified onboarding experience replaced static documentation with interactive elements designed to improve new hire engagement and retention.

The self-serve hiring enablement tool allows hiring managers to access resources and complete tasks without intermediary support from the People team, directly reducing the team's reactive workload.

Madsen's account includes the frustrating parts. Not every experiment succeeded. Some tools required multiple iterations before becoming useful. Security reviews identified issues requiring substantial changes. The team learned to build with scale in mind even when starting small, avoiding technical debt that would complicate future expansion.

Netlify has positioned itself as infrastructure for AI-generated code deployments. The company recently outlined a code trust framework addressing security concerns around AI-assisted development, suggesting internal teams like People are testing approaches the platform will support at scale.

The People team's success aligns with growing adoption of visual development platforms and AI coding assistants across non-technical business functions. Tools like Cursor, Replit, and Bolt have reduced technical barriers to software creation, enabling precisely this kind of departmental autonomy.

For organizations considering similar initiatives, Madsen's guidance centers on three principles. First, begin with low-risk projects where failure has minimal consequences. Second, integrate security and engineering oversight from day one rather than treating it as a gate before launch. Third, design for future growth even when initial scope is limited.

The $10,000 annual savings, while significant for a department budget, represents only part of the value. The time reclaimed from manual processes and vendor management allows the team to focus on strategic initiatives rather than operational tasks.

The full account of Netlify's People team experiment, published on the company blog, provides implementation details and candid assessment of what worked and what required adjustment. It's one of the more transparent case studies available on non-technical teams building production software.