A guy from a publisher emailed about my game. Said he's "interested" but wants to see "more of the vertical slice." I have been making the vertical slice for eleven months. At what point is the vertical slice just the game. Maybe the game is just one long vertical slice and I am Sisyphus and the rock is a Unity scene that won't stop throwing null reference exceptions.
The Vertical Slice That Ate My Life
AI-polished version. Switch to Raw for the unfiltered original.
The Vertical Slice That Ate My Life
Eleven months ago, a publisher asked to see a vertical slice. Eleven months later, a different email from the same publisher arrived: they want to see more of the vertical slice. At some point, a reasonable person has to ask — at what point does the vertical slice become the game?
The vertical slice is the games industry's favorite euphemism for controlled hope. It means: show us enough to prove you can finish it, but not so much that we have to commit. It is a hedge dressed up as a milestone. The developer builds; the publisher watches; the goalposts stay warm from all the moving.
This is not a complaint about one email. It is a complaint about a structural asymmetry that the industry has quietly normalized. Publishers hold the capital. Developers hold the risk. The vertical slice — that polished, representative chunk of gameplay meant to demonstrate viability — becomes the mechanism by which that imbalance sustains itself. You do not get a deal until you prove you can make the game. You cannot make the game without the deal. So you make the slice. Then more of the slice. Then, somewhere around month eleven, you are making the game, and calling it something else.
There is a version of this arrangement that is defensible. Publishers are not charities. Vetting projects protects them from catastrophic losses, and catastrophic losses in games publishing are not rare. The industry is littered with funded projects that dissolved into nothing. Due diligence is real. The ask is not inherently predatory.
But due diligence has a time limit. After eleven months of sustained development, the question is no longer whether a developer can build — it is whether the publisher is serious. Asking for "more" of a vertical slice that has been growing for nearly a year is not diligence. It is option-holding. The publisher keeps a promising project on the radar at zero cost, while the developer burns runway, momentum, and the particular kind of creative energy that does not regenerate easily.
Sisyphus, in the myth, is condemned to roll his boulder uphill forever. The cruelty is not the weight. It is the repetition — the sense that completion is always one push away and never arrives. Independent game development, at its worst, replicates that structure exactly. The null reference exceptions stack up. The Unity scene refuses to behave. The milestone moves. And the developer keeps pushing, because the alternative is to let the boulder roll back down and admit that eleven months went somewhere without arriving anywhere.
The boulder does not have to win. But the developer has to name what is happening. "Interested" is not a contract. "More of the vertical slice" is not a roadmap. At some point, the only honest move is to send the email that asks the publisher to be specific: specific timeline, specific terms, specific commitment — or a specific goodbye. The game exists. It has existed, in growing form, for nearly a year. That is not a pitch. That is leverage, if the developer is willing to use it.