Ask HN: How much should we charge for a bespoke version of our site?

Just two general thoughts...<p>First, don't underestimate the distraction of hosting and maintaining a separate code base. Now every time you start on a new feature you have to think about two deployments, two separate user bases, perhaps two UIs.<p>Second, you almost never make money on your first "hosted" deal like this - there are too many one-off things you have to do to get started that don't directly benefit the client so you can't easily charge for them. different deployment systems, hosting, monitoring. support, documentation, perhaps a UI refresh on your ugly admin tool because only you two used it, etc.<p>Bonus third thought - either charge all operations and support as passthrough, then track and bill hours, or setup a big monthly recurring hosting fee that is enough to make you glad you are getting distracted.<p>Extra bonus Fourth thought- don't promise feature upgrades. Sell only version 1. Tell them that version 2 is not included and then you can sell them version 2 next year when you have time. It's easy to accidentally promise infinite upgrades or let them assume that any upgrade on your main site they should get free.

The key is to remember what it is that you're selling.<p>You're not just selling 2 weeks of your time at your best consulting rate. You're selling all the time and effort it took to get the codebase into the polished shape it's in today.<p>The best way to approach something like this is to figure out how much it would cost your suitor to hire a team and build your existing site from scratch. You should be able to figure out the actual level of effort to do so, since you've actually done it yourself. Figure out a number, and that's your price.<p>It may sound extravagantly expensive, but really it's a great deal for him. The customer gets his website for the same as it would have cost him to build it himself, but with a working reference version he's guaranteed that it will work at least as well as the existing site, and he gets the benefit of delivery a full 6 months to a year ahead of what he would otherwise have.<p>So there you are. $100,000 for the source license, plus 2 weeks of your time at the highest hourly rate that you can say with a straight face, plus a monthly maintenance retainer, plus several hundred per month for hosting.<p>Good luck!

You are selling enterprise. Repeat this to yourself a few times, it changes all the rules (luckily somewhat to your favour).<p>Tips:<p>1. Charge high, particularly as they have come to you, and definitely if you are the only one in your space. A 30,000 person company does not often balk at spending $10,000's on software, particularly if it is for the entire employee base<p>2. Make sure whoever has contacted you is authorised to accept a figure. Often managers will get a sub-ordinate to co-ordinate with you to get a quote and details - at which point it flakes around the management level for a couple of weeks (while you are distracted from other important work trying to chase it). Cut through the red tape before you quote a price and make that to someone who can immediately say "yep, here's a signature".<p>3. Write a contract, make it very clear. Make sure you are not tied into upgrades or maintenance without a fee. Make sure your liability is covered in that contract.<p>4. Sell them hosting (if they want it) <i>completely separately</i>; separate price, separate contract. Don't tie the two service provisions together.<p>5. If you sell them support make it VERY clear how much support they get and at what cost. Make hourly limits per month, for example, and charge extortionately for extra hours. (this is important; we had a client once that we had a vague contract with and I ended up losing money for weeks trying to sort out an issue for them when I had other work to do).<p>In terms of cost... given your prediction for the work required I would quote somewhere in the region of $40,000. Possibly a little less if they will agree to tie into a hosting &#38; support contract. Consider charging and extra flat fee for the code itself.

I have some experience with this. My old company did a bespoke type project for a 40,000 person company with a small footprint of developers.<p>- 30,000 people means they have deep pockets.<p>- 14 days is how many man hours? You can do one of two things: 1. Charge by fixed pricing (which may put you in the hole if it goes past 14 days...humans are terrible at planning things so this is not always the right choice) 2. Charge by hour with the assumption of "Time and Materials" basis. [1] Remember - companies like this WILL come back to you when something doesn't look right.<p>- If you want to charge support you could consider this possibility: Hire up a junior guy who's only job is to support the system. Spend time ramping him up while you are actually supporting the customer. Charge the customer what the cost of that junior person requires (and maybe a very small margin). This is a great starting point for then being able to build out a future practice. Some may argue to make a larger profit margin here, but you could get push-back on price from the customer.<p>- Think about bundling hosting and support as a whole entity. Nota bene - For a 30,000 person type company you will face major IT challenges. Many large companies require strict security regulations. In many cases they will require to go through loads and loads of lawyers and IT people. Big client customers will always require crazy security things like this: <a href="http://mediatemple.net/company/technology.php" rel="nofollow">http://mediatemple.net/company/technology.php</a><p>Feel free to ping me on email (in my profile) if you want more info.<p>[1] - <a href="http://b.lesseverything.com/2009/5/7/be-wary-of-time-and-materials" rel="nofollow">http://b.lesseverything.com/2009/5/7/be-wary-of-time-and-mat...</a>

Is there a reasonable chance that you could sell bespoke versions of your site to more companies and is that a business you'd want to be in? If so it might worth taking this as an opportunity to sink a few extra hours to rewrite your site in such a way that future re-brandings become much easier. If you really don't want to be in that business ask yourself if perhaps it's best to walk away from this offer, as it could lead to you ending up somewhere you don't want to be.<p>As for a fee, a simple man-hours * $150-200 * 15% seems reasonable, plus monthly maintainance fee, plus hosting fee. And don't feel bad charging a couple hundred a month for hosting even if you're hosting on $15 vps.<p>The important thing to remember through is that once you start to take their money, you are committed. You have to willing to deal with all the support issues and updates that they will be asking for. If you think that after 14 days money will change hands and you'll never hear from them again then you're probably in for a rude surprise. That being said, bespoke software for large companies can be a lucrative niche to be in.

Without details it's impossible for us to tell you how to price any of this stuff.<p>But I will say if your goal is to make money off selling your services, then yes obviously you should include a bunch of line items in your proposal for hosting, support, etc.<p>When you offer them a proposal, try to establish a few tiers ranging from "way more than they'll probably pay" down to "what you think they will pay". Don't ever say "we could go lower" unless it's coupled with "but only if we remove these features".<p>A 30,000 person company is likely trying to buy enterprise software from you, so read up on how enterprise software is priced and sold. Don't sell yourselves short.

I'd just multiply my usual consulting rate by the hours it's going to take me. If you don't have a consulting rate, ask around you area, because it depend of your country/city.<p>&#62; It will take us 14 days (full time) to satisfy the request<p>An organization that employs 30,000 people has probably a lot stakeholders. Unless there's a hard deadline, you will be looking into a huge amount of "release fallout". Expect stupid requests such as "change the font —why? —Because the boss says he doesn't like it". I'd estimate 20 hours of petty changes spread over three weeks.<p>&#62; Should we be offering to support it going forward (we have full time jobs) and if so how much should we charge for this?<p>If you have full time jobs, avoid it like the plague. Recommend someone you trust.<p>&#62; Should we be charging them a monthly fee for using our technology as well as a one off fee?<p>Is your technology infrastructure? Is it open source software? Proprietary software? You're potentially looking into a handsome amount of money here, depending on the nature of what it is, and if it can be easily replaced by something else.<p>&#62; If they ask us to host it I presume we should be asking for a hosting fee as well?<p>Yes, they will expect you change a monthly amount for this. Usually it's billed under "support &#38; hosting" for a fixed monthly fee, which can be substantial (say, 500 USD/mo). But again, avoid it if you value your free time.

Charge 2 people * 8 hours * 14 ddays * 200$ = 50,000$, plus an obligatory 6-month retainer of 10 hours a month = 2000$/month for 6 months. Total = about 65,000$.<p>That would be reasonable. If they negotiate it down to 50,000, you're still ok with that, I'd imagine.<p>If they ask you to host it, charge plenty for that as well.<p>(The rather high hourly rate takes into account that you're selling them something you already built before.)

$5/client license a month with a minimum of $50k per month. If a 30,000 person company wants your stuff, you've made it. Charge accordingly so you can ramp up and do it over and over.<p>The people who are telling 60k all in have never done anything in a corporate world.

Are you going to let them resell your stuff? They may <i>bespoke the bespoken</i>. You have to be careful in your contract with that stuff as well. And if thats ok with you then you should charge for that.

As they have 30k users, they are obviously prepared to spend a decent amount of money on using your product therefore, I highly recommend that you follow the route of Google Apps, Yammer, Salesforce's Chatter (Chatter Plus) etc and charge on a per user basis as well as, charging an inital setup fee.