What happens after you submit
Most operator applications disappear into a black hole. Ours doesn't. Here's exactly what happens between submit and your first slice of paid work.
The default version of an operator application is a black hole. You fill out a form, you get an autoresponder, and then nothing — until a recruiter pings you six weeks later about a role that has nothing to do with what you sent in.
That's not a process. That's a database.
Our questionnaire is the front of a real conversation, not the front of a CRM. If you've already read what 1099 actually looks like and the structure made sense, this post is the next layer down: what actually happens between the moment you hit submit and the moment your first slice of paid work lands.
What we read first
The questionnaire has seven stages — Identity, Values, Capabilities, Book of Work, Terms, Posture, Submit. We don't weight them evenly.
Book of Work and Capabilities get read first. We're looking for evidence you've shipped real things, on real timelines, for real money. Links beat descriptions. A live URL or a deployed product is worth more than a paragraph about what you "led."
Values and Posture get read second. Not for vibes — for fit with how we run engagements. Operators who need a manager, need a roadmap handed down, or need a Slack channel to feel productive aren't a fit, and we'd rather both sides know that on day one than month three.
Identity and Terms are last. Those are logistics; they don't decide anything until everything else clears.
What the first reply looks like
Inside about a week, you get a real human reply from us — not a templated one. It says one of three things:
"Let's talk." A 30-minute call to dig into the specifics of your book of work and where you'd want to plug in. No deck, no pitch — we're listening.
"Not right now, here's why." Specific reason, not "we'll keep you on file." Sometimes it's a capability gap on our side (we don't have client demand for that lane yet). Sometimes it's a fit gap on yours. Either way, you get the actual answer.
"Almost, but we need X." A specific follow-up — a sample, a reference, a clarification on something in the questionnaire. Not a homework assignment, just the missing piece.
Whichever one you get, you get it in days, not silence.
What the first slice of work looks like
If the conversation goes well, the first slice of work is small on purpose.
A defined deliverable. A budget that fits the deliverable. A timeline measured in weeks, not quarters. A single client point of contact — usually us, sometimes the client directly if the engagement calls for it. Payment terms agreed in writing before anything ships.
We don't start anyone on a multi-month engagement. The first slice exists so both sides can see how the other works in practice. If it goes well, the next slice is bigger and the relationship compounds. If it doesn't, we both learned something cheap.
That's the whole onboarding. There's no bench training, no certification, no "ramp." If you're already senior at what you do, the slice is the ramp.
What disqualifies an applicant after submit
Not many things, but a few are non-negotiable.
We won't route work to operators who can't produce a working sample of recent work. The questionnaire asks for it; "I can't share it, it's all under NDA" across the board is a hard signal, not a neutral one.
We won't route work to operators who treat the first conversation like a negotiation. Rate, scope, and terms are fair to discuss — posture toward the client isn't. If the first call surfaces a vendor mindset, we close out the loop politely and move on.
We won't route work to operators who go quiet between submit and the first call. The relationship is async by design, but async still requires responding. If a three-day reply is a stretch now, it'll be a problem on a live engagement.
None of these are common. We mention them because the rest of the process is generous, and the few hard lines are worth naming up front.
Why we run it this way
The questionnaire takes about ten minutes because the conversation that follows is the actual screen. A two-hour application would screen for endurance, not for fit. A 90-second form would screen for nothing.
Ten minutes of specific, structured questions tells us most of what we need to know. The rest is a real conversation with a real human, on a real timeline, ending in a real first slice of work — or a clear no.
That's the deal. It's how we wish every operator application worked when we were on the other side of one.
If you've been waiting for a process that runs like that, take ten minutes and tell us about your work.
