OZP

000%

OZP Studios

4 min read

Work we don't take

A short list of no — so you can skip the call if this is the job, and so we don't become a staffing firm with worse hours.

Written by OZP Studios, Seattle, WA

The fastest way to waste both of our time is to hire us as a substitute for a decision. We get that request more often than you'd think: a date, a feature list, no owner, and an expectation that the studio will figure out what this is supposed to be.

We take fewer projects than we're offered. That isn't a positioning line. A small studio that says yes to everything becomes a staffing firm with worse hours. Here's what we decline, so you can skip the call if this is you.

No owner in the room

If the person who can approve scope and budget is “looped in later,” we aren't starting. We've watched those projects wait on a ghost. We'll talk before that person shows up. We won't estimate as if they already did.

A rebuild with no replacement plan

“Rip and replace by Q3,” and the current system is still the one payroll runs on. Modernization is real work. It needs a cutover, a fallback, and someone who understands the old thing. If nobody on your side can explain the old thing, we're not the archaeologists you need first. We can help you find them. We shouldn't pretend the finding already happened.

AI as the pitch

If the sentence starts with “we want to add AI” and doesn't include a job a person is failing at today, we'll ask you to put the model down. We use models when they earn it. Kual Notes is the case we can actually point at: writing is the labor, the model is supposed to give something back. Sprinkling a chatbot on a product to make a deck denser is a different request, and we usually say no.

A date with nothing behind it

We'll move for a launch, a season, a compliance deadline. We won't sprint because a month landed on a slide. Fake urgency just compresses the same undecided work into nights.

Us as the IT department

We build products and systems. We don't become on-call for every vendor password. Ongoing support exists, and it's scoped. It isn't “Kyle will know” — there are two Kyles, so that was never going to work.

If the problem is real and someone owns it, we're interested. Messy brief, small first version, all of that is fine. Send that. A clear no is faster for both of us than a maybe that drags.