5 ms·

> Freelancers too often either accept a price the customer attaches to a project (based on what?) > You should focus on adding business value and how to attach

> Freelancers too often either accept a price the customer attaches to a project (based on what?) > You should focus on adding business value and how to attach fair prices for delivering that value, in concrete terms. Based on what? I'm not a business analyst. I have no idea how much business value a particular project could be worth to my client.

gregjor 3y ago
You talk to the customer. If the customer doesn't have a budget or a price range based on value to the business, red flag. The customer should have some idea what they expect to make (additional revenue) or lose (costs or risk) before they start asking for bids or looking for a freelancer. I just ask, "What is this worth to your business?" or "How much is this bug/missing feature costing you?" If they don't know or won't say I probably don't want the gig. Sometimes the customer needs help identifying the business value, costs, and risks. A successful freelancer has to do some analysis, business and technical. Otherwise they are just selling their time for money as a temporary employee.
- mettamage 3y ago
  I wish there was a small course on this on how to navigate this.
  - gregjor 3y ago
    You need domain expertise to do useful business analysis. Sometimes the customer can explain their business in sufficient detail, sometimes they can't, or the business domain is sufficiently complicated that you can't just pick it up. I don't know any good way to get domain expertise other than on the job. One thing you can do in a programming role is to take an active interest in how the business works. Talk to people in other departments, ask questions. Early in my career I had to "cross training," which meant shadowing or even actually doing other jobs so I could see how the business works. I not only write code, I can operate a fork lift, thanks to cross training.

gregjor 3y ago

You talk to the customer. If the customer doesn't have a budget or a price range based on value to the business, red flag. The customer should have some idea what they expect to make (additional revenue) or lose (costs or risk) before they start asking for bids or looking for a freelancer. I just ask, "What is this worth to your business?" or "How much is this bug/missing feature costing you?" If they don't know or won't say I probably don't want the gig. Sometimes the customer needs help identifying the business value, costs, and risks. A successful freelancer has to do some analysis, business and technical. Otherwise they are just selling their time for money as a temporary employee.

mettamage 3y ago
I wish there was a small course on this on how to navigate this.
- gregjor 3y ago
  You need domain expertise to do useful business analysis. Sometimes the customer can explain their business in sufficient detail, sometimes they can't, or the business domain is sufficiently complicated that you can't just pick it up. I don't know any good way to get domain expertise other than on the job. One thing you can do in a programming role is to take an active interest in how the business works. Talk to people in other departments, ask questions. Early in my career I had to "cross training," which meant shadowing or even actually doing other jobs so I could see how the business works. I not only write code, I can operate a fork lift, thanks to cross training.