A local dog-walking business brought together through its identity, public website, client diary and management tools — from the first enquiry to the next booked walk.
Brand, website, product design & AI-assisted development
Credit
Direct client project · business owned and operated by Tanya Wenczel
Status
Public website · portal implementation
The live public website connects the Good Walks identity, local service and introduction journey.
How we approached it
01
Make the brand feel like the service.
The friendly dog identity, neighbourhood tone and clear service information carry through the website, diary, management dashboard and communications. The aim was a recognisable, approachable business rather than a disconnected booking tool.
02
Separate signing up from being approved.
Account access, dog intake and approval are distinct steps. Clients can provide their details before Tanya decides which services suit the household. The diary brings booking, pickup details, walk history and payments into one place.
03
Build around real operating decisions.
A Cloudflare backend and D1 database support capacity checks, household records, bookings, walk credits and payment records. Management tools keep approval and transfer checks explicit. We used AI tools to design and build the experience, checking workflow logic separately from provider and inbox outcomes.
Visual identity, illustrations and public website
Client accounts, dog intake and approval workflow
Client diary with booking, household details and walk history
Management dashboard for sessions, households and booking review
Cloudflare Pages Functions and D1 data model
Walk-pack, payment-record, notification and calendar workflows
Actual client diary in sample-data mode. Approved services, available places and household context appear together.Sample-data payment view distinguishes available and reserved walk credits. This is interface evidence, not a live transaction.Actual management dashboard with synthetic sessions and bookings. The preview disables booking and payment changes.
Project status & imagery
The public website was inspected live. Client and management screens were captured from the actual local interface using its built-in sample-data mode; no customer records were accessed. Backend workflows are implemented in the repository. These captures do not establish live payment, refund or email-delivery outcomes.