A former manager of mine, who had some consulting background, once told me that the big management consulting firms like McKinsey do something like this. They compile tons of detailed case studies from former engagements (that's what consulting gigs are called in that field) and then reuse the hell out of them for new gigs, thereby saving a lot of their staff's working time on those. Also probably surprise the clients (who may not know about this practice) by being able to come up with results sooner due to this.
1. Partner hears client is interested in a certain type of engagement
2. Partner promises that their firm has extensive expertise in the area
3. Partner commits to writing a proposal for the potential project
4. Lower level staff scramble to talk to other consultants in their firm (same industry) and dig through old case studies to figure out if #2 is actually true
5. Staff hurriedly compiles a proposal deck from a mish-mash of slides from other projects that are mildly relevant
6. Multiple iterative feedback loops where the partner gives vague suggestions on improvements and staff makes the changes
7. Send finalized proposal to design/production team
If you win the proposal, you use some lead time before the project to build an approach using past projects. In rare cases there would be a firm-sponsored template or framework (often when there is associated whitepapers or other marketing materials), but in general the situation was a more reactive "I do not have time to start this from scratch, so what can I gather from past projects?" and less of a proactive "let's build a template to reuse for new projects"
1. I did not claim to "paint" the full picture. 2. I did not paint the picture. Was saying what my ex-manager said to me. 3. The plural of anecdote is not data.
Interesting to hear of your experience, though.
Regardless of your experience, systematically collecting and analyzing data on prior projects, with a view to applying the learning to future ones, is useful, for any discipline, not just management consulting or software engineering. That's part of how progress in any field happens.
I made a lot of money in consulting over the years, but at the middle of my career I find myself looking for a product company to call home. Consulting can be great... or it can be terrible. My friend is now charging $165/hr for his solo corp... but sometimes the invoices never get paid and you have to swallow a loss(I'm owed over $14k currently and will probably never see it).
Product development is in some ways more gratifying than consulting. But consulting has its own rewards, too.
For comparison, I know a local engineering staffing/design services firm that charges $200/hr for principal engineer time. You're getting more out of that sort of company though.
That said, I've often felt like the sales team doesn't provide much value. It depends on the company.
I will say though that companies are generally more comfortable paying a higher rate to another company vs. one guy working out of his house. There is a greater expectation of responsibility. Also, many companies will not even deal with you as an individual corporation unless certain rules are met. One rule might be that no more than, say, 30% of your income can come from the company looking to hire you. They want to see a diverse revenue stream and a well established business.
Where have you seen people charging that much?
I've been consulting professionally since 2005, and I think I've gotten pretty good at it? And my take on this is, graduating from "IC" to "manager" in the eyes of your client is presumably one way to ratchet up your status. But there are others, and I think they can be more lucrative.
Two straightforward alternative approaches to leveling up a consulting business that you've started by freelancing IC-type work:
1. Scale it out. Take on more work, find trusted people to subcontract it out to, eventually bring on a partner, standardize and methodologize what you do, get to the point where you can train other people to do it, start hiring people. You will probably find that when you get to the point of hiring consultants to work for you, your business accelerates naturally --- one of the most overlooked and important value components of most consulting businesses is on-demand availability, which is expands as your roster does.
2. Specialize. Start looking for commonalities between the projects that you do. Build tooling for them. Maybe publish some open source stuff. Build a specialty practice around that. You can do this repeatedly, for different areas; eventually, you'll do it for business verticals. In both kinds of cases you'll find that you become attractive to different kinds of companies when you change from generic to specific.
In neither case do you stop coding, or reposition yourself from the kind of company that writes code to the kind of company that tells other people how to write code.
We agree about hourly billing, though!