If the scope does not hold, we say so on the call, not after three weeks of "we'll think about it". Snowinch is not the automatic-yes studio; an easy yes on scope is how you work badly.
You arrive with a list. Everything is priority. The marketplace, the app, the back-office, "and then the AI". You want to hear that it can be done. It can always be done, on the slide.
Examples of no (not theoretical)
No to "we build everything, security later". That is not a scope. It is a delay with a polite name. Other people's data is not phase two. If the idea is "validated, now the whole product", and live is still a trial environment, the no is the same piece: validation does not close the risk.
No to "everyone can use it, we start wide". Wide is a way not to choose. Scope becomes a pile of exceptions. Who pays, who has the sharp problem, who can refuse: if that line is empty, there is no perimeter. There is an ICP that was not done.
No to an MVP that must stay in demo "because it is the first version". First version of a theatre. The perimeter we accept is on, or we say it is not.
No to hours only, nobody on live. You can buy hands elsewhere. Here someone has to be able to answer when a job dies, not only close a ticket.
No to a glossy brand and a duct-taped product, sold as the same project. Identity can be done. Not instead of live.
These nos are not a personality. They are a filter. If you remove them, you take work you cannot hold at night, and you work badly. The sentence is dry because the alternative is fake courtesy.
The cost of an easy yes
The easy yes has a known shape. You nod on the call. You widen the perimeter "just a bit". You promise a date that assumes integrations tell the truth. The founder leaves relieved. You signed an object you have not seen yet.
Then scope walks. Every "also" is already included, in the listener's head. The repo fills. Live slips, or ships with holes. At that point the original yes has become a fight: you lie about dates, or you cut in silence, or you do overtime nobody bought.
I would rather say no on a Tuesday than yes that explodes in November. The cost is visible: you lose a call, you lose a founder who wanted to be told yes. I take that. The other cost is a product that does not sleep, and a relationship already crooked.
There is a yes that looks like courage and is laziness: "we'll do that too, then we'll see". Seeing later is how you build debt. Honest scope has an outside. If the outside is empty, you are already lying.
An aside: I still have a list sent in chat, twenty-two items, all "must". It was not a brief. It was numbered anxiety. We closed the call on the first item that, alone, did not stand. The rest was noise.
How we work it
We start from what must stay on, and for whom. Not from how many screens. If that sentence cannot be said in one line, there is no scope yet. You work that line, or you stop.
Then you cut. Integrations, roles, exceptions. Every piece that stays needs a why tied to the signal, not the slide. The rest goes in a declared later, not in a "it fits".
If in that conversation the founder only wants confirmation, the call is over. We are not a chorus. On services the build starts from a perimeter someone is willing to defend. Not from a wishlist.
The limit: this page is not a discovery playbook, nor a printable "red flag" list. It does not cover tenders, nor partners who must say yes by contract. It covers how we decide.
If you want someone who always says yes to scope, that is not us. If you already have a signal and want a perimeter that holds, we talk on contact.
