IT companies How to become a Value Added Reseler for the Octopus Community © Octopus Microfinance 2009 Images by Bidulz.com

MFIs are challenged with their MIS Many MFIs are using spreadsheet or manual systems: That is free They can control the tool But it becomes quickly a clear limitation for growth: Errors Difficult reporting Frauds Etc.. © OCTO Technology 2008 Excel (2005) Flexible Secured & automated Excel (2006)

Many MFIs are using spreadsheet or manual systems:

That is free

They can control the tool

But it becomes quickly a clear limitation for growth:

Errors

Difficult reporting

Frauds

Etc..

MFIs are challenged with their MIS The available software are often unsatisfactory: Expensive : License Technical assistance (often done remotely) Not agile/adaptable: When new features are needed, it takes a long time before it can eventually be integrated © OCTO Technology 2008 $ Flexible Excel (2006) Secured & automated MIS (2007)

The available software are often unsatisfactory:

Expensive :

License

Technical assistance (often done remotely)

Not agile/adaptable:

When new features are needed, it takes a long time before it can eventually be integrated

Octopus proposes a different model © OCTO Technology 2008 Costs Adaptability No license Only value-added services Cheaper local assistance Designed to be adaptable Develop adaptations for your clients IT partners Community Open Source platform

Develop your business The Community provides the tools to get autonomuous © Octopus Microfinance 2009 VAR MFI Contracts ($) Community Installation, configuration, training, maintenance, small adaptations New releases Forum University Wiki Advice

Get accompanied Octopus Microfinance propose insurance contracts for your most challenging projects VAR MFI Octopus Microfinance SLA (20% of your revenues) Contracts Quality guarantee, difficult development, risk mitigation Installation, configuration, training, maintenance, adaptation

Contribute to a continuously improved project © Octopus Microfinance 2009 Need from the MFI Discussion and schedule with the Community Test-driven Development New release every 4 weeks Training/assistance to the final user

First step to get onboard: get trained! (Octopus University) © Octopus Microfinance 2009 VAR The Octopus University is an onsite session aiming at: improving your knowledge of the software functionalities Convincing you on the business model (value-based SLAs) and implementation process Training you on the project management tools and coordination process Accompanying you in the exploration of the code and in the appropriation of the development methods Check on the website to know where the next Octopus University is scheduled, or contact us to organize it in your country Octopus Microfinance

The Octopus University is an onsite session aiming at:

improving your knowledge of the software functionalities

Convincing you on the business model (value-based SLAs) and implementation process

Training you on the project management tools and coordination process

Accompanying you in the exploration of the code and in the appropriation of the development methods

Your commitments Your developments will be shared with the whole community in the common source code: There should be only one software (the isolated installations cannot benefit from the future upgrades and lead to a dead-end) You should discuss and get advise from the Community before starting developing (coordination is necessary!) When coding/developing, you must respect the rules that are described in the ‘Architecture document’, such as: Write unit tests for each line of code Respect the ‘layer’ architecture Update before commiting and check that all tests are OK Commit everyday, etc. © Octopus Microfinance 2009

Your developments will be shared with the whole community in the common source code:

There should be only one software (the isolated installations cannot benefit from the future upgrades and lead to a dead-end)

You should discuss and get advise from the Community before starting developing (coordination is necessary!)

When coding/developing, you must respect the rules that are described in the ‘Architecture document’, such as:

Write unit tests for each line of code

Respect the ‘layer’ architecture

Update before commiting and check that all tests are OK

Commit everyday, etc.

© Octopus Microfinance 2009 WWW.OCTOPUSNETWORK.ORG