A publisher isn't a "wallet" or a magic release button.

In its most basic form, a publisher is a partner that assumes some of the project's risks and responsibilities.

To put it simply, a publisher looks at a project from three perspectives simultaneously:

Idea Potential

- Not only how interesting the project is as art, but also:

who might need it;

- What form can it take on the market;

- Will it survive until release?

- Realistic Implementation

- Does the project's scale fit the team's needs;

- Is there a development vector, not just a set of ideas;

- Does the developer understand what they're doing now, and not "someday later."

Long-Term Collaboration

A publisher is often looking not just for a single project, but for people they can continue to work with. Therefore, a perfect build isn't as important as:

- Adequacy;

- The ability to listen;

And the most important trait in a developer for a publisher is a willingness to see things through to completion.

It's important to understand:

a publisher isn't obligated to take on every project and doesn't guarantee success.

But they can:

- help structure the development;

- soberly assess the strengths and weaknesses;

- suggest where the project is losing its appeal or the market.

A rough project isn't a problem.

A lack of direction and understanding is.