Benefits of source control go far beyond allowing multiple developers to work on a single piece of code. Eric Sink, the founder of SourceGear, lists a few compelling reasons to use source control as a sole developer, a quote:

- It's an undo mechanism. - It's a historical archive. - It's a reference point for diff. - It's a backup. - It's a journal of my progress. - It's a server. 

Eric also happens to have a very nice beginners' Source Control How-to. There is a free online Mercurial tutorial available by Joel Spolsky, Mercurial is a popular distributed version control system.

As the next step I suggest - just start using source control locally on your machine, as a sole developer. Very soon your boss will notice that you're capable of sheer magic, like telling within minutes if not seconds how far back a super-critical bug dates and then you telling him precisely which customer records to fix before all hell breaks loose. Or being able to undo any changes CEO disapproves of super fast.

And finally before you try to convince your boss you may want to delve into the topic of objection-handling. It's 101 of sales.

If unsuccessful - move on as soon as practically possible, not much point in wasting your time tilting at windmills.

Benefits of source control go far beyond allowing multiple developers to work on a single piece of code. Eric Sink, the founder of SourceGear, lists a few compelling reasons to use source control as a sole developer:

- It's an undo mechanism. - It's a historical archive. - It's a reference point for diff. - It's a backup. - It's a journal of my progress. - It's a server. 

Eric also happens to have a very nice beginners' Source Control How-to. There is a free online Mercurial tutorial available by Joel Spolsky, Mercurial is a popular distributed version control system.

As the next step I suggest you to start using source control locally on your machine, as a sole developer. Very soon your boss will notice that you're capable of sheer magic, like telling within minutes, if not seconds, how far back a super-critical bug goes and then you would tell him precisely which customer accounts were affected and need fixing before all hell breaks loose. Or being able to undo any changes CEO disapproves of super fast.

And finally before you try to convince your boss you may want to delve into the topic of objection-handling. It's 101 of sales.

If unsuccessful - move on as soon as practically possible, not much point in wasting your time tilting at windmills.