Slashdot Mirror
Freelancing with Companies in Other Countries?
DutchSter asks: "I've been doing PHP web development for a few years now, including a few small jobs for a client in the UK (I'm currently in the US). The jobs have been so small I've never worried about a contract or anything. I was recently offered to do some long-term projects (about 6 months of full-time work). Does anyone have experience doing freelance work for another country, and if so, how did you handle contractual issues? Basically, I'm looking to minimize the risk of me being ripped off, and second, eliminate problems caused by miscommunication due to the lack of a written agreement."
The way our small company does it, depending on project size we either divide the total estimate costs by 2, and ask for the first part at contract signing and the rest on completion, or split in 3 parts and ask for the first part at contract signing, the next part at about halfway through the project and the rest on completion. That splits the risk about evenly between yourself and your customer.
By the way contracts with oversee partners are virtually impossible to enforce (unless you have huge financial resources), so don't waste too much money on it, and make it just simple and clear. They're more intended to point out some rules between the two parties and point out copyright issues etc, but I highly doubt you'd be able to enforce anything with it.
Reinard
Hi,
I would recommend using www.guru.com.
Register there (It's free) and you will find quite a bit of information regarding what you're looking for.
Hope this helps
Good Luck
... near the border to the Netherlands, I often see craftsman working here. They even seem to shuttle between the two countries.
I know, it's not the same. But I (working as a PHP-Dev, too) also worked for a company in Spain and once for one in Australia. Both projects were longer than 4 months.
We used IM to cummunicate and sent the protocols by email to each other (to have it written down). In the time of digital delivery, when you don't need to transport hard good to your customer, it's going easy and fast.
But I allways (even to customers in Germany) send a CD with the final version together with the bill (printed out) to my customers. It just feels better having something in your hand.
I get ~half my income from overseas contracts. (Contracting on Squid development, living in Australia).
I always use a written contract - on the simple basis that if the work isn't long enough to need a clear statement of who,what,where,when and for how much, it ain't worth doing for money.
Once the contract is signed, you still have to communicate often, and clearly. All contracts do is set the goal posts - it's up to you to keep your customer happy while you approach them.
Obvious first point: you're a fool if you don't have a contract. UK law is sufficiently similar to US law that you should not have any great difficulty in understanding it (and if it's so legalese that you don't understand it, beware!). If you're not confident that you understand what your obligations and rights are, engage a solicitor (UK version of a lawyer).
The contract should cover at least:
- What you need to deliver, and when
- What you will be paid, and when
- What happens if you fail to deliver for
some reason
- Who owns the work before you have been paid
- What happens in the event of dispute
- Who is responsible for failings in the
software, and to what extent
- Who is responsible for ensuring that all
relevant taxes are paid.
- Jurisdiction of the contract (usually the
state/country of the client)
There are basically two types of contract work. In one case, you turn up at the company for whom you are doing the work every day, and get paid an hourly (daily, weekly or whatever) rate. In such a case, the contact will stipulate your holiday rights, what happens if you go sick, and will probably have a fixed duration (renewable, with trial period). This is low risk for you, but you'd obviously need to be in the UK woth valid work permit (or be an EU citizen, ancestral visa holder or whatever). If not, it's probably not an option for you.
The second type is work on a defined project (e.g. "you will deliver the foomatic e-commerce enabled profit maximiser website").
The issue with such a project is to get the scope of the work you will do tied down from the start. Issues to think about: who pays if the customer changes the requirements, what consitiutes a "change" anyway. Please be *very* careful here - probably the #1 cause of problems for people doing this kind of work is that the two sides have different expectations.
If you're not 100% clear about what is being asked for, I'd suggest splitting the contract into two parts: a specification and implementation. Idea is that you get paid for writing a specification, which the customer can change, but once this is agreed, you have a fixed price for delivering what was requested.
In such a contract, payments are usually phased on demonstrating milestones. One possibility would be (assuming a website):
1) Milestone payment for agreed specification (~10% of total) - accompanied by an annexe specifying your following milestones and payments.
2) Milestone payment for delivering interface mock-up (~20%)
3) Milestone payment for prototype fully functional site on small server (~20%)
4) Milstone payment for "beta" delivery on production server (~20%)
5) Final payment on acceptance (~10%)
6) Bonus (10%) for early completion (maybe a penalty for late completion as well)
I hope you're good at estimating how long you will take to do this: many software engineers are natural optimists, and will say that they can do something in 3 months which actually takes 6 (and which would kill your profit from this work), and remember that the customer will want 'finished' - i.e. documented, reliable, commercially acceptable - software. If you're not certain that you know how to do this, better work on an hourly basis.
You would be well advised to work via a limited liability company (these can be purchased off the shelf, for around UKP100), and to have professional indemnity insurance (another UKP160 or so).
Please bear in mind that if you are on a time and materials basis in the UK, you may see some odd contractual clauses which are concerned with ensuring that your customer cannot be liable for your tax (the so called IR35 rule).
Good luck, but take care...