say the problem
out loud.

02  ·  the follow-ups

five questions, then a number.

every one of these changes the estimate. the last two change it a lot .. connectors are where the time actually goes.

03  ·  what happens next

seven steps, & you are only responsible for two of them.

1. you describe it

   plain words. the follow-ups do the shaping, not you.

2. a number lands before anyone talks price

   the estimate comes off the scope signals. it will be well under what an agency quotes, because the work is assembled from connectors rather than written from scratch.

3. it lists in the market

   public. anyone can read it, vote it up, or argue with it.

4. teams claim it — more than one, on purpose

   competing claims are the feature. two teams building the same brief is how you find out which reading of the problem was right.

5. the money sits in escrow

   funded but not paid. nobody is trusting anybody yet.

6. review, then you pick

   code, connectors, scalability & security get checked before anything reaches you. then the choice is yours.

7. everyone who built gets paid something

   the team you picked takes 70 percent. the teams you did not still share in it. that is deliberate.

04  ·  the split

where a rupee goes.

published, versioned, & enforced by the database rather than by a promise. the policy row that applied to a payout can be read back years later.