Skip to content
kumo

Publishers and investors

A publishing deal is paid milestone by milestone. In kumo the studio invites its publisher to follow the project, shares what each milestone needs, and the publisher’s acceptance makes the milestone’s payment due in Money.

Publishing is in Production. It shows who follows the project and exactly what each of them sees.

Press Invite to follow on Publishing, on a Legal agreement whose counterparty is a company, or on a company’s card in People. Pick one of the studio’s companies or name a new one, say whether it follows as a publisher (it accepts milestones) or an investor (it follows only), and who the link is for. kumo never sends it: copy the link and hand it over yourself. It works once, for a week.

Whoever signs in with the link joins the project as a guest and is placed in that company. A company’s people are free guests: they hold no seat.

Nothing is shared until you tick it. For each company, choose:

  • Milestones: each one, with its dates, its status as it is now and the payments a deal names on it.
  • Builds: the development build or the release. Every download is logged under the company’s card, with who and when.
  • Playtest summaries: how many playtests, how many players took part and answered, and what they said most.
  • Crash health: errors in the last 14 days against the 14 before, the players they reached and the releases most affected.
  • Spend against the plan: what the project paid and owes, beside the cost Production plans for it.

A following company never sees the board, the wiki, chat, HR, people’s emails or anything you did not tick. Changing a tick applies at once. Stop sharing removes the follow and denies the company everything in the project at once.

Press Submit beside a shared milestone. kumo takes a snapshot: each of the milestone’s tasks and whether it is done, the goals that measure it, the deal’s payment on it, and the shared build, playtests, crash health and spend as they are at that moment. The build is kept while the submission waits or once it is accepted, whatever the build retention says.

What was submitted never changes. If something changes after you submit, submit again: submissions are numbered, and the earlier ones stay. While one waits you can Withdraw it.

The publisher downloads the build, comments on any line, and then either accepts the milestone or asks for changes, a line at a time.

  • Accepted moves the milestone to accepted. A deal’s milestone payment whose status is accepted is then owed in Money (set the status in the agreement’s money terms).
  • Changes become tasks on the milestone, each saying which line it is about and who asked.

Both reach the project’s News, and both are automation events (A publisher accepts a milestone, A publisher asks for changes to a milestone), so you can post them to a Discord channel.