Sometimes pricing a freelancing project can be as simple as :
Freelancer: "I'm happy to do the work for this price".
Client: "I'm happy to pay this price for the work completing".
Rules for fixed-price projects:
1. Get a deposit 2. Get a fixed scope 3. To reduce the price you must reduce the scope 4. Don't use estimated days x day rate = price 5. Add a minimum 20% contingency 6. Price high enough to make a profit after you've paid yourself
Get.
A.
Deposit.
Remember that when you give a fixed-price for a scope of work,
You are guaranteeing completion.
Going back to the table for more money at this stage leaves a bad taste.
Fixed-price projects are highly beneficial to efficient freelancers.
*If* quality is retained.
Some people will pick the cheapest price because it's the cheapest.
Some people will pick the most expensive price because it's the most expensive.
If you're the most expensive option,
And a prospect who cares can't understand why,
Your positioning is off.
Price tells it's own story, but it needs back up from credibility.
The way that pricing methodologies are received differs from country to country.
Be aware of this when making offers.
Value-based pricing requires the most effort when making offers.
But you should still research your client when using other strategies.
How valuable will you be to them?
Value-based pricing TLDR version:
Your client's average lead value = £500
You estimate that your work will get them 100 leads in year 1.
That's £50,00 of value.
You give a price for your work based on a % of that figure.
If you can show the value, you can justify the price.
"Day rate" where you guarantee a set amount of logged hours is worse than billing hourly.
It's billing hourly for less money.
Retainer agreements are a useful safety strategy.
Give preference to retainer engagements that sell your availability to deliver knowledge, not your labour.
Estimates are never accurate.
Fixed-price terms are nearly always best.
When a hard deadline is introduced to a fixed-price project,
Add 20%.
If it's most risky for you to work with the client the price should be higher.
If it's most risky for the client to work with you the price will be lower
Price mirrors risk.
Never use your bottom line as your price.
Negotiate on terms, not price.
Reducing your price means reducing your perceived value.
*If* you don't also reduce scope.
If you think there's a chance you might kick yourself for not charging enough,
It'll probably happen during the project.
Add 20%.
Pricing freelancing projects is tough
There's no 1-size-fits-all solution
Understand each method
Have your preferences
Be aware of your position
Gauge what your clients are most likely to accept
Apply the most appropriate strategy to get the job at a price you're happy with
1. Allow people to purchase a limited NFT providing access to all of my products
2. Incentivise buying an NFT (+ holding it) over paying in $ with access to future products too
3. Let holders sell their NFT after they've consumed the content for a potential profit
Initial thoughts on stack:
- Solidity ERC721-based smart contract on Ethereum
- Hardhat for local development, testing and deployment
- Next.js for the front-end application and token API
- Vercel for hosting
- Tailwind for styling
- Token gating the content... not sure yet