JFitzDela

Thank you for your thoughts, particularly regarding the low price point -- it's certainly something I'll look into (and A/B test, as you mentioned, but I need traffic first...).

I hadn't even thought of talking to insurance companies -- I'll start looking at that, too, with a buddy I've got in that business.

Thanks again!

Thanks! I'll see about cleaning up the pricing offerings. I'd like to offer shorter options for (as you mentioned) short trip takers, but if it's just confusing or unnecessary, it's certainly not doing any good.

I appreciate the feedback!

Clickable: http://monitorfor.me

Don't forget the invite code: HNFTW

I appreciate your thoughts, and I can certainly see where you're coming from.

For me, the cost of the more traditional services is prohibitive, and especially so in the case of automated calls to the police and fire departments -- the city (at least down here) and the monitoring company begin to levy extra fines in false alarm situations (forgot your access code, burned something in the oven, etc.).

My personal take is that I would rather make the judgement call, myself. I can guarantee there will be more "false alarms" (since my service just listens for a sustained increase in volume and isn't wired to sensors directly), but at least the user can weed them out and not the city. And it's a lot cheaper.

Thanks again for your thoughts!

This is the new service I mentioned the other day. No bites from the big guy I sent it to, so I'll just start by showing it here, get some feedback, and go from there.

The first 25 folks can use the invite code: HNFTW for a 7 day subscription.

The blog explains why I built it (http://bit.ly/ginK1e), so I won't repeat it here.

I look forward to any feedback you guys can offer -- it's definitely an MVP at this point, but I think the idea is sound. I hope you'll agree!

Excellent suggestions, and I should have been more specific. I'll edit the post to better address the specific situation, but I appreciate your advice!

- John

I reckon I'll be different, here.

I'd say PHP (particularly if the new coder has interest in web programming).

It's syntactically easy-ish, freely available, very well documented and supported, and sets the newbie up for easy freelance or professional work.

- John

Great job! I used it to analyze my most recent project, and I was genuinely surprised by the results -- your questions highlighted areas I've neglected to consider or approached incorrectly. I especially love the detailed feedback after the quiz.

Only feedback I can offer is to perhaps re-evaluate the grammar and spelling in some of your questions -- not a big deal, but an easy fix.

Good luck!

I'll try to tweak those colors, then -- it already looks different between my own monitors. Thanks!

- John

I've thought more and more on the no-refund stance, and I believe you are correct -- I'll add a clause allowing them, perhaps up to 15 days from listing close (45 from listing purchase/approval).

As for pricing, you're correct again -- $75 (or anything, really) is a great deal to ask for a site with no track record. Even your "tens of hits" is overestimating at the moment.... I don't, however, want to set a low price and then raise it -- that's always irked me in any situation. Perhaps making new listings free during the beta test (a month or two)?

I'll certainly reconsider requiring users to register. I DO want employers to feel safe in that they won't see ALL of the spam that comes with an open site, but maybe an option to only allow members to apply? Tier II jobs will retain the requirement, as they're for premium members exclusively (they're screened by the staff and pay a fee), but Tier I would be fine.

For your other comments: - I'll make the delineation between employer and provider (or at least the definition or nomenclature of a provider) more clear).

- Glad the UI grew on you -- it did me, too! :)

- All jobs posted are screened for compliance with our Acceptable Use standards (basically nothing offensive or harmful). All PREMIUM members will be screened for access to the premium features (before being asked to pay, of course) -- basically, we'll check portfolios and references.

- The problem we're trying to solve is too high a cost and/or too little value (for both employers AND providers). A listing can run, as you mentioned, $200-$300 dollars (which I believe is a bit excessive). The employer can be inundated with crap applicants -- we allow peer reviews and screen premium members. The providers can be inundated with jobs with minuscule pay -- we have minimum budgets.

I reckon I oughta make all of that more clear.... :)

Thank you for your detailed analysis, particularly having worked where you have. I truly appreciate it!

- John

I'll definitely find a place to (simply) explain the differences between Tiers/purchase prices.

I'll consider your thoughts on the location search; at a minimum, I'll add an "auto-suggest" type feature to help narrow your search.

Thanks!

I appreciate any advice given at all. I'm a programmer, not a designer, so don't expect a whole lot outta me in that department.

I'd like to know what you think of the a) usability of the service and b) ideology behind the pricing, restrictions on budget, etc.

Thanks a million!