Cohort progress you did not have to take anyone's word for

If you run an E-Cell, an incubator batch or a college programme, you already know the failure. At the end of the cycle you have forty teams and forty slide decks, and the ranking you produce is mostly a ranking of who presents well. The teams that talked to twenty customers and the teams that talked to none both arrive with a milestone slide saying customer validation: complete.

The usual fixes make it worse. A reporting template gets filled in the hour before it is due. A weekly form asks the builder to grade themselves. A jury adds a second layer of judgement on top of the first, and the thing being judged is still the account rather than the work.

What the board is

Masterji is an execution coach your builders use daily: one goal, one task declared each morning, proof filed each evening, and phases that open on accepted evidence rather than on their say-so. The cohort board is the aggregate of that — one row per builder, and nothing on it the builder typed.

• Phase reached — where they are on IDEA → VALIDATION → BUILD → LAUNCH → TRACTION, and each rung was earned against a bar.
• Proofs from real contact, leading the row, because it is the question you actually have: which of these forty talked to somebody. Every one cleared a gate stamped VALIDATION or later.
• Proofs banked — the total accepted, whatever phase stamped them.
• Day streak — consecutive days with proof filed.

What is not on it: no goal title, no proof text, no reason a builder gave for closing an idea, not one word they wrote. A member between ideas shows as between ideas — unranked rather than scored zero, because ranking an absence would be the board making a judgement the record does not contain.

There is no field on the board a deck can be written in.

Why counts rather than reports

Because the number a builder cannot inflate is the only one worth ranking on. A proof becomes accepted by clearing a gate that is a database query, not a prompt — the model can propose an advance and the server counts the rows and refuses if they are not there. So a row reading three conversations means three, with three different people, and the builder could not have talked their way to it.

That also settles what the board is for. It is not a leaderboard to motivate anyone — it is the answer to is this cohort actually in front of customers, available on any Tuesday rather than at the demo day.

How you would see one

A read-only watch link. No account, nothing to install: staff generate it and you open it. It renders the same rows the members see, ranked the same way, with the join box and the leave button taken away — a watcher is not a member and has nothing on the page to change. Revoke or rotate the link and it reads as nothing here rather than forbidden.

Builders join with a code and can leave. Nobody is counted inside somebody else's aggregate without having joined it.

Where this honestly stands

Cohorts are set up by hand right now. There is no self-serve creation and no signup on this page that would work — the product has the board, the join flow and the watch link, and creating a cohort is something I do for you. If a queue forms that gets built; until one does, building it would be guessing.

And there are no logos to show you. Masterji is early and this page is not going to pretend otherwise. What there is: a working board, a gate that has refused its own author on the record, and a method borrowed from The Mom Test, The Lean Startup and MAKE, credited by name. If you want to see it refuse an advance before you consider it, the walk-through needs no sign-in.

If you run a cohort and the ranking problem above is one you recognise, the useful next step is a conversation rather than a trial — I would rather hear how you currently decide who is doing well than show you a screen.