We got a quote without a spec sheet, now there's a dispute between parties — how to resolve?

bro what are u even saying... exactly this is why u got into trouble, everyone does. i made the same mistake at the start i wouldn't do work without a contract now in my life. once i just signed a quote for a big amount, then they demanded unlikely things, turned out to be a cheap architect in the end

Technically: in a software development contract, the scope should be defined as 'user stories' or a 'requirements specification'. The quote should only include price + time estimate. Lack of scope is defined as scope creep without change management.

i encountered a similar situation the part i struggled with was that the money outflow never ended. honestly the agency came up with such things as 'extra requests' that if u didn't check it suddenly became ur responsibility

Good news: maybe u can still fix it. have a friendly chat with the agency. say 'there's a misunderstanding here, let's write down what's in scope together'. most agencies accept this, because if u've already paid and they've done 80%, clarifying the rest works in their favor.

if u've already paid the agency, they have the upper hand from an accounting perspective. it's hard for u to increase the unwritten scope. worst case: u get the product, but u also pay for the extra work. i'd just say 'at least it's done' and close it.

Quick solution: send it to the agency via email. 'Based on the quote scope, I'm writing down the features as I understand them — please confirm or correct.' Once u get written confirmation from them, that counts as documentation too.

Following.

The discussion got scattered, let me summarize. Processes without records never improve, because you don't know what to fix.

I'm also curious if anyone does it differently.

Thanks, this was very helpful.

Generally correct, but one part is missing. The biggest time-waster for us was not knowing who had the final say.

Proven by experience.

There's a common mistake people make when doing this. Start with a small trial; don't commit to everything at once.

When making a decision, first look at what data you have on hand.

sorry but this doesn't apply in every case and i mean if you don't write this down from the start, it leads to arguments later.

when maaking decisions, write down the worst-case scenario too not just the best. this is my opinion, I'm not claiming it's absolute truth.

Thanks, this was very helpful. If acceptance criteria aren't written, when the work is done is open to debate.

If you have questions, write them; I'll answer as best I can.

I'll argue the opposite, don't get mad. The harder it is to reverse a decision, the slower you should make it.

That's all, sorry if I went on too long.

Saved.

I'll try it.

Same here.

The opposite happened to me, that's why I'm writing. When we decide without measuring, we always end up in the same place.

If you post the result here, it will help others too.