What I’ve built
From one small connection to a whole company.
Short answer: In 2025 I connected tools I already used. In early 2026 I worked with developers to finish whole systems, and writing the documentation with AI was the most useful thing I did. Now I’m building toward fewer screens: I say what I need and the report appears.
Everything here was built for my own businesses, Rim Tours Mountain Bike Adventures and Village Roaster Coffee and Tea. Most of it was built by directing AI tools. The counts and dates come from the project histories, and they say nothing about quality.
Small connections between tools
Reservations kept in sync with a shared calendar, sales sent toward the books, and reservation and sales data pulled into spreadsheets, so it could be read and questioned in tools people already knew.
One workflowReservations and schedules, together
Reservations in Arctic and staff schedules in 7shifts, brought together with Google Sheets and Google Calendar in the middle. That project has had well over 300 changes since.
One workflowA first try at one source of truth
Bookings, trips, schedules and documents from several services, combined in one place.
One workflowA website and a shared inbox
The Rim Tours website with live trip availability, and one shared inbox for customer email, texts, WhatsApp and calls, with AI-drafted replies for a person to review.
A departmentA time clock and a staff portal
A phone-friendly time clock connected to the scheduling service, and a staff portal for a company of about 20: schedules, clock-in, trip reports, fleet and bike maintenance, and contracts that employees sign electronically.
A departmentA staff system and an ERP
Scheduling, time tracking, payroll preparation and HR for a company of about 30, and an ERP for a roastery and wholesale operation: accounts, orders, roasting, green coffee buying, labels, support tickets and email.
The whole companyOne time clock and payroll engine
A shared engine for time cards and payroll, run separately for each company, from one codebase.
The whole companyAsking for a report in plain words
The same systems can be asked questions through AI assistants. Increasingly I don’t open a screen. I say what I need.
Ask, don’t clickThe foundation was explaining it
In early 2026 I was working with developers to help me finish projects. I used AI to help me define and write the technical documentation for what I needed: the business process, the logic, and the workflow to recreate in code and on a screen. Learning to explain my way around the business that clearly was the foundational piece. It is also what I teach.
Screens are friction
A lot of the early work went into the user interface. Now I’m heading toward systems that need none. I’d rather say “show me the latest sales report,” or “give me a menu of the reports,” and get it. I expect that to get faster and easier every month.
That is also why the method starts with saying how you think, out loud. The case studies explain why the data was brought together, and the About page has my background.