[ednite]

I don’t think there’s a one-size-fits-all pricing strategy, despite in the age of AI. I separate my approach: On-site labor: is billed hourly, excluding travel.

Project-based work: Whether it’s a new project or fixing legacy code, pricing strategy is per project, with clear timelines so clients can assess value. If they need it faster, I adjust the pricing accordingly.

Pricing on project-based work can be a competitive risk, but ultimately it comes down to building trust and long-term relationships.

When both sides feel it’s a win, that’s when the real value happens.