First work proposal
I finished my first work proposal today.
I started working on it Tuesday afternoon, after talking to the client. I had two proposals Mike had written for previous projects as examples / outlines, but I definitely felt like I was fumbling around somewhat ignorant of what I needed to do.
Which isn't to say I can't figure it out. I'm good at making lists, at breaking down tasks into smaller and smaller pieces. My index cards can certainly attest to that ability.
What I'm not so good at, however, is estimating time. A friend once suggested I estimate a task, and multiply by three, because that seems to be how long a task will really take. Given how cynical and pessimistic I can be about life and the human condition, the optimism I have when estimating time is incongruous.
Of course, that inability to accurately estimate how long a task will take could easily explain why I'm frequently late.
This time, however, I had Mike to help me out. He reviewed my numbers, reviewed the task list, added items and such. I look at the total and think, wow, that total is a lot of money, but each step is justified.
Writing here, I can be satisfied with my words. I can edit and adjust and, when I hit the submit button, be done. With a proposal though, it's my writing going to someone else. I can't help but wonder, did I explain everything? Was I succinct? Was I clear? Did I estimate too high? Did I estimate too low? Is the guy going to think I'm an idiot with this quote?
After a few moments of nervousness, I gave up on the internal torture, the need to be perfect and the urge to make everyone else happy. I sent the proposal off with the realization that, yes, the process will take as long as I estimated, and, yes, my time is worth the money I quoted.
If the quote is too high, well, I have internal projects to work on, too.