4 ms·
Having seen all type of consultants over the year: - The strategic consultant you describe manages to have a higher tariff, but the sales cycle is long and the
by PeterStuer 8y ago
Having seen all type of consultants over the year:
- The strategic consultant you describe manages to have a higher tariff, but the sales cycle is long and the downtime between gigs significant
- the 'software consultant' has an on average lower tariff (depending on the specialization), but little downtime and faster sales.
Pick your poison and do what you feel most comfortable with.
- warent 8y agoWhen you say tariff do you mean price?
- abainbridge 8y agoI think this is a British-ism. I'm British. The parent's post used tariff in a way I found normal. Google tells me: tariff - noun: BRITISH a list of the fixed charges made by a business, especially for use of gas, electricity, or a mobile phone.
- dboreham 8y agoFwiw US telco-speak still uses tariff to mean price.
- civilian 8y agoIn American english tariff is usually used as "tax". Especially in the context of import & export taxes on goods and services. (E.g. The American colonies revolted over the tea tariff.)
- datavirtue 8y agoIndeed. Tariff is a dirty word in American English.
- PeterStuer 8y agoSorry for the confusion, I think the correct term is 'hourly rate', what you charge as a consultant for your time.
- gk1 8y agoI disagree. I fit into the “strategic consultant” category and my sales cycle from referral to signing is a few weeks, with zero downtime because I work on several projects at once. The great thing about being independent is you can design your engagements however you want. Not happy with amount of downtime? Find a way to do two (or more) projects at once. Not happy with sales cycle length? Simplify your offerings. And so on...
- beatgammit 8y agoWhat does this mean exactly? Do you essentially build the specs and someone else does the work? Or do you see the project to completion (you design and implement the product)? I'm really confused because I really didn't see anything meaty in the article other than "talk about problems, not implementation". I thought the article was going to be about "licensing" vs "copyright transfer", but instead got a lecture about something far more nuanced. Is the difference just terminology and how you present yourself? If so, what terminology to people look for, and how does a project work from start to finish for you?
- gk1 8y ago> Do you essentially build the specs and someone else does the work? Yes, something like that. See: https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-programmer/ https://www.kalzumeus.com/2011/10/28/dont-call-yourself-a-pr... That post goes into much more details and reasoning for this argument.