Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Work out required contribution to overheads to make dwyl client services sustainable long term #187

Open
iteles opened this issue Jan 28, 2017 · 4 comments
Assignees
Labels
dependency enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished

Comments

@iteles
Copy link
Member

iteles commented Jan 28, 2017

For the last year, whilst we have been working to continuously build up both the skills of the majority of the dwyl team through continued practice, guidance and exposure on our client projects as well as our reputation, we have kept our contributions to overheads incredibly low. Far lower than any other 'agency' on the market.

This means we have relied heavily on our more experienced developers as well.

Our aim will always be for the majority of the income to go straight to our team, but with our renewed focus on product (which will only be bringing in revenue a little further down the line), making dwyl the best place to work #145 and a foreseeable increase in rent (#180), we need to know exactly what we need to do to break even in 2017 and proactively work towards making this happen.

@iteles iteles self-assigned this Jan 28, 2017
@nelsonic nelsonic changed the title Work out required margins to make dwyl client services sustainable long term Work out required contribution to overheads to make dwyl client services sustainable long term Jan 29, 2017
@nelsonic nelsonic added enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! labels Jan 29, 2017
@iteles
Copy link
Member Author

iteles commented Jan 29, 2017

Big 👍 on the title, that is a lot clearer.

@ghost ghost added the priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished label Feb 25, 2017
@ghost
Copy link

ghost commented Oct 26, 2017

Closing in favour of #373

@ghost ghost closed this as completed Oct 26, 2017
@iteles iteles reopened this Oct 26, 2017
@iteles
Copy link
Member Author

iteles commented Oct 26, 2017

This is about the required contribution vs the actual, which as you say, is being dealt with in #373

@iteles
Copy link
Member Author

iteles commented Nov 28, 2017

Dependent on having a clear financial picture of where we're at. #229 #321

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependency enhancement New feature or enhancement of existing functionality help wanted If you can help make progress with this issue, please comment! priority-2 Second highest priority, should be worked on as soon as the Priority-1 issues are finished
Projects
None yet
Development

No branches or pull requests

2 participants