db passwords are in .env. like agency: I won't give them for security reasons I'll change them when you ask.
.env file has API keys, agency won't hand it over
- Job title
- Social media manager
- Sector
- Sports and fitness
- Organization type
- boutique agency
- Joined
- Nov 2024
- Message
- 56
The .env file must be delivered to the client. Is the agency providing hosting? If not passwords must be delivered (can be encrypted).
- Job title
- Production planning
- Sector
- IT services
- Organization type
- early-stage startup
- Joined
- Nov 2024
- Message
- 249
Let me summarize what's been said so far. If acceptance criteria aren't written, when the work is done is open to debate.
If you post the result here it will help others too.
- Job title
- Production planning
- Sector
- Leather
- Organization type
- early-stage startup
- Joined
- Dec 2025
- Message
- 385
Let me speak from the other side; I'm on the supplier side. Every "we'll look at it later" in a meeting means unbilled work.
This is my opinion Im not claiming its absolute truth.
- Job title
- Social media manager
- Sector
- Insurance
- Organization type
- 8-person team
- Joined
- Nov 2024
- Message
- 19
I'm a small business, let me explain from my side. If you don't write this down from the start, it leads to arguments later.
That's all, sorry if I went on too long.
Let me speak from the other side; I'm on the supplier side. The answer varies greatly by industry; there is no one-size-fits-all rule.
- Job title
- System support specialist
- Sector
- Law
- Organization type
- 20-person company
- Joined
- Nov 2022
- Message
- 147
There's one point I'm curious about. When we decide without measuring, we always end up in the same place.
- Job title
- Data entry clerk
- Sector
- Accounting & advisory
- Organization type
- workshop
- Joined
- Oct 2023
- Message
- 93
My perspective changed after experiencing that. Start with a small trial; don't commit to everything at once.
Taking notes for two weeks yields better results than a six-month estimate. Correct me if I'm wrong.
I disagree with you on this point. Code without setup documentation isn't yours, even if you have it.
Start with a small trial; don't commit to everything at once. That's all, sorry if I went on too long.
Just a heads-up. The biggest time-waster for us was not knowing who had the final say.
Hope this helps.
The most overlooked point about environment variables delivery is this: Every "we'll look at it later" in a meeting means unbilled work.
Of course, it varies if your situation is different.
- Job title
- QA Tester
- Sector
- Retail
- Organization type
- a company within a holding
- Joined
- Jul 2025
- Message
- 241
I agree, and I'd like to emphasize that. Start with a small trial; don't commit to everything at once.
Correct me if I'm wrong.
- Job title
- Graphic Designer
- Sector
- Furniture manufacturing
- Organization type
- chain store
- Joined
- Sep 2026
- Message
- 9
Let me speak from the other side; I'm on the supplier side. Hasty decisions become decisions you have to fix six months later.
If you post the result here, it will help others too.
Let me share my experience. honestly when we decide without measuring, we always end up in the same place.
I'm also curious if anyone does it differently.
Could you elaborate on that? I mean ask who prepared the quote and who will actually do the work.
If I were you I'd go this route.
let's separate the concepts, they're getting mixd up but ask who prepared the quote and who will actually do the work.
just leaving this note, it might be useful.