diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
deleted file mode 100644
index 5e582ed..0000000
--- a/.github/CODEOWNERS
+++ /dev/null
@@ -1 +0,0 @@
-* @transferwise/analytics-platform
\ No newline at end of file
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
deleted file mode 100644
index 1bb4c74..0000000
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ /dev/null
@@ -1,32 +0,0 @@
-## Problem
-
-_Describe the problem your PR is trying to solve_
-
-## Proposed changes
-
-_Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. 
-If it fixes a bug or resolves a feature request, be sure to link to that issue._
-
-
-## Types of changes
-
-What types of changes does your code introduce to PipelineWise?
-_Put an `x` in the boxes that apply_
-
-- [ ] Bugfix (non-breaking change which fixes an issue)
-- [ ] New feature (non-breaking change which adds functionality)
-- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
-- [ ] Documentation Update (if none of the other choices apply)
-
-
-## Checklist
-
-- [ ] Description above provides context of the change
-- [ ] I have added tests that prove my fix is effective or that my feature works
-- [ ] Unit tests for changes (not needed for documentation changes)
-- [ ] CI checks pass with my changes
-- [ ] Bumping version in `setup.py` is an individual PR and not mixed with feature or bugfix PRs
-- [ ] Commit message/PR title starts with `[AP-NNNN]` (if applicable. AP-NNNN = JIRA ID)
-- [ ] Branch name starts with `AP-NNN` (if applicable. AP-NNN = JIRA ID)
-- [ ] Commits follow "[How to write a good git commit message](http://chris.beams.io/posts/git-commit/)"
-- [ ] Relevant documentation is updated including usage instructions
\ No newline at end of file