How Wine and Beer Supply built a $20M software pipeline with zero engineers

The foundation

Before anyone builds anything, we lay the ground under it. We stand up a dedicated Google Cloud VPC, Wine and Beer’s own corporate network. We connect their existing data sources and transform them into a knowledge fabric that AI systems can query directly. Then we put every team member on a Claude Team plan and walk them through the platform.

Building without engineers

With the foundation in place, non-technical staff build applications themselves, in plain language, wired directly into Wine and Beer’s live data through the connectors we set up. No developers required to go from idea to working prototype.

From prototype to production

A prototype built inside Claude isn’t running on Wine and Beer’s infrastructure yet. To move it there, Wine and Beer spends one credit. A Knight exports the application and puts it through a standard checklist before it goes live: a security scan, authentication, a live database connection, and our support bot wired in for ongoing help. What comes out the other side is production software.

Pricing that scales with usage, not headcount

The commercial model is as simple as the technical one. Wine and Beer buys a tranche of credits upfront. Every deployment costs exactly one credit, no matter how complex the application. The price of shipping is fixed and known before anyone builds anything.

Knights, embedded

Knights aren’t a help desk. They sit inside Wine and Beer’s delivery process the way an internal platform team would: reviewing every release before it reaches production, and remaining the standing point of contact once it’s live.

What the lifecycle gives back: 150+ hours a month

The applications now running in Wine and Beer’s VPC give the business over 150 hours back every month and unlocks new avenues for revenue. Work that used to be done by hand in spreadsheets, chased over email, or re-entered between systems, now handled by automation.

Those hours come from applications the staff (who know the business better than anyone) built themselves, which is what makes them valuable. The person who felt the friction wrote the tool that removed it, so the tool matches the job. Nobody wrote a requirements document, waited on a roadmap, or trained a contractor on how the business actually runs.

And the loop keeps running. Every month the team finds another manual routine, builds it in plain language, spends a credit to ship it, and the hours compound.