Skip to content
BATES CENTER Sign in
The studio books in slices. Bring the hard problem — not a forty-page RFP. Start a brief

What we ship

01

Web development

Product sites, portals, and apps that stay fast. Clean architecture, no clutter.

02

Mobile

iOS and Android — native or hybrid. App Store, Play, and TestFlight pipelines.

03

IT services

Networks, servers, backups, identity. Quiet infrastructure you forget is there.

04

Geek stuffs

Labs, homelabs, hardware, Linux, 3D, gadgets. If it has a serial port, we speak it.

One desk

The whole stack on one mark.

Product, infrastructure, and the box in the closet usually live in three vendors. We keep them on one desk so the brief does not leak between tickets.

  • Web and mobile on the same system
  • IT that stays boring on purpose
  • Hardware when a person has to hold it
  • Handoff with docs, not a PDF dump

How a brief moves

Work should travel the way a good ticket does: short, named, and visible.

  1. 01

    Brief

    Scope, constraints, and the real problem — not the ticket title.

  2. 02

    Slice

    The smallest shippable that proves the shape. A date, not a vibe.

  3. 03

    Build

    Ship in the open. Review as we go. No mystery sprints.

  4. 04

    Run

    Docs, watch, the boring week after launch. We stay until it is quiet.

Jobs the studio takes

Product

A thing people use

A portal, an app, a public site that has to feel expensive and stay fast.

Ops

A layer that holds

Identity, backups, networks — the work nobody sees until it fails.

Lab

A box that blinks

Serial, print, homelab, the closet hardware a SaaS will not touch.

Civic

A quiet public tool

Rooms that are not startups. Clear type. No dark patterns.

Signal, not noise

40+Products shipped
99.9%Uptime target
12Years in the stack
24/7On-call when it counts

The stack we actually keep

  • Linux
  • Docker
  • Postgres
  • React
  • Swift
  • PHP
  • Node
  • Figma

From the room

They treated the product like it was theirs. Launch was quiet. That is the compliment.

Founder, logistics SaaS

Finally an IT partner who talks in systems, not invoices.

Ops lead, regional org

The app feels expensive. The process did not.

Product manager, mobile

Before you write

How do we start?

A short note is enough. Tell us what is stuck, the constraint, and when it has to move. We will answer from the studio with a slice, not a deck.

Do you take retainers?

Care is optional: hosting, watch, a monthly note. Most work is a bounded slice with a ship date. We do not sell fog.

Who owns the code?

You do. Repos, keys, and the production box transfer on handoff. We do not hostage a codebase.

Where are you?

The prairie. Remote is the default. On-site when the rack, the room, or the hardware needs a person.

Bring the hard problem.

Web, mobile, IT, or the weird box in the closet. Tell us what is stuck.