A studio owner opens the admin app every morning at 6:40am, finishes their first coffee inside it, runs payroll on a Sunday night inside it, and closes the laptop with that same admin app as the last tab open. Roughly forty hours a week, sometimes more in the busy months. That's not a tool. That's an apartment.
Most studio software treats that as a chore. The default aesthetic is a beige spreadsheet with a logo on top. The defence is usually it's a business tool, not a toy. We think that's a category error. The fact that someone is going to live in something for forty hours a week is the strongest possible argument that it should be a little bit pleasant to be there.
So we put a pet on every staff member's profile. A cat, a dog, a hamster, a parrot, or a fox. Each staffer picks one. It lives on their profile, follows them around their own corner of the admin app, and does absolutely nothing useful.
1. The small case for joy in serious software
There's a pattern in the software people stay loyal to over decades, and it's not the feature list. It's the small moments built into the product that exist only to make the person using it smile. Linear's loading animation has personality. Apple's first-run experience on a new Mac is theatre. Things 3 has a tiny confetti burst when you finish a task. None of those moves the metric they would show their investors. All of them are why people stay.
There's a separate, more cynical, argument: business software is hard to differentiate on features alone. Eventually everyone has the same feature list. The booking flow looks the same. The reports look the same. What's left is the texture of using it — the speed, the wording, the small flourishes. The small flourishes are the part most teams cut, because they're impossible to defend in a planning meeting.
We didn't add the pet for the cynical reason. We added it because we like working in the app more when there's a hamster on the page. Honest answer.
2. What this actually looks like in the product
Each staff member, when they open their profile for the first time, gets a little prompt. Pick a companion. Five species: cat, dog, hamster, parrot, fox. Pick a colour. Give it a name if you want. Done.
From then on, the pet lives on that staffer's profile page. A small illustrated character with their chosen name underneath. That's it. It doesn't track anything. It doesn't level up. There's no XP, no streak, no daily bonus. It exists.
Other staff can see each other's companions on the staff list. A studio with eight instructors ends up with a tiny menagerie — three cats, two dogs, a fox, a parrot, and one hamster called Beans. People show their friends. They become slightly competitive about choosing the most ridiculous name. The studio manager's hamster is called Tax Audit. We hear about it.
3. The honest trade-off
We can't pretend this was a free thing to build. Choosing the illustrations took an afternoon of arguments about whether the fox looked smug enough. Wiring it into the staff profile took a chunk of an engineer's week. Writing the species picker took another. None of that work shows up on a feature comparison page. None of it would survive a feature-prioritisation exercise that scored every initiative on revenue impact.
It survived because we don't do that exercise. We have a small list of things the product needs to be exceptional at — payroll that's correct, scheduling that's predictable, a booking portal that members actually use — and then a separate small budget for things that exist only because someone on the team wanted to build them. The pet was on that second list. It cost roughly what a single edge-case bug fix costs. Less than a normal week's worth of engineering. The amount of delight per dollar is, frankly, hard to beat.
If we had to defend it to a board, we couldn't. We don't have a board. We have a small team and a slightly opinionated view that the admin app is going to be a place studio owners spend a lot of hours, and it should feel like a slightly warmer place than the alternative.
4. Why a small useless thing earns its keep anyway
Here's the soft argument. The studio owner spends forty hours a week in the app. Most of those hours are at moderate stress. Something's running late. A client is upset. Payroll doesn't tie out by two dollars. The mood inside the app is, on average, low to medium grim.
A small illustrated hamster called Tax Audit, sitting at the top of someone's profile, is not going to fix the bad day. It is going to add half a second of a different feeling to it. Half a second per session, multiplied by forty sessions a week, multiplied by hundreds of weeks of using the software, is not nothing. It is the same emotional logic as a slightly nicer pen, or a slightly better chair. You don't think about it consciously. You just stick around longer.
The harder version of the argument is about brand. A studio choosing software is choosing a kind of company to be tied to for years. Everyone's pitch deck says they care about studio owners. Most pitches read the same. The thing that breaks the tie is whether the product feels like it was made by humans who like the customer, or by a team optimising for a quarterly target. A hamster on the staff profile is a strange signal, but it is a signal.
5. What we deliberately didn't build instead
We've seen the alternatives. They mostly fall into two buckets.
The first bucket is the gamification layer. Streaks, points, leaderboards, a fake currency you can spend on a virtual store. We don't like these for staff. Studio managers are running a business; the last thing they need is a points system telling them they've fallen behind their peers in some made-up metric. Gamification works for members, occasionally, when it's framed honestly. It works less well for staff, because staff already have a real performance review and don't need a second pretend one.
The second bucket is the corporate mascot. A friendly cartoon character who pops up to walk you through the empty state of the reports page. We don't hate this one, but it's the wrong shape. The mascot is the company's, not the user's. The pet is the staff member's. The staffer picks the species, names it, and owns the small drawing on their profile. That ownership matters. It's the difference between a brand asset and a personal one.
6. What we're not promising to build next
We get asked this every time someone notices the pet. Are you going to add accessories? Will the pet earn levels when the staffer logs in more? Are you going to build a pet store?
No. The point of the feature is its smallness. As soon as the pet starts having achievements and a level and a daily reward, it becomes a system that has to be maintained, balanced, and supported. It starts taking real engineering time. It becomes a thing the product owes its users. The current version owes nothing to anyone. It just exists. We're going to keep it that way.
If we add anything, it'll be another species, drawn the same way, given the same nothingness to do. Maybe a small turtle. We have not decided.
