What we've shipped.

First in the studio

QueueHamster.

Virtual queue management for independent service businesses.

QueueHamster replaces the clipboard at the counter and the buzzer in the waiting area. Customers scan a QR code to join the queue, get live position updates and wait-time estimates, and get notified when it's their turn — no app to install, no hardware to buy, no staff training beyond five minutes.

It runs in production today for barbershops, clinics, salons, cafés, vets, pharmacies, and tailors. Built by the Datanation team on the same React Native + Expo + Firebase stack we recommend to Labs pillar clients — and on the same Firebase + serverless data architecture we'd recommend in a Consulting engagement at this scale.

QueueHamster is what it looks like when we apply our own engineering bar to a real product with real customers.

More in the studio.

We have other products in the works. We're choosing what to ship next deliberately — there's no incentive to flood the page with vapor.

→ Subscribe to Insights to see what ships when.

Why we ship our own.

Three reasons.

To keep the engineering bar honest. A consultancy that's never shipped a product is hard to trust on questions about shipping. The constraints that actually shape software — distribution, customer support, store reviews, cost per user, real cohort behavior over months — only show up when you own the product. Without that pressure, an engineering team's standards drift toward what's elegant rather than what works.

To dogfood our stack decisions. When we recommend React Native + Expo + Firebase to a Labs client, it's because we run it ourselves. The opinions on our Consulting and Labs pages are stress-tested by the products on this one.

To compound the team's depth. Studio products are the place where engineers get to make decisions all the way through — architecture, design, support, pricing, retention. Client work is one slice of that loop; product work is the whole loop. Engineers who do both get better at both.

Where products go.

Most stay in the studio. Some — when they outgrow the studio's scope or need outside capital — may spin out as separately incorporated companies, typically as Delaware C-Corps, the standard structure for venture-backed software. The studio holds the IP, the engineering continuity, and the long view either way.

This isn't a venture studio. We're not optimizing for product portfolio velocity or for exits. We ship when shipping is the right answer; we incorporate separately when separate incorporation is the right answer; and we keep most products inside the studio because that's where they do the most for the work we do for clients.