For that it's really simple in concept but can be difficult in execution.
There are two things to do before you even create the directory for the
client or project:

1 - A contract is signed by both parties
2 - An agreed upon sum is paid as a non-refundable deposit

If a client every gives any push back on either of those, it can be a red
blimp flying red flags and shooting red fireworks. Sometimes, it can just
be that the client is new and isn't used to that behavior. Enforce those
two conditions and the beginning and it can make things much smoother. If
they question you on why you need them, the explanation is simple.

1 - It clearly defines who will do what, when, and what is expected after
each milestone in the project.
2 - The client is paying for your time, this is deposit ensure the client
that you are now invested in the project and guarantees your full attention.

The blog post I linked in my last reply has some clauses that you would
want to review to see if they are already in the contract or not. One of
them is the "kill project" clause. In the contract have it clearly stated
that if the client backs out of a project, you keep all money given to you
already and they are liable for any work you've done but haven't completed
yet. You can even go a step further and state that you also keep all rights
to the work and they forfeit any claim to the work.

On Thu, Oct 8, 2015 at 10:06 AM, Kevin Jensen <[email protected]> wrote:

> So, maybe I'm asking the wrong question. I'm still pretty new to freelance
> web development and last week I had a client back out of a proposal. From
> this I decided I need something more concrete in place to ensure I get paid
> for work done (yes, I foolishly DID NOT take money up front). So what do
> you do to ensure you get paid and decrease the likelihood that the client
> will back out of the project?
>
> I've been looking over Statements of Work and Master Service Agreements,
> and they seem to be inline with what I want, but I just don't know what is
> conventional in the web development industry (I'm in Price where there has
> never really been any successful web development firms). Any help is
> appreciated!
>
> On Thu, Oct 8, 2015, 9:58 AM Brian J. Rogers <[email protected]>
> wrote:
>
> > I haven't ever used a legal service, but there's dozens of freelance
> > software developer contract examples that are free to use.
> >
> > One particular one I've found gets most of the bases covered can be found
> > here <https://www.docracy.com/0kpa5hfcobb/freelance-developer-contract>.
> > I'd also recommend using this blog post
> > <http://www.hongkiat.com/blog/freelance-contract-clauses/> as a good
> > checklist of things to consider with every contract.
> >
> > On Thu, Oct 8, 2015 at 9:27 AM, Jonathan Duncan <
> > [email protected]
> > > wrote:
> >
> > > On Mon, Oct 5, 2015 at 6:06 PM, Kevin Jensen <[email protected]>
> > wrote:
> > >
> > > > Who does everyone go through for legal services? (contracts, privacy
> > > > policies, etc.)
> > > >
> > > >
> > > I do not use legal services much. I setup one company with my
> accountant.
> > > Setup a different company using Andrew Howell (
> > http://www.yorkhowell.com/)
> > > in Salt Lake.
> > >
> > > Depending on your needs and your budget, you may consider something
> like
> > > LegalShield (http://shieldyourselfnow.com).
> > >
> > > _______________________________________________
> > >
> > > UPHPU mailing list
> > > [email protected]
> > > http://uphpu.org/mailman/listinfo/uphpu
> > > IRC: #uphpu on irc.freenode.net
> > >
> >
> > _______________________________________________
> >
> > UPHPU mailing list
> > [email protected]
> > http://uphpu.org/mailman/listinfo/uphpu
> > IRC: #uphpu on irc.freenode.net
> >
>
> _______________________________________________
>
> UPHPU mailing list
> [email protected]
> http://uphpu.org/mailman/listinfo/uphpu
> IRC: #uphpu on irc.freenode.net
>

_______________________________________________

UPHPU mailing list
[email protected]
http://uphpu.org/mailman/listinfo/uphpu
IRC: #uphpu on irc.freenode.net

Reply via email to