A working system. A documented build.

AI-Assisted Development
in Practice

Rebuilding AlcoholBeverageTraining.com
with Claude AI and WebItems® Software

DSBWorldWide, Inc.  ·  September 2026

Open full view
First working version20 days

From first code to a working site on the client’s own server.

Business history preserved31,793

Student and certification records carried into the new system.

01

Executive Summary

Alcohol Beverage Training needed its website to run the training business: book classes, collect payment, examine students, issue certificates, and help employers manage staff training.

DSBWorldWide rebuilt those functions on WebItems® Software, our own website management system. Claude AI produced the design directions, pages, customer-facing words, and most of the supporting code. DSB directed the business rules and reviewed the work. The first working version reached the client’s server in twenty days; further improvements followed in separate phases.

02

About Alcohol Beverage Training

Alcohol Beverage Training (ABT) certifies people who sell and serve alcohol in Colorado. Its founder, a former Director of the Colorado Liquor Enforcement Division, helped write the state’s liquor rules. ABT teaches live classes in person and over video, including Spanish-language classes. Certificates last two years, making class attendance, accurate records, and renewal tracking central to the business.

03

Limitations of the Previous Website

The old GoDaddy site relied on an outside appointment service with an 80-appointment ceiling. The owner manually archived past classes to keep the calendar working. In some browsers, the class list did not appear.

“If you do not see any classes listed, try a different browser”Instruction on the old booking page, recorded in the June 2026 site review.

That warning appeared where a visitor was trying to become a customer. Exams ran through another outside service, certificates were prepared by hand, and employers had no account for buying or tracking staff training.

The business change

From separate services to connected operations

CapabilityPrevious websiteRebuilt system
Booking80-appointment ceilingBuilt-in scheduling
ExamsOutside quiz serviceExams on ABT’s siteResults connected to student records.
CertificatesPrepared by handIssued by the systemAvailable from the student’s account.
VerificationNo public lookupPublic certificate checksAnyone can confirm a certificate record.
EmployersNo employer accountsStaff and expiry tracking
Group purchasesNo bulk purchase flowTraining for whole teamsSeat coverage and consolidated billing.
SpanishClasses offered; booking screens in EnglishSpanish course listings and exam material
InstructorsWork spread across separate servicesClass rosters and student messages

Two outside systems replaced: booking and exams. Card payments continue to be processed by Stripe.

Figure 1. The differences are operational: fewer separate systems, connected records, and new tools for staff and employers.
04

Project Goals

The brief covered the full journey from choosing a class to verifying a certificate, while giving ABT control of its content and preserving historical records.

Reliable booking

Customers find a class and reserve a seat.

Verifiable certificates

Attendance, exam results, and certification stay connected.

Employer self-service

Buy training, track staff, and manage renewals.

History preserved

Former students keep publicly verifiable certificate records.

Staff in control

Manage content, schedules, and settings through the site.

Room to extend

New capabilities fit within the existing WebItems system.

05

Why Claude AI Was Selected

DSB used Claude across design, writing, and software development. It could work with WebItems’ existing patterns and the project’s written requirements, making it useful throughout the build.

The team supplied the standards it needed: the approved visual design, rules for customer language, examples from existing software, and the client’s decisions about training and billing. That gave Claude a defined job and DSB a clear basis for reviewing its output.

06

AI-Assisted Front-End Development Process

Claude produced three complete home-page directions as working pages. The selected direction established the colours, type, and spacing used across the site. From there, it produced the pages customers see, their interactive behaviour, and the words on them.

Design into delivery

One approved design, carried through the site

Explore three directionsWorking home-page designs for review.
Set the visual rulesOne palette, type scale, and page system.
Build the experienceConsistent pages on desktop and phone.
Figure 2. The design process, illustrated. Human approval set the direction for subsequent pages.
alcoholbeveragetraining.com/classes Click to enlarge ↗
1   Find a classSearch and filter the schedule.
2   Reserve a placeRegister from the class listing.
3   See the detailsDate, format, instructor, and seats.
Figure 3. The rebuilt public booking page, with annotations showing the customer’s main actions.

Claude also wrote most of the supporting code, automated tests, and tools for putting updates on the server. DSB and the client decided how pricing, employer access, billing, and certificate issuance should work.

07

Human Direction, Review, and Quality Control

The project’s written working contract covered structure, design, customer language, testing, and releases. Completion required evidence from the working screens and saved records, including repeated actions where duplicate results would matter.

The review process

Build, check, demonstrate, release

Work returns for revision when a check or review finds a problem.

How AI work moves from requirements to a checked releaseFive connected stages: agree the brief, Claude drafts, automatic checks, human review, and publish with a live check. Dashed return paths send failed checks and requested corrections back to the draft. 01Agree thebriefBusiness rulesand acceptance02ClaudedraftsPages, codeand tests03AutomaticchecksRun repeatabletests04HumanreviewUse the screens;check the data05Publish& check liveRelease, thenverify the siteFailed check → reviseCorrections → revise
How AI work moves from requirements to a checked releaseFive stages run from top to bottom. Dashed return paths from automatic checks and human review lead back to Claude drafts for revisions. Agree the briefBusiness rules andacceptance01Claude draftsPages, code and tests02Automatic checksRun repeatable tests03Human reviewUse the screens;check the data04Publish & check liveRelease, then verifythe working site05Return to the draftafter failed checks or corrections.
Figure 4. The working process pairs automated checks with human review of the actual customer and staff journeys.
71

Automated tests that use a real browser.
They exercise customer journeys to help catch changes that stop existing tasks from working.

Updates were recorded and replaced files backed up. Verification included the working site after an update, so a successful local check was not treated as the end of the job.

08

Integration with WebItems® Software

WebItems is DSB’s website management software. It supplies the shared services behind the site, including page editing, staff access, files, and email. ABT’s new business tools were built within that existing structure.

How the system fits together

ABT’s business tools. WebItems underneath.

A new ABT experience on an existing WebItems foundationThree connected layers. At the top are ABT website screens for booking classes, taking exams, and managing a team. The middle contains ABT business workflows for bookings and payments, exams and certificates, accounts and reporting. The foundation is the existing WebItems platform for pages, permissions, files, email, and data. ABT WEBSITEWhat students, employers and staff useBook a classTake an examManage a teamABT BUSINESS WORKFLOWSBookings & paymentsExams & certificatesAccounts & reportingWebItems®THE EXISTING FOUNDATIONEditable pagesStaff permissionsFiles & emailData & site services
A new ABT experience on an existing WebItems foundationThree connected layers, arranged vertically. ABT website screens connect to the business workflows. Those workflows sit on the existing WebItems foundation for editable pages, staff permissions, files, email, data, and site services. ABT WEBSITEBook a classTake an examManage a teamABT BUSINESS WORKFLOWSBookings & paymentsExams & certificatesAccounts & reportingWebItems®THE EXISTING FOUNDATIONEditable pagesPermissionsFiles & emailData & services
Figure 5. The platform remained responsible for the shared services. The new work extended the website above that foundation.

Page arrangement, installation and updating, staff logins and permissions, the file library, automatic emails, data storage, error reporting, search listings, scheduled tasks, and site settings all stayed under WebItems’ control.

09

WebItems® Module Enhancements

Fifteen functional areas, called modules in WebItems, make up the site. Two were built new. Three existing areas received major additions, and ten were adapted to ABT’s design and content.

Reuse and custom development

13 of 15 areas started with existing tools

Custom work concentrated on training, certification, reporting, and the business rules around them.

How the fifteen areas were deliveredTwo areas built new, three existing areas substantially extended, ten existing areas adapted. Counts of areas, not shares of cost or effort. 15 site areas 2 Built new Classes, exams, certificates; business reporting. 3 Substantially extended Payments; accounts and employers; support and messaging. 10 Adapted from existing tools Content, menus, forms, and other supporting tools.
How the fifteen areas were deliveredTwo areas built new, three existing areas substantially extended, ten existing areas adapted. Counts of areas, not shares of cost or effort. 15 site areas 2 Built new Classes, exams, certificates; business reporting. 3 Substantially extended Payments; accounts and employers; support and messaging. 10 Adapted from existing tools Content, menus, forms, and other supporting tools.
Figure 6. Counts describe areas of the site, not percentages of cost or effort. Thirteen is the three extended areas plus the ten adapted areas.
Training and certificationCourse listings, class booking, exams, certificates, public verification, and instructor class rosters.
Business reportingReports for training activity, payments, certificates, and instructor pay, with spreadsheet export.
Payments and invoicingCard payments, refunds, discount codes, payment by check, and consolidated employer billing.
Accounts and employersStudent accounts, organizations, locations, managers, and staff training oversight.
Support and messagingCustomer enquiries and communication between instructors and students.
10

WebItems® UAdmin Dashboard Upgrades

UAdmin, the staff administration area, changed from a welcome page into a working dashboard. Its calendar shows scheduled classes, seat counts, and instructors. Pinned alerts point staff to work needing attention.

Staff dashboard · development sample data Click to enlarge ↗
1   Schedule at a glanceSee classes across the month.
2   Class detailsInstructor and available seats.
3   Work requiring attentionPinned alerts with counts.
Figure 7. Administrative screenshot from a development system with sample data.

Other views bring together revenue, instructor pay owed, bookings, new customers, schedule coverage, and classes missing an instructor. Staff can reorder lists, page through long results, and adjust when automatic tasks run. Password protection was strengthened.

46

Improvements to WebItems itself.
Changes made during this project now benefit other sites DSB runs as well as ABT.

11

Challenges and Lessons Learned

AI output still needed correction. The recurring patterns were manageable when the team checked the business result and recorded what it learned.

  • A confident answer can misread a ruleCheck against the client’s requirement
  • An existing tool gets rebuiltFind and extend what is already there
  • Copy describes a feature instead of helpingWrite for the customer’s next action
  • Code looks finishedDemonstrate the complete task
  • The same local quirk gets missedRecord the lesson for later work
12

Project Results

A working version reached the client’s server twenty days after coding began. The complete system described in this paper includes later work requested as the client reviewed it.

20 daysFirst code to first working site
11 June 2026First code1 July 2026Running on the client’s server
Later work came in phases55 active dates across 97 elapsed days
Work came in separate phasesDaily code-change activity from June 11 to September 16, 2026. Fifty-five dates have recorded changes. Empty dates do not establish that no work occurred. Recorded work No change recorded June July Aug. Sept. 1 5 10 15 20 25 31
Work came in separate phasesDaily code-change activity from June 11 to September 16, 2026. Fifty-five dates have recorded changes. Empty dates do not establish that no work occurred. Recorded work No change recorded June July Aug. Sept. 1 5 10 15 20 25 31
Figure 8. Daily activity from the code history, 11 June–16 September 2026. A blank date means no recorded code change, not a measure of hours worked. The first delivery date comes from the deployment record.

The rebuild also preserved the history behind the business. Student accounts remained linked to historical certificate claims, and every migrated student retained a certificate that could be verified publicly.

Migration completed

Nearly 32,000 records carried forward

15,829Student accounts
15,964Historical certificate claims
31,793Records preserved
in the new system
318Exam questions
904Answer options
51Learning objectives
Figure 9. Historical migration totals, including English and Spanish exam material. Records are not a count of unique people or current customers.

What is known about time and cost

The signed proposal specified 155 design hours. A comparable estimate for the same scope without AI has not been established, so this paper makes no percentage-savings claim.

13

The DSBWorldWide AI-Enhanced Development Model

The approach carries forward as a repeatable working process:

  1. Start with the business. Agree what customers and staff must be able to do.
  2. Use the existing foundation. Build on proven tools and add the capabilities the business needs.
  3. Give AI written rules. Make the design, language, and software standards explicit.
  4. Verify the whole task. Check the screens, saved information, and working site.
  5. Keep people accountable. A human team owns the requirements, review, and delivery.
Conclusion and Call to Action

Build the system your
business needs next.

ABT gained a connected system for booking, training, certificates, and employer administration. Claude helped produce it; DSB supplied the platform, business direction, and review.

If your website has outgrown the tools behind it, bring us the steps your customers struggle with and the work your staff repeat by hand. We can help define the scope, delivery plan, and budget.

Talk with DSBWorldWide
DSBWorldWide, Inc.Web design & business systems
Built on WebItems® Softwaredsbworldwide.com