Where the design community meets.
freelancer at self Joined almost 6 years ago
Back then, that WAS the website -- and the tools.
Where else would you have put it?
Some of these may be of interest. https://www.hpe.com/us/en/insights/articles/the-13-best-developer-and-usability-conferences-in-2019-1811.html
Also, you can't be too detailed about step #1.
Be really explicit about who is doing what, when. Make sure you explain what is and isn't included in the What. And who owns what.
Be very clear about payment, and how to identify the points where you say, "Where's my money?" Most freelancers learn to ask for an advance of some kind. (Often 1/3 at signing, 1/3 at a halfway point -- which you document clearly -- and 1/3 when all is complete -- and define "complete.")
I have found, in 30+ years of freelancing, that when something is documented there isn't a problem. You might grouse to discover that damn, you did say in the contract that you'd include the source code. But the lawyers make their money on what is left out of the agreement. For instance I had one huge job, which somehow left out, "How much will client pay freelancer if the project is canceled" and I got completely screwed in that deal.
Well OBVIOUSLY! :-)
Or make the choices better!
Well where would YOU have put it?
I'd like to say something pithy and eloquent here, but basically: We agree.
I think the important point is that you take on free gigs when it benefits you and you have control. For example,it's hard to sell your expertise with a tool or skill you haven't learned yet. In such situations I might go to a community organization that would appreciate, say, a free website, as long as I get use the technology I choose. That gives a fair amount of creativity (including, "Oh, I see how awkward my first design was; I'll re-do it before I take it live), and also provides a grateful reference.
Now If it takes twice as long to get the gig done (because none of us are adept with a new tool the first time out), that's fine.. and you can get away with that for a client who can't threaten, "If you don't get it done by Friday I won't pay you!"
Most of the time, I invoice at the cadence the client is comfortable with. For most businesses, that's once a month. One of my clients currently has a system set up to pay me weekly, and I am sure not objecting to that.
It does depend on the type of work you're doing, by which I mean "ongoing project" (as with this weekly-pay client) or "one time [large or small] task." For writing a white paper, for instance, I only invoice when the work is handed in, no matter how long it took me to write it (a factor I work into pricing calculations). For a one-off ghost-written blog post, I charge 50% up-front and then at the end of the project after everything is signed off.
I've been using Freshbooks for several years, but in truth the software is a far secondary consideration. You can track your invoices with a spreadsheet, and I used to do that. Freshbooks (and its ilk) simply are better at reminding you, "Ya know it's been 8 weeks and those dudes have not paid yet...?"
Honestly, ask your accountant. Some of these things vary by the state you're in. (In more ways than one, I guess.)
If you happen to be in Arizona, I'm happy to recommend the guy I go to.
There's different kinds of pitching. Public speaking is only one of them. I suck at public speaking, but I'm very good with words. So I try to arrange for the "pitch" to be in a form that speaks to my strengths -- which means creating a document that sells the client on my proposal and my background.
In the worst case, when I've written out everything I might possibly say, I can stare at the document and repeat what I wrote. But 99% of the time I can avoid that.
Where the design community meets.
Designer News is a large, global community of people working or interested in design and technology.