Roadmap

Every surface.
And how to reach it.

What Qatoto is for, what you can do here, and where each of those things lives. Then ten stages in the order you meet them — from making an account to shipping a product and selling it. Every node is a real page.

What this is

One pipeline, from a problem to a product on a shelf.

Qatoto takes an idea from the person who had it to a product someone can buy, without that person needing capital, a network or a team they already know. A problem gets posted, people apply to work on it, the build happens in the open with a daily log, backers commit against work they can watch, and the finished thing goes to market through the Store — manufacturing, listing, orders and returns included.

Contribution is logged rather than negotiated, so the equity split is argued from a ledger. Progress is posted daily, so trust is evidence rather than a deck.

The video feed, the Blueprints hub and the Store are not a second product bolted on — they are how an idea gets found, how a team gets an audience, and how the finished unit gets sold.

What you can do

Eight reasons to be here.

Find yourself in one of these. Every capability names the page it actually lives on — and where a surface is still a placeholder, it says so instead of linking you into one.

If you have an idea

The pipeline starts with a problem worth solving, not a deck. You need the concept and the conviction to lead it — not capital, and not a team you already know.

If you want to join a build

Engineers, operators, domain specialists and hobbyists join projects they did not start. Contribution is logged, and the log is what the split is argued from.

If you want to back a project

Deal flow you can read the daily work behind. Visibility here is continuous rather than quarterly — the build log is the disclosure.

If you are just here to watch

The feed is the front door, and browsing needs no account. Every project on the pipeline publishes here, so watching is how most people first meet an idea.

If you are here to research

Long-horizon work that does not fit a launch date. Programmes carry branch maps whose gaps and duplicated effort are derived nightly, not claimed by whoever is loudest.

If you want to buy

The Store is where a shipped product lands. Everything the pipeline finishes is sold here, alongside services from providers on the platform.

If you need something made

The sourcing side of the Store. A project that reaches manufacturing does not leave the platform to find a factory.

If you want to sell or create

Studio is the other side of every buyer surface — list what you make, answer the RFQs that arrive, and publish the video that sells it.

    • Build log/research-and-development/build-logThe daily-log feed across every active project.
    • Project

      /research-and-development/project/[id]

      Overview, daily logs, team, funding and governance in five tabs.

      Reached from clicking any project card in the build log or R&D hub.

    • Virtual workshop

      /research-and-development/project/[id]/workshop

      The shared build space for one project.

      Reached from the Workshop tab on a project.

    • Proof of effort

      /research-and-development/project/[id]/proof-of-effort

      The Slicing Pie ledger — claims, re-verification and the running split.

      Reached from the Proof of Effort link on a project.

Reference

The reading room.

Not a stage of anything — the pages you open when you want to know how something works, or what you agreed to.

Start anywhere

The map is the product. Pick a stage.

Most people arrive at stage two and leave at stage ten. You do not have to walk the trunk in order — but it is the order the work actually happens in.