Masterji मास्टरजी
Sign in

The coach who makes you ship.

For first-time builders in India who never got a mentor — the plans are made, the tutorials are watched, and nobody is waiting to see it on Friday. One goal. Four phases you have to earn. A task declared every morning, proof filed every evening — and a server that will not open the next phase until the evidence is actually in.

Free. One goal at a time. Nothing to install or configure.

This is the whole app

Two cards and a conversation. Nothing to set up, no projects, no board — the screen below is what you get on day one and what you get on day ninety.

The goal

Tiffin-delivery app for my college

  1. IDEA
  2. VALIDATION
  3. BUILD
  4. LAUNCH
  5. TRACTION

Third conversation. Ask for something that costs them — an hour, an intro, money.

Today

Declared: Interview the mess aunty about the 9pm rush

✓ accepted — Ramesh gave you a number and an intro to Block B. That's a conversation, not a survey.

Quick one — should I build this in Next.js or Remix? And Postgres or Mongo?

Fair question, wrong week. Both of those are BUILD's problem, and neither answer survives a user you haven't met. The Mom Test says talk about their life, not your idea — go ask the mess aunty what she does when orders pile up. Bring me notes tonight.

I don't have an idea yet.

Then we start before the ladder. Twenty turns, and the first one is yours: what did you stand in a queue for this week, or watch somebody work around? Park up to three, pick one — then we make the winner specific enough to act on. Nothing in here is graded and nothing banks; when it's sharp I'll fill the commit box, and pressing it is still yours.

A day with Masterji

  1. Morning

    Declare one task under Today, or where he drafted it in the chat. Ten seconds. He tells you if it's the wrong week's work.

  2. During

    Do it. Think out loud with him when you're stuck — he writes tonight's proof from what you tell him. Nothing counts until you file it.

  3. Evening

    File the proof under Today — or right there in the chat, where he drafted it from what you told him. That's one tap.

  4. When the proofs are in

    The gate opens the next phase. Not before, however well you argue.

You don't get to skip a phase

  1. IDEA
  2. VALIDATION
  3. BUILD
  4. LAUNCH
  5. TRACTION

Before IDEA there's a room that isn't on this ladder — the workshop, under the commit box: twenty turns to find the idea and sharpen it, if you don't have one yet. It works through the four things IDEA will ask you for, and what you tell him carries over so your first morning doesn't start from nothing. Nothing in it counts toward anything, and it refuses nothing — that's the point of it.

Each phase opens on evidence you banked in the phase before it. The coach can be argued with; the gate can't — it's a WHERE clause, and the model only gets to propose an advance. Talk about tech stacks all you like in VALIDATION. It won't count, and he'll say so.

Why trust this coach?

Not on anyone's track record. Masterji makes no claim to founder wisdom — be suspicious of any tool that does. Its authority is procedural: the method is borrowed in the open from The Mom Test, The Lean Startup and MAKE, and every refusal it makes traces to a condition you can read in gates.py and a test that pins it. A referee doesn't need to be a better player than the players.

One goal, declared tomorrow morning.