Multi-tenant SaaS · art museums and their visitors
Harkelo
A guided museum tour normally needs a docent, and docent time is the scarcest thing a museum has. Harkelo models a visitor’s taste in art, recommends works from that museum’s own collection, and walks them through the building solo or in a group, with no staff required. I owned the architecture end to end, and after six months of building, two museums, one in Utah and one in California, were paying to use it.
- My role
- Co-founder and CTO — architecture and primary developer
- Timeframe
- January 2026 – July 2026
- Built with
- AWS Lambda · API Gateway · PostgreSQL · DynamoDB · WebSockets · Stripe
Problem
The best museum experience doesn’t scale
Walk through a gallery with a good docent and the building changes. Someone reads what you’re drawn to, points you at three works you’d have walked past, and asks the question that makes you actually look. It’s the single best thing a museum can offer a visitor.
It’s also the thing museums can least afford to give away. A docent-led tour costs staff time, has to be scheduled, and serves one group at a time. So most visitors get the other version: a map, a wall of placards, and a slow drift toward the exit. Museums know they’re losing the visit, and they know what it would cost to fix it at scale.
Harkelo’s bet was that the docent’s job breaks into parts a system can do: work out what this person responds to, pick works worth their time, get them there, and give them something better to do than read a label.
Solution
A platform that plays docent, per museum, per visitor
A visitor scans a QR code at the front desk. No app, no account. The site figures out which museum they’re standing in, either from that code or from their location, and hands them a short quiz about how they engage with art: whether they go to form and craft or to subject and story, whether the distant past pulls harder than the modern, what they came in for today. Out of that comes an archetype and a set of recommendations drawn from that museum’s own collection, with pins on the museum’s own floorplan to find them.
At each work, the platform gives them an activity rather than a paragraph: a prompt, a poll, a question to sit with. When they’re done, they pick the next piece and go again.
Placeholder — not yet published
Screenshot needed: the visitor recommendation screen — archetype result plus the recommended works for that museum
This is the moment the product’s premise becomes obvious, and it’s hard to convey in prose alone.
Drop the file in public/images/ and swap this component for next/image.
The group mode is the part I’m proudest of. Several visitors join one session with a four-character code and move through the museum together. Everyone answers on their own phone, the group sees each other’s art preferences, and discussion at each work is turn-based, with a passed “talking stick” so one person doesn’t run the conversation. It’s built for families and school groups; a lone visitor can ignore it entirely.
Museums run their side themselves at museums.harkelo.com: their branding, their floor plan and artwork pins, which activities are turned on, and who on their staff has access.
Result
Shaped by six museums, then paid for by two
I was a co-founder, the CTO, and the primary developer. Before any museum used Harkelo for real, we spent four months running product demos with small teams at six Utah museums, taking their feedback and reshaping the product around what museums need rather than what we assumed. After six months of building, two museums became paying customers and began using it live: one in Utah and one in California.
Why this is here, and what it is not
This is not a project I’d take on at freelance pricing, and it isn’t what you’re buying if you hire me for a small-business site. A platform like this is months of full-time work and a real cloud bill.
It’s on this page for one reason. Hiring a developer means trusting that they know what they’re doing, and Harkelo is the evidence that I do. I’ve built software that keeps each museum’s data separate, billing that had to be right every time, and group tours that stay in sync across everyone’s phone. A small-business site sits comfortably inside that range.
What I offer is on the services page, and if you want to see something I built for a small business, take a look at Clover Creek Guest House.
More work
Other case studies
Or go back to the full portfolio.
Next step
Need something more complicated than a website?
Booking, scheduling, online ordering, an admin dashboard, a database behind the scenes: that’s the kind of thing I can build, and the Growth package exists for it. Bring me the problem and we can work out whether it fits.
15 minutes, no cost, no obligation. You leave knowing what your site would take.