diff --git a/README.md b/README.md
index d882332f5137..df0bfa0373f9 100644
--- a/README.md
+++ b/README.md
@@ -6,11 +6,11 @@
 [![codecov](https://codecov.io/gh/invoiceninja/invoiceninja/branch/v2/graph/badge.svg)](https://codecov.io/gh/invoiceninja/invoiceninja)
 [![Codacy Badge](https://api.codacy.com/project/badge/Grade/d39acb4bf0f74a0698dc77f382769ba5)](https://www.codacy.com/app/turbo124/invoiceninja?utm_source=github.com&utm_medium=referral&utm_content=invoiceninja/invoiceninja&utm_campaign=Badge_Grade)
 
-**Invoice Ninja v 2** is coming soon!
+# Invoice Ninja version 2.0 is coming! 
 
 We will be using the lessons learnt in Invoice Ninja 4.0 to build a bigger better platform to work from. If you would like to contribute to the project we will gladly accept contributions for code, user guides, bug tracking and feedback! Please consider the following guidelines prior to submitting a pull request:
 
-# Contribution guide.
+## Contribution guide.
 
 Code Style to follow [PSR-2](https://www.php-fig.org/psr/psr-2/) standards.
 
@@ -26,9 +26,14 @@ PHP >= 7.3 allows the return type Nullable so there should be no circumstance a
 
 `public function doThat() ?:string`
 
-To improve chances of PRs being merged please include teststo ensure your code works well and integrates with the rest of the project.
+To improve chances of PRs being merged please include tests to ensure your code works well and integrates with the rest of the project.
 
-
-# Documentation
+## Documentation
 
 API documentation is hosted using Swagger and can be found [HERE](https://app.swaggerhub.com/apis-docs/InvoiceNinja/InvoiceNinjaV2/1.0.3)
+
+## Current work in progress
+
+Invoice Ninja is currently being written in a combination of Laravel for the API and Client Portal and Flutter for the front end management console. This will allow an immersive and consistent experience across any device: mobile, tablet or desktop.
+
+To manage our workflow we will be creating separate branches for the client (Flutter) and server (Laravel API / Client Portal) and merge these into a release branch for deployments.