Hacker News new | ask | show | jobs
by lowercased 2706 days ago
> The kind of clients you want to work with will pay this without blinking. Sometimes they won't even know about the bill because it goes straight to AP.

I agree #3, but on #2 - I've never dealt with any business of individual who operated like a blank check ("just send the bill to AP"). They all have budgets - implicit or explicit - and all want a rough idea of range at the very least. Is this a $3k project or a $20k project? They all have a need to know up front. You can sometimes tell up front - you get better at it - when people are going to complain about it more.

Told someone on a project they were looking "in the $2k range, at $x/hr". Sent a bill for $2200, and they flipped out. "You said it was $2000!"). Well.. no, I emailed you that it would be roughly in the $2k range, and if it was going to go much outside that, I'd let you know beforehand. I got you your project done 3 days ahead of when you wanted as well... blah blah blah.

Written agreements up front with clear expectations, etc.

More to the point on money, working with people where the money is coming directly out of their pocket (vs an operating business where there's a budget, and the person you're dealing with is simply managing a budget) will take you much further. IME, most of the people you work with where the money is directly from their pocket will watch every nickel and take $9 of time to explain a $2 expense.

This isn't to say you should pad billing or rip people off by any means, but... taking hours to explain how web hosting works, and that no, we can't build a custom ERP system on your godaddy account that you prepaid for 4 years in advance last week when you bought your domain name, and that if this really is a "million dollar idea", you will need to spend more than $200 for an MVP. All of that is low-value stuff you want to figure out how to avoid.

2 comments

> taking hours to explain how web hosting works, and that no, we can build a custom ERP system on your godaddy account that you prepaid for 4 years in advance last week when you bought your domain name, and that if this really is a "million dollar idea", you will need to spend more than $200 for an MVP.

You joke, but I was in this exact position on Wednesday. It's natural to think that web consulting is dying or that there's a race to the bottom on pricing, until you come face-to-face with the level of ignorance many business owners (even successful ones!) have about technology. The world of business software is mysterious to many people. And while it's easier than ever to build a solution that replaces clunky .xls files or (worse) paper -- that can still be a major hurdle for someone not familiar with it.

I think the solution to OP's question is to see yourself as not just a developer but also a tour guide. Educate your customers without judgement. Teach them why what you do matters (translation: market to them!) Lots of people won't see the value and will never pay $100+/hour. But some of their competition will. And that's how you build a consultancy of your own.

Well... I don't joke :) The $200/MVP is a slight exaggeration, but not much. I've been approached by people about MVP, but they only focus on the M, not the V or P.
You're right on #2.

To clarify, any clients I have that behave that way are firmly out of the SMB segment (or have grown to that point as we have worked together), seem to be in cash-flow heavy industries like manufacturing or construction, and we've been working together for several years.

I think you made the point I was going for - it may be more hassle than it's worth to do work for a client that makes a fuss over $2200 vs $2000.

What's your strategy to avoid future work from such clients? I've thought the contract should include creating documentation for maintenance (e.g. login details to various services to update payment information or software versions or whatever) that the business can keep secured and that while you can be reached to perform certain kinds of maintenance at some fee you aren't obligated to. I had a friend in freelancing who self-hosted everyone on his own servers and charged an ongoing fee, though if I were a client I'd be nervous if the freelancer decided to raise their fee for the understandable reason that maintenance costs can increase.