create new clients process #132
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,34 @@ | ||
| # New client setup | ||
|
|
||
| So you've won some work from a new client - good for you! | ||
|
|
||
| This is how we set new clients up on all of our various systems. | ||
|
There was a problem hiding this comment. Something about the wording here makes the hairs on my arms stand on end - we spend so much time minimising the number of systems we use, could we simply say something like 'This is a checklist of what we aim to have completed before we start working with any new client:' or something to make it seem less "spread out"? 😛 |
||
|
|
||
| * [ ] Create and sign contracts | ||
| * Template contract is saved in the `Clients` folder. Unless there are non-standard terms, only pages 1, 9, and 10 should change | ||
| * [ ] Book initial workshop | ||
|
There was a problem hiding this comment. I should add something in here about the aims of the initial workshop too... 😬 |
||
| * This will be the responsibility of the client contact | ||
| * Bear in mind that our standard terms are for the first invoice to be paid at once, so that can be raised and sent out immediately | ||
|
There was a problem hiding this comment.
|
||
| * [ ] Set client details up on Xero for invoicing | ||
| * `Xero > Contacts > Customers > Add customer` | ||
| * You'll need their accounts contact email address at least | ||
| * Other contacts can be copied in or not as they prefer | ||
| * (You should also ask what information they need for their system, if they haven't already requested it.) | ||
| * [ ] Set up Google Drive | ||
|
There was a problem hiding this comment. Shouldn't this come before the contract so that it can be saved immediately and other materials (proposals, budgets, etc) can also be saved there |
||
| * (This is still a WIP as it's not currently possible to duplicate entire folders on Drive) | ||
| * Set up a folder to match the `.template` structure (hopefully we'll find a way to just dupe it) | ||
| * Be careful to keep the `permissions` the same | ||
| * Save all documents with financial/sensitive information in the `.private` folder | ||
| * Proposal | ||
| * Contract | ||
| * Budget planner | ||
| * [ ] Set up github | ||
|
There was a problem hiding this comment. I read this as |
||
| * Create a client organisation | ||
|
There was a problem hiding this comment. *Ensure the client creates an organisation on github and either also creates the project repository or provides a member of the dwyl team with enough permissions to create a project repo (provide them with a reference to https://github.com/dwyl/github-reference ?) |
||
| * Create project repo | ||
| * Initialise with `readme` | ||
|
There was a problem hiding this comment. Could we simply reference this checklist here rather than duplicating? https://github.com/dwyl/contributing#minimum-requirements-for-a-new-repository |
||
| * Call it something _sensible_ | ||
| * Copy across our labels using [labelsync](https://label-sync.herokuapp.com/) as per https://github.com/dwyl/labels | ||
| * Give permission to all team members who'll be working on the project | ||
| * Either at the `org` level, if we have access to that, or at the repo level if that's all we have access to | ||
| * [ ] Set up gitter | ||
| * Decide whether this will be a `dwyl` channel or coming from the client repo | ||
|
There was a problem hiding this comment. Add:
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would add a little 🎉 at the end of this sentence for both visual interest, dwylifying the readme and because otherwise we risk it coming across as a bit sarcastic 😆